Charles Uchu Strader writes:
Review of issue and fix.1) Incoming email to a valid address ([EMAIL PROTECTED]) was all getting temporary errors such as below Jun 21 10:38:27 emailserver1 courierlocal: maildrop: Unable to create a dot-lock. Jun 21 10:40:38 emailserver1 courieresmtpd: 456 Address temporary unavailable. 2) All permissions, quota, etc were fine for this mailbox and logging in via POP3 or IMAP was fine 3) Removed the mailbox from the server entirely, added it back in and the problem still existed.
See http://www.courier-mta.org/install.html#backscatterPlease read this _entire_ section of INSTALL. Do not stop after the first two paragraphs.
Questions: So what could have caused the original problem? Was the mailq for this user corrupted somehow? What are possibilities for causing corruption?
No. The mail queue was not corrupted.
Are there any tools for situations like this to purge any information in the spool directories besides cancelmsg? I know it would not follow RFC for delivery failure notification, but that method did not work in this situation. What do the /track/ files do?
Implement backscatter suppression. See the 'courier clear' command in the courier(8) man page for the correct procedure to resolve this.
pgpAACTSDIQTL.pgp
Description: PGP signature
------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/
_______________________________________________ courier-users mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
