"Jon Kyme" <jrk(_at_)merseymail(_dot_)com> wrote:
A spamtrap is a rather particular case. All messages are accepted - all
are successfully delivered ("success" and "deliver" have very particular
meanings in this context). No DSN are issued. No problem.
You're missing a key point: The spamtrap is usually a spamtrap ONLY
because it gets so much spam that it's useless as a normal domain.
i.e. It was getting massively attacked by spam, which is *why* it
was made a spamtrap.
It's not the case that it became a spamtrap, and *then* started
receiveing large amounts of spam. That would imply that the spammers
know it's a spamtrap, and increase their messages to it... which is
not realistic.
I think it's probably right to mention the spamtrap case in any document
dealing with filtering in SMTP (such as the one I'm *still* writing).
It's also a problem with IP firewall whitelists. If the MX for a
domain is publicly advertised, but the MTA is behind a firewall with a
whitelist, then the firewall will get whacks of TCP SYNs from
spammers. And the rate at which the SYNs arrive will drop, once the
firewall rules are removed.
In other words, any attempt to protect yourself from spam will
result in the spammers attacking you even more, in the hope that
*something* will get past your filters. This increase in spam volume
means that the filters become less effective...
Alan DeKok.
_______________________________________________
Asrg mailing list
Asrg(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/asrg