In article <47993516(_dot_)90501(_at_)mtcc(_dot_)com> you write:
I don't think this is handled in the current spec, but it's certainly
possible to get delivered an otherwise valid 2822 message that doesn't
have a From: address (or a null header field). What should an
implementation do in this case?
It's not a valid RFC 2822 message, so I think it'd be fair to declare it
out of scope. And in any event, if there's no From: line, the chances
of author forgery would seem to be, ah, limited.
R's,
John
_______________________________________________
NOTE WELL: This list operates according to
http://mipassoc.org/dkim/ietf-list-rules.html