I have two websites hosted on the same server. I set up the second site after I had already set up the first site and its corresponding email server. This is more of a DNS question. The first server has been working trouble free for a long time, and its SPF record checks out just fine and I send mail with no issues. I set up a second web server using an apache vhost, and I used iRedAdmin to set up a second email domain. The problem appears to lie with my SPF record, and whenever I send mail form the second domain, it gets flagged as spam. I've set it up using the original mail server as its MX, but I've never done two e-mail server on the same IP address and I'm not sure if I'm mucking it up.
Here are the two SPF records for reference (hostnames obfuscated):
This works fine:
v=spf1 a mx a:server1.com mx:mail.server1.com ip4:x.x.x.x ~all
This does not work:
v=spf1 a mx a:server2.com mx:mail.server1.com ip4:x.x.x.x ~all
And ideas? Server 2 insofar as mail is concerned is simply a front for server1. You can send mail to email@example.com, but it gets routed through the iredmail server at server1.com.
Any insight would be appreciated as I need my messages to stop being flagged as spam.
Received-SPF: neutral (google.com: x.x.x.x is neither permitted nor denied by best guess record for domain of firstname.lastname@example.org) client-ip=x.x.x.x;
Ok. I don't care if you guys know my ip addresses, I just need to know why gmail sends this to the spam folder. According to the headers in the message, it passes the SPF tests and etc.
Delivered-To: email@example.com Received: by 10.58.206.18 with SMTP id lk18csp38915vec; Fri, 22 Feb 2013 11:17:09 -0800 (PST) X-Received: by 10.68.203.100 with SMTP id kp4mr4779507pbc.186.1361560628737; Fri, 22 Feb 2013 11:17:08 -0800 (PST) Return-Path: <firstname.lastname@example.org> Received: from signtelligence.com ([188.8.131.52]) by mx.google.com with ESMTP id d10si3813292paz.55.2013.02.22.11.17.08; Fri, 22 Feb 2013 11:17:08 -0800 (PST) Received-SPF: pass (google.com: domain of email@example.com designates 184.108.40.206 as permitted sender) client-ip=220.127.116.11; Authentication-Results: mx.google.com; spf=pass (google.com: domain of firstname.lastname@example.org designates 18.104.22.168 as permitted sender) email@example.com Received: from localhost (localhost.localdomain [127.0.0.1]) by signtelligence.com (Postfix) with ESMTP id DD33E5362890 for <firstname.lastname@example.org>; Fri, 22 Feb 2013 23:17:07 +0400 (MSK) X-Virus-Scanned: Debian amavisd-new at signtelligence.com Received: from signtelligence.com ([127.0.0.1]) by localhost (signtelligence.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NhgKkX5jwSBC for <email@example.com>; Fri, 22 Feb 2013 23:17:07 +0400 (MSK) Received: from claygarland.com (localhost.localdomain [127.0.0.1]) by signtelligence.com (Postfix) with ESMTPA id 76033536288F for <firstname.lastname@example.org>; Fri, 22 Feb 2013 23:17:06 +0400 (MSK) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Date: Fri, 22 Feb 2013 14:17:06 -0500 From: email@example.com To: <firstname.lastname@example.org> Subject: It's been a long time. Message-ID: <email@example.com> X-Sender: firstname.lastname@example.org User-Agent: RoundCube WebMail Hey. I just wanted to say hello. It's been a long time since we've talked. My new phone number is (xxx) xxx-xxxx. Give me a ring! Peace, Clay