I'm using "v=spf1 mx ip4:84.16.237.162 -all", so I think that is not the problem. I think there are simply too many email servers that do not check SPF records or do the checking too late. A common set-up is to accept mail and later check it for spam, possibly after forwarding it to yet another server.

Werner

Hans Salvisberg schrieb:
Since this thread is still active, I'll add my 2 cents:

Werner Fleck wrote:
I did not mean forged bounces but real bounces for forged mails. Spammers discovered my domains some months ago and are increasingly using them for forged mails. I am using SPF to protect my domains but if other mail servers don't check it on reception and then additionally bounce the forged mail, I'm getting the bounce, not the spammer.

I'm surprised that adding an SPF record to your domain is not working for you. Maybe your SPF record is too weak? I've experienced several misdirected bounces floods on various domains, and these floods have dried up completely within a few days or weeks every time after adding an SPF record that ends with

   -all

Apparently, this causes enough rejections to annoy the spammers and get them to move on to other domains that they can exploit with less hassle.

If this has gone on for an extended period of time, it may take longer to dry up, but I think your chances are intact, with a strong SPF record.

Hans

Reply via email to