On 4/21/2014 6:08 PM, Vlatko Salaj wrote:
On Monday, April 21, 2014 11:32 PM, Hector Santos <[email protected]> wrote:
How do you define a 3rd party SPF condition that isn't already defined
and authorized by the 1st party?� IOW, by virtue of the 1st party
adding the 3rd party information into a SPF record, it is inherently
ready for 3rd party operations. No?
no. 3rd party SPF support in DMARC's alignment context means support
for 3rd party SMTP MAIL FROM, or 3rd party HELO/EHLO. by SPF specs,
there are no provisions for 3rd party SPF support in this sense.
You mean Multi-hop, relays where there is a nodal IP transition point
which fails the LMAP IP::DOMAIN assertion. (SPF is an LMAP protocol).
The Association of the Sender IP and SMTP Envelope Domains:
LMAP Validation and Trust Analysis
http://www.winserver.com/public/antispam/lmap/draft-lmapanalysis1.htm
what SPF specs do allow is adding 3rd party servers to the IP pool of
senders, but that's not full 3rd party support actually, in DMARC
alignment terms.
Right.
I think the DKIM 3rd party resigner issue is the more important issue
at this point.
If this is not resolved, mail system developers like myself will be
forced to provide undesirable "mail tampering" kludges and
considerations to customers. :(
--
HLS
_______________________________________________
dmarc mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/dmarc
