> Take your righteous "configured properly" bullshit and stuff it. That > isn't the issue here.
Excuse me, but that is the only issue here. There is no call for that sort of language, all the people on this list have done is tried to help solve the issue. > 1) Mail comes in from "[EMAIL PROTECTED]" to > "[EMAIL PROTECTED]". Yes > 2) Mail doesn�t get delivered because "[EMAIL PROTECTED]" is not a > user. If the user does not exist and there isn't a catch-all set for the domain then SMTP session gets 5xx User Unknown for each unknown user, any valid users will be accepted. Any DATA command trying to send when it has no valid users gets a 5xx ESMTP Command Error, or whatever Courier's actual text is. The message is not accepted for that user in any form, it never enters the queue. > 3) Courier tries to return that failure to "[EMAIL PROTECTED]". No it doesn't. That's the responsibility of the upstream server. The only case where this happens is if there's a catch-all for the domain which THEN denies delivery. The SMTP server will reject an unknown user outright. Check with mail.sitharus.com - sending mail to [EMAIL PROTECTED] will just be rejected in the SMTP stage, I'll see a 5xx User Unknown entry in my log files and never hear from it again. The only time courier would bounce an email like this is if a maildrop filter tells it to, eg spamassassin bouncing stuff. Bouncing stuff from maildrop/any delivery agent is a Bad Idea. If you must, then reject it from a courierfilter, once you've accepted it the damage is done and there's no sense in increasing your bandwidth use by bouncing. > 4) "nowhere.com" doesn�t exist or isnt a mail server, so courier 'defers' > it either due to connection refused, connection timed out, or dns lookup > failed. Well, yes. You want to ensure a genuine email bounce is sent, and the server can't tell what's what. > 5) Courier keeps on trying over and over for a week (default settings). Yes, that's in case a server's down, so emails aren't lost or bounced when not needed. Dates right back to the days when the internet wasn't so reliable... You can adjust the retry time, check the man pages. > 6) All the while the logfile grows and grows. That's what a log file does, logs stuff so sysadmins know what's going on. > What we are attempting to solve, is killing those messages from being > deferred and thus sitting in the mail queue with no hope of ever returning > the failure notice to the original sender. Why not solve the real problem here, remove the catch-all that's accepting the mail. There MUST be one, Courier WILL NOT accept mail to a nonexistant user, ever. > If you would have read the first emails about this from me and the others, > you would have understood that from the start. And default settings of > courier compound this issue, and thus why this issue exists to begin with. I've been reading the mails all along, and I'm wondering why this is an issue. It's not one I have, things to an unknown address get denied, other spam is just dropped to a certain folder (INBOX.Junk) and deleted after a while. There's no point bouncing. -- Phillip Hutchings [EMAIL PROTECTED] http://www.sitharus.com/ ------------------------------------------------------- This SF.Net email is sponsored by: SourceForge.net Broadband Sign-up now for SourceForge Broadband and get the fastest 6.0/768 connection for only $19.95/mo for the first 3 months! http://ads.osdn.com/?ad_id%62&alloc_ida84&op=click _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
