[First off, I want to apologize for the two brain-dead previous e-mails I sent to this list this last weekend. Converting over an old Sendmail-based system to Courier in my production environment at work was very nerve-wracking and I paniced and posted to the list a little too soon.]

This may be somewhat related to the back-scatter work Sam put into 0.49, but I'm running an older release (0.45.6).

Here is the scenario:

My work Courier server is also serving as a secondary MX for my home e-mail server.

So, occasionally, mails will come in to the work server that are intended for my home e-mail address. I've got the right bits in the Courier setup to allow this (this home address I'm posting from is in etc/esmtpacceptmailfor.dir/default), and everything works just fine.

However - and again, I don't know why this has increased over the past few days (since I moved my server from being a testbed into production use) - it seems like the following is happening a lot more nowadays:

(1) Mail comes in to work/Courier server, destined for my home (2) Courier connects to my home server (currently Sendmail-based, with spamass-milter running to stop SPAM at the front door) (3) Home server recognizes SPAM and rejects it with a 5.7.1 (4) Courier sees the rejection, tries to Return To Sender with a DSN (5) Return To Sender DSN fails due to obviously bogus SPAM return address (6) Courier sends a new DSN with the transcript of the whole thing to the local Postmaster account (me, co-worker, our boss) (7) Boss and co-worker/officemate get peeved at me for filling their inboxes with bounced SPAM mails/DSNs for my home address

Is there any way to configure Courier to *not* generate DSNs for this kind of situation?

Actually, what would be really cool is if there were some way to configure what "Diagnostic-Code" messages are acted upon with DSNs, and what are just silently dropped. An example of this would be:

Action: failed Status: 5.0.0 Diagnostic-Code: smtp; 550 5.7.1 Blocked by SpamAssassin

I'd want to silently drop sending the DSN back to the originating "From: " address, since it's a bogus faked SPAM "From: " line;

Action: failed Status: 5.0.0 Diagnostic-Code: smtp; 550 5.1.1 \ <a1aa...@isolar.dyndns.org>... User unknown

Return the DSN in this case (even though, in this case, it's also a SPAM, so it would be of no use), or else provide a configurable way to choose to silently drop it in the case of a 5.1.1 User unknown failure like this.

Is this doable? Or does it violate some RFC, are all failures like this required to generate DSN's? (If they're not considered Yet Another form of controllable back-scatter, like in Courier 0.49 or newer)

Thanks,

- Greg