On 12/07/2017 07:19 PM, Chip Davis wrote:
And I have no problem with that (except that editorial advice probably doesn't belong on a settings page) because it refers to a "mailing list". I have no statistics, but my exposure to Mailman has been almost exclusively as a "discussion list". Therefore, all of the Mailman instances that I admin ignore this "strong recommendation" and set 'reply_goes_to_list' to 'This list'. Yes, that does open the DMARC/DKIM can-o-worms, but just about everything useful does... :-/
I came to the conclusion long ago that there are effectively two types of mailing lists, 1) broadcast lists where replies go somewhere other than the list and 2) discussion lists where replies go back to the mailing list.
Which should be used is an often debated topic. In some ways, it's as religious as vi vs emacs.
Ultimately, it comes down to what you, as a mailing list administrator want to do. Sure, you can take some influence from your subscribers. But it is /your/ choice as the administrator.
I think that Mailman (et al) should inform administrators of the potential caveats of their decision, not try to persuade them one way or the other.
I personally feel like discussion mailing lists are their own entity. Thus they are the author of the message (with content heavily based on incoming emails) and as such all aspects of the message should reflect the discussion mailing list. (I'm also a vim user.)
-- Grant. . . . unix || die
------------------------------------------------------ Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
