At the moment the following spf is set for the domain which is sending email from exchange server.
v=spf1 mx a:mail.firstdomain.co.uk -all
What is wrong with this spf ? as when I send email i get SPF fail
Main Topics
Browse All TopicsI have two domains and I want to make a valid spf for both:
1. firstdomain.co.uk [66.249.91.89]
2. seconddomain.com [206.190.60.37]
firstdomain.co.uk is only sending email from exchange server
second domain is sending email from exchange server and also from website (newsletters)
What would be the valid spf for both? because at the moment when I send email to someone they get caught with the message [SPF Fail]
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
I guess that's a silly question really, because obviously you think it is :) I would double check the IP address used as outbound for the SMTP server though.
Perhaps send a mail to spf-test@openspf.org and see if that agrees with the rejection assessment. It'll return an NDR with the result of the test (whether you pass or fail).
Chris
Your message did not reach some or all of the intended recipients.
Subject: test
Sent: 12/17/2008 3:44 PM
The following recipient(s) could not be reached:
spf-test@openspf.org on 12/17/2008 3:44 PM
You do not have permission to send to this recipient. For assistance, contact your system administrator.
<mail.firstdomain.co.uk #5.7.1 smtp;550 5.7.1 <spf-test@openspf.org>: Recipient address rejected: SPF Tests: Mail-From Result="pass": Mail From="administrator@firstd
You can always use the wizard (available at http://www.openspf.org/) to create your spf records. There shouldn't be any error with such generated records.
Could it be that the problem is at the remote site?
I've already seen the following situation:
Recipent has Mailserver A and backup mailserver B and employs SPF check.
A sender with valid SPF somehow fails to reach A and correctly sends to B instead.
B accepts because of valid SPF.
B tries to forward to A, but that fails because A's SPF check reveals that B is not an allowed sender for the senders domain.
The solution would be that A should not perfrom SPF checks for mails coming in via B.
@ chris: yes specific users,
I have another aol account, I tried to send a couples of email but didn't get it even i didn't get any bounceback or so.
When I send email from my own domain (pop3 account) from remote location, they get catch by gfi as SPF fails unless I put my own domain in whitelist but I dont wanna do that.
e.g: when I send from user@myfirstdomain.co.uk to anotheruser@myfirstdomain.
> ... AOL ...
Are extremely difficult to troubleshoot, if you're having problems with the SPF change -all to ~all, or even +all for a while and take a look at the headers on messages that were previously failing.
Bear in mind that AOL take ages to update DNS changes so don't expect anything like immediate results. I'd allow anything up to two weeks for them which makes them a poor platform to test against.
> When I send email from my own domain (pop3 account) from remote location
What does it use as the SMTP server in that instance? Because if that SMTP server doesn't have permission to send as your address in the SPF it will reject the message.
Chris
Check here
http://www.squish.net/dnsc
if the TXT record for firstdomain.co.uk is ok (no different versions somehow available)
same for what's used in the record, i.e.
MX of firstdomain.co.uk
and
A of mail.firstdomain.co.uk
Has any of the entries been changed recently?
@ thehaqman
I checked the link and it's OK in all the boxes.
I have GFI installed and the SPF is set to low, when I send email from remote locate using one of my own domain account through pop3, it is blocked as the spf failed.
user1@myfirstdomain.co.uk ---->via pop3----> send email to---->user2@myfirstdomain
Here is the header:
--------------------------
Microsoft Mail Internet Headers Version 2.0
Received: from mail pickup service by mail.firstdomain.co.uk with Microsoft SMTPSVC;
Mon, 22 Dec 2008 14:16:58 +0000
x-endofinjectedxheaders:28
Thread-Topic: user2@firstdomain.co.uk - Sender is forged (SPF Fail) - test15
X-GFIME-MASPAM: SPAM
Received: from remotepc ([182.RE.MO.TE]) by mail.firstdomain.co.uk with Microsoft SMTPSVC(6.0.3790.3959); Mon, 22 Dec 2008 14:16:57 +0000
From: "user1" <user1@firstdomain.co.uk>
To: <user2@firstdomain.co.uk>
Subject: user2@firstdomain.co.uk - Sender is forged (SPF Fail) - test15
Date: Mon, 22 Dec 2008 14:19:00 -0000
Message-ID: <063275E7A72A4844B81236BFD
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="----=_NextPart_0
X-Mailer: Microsoft Office Outlook 11
thread-index: AclkQDt7xLsSp/6PdSiIstbHNh
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.4325
Return-Path: <user1@firstdomain.co.uk>
X-OriginalArrivalTime: 22 Dec 2008 14:16:57.0663 (UTC) FILETIME=[F2D76CF0:01C9643
------=_NextPart_000_0014_
Content-Type: text/plain;
charset="us-ascii"
There's no such thing as sending using POP3, doesn't happen. You can receive using POP3, but you must send using an SMTP server. This is important here because it looks to be the reason for failure during SMTP transport.
1. Either the SMTP server the client is using is attempting to delivery the mail as inbound and cannot because that SMTP server fails SPF. That is, it uses smtp.somedomain.co.uk for the Outgoing mail server.
e.g.
SMTP Client (Outlook / Outlook Express) -> Third SMTP Server -> mail.firstdomain.co.uk
Here Third SMTP Server must pass the SPF check, if it fails the mail will be rejected.
2. Or the client is being checked while trying to deliver directly to mail.firstdomain.co.uk. In which case the check fails because it's not listed as a valid sending system. That is, it uses mail.firstdomain.co.uk as the Outgoing mail server.
e.g.
SMTP Client (Outlook / Outlook Express) -> mail.firstdomain.co.uk
Here the SMTP Client must pass the SPF check, if it fails the mail will be rejected.
This occurs because there is no practical difference between a server submitting a message and a client submitting a message. To all intents and purposes they appear to be the same.
Chris
sorry chris, my bad, I think I didn't explain well what I mean. Basically I mean that I'm not in exchange mode I'm have setup a pop3 account for same domain and trying to send email to another user in same domain and I'm sure I'm using SMTP to send emails.
user1@firstdomain.co.uk---
Which SMTP Server are you using above? mail.firstdomain.co.uk?
Sorry, I think I'm just not quite explaining it properly. It requires a bit of a perspective shift this one.
SMTP Client and SMTP Server are loose terms. They describe, without any further thought, the roles of two systems having a conversation using SMTP. For instance, Exchange can act as both an SMTP Client (when it's sending mail) and an SMTP Server (when it's receiving). Outlook can act as an SMTP Client (when it's sending mail / delivering mail).
When we consider SPF we have to note that the SMTP Client, the system trying to submit a message, must pass the SPF rule if the rule is enforced. Considering the above, that the SMTP Client role is available to anyone, we should be able to see that any direct connection to mail.firstdomain.co.uk will be tested.
Effectively it sounds like you're using one of these scenarios (---SMTP---> is just a connection, not another server):
IP: 1.2.3.4 IP: 1.2.3.5
MyOutlook ---SMTP---> MySMTPServer ---SMTP---> mail.firstdomain.co.uk
SPF Result: FAIL - IP 1.2.3.5 is not listed in SPF for sending as @firstdomain.co.uk
IP: 1.2.3.4
MyOutlook ---SMTP---> mail.firstdomain.co.uk
SPF Result: FAIL - IP 1.2.3.4 (even though it's the end user) is not listed in SPF for sending as @firstdomain.co.uk
That means you need a mechanism to bypass the SPF check when you're using a client from a remote site. The options would seem to be:
1. Create a VPN connection, connect directly to Exchange from Outlook.
2. Add a rule to GFI (if possible) to allow authenticated senders to send as @firstdomain.co.uk regardless of the SPF check.
3. Add another SMTP Server, either relay directly to Exchange or add it to the SPF record. Allow clients to relay (ideally using authentication).
Chris
this is getting more complicated for me as I can't create VPN for every user as they can connect from anywhere, with dynamic IP, I thought pop3/smtp would be easier.
I only want to [pop3/smtp] account to [receive/send] email using my exchange server.
I do have the option for authenticated users to relay through exchange server, there is no such option in gfi though.
I have another server with different domains but same settings, and users don't have such problem from remote location/IP.
sorry if I'm wrong here.
A picture is worth a thousand words ;-)
http://i41.tinypic.com/fu0
In this case GFI is busily testing your POP3/SMTP client for SPF validity whenever you try and send. Damn silly thing to do because it really doesn't help much.
We need it to get around the GFI thing because that's where we're dying. But that runs on the same server?
Does the Default Virtual SMTP Server in Exchange still run on there?
/me never used GFI despite having a copy kicking around somewhere.
Chris
Try this websites to accomplish your goals
1) create spf record using
http://www.microsoft.com/m
2) add spf record to your dns
(here are guidelines on wesbite http://help.campaignmonito
Business Accounts
Answer for Membership
by: Chris-DentPosted on 2008-12-17 at 07:11:00ID: 23193967
1.
From a single IP or name:
v=spf1 ip4:1.2.3.4 -all
Where 1.2.3.4 is the public IP Address of the server sending the message. You can use a name there instead with:
v=spf1 a:<name> -all
2.
From multiple IPs:
v=spf1 ip4:1.2.3.4 ip4:1.2.3.5 -all
Again, you can use the a mechanism and a name if that's easier to read.
Chris