--On Wednesday, August 11, 2004 6:14 PM -0700 ned(_dot_)freed(_at_)mrochek(_dot_)com
wrote:
[regarding section 4.1]
| I'm also not comfortable with the bit about modifying the RFC 2822
| header to match the SUBMITTER field. I understand the rationale for
| having this, but I think giving license to piddle with the headers
| to an SMTP client goes a bit too far. How about saying that the
| SMTP client can only do this sort of thing if the SUBMITTER value
| on hand is found not to match the header and the SUBMITTER value is
| known to be more "accurate" than what's in the header. If the
| header is more definitive, the right thing to do is set the
| SUBMITTER to match it, not the other way around.
Ned, I don't see where it says this -- in fact, it seems to say the
opposite (the SUBMITTER must match the RFC 2822 header). It does say
that the _clients_ (not the SMTP servers) MUST make sure they match
by adding a 2822 header if necessary, and that servers SHOULD verify
that the SUBMITTER matches the PRA from the header (section 4.2).
eric