Mitch (WebCob) writes:

I've removed the domain names to protect the innocent.

A user on my new server can receive email from SOME users... not all... the
reset are being deferred.

Dec  3 19:14:37 slim1 courierd:
started,id=0001BC68.3FCE361D.00003108,from=<[EMAIL PROTECTED]>,module=local,host=kar
[EMAIL PROTECTED]/home/vserver/l/2/karen!!,addr=<[EMAIL PROTECTED]>
Dec  3 19:14:37 slim1 courierlocal:
id=0001BC68.3FCE361D.00003108,from=<[EMAIL PROTECTED]>,addr=<[EMAIL 
PROTECTED]>,size=1097,su
ccess: Message delivered.

Dec  3 19:28:24 slim1 courierlocal:
id=00018709.3FCCCE0B.0001378A,from=<[EMAIL PROTECTED]>,addr=<[EMAIL PROTECTED]>: 
maildrop:
error writing to mailbox.
Dec  3 19:28:24 slim1 courierlocal:
id=00018709.3FCCCE0B.0001378A,from=<[EMAIL PROTECTED]>,addr=<[EMAIL PROTECTED]>:
/usr/local/courier/bin/maildrop: Unable to deliver to mailbox.
Dec  3 19:28:24 slim1 courierlocal:
id=00018709.3FCCCE0B.0001378A,from=<[EMAIL PROTECTED]>,addr=<[EMAIL PROTECTED]>,status:
deferred

They receive SOME (mitch) mail fine... from the same server as the "max"
account - different domain though - but some mail from "max" and from some
remote users displays this error.

Any thoughts?

Check whatever you're doing in the maildrop recipe.

You are probably invoking some external filter. When the external program barfs, you get the results shown above.



Attachment: pgp00000.pgp
Description: PGP signature

Reply via email to