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

2016-06-23 Thread Mark Sapiro 
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.


> My primary issue with MM 2.1.17 is about list messages from members who don't 
> have their human names configured into their email clients, resulting in a 
> list message from an unknown. It is just from "via listname 
> " 
> Since I'm still stuck on 2.1.17. I don't know what I am missing in the newer 
> versions. I just know that it's been over 2 years since 2.1.17 which has an 
> annoying omission due the the whole DEMARC thing. 


You have set from_is_list to Munge From. As Andrew says, in 2.1.18 and
beyond, there is a more selective dmarc_moderation_action setting that
does this munging only for post From: a domain with DMARC policy
p=reject and optionally p=quarantine.  Also, at some point (see the NEWS
file for when) this munging was fixed to use the user's real_name list
setting if the display name was not in the email.


> What are the advantages of upgrading beyond 2.1.17? 
> How best to make a good case to convince them to upgrade their MailMan?
> What version should I ask for? 


You should look at the NEWS for all the things that are enhanced/fixed
since 2.1.17. You should ask for the latest possible version. Note that
the Mailman that manages this and over 300 other @python.org lists is at
the head of the 2.1 branch at
. The latest
'official release' is 2.1.22 and 2.1.23 is coming soon.

It is possible, even likely, that your hosting company has installed a
downstream packege (.rpm or .deb) for which there is no upgrade
available. In this case, upgrading may be tricky, but at least if it is
Debian/Ubuntu, see , and in any case,
we're here to help.

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
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

Re: [Mailman-Users] NotAMemberError on Subscribe

2016-06-23 Thread Christopher A Puchalski 

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
Sent by:"Mailman-Users" 





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 already
a member of other lists. For the sake of example we can call that person's
correct email is wwwr...@domain.com which takes fine and is already an
established user. When you try to add wwr...@domain.com the error comes up.
I have been unable to duplicate except that one exact example and another
slight misspelling. Thanks for any help that I can get in advance.


Christopher Puchalski
--
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/chris.puchalski%40raytheon.com

--
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

[Mailman-Users] NotAMemberError on Subscribe

2016-06-23 Thread Christopher A Puchalski 


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 already
a member of other lists. For the sake of example we can call that person's
correct email is wwwr...@domain.com which takes fine and is already an
established user. When you try to add wwr...@domain.com the error comes up.
I have been unable to duplicate except that one exact example and another
slight misspelling. Thanks for any help that I can get in advance.


Christopher Puchalski
--
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

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

2016-06-23 Thread Andrew Hodgson 
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 provider had the 
DMARC set up on the domain.  With 2.1.18, you can set it up so the headers only 
get munged if the DMARC action on the domain is quarrentine or reject.  It is 
worth noting however that depending on how your host get Mailman, this feature 
may already be available.  For example, some RedHat packages prior to 2.1.18 
already have this feature built into them.

Sorry about that.
Andrew.


From: Andrew Hodgson
Sent: 23 June 2016 12:51
To: Dave Nathanson; mailman-users@python.org
Subject: 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 directed back 
>to the list.

>My primary issue with MM 2.1.17 is about list messages from members who don't 
>have their human names configured into their email clients, resulting in a 
>list message from an unknown. It is just from "via listname 
>"
>Since I'm still stuck on 2.1.17. I don't know what I am missing in the newer 
>versions. I just know that it's been over 2 years since 2.1.17 which has an 
>annoying omission due the the whole DEMARC thing.

If you download the tar package for the latest version, 2.1.22, the NEWS file 
will give a changelog of what has changed between the versions.  I don't 
believe a newer version would help you with the issue you are experiencing, 
however, as that is due to the way that Mailman handles messages which come 
from senders who's email operator publishes DMARC records for their domain.

Andrew.
--
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

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

2016-06-23 Thread Andrew Hodgson 
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 directed back 
>to the list.

>My primary issue with MM 2.1.17 is about list messages from members who don't 
>have their human names configured into their email clients, resulting in a 
>list message from an unknown. It is just from "via listname 
>"
>Since I'm still stuck on 2.1.17. I don't know what I am missing in the newer 
>versions. I just know that it's been over 2 years since 2.1.17 which has an 
>annoying omission due the the whole DEMARC thing.

If you download the tar package for the latest version, 2.1.22, the NEWS file 
will give a changelog of what has changed between the versions.  I don't 
believe a newer version would help you with the issue you are experiencing, 
however, as that is due to the way that Mailman handles messages which come 
from senders who's email operator publishes DMARC records for their domain.

Andrew.
--
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