Alexandros Vellis <avel(_at_)noc(_dot_)uoa(_dot_)gr> writes:
Based on the above comments, with which I wholeheartedly agree, I would
like to propose actually adding the envelope-auth capability in the base
spec. It is only a matter of one more paragraph clarifying the "auth"
value to the envelope argument.
Unfortunately, it's a bit more than that: I'm fairly certain that the
SMTP-AUTH reference would need to be normative ("...must be read to
understand or implement..."). Rather than involving 3028bis in the
tangle that moving any sort of authentication protocol along the
standard track appears to be, I suggest the envelope-auth extension be
defined in a separate document.
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
Perhaps I'm misreading the work/pain implied by the SMTP-AUTH reference.
Do those with more experience think it'll be easy?