Is SPF Supported by Exchange 2003 Ent SP2

Scott · Joined: 05 Aug 2007 Posts: 22

We implemented an SPF record for our Exchange 2003 Ent SP2 server in our
external DNS zone file. This won't pose problems will it? Exchange supports
SPF (Sender Policy Framework)...correct?

Archived from group: microsoft>public>exchange>misc

Bharat Suneja [MVP] · Joined: 05 Aug 2007 Posts: 1043

- Exchange supports SenderID, based on SPF (aka "SPF Classic") and
Microsot's own CallerID.
- Publishing your own SPF records has nothing to do with your Exchange
server supporting SPF/SenderID - that's for inbound mail. With SenderID
enabled, your server will check the SPF records of the purported responsible
address of the sender. Not an anti-spam solution per se, it is designed to
protect from header spoofring.
- Publishing SPF record for your domain(s) ensures recipients of messages
claiming to be from your domain can check whether they are being sent from
servers authorized by your domain.
More info:
SenderID
http://www.microsoft.com/mscorp/safety/technologies/senderid/default.mspx

Sender Policy Framework
http://www.openspf.org/

--
Bharat Suneja
MVP - Exchange
www.zenprise.com
NEW blog location:
exchangepedia.com/blog
----------------------------

"Scott" wrote in message @microsoft.com...
> We implemented an SPF record for our Exchange 2003 Ent SP2 server in our
> external DNS zone file. This won't pose problems will it? Exchange
> supports
> SPF (Sender Policy Framework)...correct?

Scott · Joined: 05 Aug 2007 Posts: 22

Bharat,

Thanks for the clarification. By enabling Sender ID, will this adversely
affect Exch server performance? Will it interfere with mail flow in any way
for messages from domains not having SPF records?

"Bharat Suneja [MVP]" wrote:

> - Exchange supports SenderID, based on SPF (aka "SPF Classic") and
> Microsot's own CallerID.
> - Publishing your own SPF records has nothing to do with your Exchange
> server supporting SPF/SenderID - that's for inbound mail. With SenderID
> enabled, your server will check the SPF records of the purported responsible
> address of the sender. Not an anti-spam solution per se, it is designed to
> protect from header spoofring.
> - Publishing SPF record for your domain(s) ensures recipients of messages
> claiming to be from your domain can check whether they are being sent from
> servers authorized by your domain.
> More info:
> SenderID
> http://www.microsoft.com/mscorp/safety/technologies/senderid/default.mspx
>
> Sender Policy Framework
> http://www.openspf.org/
>
> --
> Bharat Suneja
> MVP - Exchange
> www.zenprise.com
> NEW blog location:
> exchangepedia.com/blog
> ----------------------------
>
>
> "Scott" wrote in message
> @microsoft.com...
> > We implemented an SPF record for our Exchange 2003 Ent SP2 server in our
> > external DNS zone file. This won't pose problems will it? Exchange
> > supports
> > SPF (Sender Policy Framework)...correct?
>
>

Bharat Suneja [MVP] · Joined: 05 Aug 2007 Posts: 1043

No. The default settings do not drop messages from domains that do not have
SPF records. Messages are only dropped on an explicity FAIL response. As far
as performance goes, it's just another DNS lookup and generally nothing I
would be concerned about.

--
Bharat Suneja
MVP - Exchange
www.zenprise.com
NEW blog location:
exchangepedia.com/blog
----------------------------

"Scott" wrote in message @microsoft.com...
> Bharat,
>
> Thanks for the clarification. By enabling Sender ID, will this adversely
> affect Exch server performance? Will it interfere with mail flow in any
> way
> for messages from domains not having SPF records?
>
> "Bharat Suneja [MVP]" wrote:
>
>> - Exchange supports SenderID, based on SPF (aka "SPF Classic") and
>> Microsot's own CallerID.
>> - Publishing your own SPF records has nothing to do with your Exchange
>> server supporting SPF/SenderID - that's for inbound mail. With SenderID
>> enabled, your server will check the SPF records of the purported
>> responsible
>> address of the sender. Not an anti-spam solution per se, it is designed
>> to
>> protect from header spoofring.
>> - Publishing SPF record for your domain(s) ensures recipients of messages
>> claiming to be from your domain can check whether they are being sent
>> from
>> servers authorized by your domain.
>> More info:
>> SenderID
>> http://www.microsoft.com/mscorp/safety/technologies/senderid/default.mspx
>>
>> Sender Policy Framework
>> http://www.openspf.org/
>>
>> --
>> Bharat Suneja
>> MVP - Exchange
>> www.zenprise.com
>> NEW blog location:
>> exchangepedia.com/blog
>> ----------------------------
>>
>>
>> "Scott" wrote in message
>> @microsoft.com...
>> > We implemented an SPF record for our Exchange 2003 Ent SP2 server in
>> > our
>> > external DNS zone file. This won't pose problems will it? Exchange
>> > supports
>> > SPF (Sender Policy Framework)...correct?
>>
>>

Out of office supported features We are planning to install Exchange 2007 over the Xmas break. Most of the users in the office will access Exchange using Outlook from their desktop computers. However there are some users who have laptops. I presume that when in the office they will conne

5.6.1 smtp;554 5.6.1 Body type not supported by Remote Host> Anyone seen NDR below before and any clue? User (e2k7) sending mail to a user (e2k). Delivery has failed to these recipients or distribution lists: User ABC The e-mail system had a problem processing this message. Microsoft Exchange will not try to redel

Outlook 2003 Disconnected from Exchange Server 2003 We have one laptop (XPP) where Outlook 2003 is showing as Disconnected. The client can still connect to the network drives. When the client logs into our terminal server and attempts to open Outlook, it states that exchange is unavailable and may be down

Install Exchange 2003 Standard on Server 2003 R2 Hey everyone. I have a question about an Exchange 2003 installation. Whenever setup is run it says that there is a "Known Compatibility Issue" with Exchange and our version of Server which is Server Standard 2003 R2. If we continue the exchange install

Exchange 2003 / Outlook 2003 performance Hello, we have SBS 2003 (not R2) and only 3 mailboxes. At the moment, one mailbox has about 7 GB and much mails with big attachments (we have to send and receive big attachments up to 10 MB). Opening emails in Outlook 2003 needs sometimes up to 2 or 3 min