On Saturday 30 December 2006 15:23, Samir M. Nassar wrote:
On Saturday 30 December 2006 13:43, Jim Horner wrote:
So is dovecot not picking this up?
suggest putting garbage in your .dovecot.sieve file, sending yourself an email and checking for .dovecot.sieve.err file ... at least this way you know whether deliver is reading your .dovecot.sieve or not ... then you can backtrack problem.
a .dovecot.sieve file with the following require
require ["nosuchreq", "subaddress", "envelope", "fileinto"];
should produce a .dovecot.sieve.err file:
I have done so, both in the users $HOME as well as in the maildir. No such luck.
yeah, we still can't tell if it is a postfix or dovecot issue ...
using the malformed sieve script just do a simple deliver
$ cat /etc/hosts | ./deliver -d me@mydomain.com -f blah@blah.com
(obviously) dovecot should be running and me@mydomain.com should be the person with the screwed up sieve script. if you still don't have a .dovecot.sieve.err file then it is on the dovecot side.