On Sat, 16 Jan 2016 05:00:58 PM Craig Sanders via luv-main wrote:
because overwriting the Reply-To: header can make it impossible to reply to the original sender.
I'm up for negotiating on that matter.
what's to negotiate? you're either going to fix the damage you caused or you're not. i'm not going to beg you to do what. you're the list admin, if you insist on breaking the list, there's nothing i can do about it.
If you believed that there was nothing you could do then you wouldn't have spent months arguing.
because what mailman is doing with DMARC is broken.
It's doing the best it can in a difficult situation.
even if you can manage to think of that as being only partly broken, partly broken is still broken. it's doing the wrong thing with DMARC. that means it's a "feature" that shouldn't be used.
OK, please go tell Yahoo etc that they are doing it wrong. Let's leave the list server in it's current configuration until you convince Yahoo and Gmail of the error of their ways.
I fixed it, mail is now being delivered reliably. If you want "comments" to be different in email then you can help figure out how to do that without compromising mail reliability.
you haven't fixed anything. you've solved one minor problem that affected only a handful of people (who inflicted it on themselves by using DKIM) at the cost of screwing up the From: and Reply-To: headers on all messages forwarded by the list, which affects all subscribers.
Actually the Gmail users didn't do anything, they just signed up for a mail service knowing nothing about DKIM or the Gmail actions that would happen when they received DKIM signed mail via a list.
Translation: You think that Yahoogroups, the Mailman developers and everyone else have got it wrong
the fact that yahoogroups does it is undeniable proof that it's wrong. they never get anything right, they've been screwing up mail since the 90s.
If they were so wrong then Gmail wouldn't implement DKIM/DMARC checks on mail it receives.
the mailman devs have obviously got it wrong. even they admit that their implementation is buggy and broken.
What is buggy is the fact that they can't preserve headers and body encoding.
but can't be bothered showing us all how to do it in a way that you like.
you're assuming that there is such a way. IMO DMARC is broken-by-design so it's impossible to do it in any good or even reasonable way.
in other words: the way i'd like is to not do it at all. i've said that repeatedly.
It's OK to wish that Yahoo, Gmail, Hotmail, Facebook, and other big companies would do things differently. But your wishes aren't going to change anything. Let's stick to discussing the reality of how to deal with mail to/from such services. -- My Main Blog http://etbe.coker.com.au/ My Documents Blog http://doc.coker.com.au/