Cyrus + Sieve

Gottschalk, David dgottsc at
Thu May 21 16:08:34 EDT 2009

Good thinking. I sent a email from a completely new address, and it still didn't work.

I wonder if this has something to do with how Sendmail and Cyrus talk to each other. This production environment was not setup by me, and there is a actual .promailrc script that hands off from sendmail to Cyrus. I wonder if this is causing mail to get malformed, and sieve not handle it.

I saw some other posts online with users talking about this very issue.

I'm not sure how that would affect the vacation portion, but maybe it could be?

David Gottschalk
UTS Email team
david.gottschalk at

-----Original Message-----
From: Simon Matter [mailto:simon.matter at]
Sent: Thursday, May 21, 2009 3:54 PM
To: Gottschalk, David
Cc: Blake Hudson; info-cyrus at
Subject: RE: Cyrus + Sieve

> Well, I think duplicate surpression might be already working. I just
> looked at my logs and see entries for it.
> I don’t have a deliver.db though, which is interesting. I did look at
> the Cyrus change log, and noticed that at some point they did merge the
> deliver.db and the duplicate.db.

Hm, IIRC the duplicate db is always stored in deliver.db.

> Any other ideas I could try, or tests I could do?

The thread is already quite long and I don't remember all details. But the
problem you report is very common. Everything works but vacation does not.
It usually boils down to the fact that everything is okay but the tester
thinks it doesn't because he expects a message but cyrus thinks it has
already sent one message.
One thing you might check is your "sendmail" option in imapd.conf. Does it
point to a usable sendmail command which really does the right thing?


This e-mail message (including any attachments) is for the sole use of
the intended recipient(s) and may contain confidential and privileged
information.  If the reader of this message is not the intended
recipient, you are hereby notified that any dissemination, distribution
or copying of this message (including any attachments) is strictly

If you have received this message in error, please contact
the sender by reply e-mail message and destroy all copies of the
original message (including attachments).

More information about the Info-cyrus mailing list