Mark Lentczner wrote:
SPF is actually deployed and we are wary of changes to the
syntax that will break existing parsers.
How do existing parsers handle %{e} ? I haven't found a %{e}
definition in macros.html or in your original SPF document.
If that's already v=spf2 you're IMHO free to use new syntax.
if you trust all of 192.168.0.0/16 to use your domain name
in MAIL-FROM, then surely you trust any such host to use it
in HELO. Guarding against your own errors in configuring
your own machines isn't good enough for my purposes.
Yes, maybe you could use another approach, say that all MX for
a domain are always allowed to use HELO domain in the case of
a bounce independent of the sender policy.
Something along the line "for HELO checks add +mx implicitly".
If even that's not good enough my imagination fails: Who uses
"HELO domain" in bounces, but is not allowed to send real mail
from this domain ? If that's what this discussion is about (?)
Bye, Frank