Hello Again,
now after some more reading of the logfiles i found this:
lmtpunix[2882]: duplicate_check: <[EMAIL PROTECTED]>[EMAIL PROTECTED]
.bluemaex.sieve. 0
lmtpunix[3774]: FATAL: couldn't exec() sendmail
lmtpunix[2882]: sieve runtime error for bluemaex id <[EMAIL PROTECTED]>:
Redirect:
I'm not on the -devel list, and this was a quick fix, so I'm just
posting this here
Compiling on Solaris with Sun Studio 11 with CFLAGS=-xO3 yields a
unresolved symbol error when linking sievec:
cc -L/usr/local/lib -R/usr/local/lib -L/usr/local/lib -R/usr/local/
lib -o sievec sievec
Hello,
i've got a serious problem with Cyrus Database. Since yesterday mails
will just sporadically be delivered and at some time Cyrus stops work
so no IMAP/POP3 access is possible. Also mails are hanging out in
queue of sendmail.
In the logfile i get a lots of errors which are:
pop3[14196]: DB
Yesterday our Cyrus server stopped responding and I saw the following
messages in the log file:
Dec 7 18:13:55 email imaps[9684]: [ID 866726 local6.warning] DBERROR
db4: PANIC: Invalid argument
Dec 7 18:13:55 email imaps[9684]: [ID 864961 local6.crit] DBERROR:
critical database situation
De
Daniel Eckl a écrit :
Hi!
deliver.db is just used to suppress duplicate delivery and for
suppressing sieve vacation mails coming more often that configured
("days" setting).
So I'd suggest to stop cyrus and just delete deliver.db (and
deliver.db.NEW if existing) and start cyrus again.
Best,
Da
Hi!
deliver.db is just used to suppress duplicate delivery and for
suppressing sieve vacation mails coming more often that configured
("days" setting).
So I'd suggest to stop cyrus and just delete deliver.db (and
deliver.db.NEW if existing) and start cyrus again.
Best,
Daniel
On 06.12.2006 19:1
