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

Mailing List Archive: SPF: Help

SPF -> SenderID

 

 

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


murthy+spf at teamon

Jul 19, 2004, 4:58 PM

Post #1 of 2 (772 views)
Permalink
SPF -> SenderID

Hi,

We are an email company -- we have products that generate email on behalf of end-users (similar to how greeting companies generate email) and we also provide hosted email services. We are looking into complying with SPF and have some questions regarding SPF and support of SenderID.

1. We like SenderID idea over SRS as it simplifies bounce handling especially in cases where we generate email on behalf of end-users.
So, is the new suggested path of adoption similar to:
-- provide SPF records
-- provide SenderID compliant RFC822 headers (Resent-From, Sender etc. depending on the case)
-- support SMTP MAIL SUBMITTER

If companies are adopting different paths, what is it?

2. Are e-mail forwarding companies still using SRS schemes, even after SenderID came out? If so, what is the advantage?

3. dumb question: SenderID draft (Section 5.3, point 2) specifies
"If the domain "$DOMAIN" does not exist, the EMail policy document cannot be obtains, and the result of validation is "fail".
Is this also true for SPF implementations? I'm hoping it is not as this would cause problems when
MAIL FROM: root [at] bouncehandler
is used for handling bounced messages in current world. I can see how this would be a new feature in SenderID as it doesn't rely on MAIL FROM (atleast not until flag day).


Thanks a Lot,
Murthy Gorty

-------
Archives at http://archives.listbox.com/spf-help/current/
Donate! http://spf.pobox.com/donations.html
To unsubscribe, change your address, or temporarily deactivate your subscription,
please go to http://v2.listbox.com/member/?listname=spf-help [at] v2


spf at metro

Jul 20, 2004, 12:12 PM

Post #2 of 2 (781 views)
Permalink
Re: SPF -> SenderID [In reply to]

Hi,

On Mon, Jul 19, 2004 at 04:58:50PM -0700, Murthy Gorty wrote:
> 1. We like SenderID idea over SRS as it simplifies bounce handling especially in cases where we generate email on behalf of end-users.
> So, is the new suggested path of adoption similar to:
> -- provide SPF records
> -- provide SenderID compliant RFC822 headers (Resent-From, Sender etc. depending on the case)
> -- support SMTP MAIL SUBMITTER

SenderID is still being worked out by the workgroup if i am correct.

> If companies are adopting different paths, what is it?

We're sticking with SPF-Classic for the moment.

> 2. Are e-mail forwarding companies still using SRS schemes, even after SenderID came out? If so, what is the advantage?

To the best of my knowledge, SenderID is not 'out' yet, but still being
worked out by the workgroup. We are still doing SRS on forwarded mail.

> 3. dumb question: SenderID draft (Section 5.3, point 2) specifies
> "If the domain "$DOMAIN" does not exist, the EMail policy document cannot be obtains, and the result of validation is "fail".
> Is this also true for SPF implementations? I'm hoping it is not as this would cause problems when
> MAIL FROM: root [at] bouncehandler
> is used for handling bounced messages in current world. I can see how this would be a new feature in SenderID as it doesn't rely on MAIL FROM (atleast not until flag day).

Sorry, can't help you here...

Koen


--
K.F.J. Martens, Sonologic, http://www.sonologic.nl/
Networking, embedded systems, unix expertise, artificial intelligence.
Public PGP key: http://www.metro.cx/pubkey-gmc.asc
Wondering about the funny attachment your mail program
can't read? Visit http://www.openpgp.org/

-------
Archives at http://archives.listbox.com/spf-help/current/
Donate! http://spf.pobox.com/donations.html
To unsubscribe, change your address, or temporarily deactivate your subscription,
please go to http://v2.listbox.com/member/?listname=spf-help [at] v2

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


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.