exim router - header and spf verification help...
hey everyone -
having an issue that is related to an exim router and spf checks. my server works closely with another domain and has a router in it to deliver mail for one domain (trmacs.com) directly to gmails servers - bypassing the spam filter etc. the weird thing is that when doing this gmail fails SPF verification as it thinks the mail is coming directly from the ip address the client is at instead of my server who is delivering the message and is listed in SPF. attached here are the sample headers of the failed SPF and the router config etc. what am i missing? if i deliver without the router it works perfectly.
and router:
Delivered-To: XXXX@trmacs.com
Received: by 10.50.57.84 with SMTP id g20csp37073igq;
Fri, 23 May 2014 07:34:51 -0700 (PDT)
X-Received: by 10.140.51.172 with SMTP id u41mr6669213qga.69.1400855690751;
Fri, 23 May 2014 07:34:50 -0700 (PDT)
Return-Path:
Received: from vps2.boylehost.com (vps2.boylehost.com. [207.58.138.7])
by mx.google.com with ESMTPS id y46si3663520qgy.90.2014.05.23.07.34.50
for
(version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
Fri, 23 May 2014 07:34:50 -0700 (PDT)
Received-SPF: fail (google.com: domain of XXXX@socialalchemydesign.com does not designate 173.9.80.213 as permitted sender) client-ip=173.9.80.213;
Authentication-Results: mx.google.com;
spf=hardfail (google.com: domain of XXXX@socialalchemydesign.com does not designate 173.9.80.213 as permitted sender) smtp.mail=XXXX@socialalchemydesign.com
Received: from 173-9-80-213-newengland.hfc.comcastbusiness.net ([173.9.80.213]:45868 helo=[10.0.10.136])
by vps2.boylehost.com with esmtpsa (TLSv1:AES128-SHA:128)
(Exim 4.82)
(envelope-from )
id 1WnqYc-0007VB-3C
for XXXX@trmacs.com; Fri, 23 May 2014 10:34:50 -0400
From: colleen
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: test3
Message-Id:
Date: Fri, 23 May 2014 10:34:48 -0400
To: XXXX@trmacs.com
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\))
X-Mailer: Apple Mail (2.1878.2)
test3
and router:
send_gmail:
driver = manualroute
transport = remote_smtp
route_list = trmacs.com ASPMX.L.GOOGLE.COM
-
Hello :) Have you tested to determine if the same issue persists with other mail servers, or is it isolated to Google? Have you considered designating the client's IP address as a permitted sender in the SPF record? Thank you. 0
Please sign in to leave a comment.
Comments
1 comment