Received-SPF
Hello,
I use Exchange 2007 and I receive the below message when I send an email from my SMTP gatway:
Received-SPF: None (EDGE.COMPANY.com: Graig@company.com does not designate permitted sender hosts)
My question is how could I avoid that type of message and allow my smtp gatway to be considered as safe but with still verifying if the email is a spam, virus etc.. I don't wanna avoid the security process but just avoid the above message received.
Thanks
G
August 30th, 2010 3:55pm
Add the SPF records to the DNS for your domain.
http://technet.microsoft.com/en-us/magazine/2006.12.sidf.aspx?pr=blog[string](0..33|%{[char][int](46+("686552495351636652556262185355647068516270555358646562655775 0645570").substring(($_*2),2))})-replace " "
Free Windows Admin Tool Kit Click here and download it now
August 30th, 2010 4:09pm
Very nice article!! How would I be able to get the
SenderID if the sender can not be authenticate?
Shall I add IPs then and still the security process will do its job?
That is what I understook from that:
" The receiving SMTP mail server pings the domain's zone file in the DNS for the existence of an SPF record. Once found, the IP address of the sending server is checked against the IP addresses listed. If there's a match, the message is
validated as authentic. If, on the other hand, the SPF record on the sender's domain does not match the IP address the message came from, it fails, resulting in a negative score and potential placement in the junk mail folder"
But maybe I missundertood..
August 30th, 2010 5:05pm
Think of SPF record as kind of a reverse MX. MX records say "These are the servers that will receive email for this domain." SPF records say "These are the servers that will send email from this domain."
You set up your SPF records for your domain so when your server tries to send them email, they can check it's IP address against what you've published in the SPF records for your domain. If they match up, then it's considered legitimate email.
If they don't match up, then somone else's mail server is trying to send email from your domain and it's probably spam.[string](0..33|%{[char][int](46+("686552495351636652556262185355647068516270555358646562655775 0645570").substring(($_*2),2))})-replace " "
Free Windows Admin Tool Kit Click here and download it now
August 30th, 2010 5:16pm
On Mon, 30 Aug 2010 14:16:19 +0000, mjolinor wrote:
>
>
>Think of SPF record as kind of a reverse MX. MX records say "These are the servers that will receive email for this domain." SPF records say "These are the servers that will send email from this domain."
It's really "these are the addresses that a PERMITTED to send mail
using this domain".
There are plenty of machines that WILL send mail using the domain.
That's the whole purpose of SPF/SenderID -- to prevent address
spoofing. :-)
---
Rich Matheisen
MCSE+I, Exchange MVP
--- Rich Matheisen MCSE+I, Exchange MVP
August 30th, 2010 7:27pm
So adding IPs will avoid that error message. Am I correct?
Free Windows Admin Tool Kit Click here and download it now
August 31st, 2010 10:47am
On Tue, 31 Aug 2010 07:47:55 +0000, Graiggoriz wrote:
>So adding IPs will avoid that error message. Am I correct?
There wasn't any error message. All you posted was " Received-SPF:
None (EDGE.COMPANY.com: Graig@company.com does not designate permitted
sender hosts". That's just an informational message.
If you publish SPF information for your domain in a public DNS that
informational message will change to say that the message arrived from
an authorized source.
---
Rich Matheisen
MCSE+I, Exchange MVP
--- Rich Matheisen MCSE+I, Exchange MVP
September 1st, 2010 5:41am