Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: SPF: Help

spf2.0/mfrom

 

 

SPF help RSS feed   Index | Next | Previous | View Threaded


millie at caea

Apr 29, 2008, 5:44 PM

Post #1 of 2 (226 views)
Permalink
spf2.0/mfrom

Hello,

I just created our SPF records with the following two lines and sent the information to our ISP to enter into our DNS:

caea.com. IN TXT "v=spf1 ip4:216.138.203.130 -all"
email-server.caea.com. IN TXT "v=spf1 a -all"

In the "SPF vs Sender ID" article, it mentions that:

"The Sender ID specification contains a recommendation to use SPF's v=spf1 policies - which are originally defined to apply to MAIL FROM and HELO identities only - and apply them to the PRA identity as well. Specifically, it says to consider v=spf1 as equivalent to spf2.0/mfrom, pra. This is technically wrong, as it is explained in detail below. Sender ID implementors should correct this and treat v=spf1 records as equivalent to spf2.0/mfrom"

"Microsoft is aware of the problem and representatives of theirs have stated that they anticipate the conflict to resolve itself as soon as domain owners are publishing all their v=spf1 policy records with the possible PRA interpretation in mind. Of course this is not going to happen as there are hundreds of thousands of v=spf1 records out there that were published long before Sender ID even existed."

I am just about to publish my v=spf1 and I didn't have any possible PRA interpretation in mind. Is there something else I need to add to our SPF record?

Is the "spf2.0/mfrom" something I need to configure within our Exchange Server's Sender ID configuration? I haven't configured the Sender ID yet.

Thanks for your help.

Millie Kwan



The foregoing communication is intended only for the use of the individual or individuals named above and should not be read by or delivered to any other person. Such communication may contain information which is privileged, confidential or otherwise exempt from disclosure. Any collection, use, disclosure, forwarding or copying of this communication is strictly prohibited. If you have received this information in error, please accept our apology and immediately return the communication to the sender by electronic mail and destroy the message. See also Equity's Privacy Policy available at www.caea.com.

-------------------------------------------
Sender Policy Framework: http://www.openspf.org
Modify Your Subscription: http://www.listbox.com/member/
Archives: http://www.listbox.com/member/archive/1020/=now
RSS Feed: http://www.listbox.com/member/archive/rss/1020/
Powered by Listbox: http://www.listbox.com


steve at teamITS

Apr 30, 2008, 8:25 AM

Post #2 of 2 (214 views)
Permalink
RE: spf2.0/mfrom [In reply to]

Millie Kwan wrote on 4/29/2008 7:44:08 PM:

> I am just about to publish my v=spf1 and I didn't have any possible
PRA
> interpretation in mind. Is there something else I need to add to our
SPF record?
>
> Is the "spf2.0/mfrom" something I need to configure within our
Exchange
> Server's Sender ID configuration? I haven't configured the Sender ID
yet.

If you want to force SenderID to be the same as SPF, you can
just add a second identical TXT record:

caea.com. IN TXT "v=spf1 ip4:216.138.203.130 -all"

caea.com. IN TXT "spf2.0/mfrom ip4:216.138.203.130 -all"

Sender ID is set up in DNS just like SPF. If your Exchange server is
your MX, it can be set to check for Sender ID on incoming mail.

-----
SPF FAQ: http://www.openspf.org/FAQ
Common mistakes: http://www.openspf.org/FAQ/Common_mistakes

- Steve Yates
- ITS, Inc.
- Proving once again my Theory that GERMANS LOVE DAVID HASSELHOFF.

~ Taglines by Taglinator - www.srtware.com ~

-------------------------------------------
Sender Policy Framework: http://www.openspf.org
Modify Your Subscription: http://www.listbox.com/member/
Archives: http://www.listbox.com/member/archive/1020/=now
RSS Feed: http://www.listbox.com/member/archive/rss/1020/
Powered by Listbox: http://www.listbox.com

SPF help RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact lists@gossamer-threads.com
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.