Now sivtest, sieveshell (,imtest, mutt) are all happily connecting, but when
I actually try out the test sieve script, I get an lmtp mail delivery error(!)
This is the test script:
require ["reject","fileinto"];
if address :is :all "From" "[EMAIL PROTECTED]"
{
reject "testing";
}
and it is successfully installed. When it is active, a test message gets:
exim[379]: 2003-02-08 22:30:28 18hdUS-000067-00 <= [EMAIL PROTECTED] U=prlw1
P=local S=470 [EMAIL PROTECTED]
exim[380]: 2003-02-08 22:30:29 18hdUS-000067-00 == [EMAIL PROTECTED]
<[EMAIL PROTECTED]> R=newnham_user T=cyrus_delivery defer (-1): LMTP error
after end of data: 421 4.3.0 lmtpd: couldn't exec
Feb 8 22:30:28 tape master[384]: about to exec /usr/cyrus/bin/lmtpd
Feb 8 22:30:28 tape lmtpunix[384]: executed
Feb 8 22:30:28 tape lmtpd[384]: accepted connection
Feb 8 22:30:28 tape lmtpd[384]: lmtp connection preauth'd as postman
Feb 8 22:30:28 tape lmtpd[384]: mystore: starting txn 2147483660
Feb 8 22:30:28 tape lmtpd[384]: mystore: committing txn 2147483660
Feb 8 22:30:28 tape lmtpd[384]: duplicate_mark: <cmu-sieve-384-1044743428-0@tap
e.newn.cam.ac.uk> .dburs3.sieve. 1044743428
Feb 8 22:30:28 tape lmtpd[384]: sieve runtime error for dburs3 id <200302082230
[EMAIL PROTECTED]>: Reject: Sendmail process terminated normally, exit
status 75
Feb 8 22:30:28 tape lmtpd[384]: DBERROR db4: Locker does not exist
Feb 8 22:30:28 tape lmtpd[384]: DBERROR: error fetching <20030208223028.A372@ta
pe.newn.cam.ac.uk>: Invalid argument
Feb 8 22:30:28 tape lmtpd[384]: duplicate_check: error looking up <200302082230
[EMAIL PROTECTED]>/user.dburs3: cyrusdb error
Feb 8 22:30:28 tape lmtpd[384]: duplicate_check: <[EMAIL PROTECTED]
.cam.ac.uk> user.dburs3 0
Feb 8 22:30:28 tape lmtpd[384]: DBERROR db4: Locker does not exist
Feb 8 22:30:28 tape lmtpd[384]: DBERROR: error fetching user.dburs3: Invalid ar
gument
Feb 8 22:30:28 tape lmtpd[384]: DBERROR: error fetching user.dburs3: cyrusdb er
ror
Feb 8 22:31:29 tape lmtpd[384]: DBERROR: error closing: Invalid argument
Feb 8 22:31:29 tape lmtpd[384]: DBERROR: error closing deliverdb: cyrusdb error
Feb 8 22:31:29 tape lmtpd[384]: DBERROR: error closing: Invalid argument
Feb 8 22:31:29 tape lmtpd[384]: DBERROR: error closing mailboxes: cyrusdb error
Feb 8 22:31:29 tape master[187]: process 384 exited, signaled to death by 10
I upgraded to db-4.1.25 just in case.. I don't understand the "sieve runtime
error" line - it says "Reject", but isn't that precisely what the script says
should happen? Any hints on how to debug this?
Cheers,
Patrick
