John R. Levine wrote: >> I think the long term solution would be for mailing list software to >> stop mucking around with the message body, and for MUAs to work better >> at exposing meta data added by lists (like the list-unsubscribe header). > > Actually, I think the long term solution is for people to stop > pretending there is a problem. Can you describe the operational > problems you're experiencing here?
eh, non-DKIM intermediaries? > "Broken signatures" is a fact, not a problem. Sure it is. You are saying there is a SOLUTION - resign it. > Mailing lists have worked quite well for 40 years with no > signatures at all, making all sorts of random changes to the mail, so it > has to be something more than that. But it doesn't have 40 years of dealing with DKIM or authentication issues. DKIM was around 40 years ago, Mailing List software would be a whole lot different today. > Also, if you're suggesting changes to list software, please explain why > they would have greater benefits than the obvious and simple one to have > lists add their own signature on the way out. Not all list operators are agreeing with your general always resign "Pottery Theorem" model and/or take over the "responsibility" of the originating domain, copyright holder author mail. The Broken Signature Resign solution is only one solution. It doesn't cover all the problems for one reason only - you can't assume everyone is going to resign yet alone add DKIM to their software. -- Hector Santos, CTO http://www.santronics.com http://santronics.blogspot.com _______________________________________________ NOTE WELL: This list operates according to http://mipassoc.org/dkim/ietf-list-rules.html
