cour...@lists.sourceforge.net wrote:
Greg Earle writes:
(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?
No. This is how SMTP is supposed to work.
You will have to either stop using a secondary MX, or
reconfigure your spam filter to drop unwanted mail, instead
of rejecting it.
Dropping mail without letting the sender know, can be a dangerous thing.
What if it is a FP that is dropped (instead of rejected)? In some countries,
dropping or blackholing email is against the law. Meaning if you drop/reject
mail without letting the sender know, you can get in some trouble.
I think a sollution here would be to accept spam at step 3, tag it someway
and later in the process, delete it or move it to a specific spam-folder.
An other option could be to use a dialout-filter at step 1, checking the
from-address of the mail as it comes in, and reject it if the specified
from-address does not exist or is unavailable somehow. Not a 100% sollution,
but it should alleviate your problems. Only problem is that there isn't a
mature dialout-filter :-( Also, to be more effective, you probably want to
combine it with greylisting.
Kind Regards,
Sander Holthaus
6 messages in net.sourceforge.lists.courier-usersRE: [courier-users] "Notice: mail del...
