RE: Work plan for Sender ID

ietf-mxcomp

RE: Work plan for Sender ID

2004-09-13 21:55:46


wayne wrote:

The SPFv1 records can not transition to the SPFv2 records unless the
both the MAILFROM and HELO scopes are added.

I again ask that the "v=spf1 " magic number be interpreted as
"spf2.0/mailfrom,helo" in the SenderID spec.


I am also interested in a response to this request. It seems reasonable to
me.

Michael R. Brumm

[More with this subject...]

<Prev in Thread]	Current Thread	[Next in Thread>
Work plan for Sender ID, Andrew Newton Re: Work plan for Sender ID, Daniel Quinlan Re: Work plan for Sender ID, Yakov Shafranovich Re: Work plan for Sender ID, Andrew Newton Re: Work plan for Sender ID, Ted Hardie Re: Work plan for Sender ID, wayne RE: Work plan for Sender ID, Michael R. Brumm <= Re: Work plan for Sender ID, Tony Finch Re: Work plan for Sender ID, wayne PRA is dead. Media, nanae/nanabl.(was Re: Work plan for Sender ID), Matthew Elvey Re: Work plan for Sender ID, william(at)elan.net Re: Work plan for Sender ID, Anne P. Mitchell, Esq. Re: Work plan for Sender ID, william(at)elan.net Re: Work plan for Sender ID, Stephane Bortzmeyer Re: Work plan for Sender ID, Yakov Shafranovich Re: Interpreting "v=spf1" (was Work plan for Sender ID), Mark Lentczner Re: Interpreting "v=spf1" (was Work plan for Sender ID), Yakov Shafranovich

Previous by Date:	Re: consensus call of RR prefix, Jonathan de Boyne Pollard
Next by Date:	Re: DEPLOY: Over-running TXT dataspace in FQDN (-protocol I belie ve), Jonathan de Boyne Pollard
Previous by Thread:	Re: Work plan for Sender ID, wayne
Next by Thread:	Re: Work plan for Sender ID, Tony Finch
Indexes:	[Date] [Thread] [Top] [All Lists]