Mark Delany wrote:
Maybe, but if they're going through the usual MTAs, they're breaking
already so I can't get too worried about it.
That's not true. Sendmail does not change these strings.
Is that true on the SUBMIT front? or the MTA front?
As far as I know, I run a submit server and it doesn't change anything.
As I said, I'm very interested in Eric's input here.
We really have
absolutely
no clue as to whether this is going to be a problem.
I guess I'm a little confused about the problem here. For non-signed
mail we don't care, yes?
For signed mail, the spec is asking signers to ensure compliance with
2822. If, as you say, sendmail passes through whatever bits it gets,
then as long as signers ensure compliant messages, what problem are we
trying to solve?
Um, there's user experience, which last I heard sort of trumps everything.
Can you say for absolute certain that the user experience of converting
compliant 822 messages into compliant 2822 messages won't cause trouble?
I sure can't. That at the very least ought to evoke some humility.
Put another way, my question is this: what evidence is there to
suggest that stray characters are likely to be introduced *after*
signing of an rfc2822 compliant mail?
That's not the issue. The introduction is at submission. By the
submitter. If changing
things after submission causes problems, then... As I've said many
times, we don't
have the luxury of aspiration, we have the duty of dealing with the
world as it is lest
we design something that is beside the point.
Mike
_______________________________________________
NOTE WELL: This list operates according to
http://mipassoc.org/dkim/ietf-list-rules.html