op 11-04-14 16:24, Steve Atkins schreef:
On Apr 11, 2014, at 12:59 AM, Patrick Peterson <[email protected]> wrote:
On Apr 9, 2014, at 6:41 AM, Dave Crocker <[email protected]> wrote:
On 4/9/2014 2:07 AM, Jonas Falck wrote:
Gents,
Perhaps this has been discussed,
what about just rewrite "from" header to actual mailing list, so you don't
violate DMARC,
http://dmarc.org/faq.html#s_3
What about recipients' not being able to reply directly to the original author?
I believe use of Reply-To header per RFC 5322 can be used to reply to author
without use of From: header
https://tools.ietf.org/html/rfc5322
When the "Reply-To:" field is present, it
indicates the address(es) to which the author of the message suggests
that replies be sent. In the absence of the "Reply-To:" field,
replies SHOULD by default be sent to the mailbox(es) specified in the
"From:" field unless otherwise specified by the person composing the
reply.
For example, in the original email sent to this mailing list to which I’m
replying, the message had the following headers:
From: Dave Crocker <[email protected]>
Reply-To: Dave Crocker <[email protected]>
and when I hit reply, my response goes to
Dave Crocker <[email protected]>
That's how you expect it to work, sure.
If the mailing list did something like replace the Reply-To with the From, then
replace the From with an email
address that isn't Dave's, that wouldn't work.
If the mailing list instead replaced the Reply-To with the From only if there
wasn't already a Reply-To, I wouldn't
be able to search for "[email protected]" in my MUA to find it.
All these mail headers have existing meanings and usage. If you remove the
content of one of them, however
you shuffle it around the others you're going to lose data and break some
usage. You can decide what to
break, but it's going to break something, sometimes.
Bandaid responses aren't going to reliably fix the problem. That doesn't mean
it's impossible to fix, just that any
half-assed response that starts with "It's easy, you just need to ..." is
almost certainly wrong.
+1
/rolf
_______________________________________________
dmarc-discuss mailing list
[email protected]
http://www.dmarc.org/mailman/listinfo/dmarc-discuss
NOTE: Participating in this list means you agree to the DMARC Note Well terms
(http://www.dmarc.org/note_well.html)
