Re: [Mailman-Users] Making a Case for Upgrading MailMan from 2.1.17

On 6/22/16 11:04 PM, Dave Nathanson wrote: > I'd like some help in making a case to convince my hosting company to upgrade > from Mailman 2.1.17. See the NEWS file at for all the features and bug fixes since 2.1.17. > M

Re: [Mailman-Users] NotAMemberError on Subscribe

Please disregard, this looks to have been an error on some customization we did not related to source files. Sorry. Christopher Puchalski From: Christopher A Puchalski To: mailman-users@python.org Date: 06/23/2016 11:44 AM Subject:[Mailman-Users] NotAMemberError on Subscribe

[Mailman-Users] NotAMemberError on Subscribe

I see several mentions of the NotAMemberError happening on unsubscribe but I am getting it when adding a member to a list. In my case we had a list of people that just one person was an issue. As it turned out that particular person's email address was a misspelled version of someone that is alre

Re: [Mailman-Users] Making a Case for Upgrading MailMan from 2.1.17

Hi, I was too hasty in sending out the prior message; actually there is a feature in 2.1.18 which I believe will help you with the issue you are having. Prior to 2.1.18, the DMARC feature was activated on a per list basis, and was set for each member regardless of whether the sender's email pro

Re: [Mailman-Users] Making a Case for Upgrading MailMan from 2.1.17

Dave Nathanson [dave.li...@nathanson.org] wrote: >I'd like some help in making a case to convince my hosting company to upgrade >from Mailman 2.1.17. >I run several email lists for clubs, these are discussion lists that get up to >20 messages per day, and include up to 150 members. Replies are