Mailman is useful. Mailman works. Mailman is ubiquitous. I am subscribed to over 50 mailing-lists managed by Mailman.
But Mailmand is software, and therefore hateful.
My particular Mailman hate is the nodupes
parameter.
Avoid duplicate copies of messages?
When you are listed explicitly in the To: or Cc: headers of a list message, you can opt to not receive another copy from the mailing list. Select Yes to avoid receiving copies from the mailing list; select No to receive copies.
If the list has member personalized messages enabled, and you elect to receive copies, every copy will have a X-Mailman-Copy: yes header added to it.
I like duplicate email. Moreover, I like the List-Id
header that makes
emails sent through a list special (at least in the sense that they
can be filtered automatically by more tools, and I can just delete
the stuff that piles up in my Inbox). And by the way, how could Mailman
be really sure that I got that other copy? Just because the headers say
so? Bah.
Oh, and I also hate the fact that Set globally never worked for me with this option.
So, because I'm lazy, and I don't want to go clikety-click to first, get a reminder of the random password that was assigned to me years ago, and two, login and change that annoying option, and because I don't want to do that fifty times, over and over again...
I wrote and put on CPAN WWW::Mailman, designed to automate that kind of tedious task out of my life (and hopefully yours). Examples included, I know you're lazy too.
PS: I've been told there is a command-line interface to Mailman, but it is reserved to people managing Mailman on the server.
There goes my idea for a CPAN module.
Guess I'll just have to use yours and see what I can add to fit my needs.
Good on you for doing this.
gizmo