Gmail spam-blocking forum mail?

[Raize]

There's been an SPF record for a while now. Did that help at all? Can someone post the anti-spam headers that Gmail adds to forum email?

Here's from one in my spam folder presently, I pulled headers referencing my email out of it. I am going to go ahead and unmark it as spam.

Code:

Received: by 10.64.147.4 with SMTP id tg4csp58327ieb;
        Fri, 3 May 2013 06:58:06 -0700 (PDT)
X-Received: by 10.180.21.167 with SMTP id w7mr13570308wie.2.1367589485021;
        Fri, 03 May 2013 06:58:05 -0700 (PDT)
Return-Path: <php@bitcointalk.org>
Received: from bitcointalk.org ([109.201.133.65])
        by mx.google.com with ESMTP id yz8si3530704wjc.194.2013.05.03.06.58.04
        Fri, 03 May 2013 06:58:05 -0700 (PDT)
Received-SPF: softfail (google.com: domain of transitioning php@bitcointalk.org does not designate 109.201.133.65 as permitted sender) client-ip=109.201.133.65;
Authentication-Results: mx.google.com;
       spf=softfail (google.com: domain of transitioning php@bitcointalk.org does not designate 109.201.133.65 as permitted sender) smtp.mail=php@bitcointalk.org
Received: by bitcointalk.org (Postfix, from userid 999)
	id 426FB2D89C1; Fri,  3 May 2013 13:57:48 +0000 (UTC)
Subject: Topic reply: [Avalon Asic] trade-in Thread
X-PHP-Originating-Script: 1000:Subs-Post.php
From: "Bitcoin Forum" <noreply@bitcointalk.org>
Date: Fri, 03 May 2013 13:57:48 -0000
Message-ID: <91fd4c93ae423c4dc2cd5f352c944700-m2015244@bitcointalk.org>
X-Mailer: SMF
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="SMF-723cd41403c090993dffcbdef6b4ba8d"
Content-Transfer-Encoding: 7bit

[theymos]

Thanks.

Why is Gmail saying that the forum fails SPF? Port25 says:

Code:

----------------------------------------------------------
SPF check details:
----------------------------------------------------------
Result:         pass 
ID(s) verified: smtp.mailfrom=php@bitcointalk.org
DNS record(s):
    bitcointalk.org. SPF (no records)
    bitcointalk.org. 3600 IN TXT "v=spf1 mx a ~all"
    bitcointalk.org. 3600 IN MX 10 bitcointalk.org.
    bitcointalk.org. 3600 IN A 109.201.133.65

[Raize]

Was May 3rd the day you transferred the domain or moved hosts? I was thinking maybe there could be some issues related to that? Especially if the domain transfer occurred around the time one gmail server was on the new record while their spam detector server was referencing the old one?

I think most people use "v=spf1 mx a -all". Not sure what the ~ gets, but it might support some forms of older SPF. In any event, it's working fine recently, just that one email from the 3rd that I missed.

EDIT: You could also try adding

Code:

IN SPF "v=spf1 a mx -all"

RFC 4408 recommends both TXT and SPF if possible, anyway.

[theymos]

Ah, that's likely the case. Do recent emails say that it passes SPF?

I think most people use "v=spf1 mx a -all". Not sure what the ~ gets, but it might support some forms of older SPF. In any event, it's working fine recently, just that one email from the 3rd that I missed.

~ is soft fail, so it doesn't reject mail too strongly in case things get messed up (as they did here).

[Raize]

Yup, they do:

Code:

Received-SPF: pass (google.com: domain of php@bitcointalk.org designates 109.201.133.65 as permitted sender) client-ip=109.201.133.65;
Authentication-Results: mx.google.com;
       spf=pass (google.com: domain of php@bitcointalk.org designates 109.201.133.65 as permitted sender) smtp.mail=php@bitcointalk.org

[theymos]

Thanks. Everything looks good, then. I don't know why some Gmail users still have forum mail marked as spam.