Wed, 06 Mar 2013
Sometimes I hate Google, or at least their mail admins. They seem to have entirely missed the point of SPF records.
I publish them, not because I believe they'll fix the spam problem, but because
a spammer has taken to forging their sender address to appear to originate from
my domain. Obviously none of my servers are involved in such loathsome activities.
I publish these records to give other mail admins the chance to reject such e-mail outright, or at least to assign it a higher spam probability but mostly so they won't bug me about having rejected it.
Google rather seem to have missed the point though because they use them to reject the spam, which is good, and then send delivery failures to me. They know that it's spam with a forged sender, that's why they're rejecting it in the first place, yet they bug me about it.
Delivery to the following recipient failed permanently: email@example.com ----- Original message ----- X-Received: by 10.68.42.9 with SMTP id j9mr23765326pbl.142.1362320729989; Sun, 03 Mar 2013 06:25:29 -0800 (PST) Return-Path:
Received: from [18.104.22.168] ([22.214.171.124]) by mx.google.com with ESMTP id tv4si18179919pbc.155.2013.03.03.06.25.24; Sun, 03 Mar 2013 06:25:29 -0800 (PST) Received-SPF: fail (google.com: domain of B37FBAB0D@sigsegv.be does not designate 126.96.36.199 as permitted +sender) client-ip=188.8.131.52; Authentication-Results: mx.google.com; spf=hardfail (google.com: domain of B37FBAB0D@sigsegv.be does not designate 184.108.40.206 as permitted s +ender) smtp.mail=B37FBAB0D@sigsegv.be From: "Tanya Guerrero" Subject: hi there To: List-Unsubscribe: Content-Transfer-Encoding: 8bit Content-Type: text/plain; chars="iso-8859-1" Date: Sun, 03 Mar 2013 14:25:21 -0000 Message-ID: <20130303142521.244356B88AC8AC5DC029.4744484@SARA-PC> SPAM SPAM SPAM