Am 30.03.2015 um 21:26 schrieb Martin Gregorie:
On Mon, 2015-03-30 at 20:07 +0100, RW wrote:On Mon, 30 Mar 2015 13:55:52 -0400 (EDT) Jude DaShiell wrote:One of them is that spammers forge your address so much you get your account blacklisted and end up having to have it shut down. That happened to me and the jdash...@shellworld.net account.AFAIK there is no blacklist that lists individual sender email addresses.As Reindl says, detecting forged addresses is what SPF is for. If you own a domain which can send mail and is one where you expect to receive mail, you should have an SPF record set up for it. The SPF record should be used by other MTAs to see if the sender address is forged before attempting to send a 5xx reject message. The benefit to you is that you don't get showered with backscatter when spammers forge your domain as the spam's originator
one correction: no server ever should *send* a 5xx reject message SPF or not REJECT with 5xx is the way to gothe real problem with get your address forged are incompetent admins accepting undeliverable mail (mostly to non existing destination addresses), some of them even realize the SPF fail but finally blow out a bounce, the final idiots are doing this with postmaster@comanly.local as sender and not accepting email to postmaster / abuse
one reason are the genius MS Exchange setips with a spamfilter in front, set the spamfilter IP to "completly trusted" and by incompetence in that moment also disable the address verification from the spamfilter
been there - 600 backscatters to my private domain on one day
signature.asc
Description: OpenPGP digital signature
