Hello Lester,
I just sent an email to my gmail.com address and the SPF fails. Here’s an excerpt from headers:
Delivered-To: [email protected]
Received: by 10.221.72.205 with SMTP id yp13csp95494vcb;
Fri, 19 Sep 2014 00:45:23 -0700 (PDT)
X-Received: by 10.66.138.46 with SMTP id qn14mr12758081pab.77.1411112723502;
Fri, 19 Sep 2014 00:45:23 -0700 (PDT)
Return-Path: <[email protected]>
Received: from p3plsmtpa08-06.prod.phx3.secureserver.net (p3plsmtpa08-06.prod.phx3.secureserver.net. [173.201.193.107])
by mx.google.com with ESMTP id m1si1545522pdr.159.2014.09.19.00.45.22
for <[email protected]>;
Fri, 19 Sep 2014 00:45:22 -0700 (PDT)
Received-SPF: fail (google.com: domain of [email protected] does not designate 173.201.193.107 as permitted sender) client-ip=173.201.193.107;
Authentication-Results: mx.google.com;
spf=hardfail (google.com: domain of [email protected] does not designate 173.201.193.107 as permitted sender) [email protected]
Received: from www.site.com ([162.242.234.125])
by p3plsmtpa08-06.prod.phx3.secureserver.net with
id svlM1o00K2j0KJy01vlMvK; Fri, 19 Sep 2014 00:45:22 -0700
X-Sender: [email protected]
Date: Fri, 19 Sep 2014 07:45:21 +0000
Return-Path: <[email protected]>
To: [email protected]
From: Martin <[email protected]>
So this is a problem – you should keep the Return-Path the real sender. Otherwise the SPF check fails. Notice that something adds the X-Sender field (probably the outgoing SMTP), but it appears this is not checked by SPF.
Thanks,
Martin