> > using 2.0.16 I see sporadic Sieve errors: > > > > Oct 2 07:20:56 pat lmtpd[21021]: sieve parse error for rink: line 3: > > address '[EMAIL PROTECTED]': parse error, expecting `$' > > > > The Sieve filter is very simple: > > ------------------------------------- > > # PHP-Sieve 1.1: forward > > > > redirect "[EMAIL PROTECTED]"; > > -------------------------------------
> Do you always see this problem with the same address? I have other local users with similar simple scripts with sporadic "parse error, expecting `$'". And the sender addresses vary. > Does this script always fail? No, most of the mails for this user are redirected properly, but some (well, 2 in the last 3 days) end with this "parse error" (sieve file unchanged). > What happens if you check the syntax of the script by > running it through sieve/test? Running sieve/test with the failed message leads to: ---------- ./test /mailbox/a/r/user/rink/60713. /imap/sieve/r/rink/default redirecting message '/mailbox/a/r/user/rink/60713.' to '[EMAIL PROTECTED]' notify msg = 'You have new mail To: [EMAIL PROTECTED] From: ..... Subject: Re: Ausgabeumlenkung und time Action(s) taken: Redirected to [EMAIL PROTECTED] ' with priority = medium --------- Looks good for me... BTW, is this sieve action no longer valid (worked in cyrus-imap 1.6.22): redirect "address1, address2"; - Frank -- Email: [EMAIL PROTECTED] http://www.tu-chemnitz.de/~fri/ Work: Computing Services, Chemnitz University of Technology, Germany
