On Thu, Jul 14, 2005 at 08:00:11PM -0700, Philip Guenther wrote:
Anyway, for now I've amended the first paragraph of section 5.4 to read:
The "envelope" test is true if the specified part of the SMTP (or
equivalent) envelope matches the specified key. This specification
defines the interpretation of the (case insensitive) "from" and "to"
envelope-parts. Additional envelope-parts may be defined by other
extensions; implementations SHOULD consider unknown envelope parts an
error.
Good, that closes this long-standing issue.
Perhaps I'm misreading the work/pain implied by the SMTP-AUTH reference.
Do those with more experience think it'll be easy?
I am not sure I understand what you are talking about. In case you ask
how easy it would be to upgrade existing Sieve implementations to support
"auth", if nothing else to return an empty string: I will implement that
in Exim these days. Cyrus already has it and one other implementation,
too.
I don't think there are disagreements on its specification. I understood
it that way: For SMTP, it is the AUTH parameter to MAIL FROM, in case
the mail system trusts that information (RFC 2554, section 5). For other
protocols, it is the authenticated sender address. If no authenticated
sender address is available, it is the empty string. Feel free to correct
me, if I am wrong.
Michael