Randall Shaw wrote:
...Gordon Messmer scribbled something like:
Good Lord, why?
If you don't define an [EMAIL PROTECTED] account at all, the mail will be rejected during the SMTP session. You don't have to deal with floods of incoming mail to invalid addresses, and you won't have to deal with unnecessary DSNs, either.
READ PROPERLY:
1) Mail comes in from "[EMAIL PROTECTED]" to "[EMAIL PROTECTED]". 2) Mail doesn�t get delivered because "[EMAIL PROTECTED]" is not a user.
All I'm trying to point out is that under a standard configuration #1 is not true if #2 is. Courier does not normally accept messages for addresses that don't exist. I'm *trying* to help you understand why this problem happened in the first place to prevent it from being an ongoing issue.
Maybe you understand that courier normally rejects the messages that you see bouncing on your server, and does not have to create or deliver a DSN, but sometimes it doesn't sound that way. So: is your server now configured properly? Does it reject mail to users that don't exist, or is it still bouncing mail delivered to non-existant users?
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.
Depends on what you see as courier's default settings. If you don't configure courier to accept mail that it could otherwise determine initially is undeliverable, then you'll never be faced with the problem you now have.
------------------------------------------------------- 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
