Re: WSJ/gmail/ML, was a permission to...
Miles Fidelman <[email protected]> Sun, 04 May 2014 07:51:51 -0400
| Newsgroups | gmane.ietf.rfc822 |
|---|---|
| Message-ID | <[email protected]> |
Paul Smith wrote: > On 03/05/2014 22:13, Hector Santos wrote: >> On 5/3/2014 2:59 PM, Paul Smith wrote: >> >>> Who is the 'author' of the message? The message you received is NOT >>> the one I sent. So, I'm not the author, so why am I in the 'From' >>> field? So, arguably, the From field should be changed. Possibly it >>> should be changed to: >>> >>> From: [email protected], [email protected] >>> >>> because we both, "collaboratively", wrote the message. However, this >>> would probably break some mail clients/filters/etc because using >>> multiple From addresses is not "normal". >> >> Paul, >> >> You need to translate this technical philosophy into client/server >> protocol rule which means that the authoring domain has authorized >> resigning with a DMARC policy. Otherwise, its will be detected as an >> unauthorized signer, spoofed mail. > No, all you need to do is admit that the mailing list server sent the > message that came from the mailing list server - so set that to be the > From/return-path. > No. If I have a secretary make 20 copies of a letter, and drop it off at the post office, I'm still the author of the message. A secretary, forwarder, mailing list, what have you, is acting on my behalf, as my agent. The letter is from me, and the return address should be mine. (In effect, when I set reply-to to list, or a mailing list sets reply-to list, is that I'm asking/expecting that everyone who got the original letter, gets a copy of any reply.) Miles Fidelman -- In theory, there is no difference between theory and practice. In practice, there is. .... Yogi Berra _______________________________________________ ietf-822 mailing list [email protected] https://www.ietf.org/mailman/listinfo/ietf-822