Re: [Mailman-Users] compare lists setup
I think that config_list is what you want: config_list -o list1config list1 config_list -o list2config list2 diff list1config list2config --- [root@lists ~]# config_list Configure a list from a text file description. Usage: config_list [options] listname Options: --inputfile filename -i filename Configure the list by assigning each module-global variable in the file to an attribute on the list object, then saving the list. The named file is loaded with execfile() and must be legal Python code. Any variable that isn't already an attribute of the list object is ignored (a warning message is printed). See also the -c option. A special variable named `mlist' is put into the globals during the execfile, which is bound to the actual MailList object. This lets you do all manner of bizarre thing to the list object, but BEWARE! Using this can severely (and possibly irreparably) damage your mailing list! --outputfile filename -o filename Instead of configuring the list, print out a list's configuration variables in a format suitable for input using this script. In this way, you can easily capture the configuration settings for a particular list and imprint those settings on another list. filename is the file to output the settings to. If filename is `-', standard out is used. --checkonly -c With this option, the modified list is not actually changed. Only useful with -i. --verbose -v Print the name of each attribute as it is being changed. Only useful with -i. --help -h Print this help message and exit. The options -o and -i are mutually exclusive. One of -i or -o is required -p -- Pat Hirayama Systems Engineer / 206.667.4856 / phira...@fredhutch.org / Fred Hutch / Cures Start Here CIT | Advancing IT and Data Services to Accelerate the Elimination of Disease > -Original Message- > From: Mailman-Users [mailto:mailman-users- > bounces+phirayam=fredhutch@python.org] On Behalf Of jdd > Sent: Monday, March 20, 2017 10:53 AM > To: mailman-users@python.org > Subject: [Mailman-Users] compare lists setup > > Hello :-) > > Gmail recipient anti spam filters get me mad. > > After some work, I have one list that reaches the gmail recipients, good! > > but I have an other list that get bounces. same server, same domain. > > I guess I forgot some setup on the other list > > comparing on the web interface is very difficult. > > is there a way to read these setups directly on the server in a config > file where I could make a diff? > > thanks > jdd > -- > Mailman-Users mailing list Mailman-Users@python.org > https://urldefense.proofpoint.com/v2/url?u=https- > 3A__mail.python.org_mailman_listinfo_mailman- > 2Dusers=DwICAg=eRAMFD45gAfqt84VtBcfhQ=lnQBMkNb1mBsioi6aP6ts4Sw0Ua5nVh > 4esYOAh4qTKU=WxlwhOInW3PJh3_MqjRt1pvf7mVa5W2x1Kaar73VjUw=GW0lapInWnCgO_ > n5bfTAP7p0W4m3L0MyL_OoSuJqCas= > Mailman FAQ: https://urldefense.proofpoint.com/v2/url?u=http- > 3A__wiki.list.org_x_AgA3=DwICAg=eRAMFD45gAfqt84VtBcfhQ=lnQBMkNb1mBsio > i6aP6ts4Sw0Ua5nVh4esYOAh4qTKU=WxlwhOInW3PJh3_MqjRt1pvf7mVa5W2x1Kaar73VjUw > =Uj6rRj8h-rxKR-PMyg-kA91_Np18W-NfaBJ0BSte4rs= > Security Policy: https://urldefense.proofpoint.com/v2/url?u=http- > 3A__wiki.list.org_x_QIA9=DwICAg=eRAMFD45gAfqt84VtBcfhQ=lnQBMkNb1mBsio > i6aP6ts4Sw0Ua5nVh4esYOAh4qTKU=WxlwhOInW3PJh3_MqjRt1pvf7mVa5W2x1Kaar73VjUw > =xI7O1DkQtfX722dVADWdV3UUVufYUDWt9DQpvWfn5ow= > Searchable Archives: https://urldefense.proofpoint.com/v2/url?u=http- > 3A__www.mail-2Darchive.com_mailman-2Dusers- > 2540python.org_=DwICAg=eRAMFD45gAfqt84VtBcfhQ=lnQBMkNb1mBsioi6aP6ts4S > w0Ua5nVh4esYOAh4qTKU=WxlwhOInW3PJh3_MqjRt1pvf7mVa5W2x1Kaar73VjUw=PfOEBS > 2LfKZdRmJjbuWl0pjkVJkn_sGaTEIYsFwasRE= > Unsubscribe: https://urldefense.proofpoint.com/v2/url?u=https- > 3A__mail.python.org_mailman_options_mailman-2Dusers_phirayam- > 2540fredhutch.org=DwICAg=eRAMFD45gAfqt84VtBcfhQ=lnQBMkNb1mBsioi6aP6ts > 4Sw0Ua5nVh4esYOAh4qTKU=WxlwhOInW3PJh3_MqjRt1pvf7mVa5W2x1Kaar73VjUw=he7b > iG1QSVFTbfjX2BOlwYPvRF0HoRKpntjpux1bshc= -- 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] Mailman and Mimecast
Greetings, I am having issues with some addresses on a couple of the few thousand lists that I am hosting in mailman. The addresses in question are using Mimecast for their email protection. So, I'm asking all of you for your opinion/advice. Problem 1: One list gets their email rejected with a 550 Rejected by header based Anti-Spoofing policy: ... https://community.mimecast.com/docs/DOC-1369#550 If I am reading the referenced (https://community.mimecast.com/docs/DOC-1419-anti-spoofing-policies) page correctly, the problem is that the sender of the list is at domain A, the recipients of the lists are at domain A, but the listserv itself is in domain B, and from Mimecast's POV, there shouldn't be mail from A to A being relayed by B. And then it goes on to say that you should reconfigure your Mimecast to put in a bypass policy for this server. What the mail folks at domain A would prefer is that I (domain B) fix this. I'm thinking that I could fix this by using either anonymous_list or changing the setting of from_is_list. But, what isn't clear to me is if this is really the correct step to take (my initial inclination is that they should follow Mimecast's direction of putting in a bypass policy). Problem 2: Another list I have -- they actually accept the mail, and then send it back. So, I see status=sent in my postfix logs, but the members don't get it. Apparently, it is running into a problem because the HELO greeting from my mail gateways (MX) doesn't match the FQDN of the mailman server. So, the mailman server is smarthosted to my MX servers, which do some scanning of the message before sending it out. Apparently, what these Mimecast users want me to do is to rewrite the envelope so that instead of the mailman server's FQDN, I replace it with either the FQDN of the MX server, or just my domain. In the /etc/aliases file on my MX servers, I have the 'post' address listed, so mail sent to listname@domain gets routed to the mailman server. I haven't listed any of the other 9 mailman addresses (i.e. -admin, -bounces, -confirm, -join, -leave, -owner, -request, -subscribe, -unsubscribe). So, my thinking is that if I do the rewrite, so the message comes from listname-bounces@domain, instead of listname-bounces@lists.domain, I will need to add this and the other addresses on my MX server so that mail routing will work. Since I have 3000+ lists, that's like 27k more lines in /etc/aliases to add/manage. Again, I'm thinking that they should put in some exception in their Mimecast configuration. Am I just being obstinate here for no reason? Should I just assume the pain and change the behavior of my mailman server? Thoughts? Thanks! -p -- Pat Hirayama Systems Engineer / 206.667.4856 / phira...@fredhutch.org / Fred Hutch / Cures Start Here CIT | Advancing IT and Data Services to Accelerate the Elimination of Disease -- 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] Sending mails to all list administrators
Thanks, Mark! -p -Original Message- From: Mailman-Users [mailto:mailman-users-bounces+phirayam=fredhutch@python.org] On Behalf Of Mark Sapiro Sent: Thursday, July 28, 2016 9:45 AM To: mailman-users@python.org Subject: Re: [Mailman-Users] Sending mails to all list administrators On 07/28/2016 09:23 AM, Hirayama, Pat wrote: > I suppose you could generate a list of people to send by doing something like: > > /usr/lib/mailman/bin/list_admins --all | sed 's/.*Owners: //'|sed > 's/,/\r/g'|sed 's/ //g'|sort|uniq You can produce the same result with /usr/lib/mailman/bin/list_owners without the post processing. -- Mark Sapiro <m...@msapiro.net>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/phirayam%40fredhutch.org -- 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] Sending mails to all list administrators
I suppose you could generate a list of people to send by doing something like:
/usr/lib/mailman/bin/list_admins --all | sed 's/.*Owners: //'|sed
's/,/\r/g'|sed 's/ //g'|sort|uniq
And that use that to send your email. Maybe combine it with xargs to do
something like:
/usr/lib/mailman/bin/list_admins --all | sed 's/.*Owners: //'|sed
's/,/\r/g'|sed 's/ //g'|sort|uniq | xargs -I {} mail -s 'subject' {} <
message.txt
At least, I think that last might work. :)
-p
--
Pat Hirayama
Systems Engineer / 206.667.4856 / phira...@fredhutch.org / Fred Hutch / Cures
Start Here
CIT | Enterprise IT Services / Advancing IT and Data Services to Accelerate the
Elimination of Disease
-Original Message-
From: Mailman-Users
[mailto:mailman-users-bounces+phirayam=fredhutch@python.org] On Behalf Of
Martin Stein
Sent: Thursday, July 28, 2016 5:15 AM
To: mailman-users@python.org
Subject: [Mailman-Users] Sending mails to all list administrators
Hi,
I'm looking for an easy way, as site administrator, to send a message to
all list administrators. Is there any possibility to set up a
autogenerated list with all list administrators of the site or another
smooth solution?
Regards,
Martin
--
Martin Stein
Attac Deutschland Webteam
Attac Deutschland
Münchener Str. 48
60329 Frankfurt am Main
Mail: martin.st...@attac.de
--
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/phirayam%40fredhutch.org
--
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] Message discarded without reason logged in vette
All, User was reusing an old message that was previously sent to the list, and then using Outlook's 'Send Again' feature, which caused the message to contain headers that mailman placed into the original message. When the IncomingRunner process saw the message come through 'again', it discarded the message. Thanks to Mark Sapiro (mark_at_msapiro.net) for catching that those headers were there when they shouldn't have been! -p -Original Message- From: Mark Sapiro [mailto:m...@msapiro.net] Sent: Friday, July 8, 2016 11:33 AM To: Hirayama, Pat <phira...@fredhutch.org>; mailman-users@python.org Subject: Re: [Mailman-Users] Message discarded without reason logged in vette On 7/8/16 10:37 AM, Hirayama, Pat wrote: > Hi Mark, > > 3892 is the IncomingRunner process. > > And I'm still running 2.1.9, since that is what was provided with CentOS 5.x. > I will have to upgrade that box soon to CentOS 7.x -- which comes with > 2.1.15. Do you have an example message? If not, have her Cc: you on the next post. I might be able to see something in the headers of the message. Also, you could patch IncomingRunner as indicated at <http://bazaar.launchpad.net/~mailman-coders/mailman/2.1/revision/1502/Mailman/Queue/IncomingRunner.py> (and restart Mailman) to get the handler name. -- Mark Sapiro <m...@msapiro.net>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] Message discarded without reason logged in vette
Hi Mark, 3892 is the IncomingRunner process. And I'm still running 2.1.9, since that is what was provided with CentOS 5.x. I will have to upgrade that box soon to CentOS 7.x -- which comes with 2.1.15. -p -Original Message- From: Mark Sapiro [mailto:m...@msapiro.net] Sent: Friday, July 8, 2016 9:55 AM To: Hirayama, Pat <phira...@fredhutch.org>; mailman-users@python.org Subject: Re: [Mailman-Users] Message discarded without reason logged in vette On 7/8/16 9:33 AM, Hirayama, Pat wrote: > > This is the message (from just a few minutes ago, in fact): > > Jul 08 09:17:51 2016 (3892) Message discarded, msgid: <...> > > I am stumped. The sender is a non-moderated member. She is in fact, listed > as a moderator. filter_content is set to no. ARCHIVE_HTML_SANITIZER does > not appear to be set. dmarc_moderation_action is set to ACCEPT. > header_filter_rules = []. The fact that she is listed as a moderator is irrelevant to this. Just to be sure, do 'ps -fww 3892' and verify that the process is IncomingRunner. Also note that starting with Mailman 2.1.19, the log message includes the name of the handler that raised the discard. See <https://bugs.launchpad.net/mailman/+bug/558096> and <http://bazaar.launchpad.net/~mailman-coders/mailman/2.1/revision/1502>. -- Mark Sapiro <m...@msapiro.net>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] Message discarded without reason logged in vette
Hi Mark, This is the message (from just a few minutes ago, in fact): Jul 08 09:17:51 2016 (3892) Message discarded, msgid: <...> I am stumped. The sender is a non-moderated member. She is in fact, listed as a moderator. filter_content is set to no. ARCHIVE_HTML_SANITIZER does not appear to be set. dmarc_moderation_action is set to ACCEPT. header_filter_rules = []. As near as I can tell, everywhere in the admin interface where one can select "Discard" is not checked. -p -Original Message- From: Mark Sapiro [mailto:m...@msapiro.net] Sent: Friday, July 8, 2016 9:27 AM To: Hirayama, Pat <phira...@fredhutch.org>; mailman-users@python.org Subject: Re: [Mailman-Users] Message discarded without reason logged in vette On 7/8/16 9:00 AM, Hirayama, Pat wrote: > > WRT Content filtering -- if filter_content is set to NO, then nothing else in > that section should apply, right? That is, even if there is stuff defined > for pass_mime_types and filter_filename_extensions? That's correct. Note that what I wrote below applies only to the exact log entry "Message discarded, msgid: <...>". It seems that's the one you've seen, but there can be other messages such as "No command, message discarded, msgid: <...>" which is logged for messages sent to the -request address with no command or to -confirm with incorrect format. > > -Original Message- ... > If the message in the vette log is "Message discarded, msgid: <...>", > that message is only produced in standard Mailman by IncomingRunner when > a handler raises DiscardMessage. Again in standard Mailman, the only > Handlers that do that are: > > MimeDel > - content filtering removes the entire message and filter_action is > other than Reject > > Moderate > - a post is from a moderated member with member_moderation_action Discard > - a post is from a non-member in discard_these_nonmembers or with > generic_nonmember_action Discard > > Scrubber > - if the top level MIME type is text/html and ARCHIVE_HTML_SANITIZER = > 0 (not the default, and this only applies if scrub_nondigest is Yes) > > SpamDetect > - when a message matches KNOWN_SPAMMERS > - A post is From: a domain with DMARC p=reject (or maybe quarantine) > and dmarc_moderation_action is Discard > - a message matches header_filter_rules with Discard action or with > Reject action and the message is to -owner -- Mark Sapiro <m...@msapiro.net>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
[Mailman-Users] Message discarded without reason logged in vette
So, I found a 10 year old post where Mark Sapiro described some of the reasons why "Message discarded" with only a message id and no reason happens: Examples are when nothing is left after content filtering, a post from a moderated user when action is discard, a post from a non-member in discard_these_nonmembers, a post from a non-member with generic action discard, some cases of a text/html post when ARCHIVE_HTML_SANITIZER = 0 and a post matching a header_filter_rule with discard action. I was wondering if there was a more complete list someplace? Mostly because I had this happen to one of my users 3 weeks ago, and I think that I've managed to rule out everything that Mark wrote back then. Thanks, -p -- Pat Hirayama Systems Engineer / 206.667.4856 / phira...@fredhutch.org / Fred Hutch / Cures Start Here CIT | Enterprise IT Services / Advancing IT and Data Services to Accelerate the Elimination of Disease -- 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] How do I prevent subscribers from sending to -bounces address instead of list address?
Ah! include_sender_header does sound like it would be helpful in this case. (And I'm the site admin, actually). Have to decide if it is worth it to either (a) switch from supplied RPMs to source code; or (b) rebuild this server with CentOS 7 instead of CentOS 5 it is currently running. Thanks! > -Original Message- > On 03/04/2016 07:06 PM, Mark Sapiro wrote: > > > > You can't control what MUA's your user's use. Attempting to educate > > them, at least in most user populations, is futile. > > > In my zealousness to rant about the clueless, I forgot to mention that > starting with Mailman 2.1.14 There is an include_sender_header setting > (if not disabled by the site admin) which can be set to no to prevent > Mailman from adding a Sender: header with the list-bounces address. This > *shouldn't* affect normal bounces as they *should* be sent to the > envelope sender, not to the Sender: header. > -- Pat Hirayama Systems Engineer / 206.667.4856 / phira...@fredhutch.org / Fred Hutch / Cures Start Here CIT | Enterprise IT Services / Advancing IT and Data Services to Accelerate the Elimination of Disease -- 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] How do I prevent subscribers from sending to -bounces address instead of list address?
Mark, > It depends on how much work you want to do. If YOU have a decent MUA, > you can open the original attached "unrecognized bounce" message and > resend it to the list. It might be held for implicit destination, but > you can avoid that by adding the -bounces address to the list's > acceptable_aliases, at least in the non-verp case, but it's probably > better to edit the original To: before resending so other innocent > reply-all messages don't go to the bounces address. I.e., there are ways > to resend that message To: the list and From: the original sender; how > much work they are depends on what tools you have at your disposal. > > But, this is the wrong answer because it puts all the effort on the list > owner. The right answer is to compose a nice helpful message explaining > the situation and what the correct list posting address is and keep that > handy on your desktop so when you get one of these you can just forward > it back to the original sender together with your message and put the > burden back on them. Maybe some will even learn. Others will just blame > your list because obviously their Microsoft software can't be doing > anything wrong. > Pretty much what I expected. Ah well. Thanks! -p -- Pat Hirayama Systems Engineer / 206.667.4856 / phira...@fredhutch.org / Fred Hutch / Cures Start Here CIT | Enterprise IT Services / Advancing IT and Data Services to Accelerate the Elimination of Disease -- 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] How do I prevent subscribers from sending to -bounces address instead of list address?
Greetings, Apparently, many of my subscribers must be using Outlook, so they see the mailto:listname-bounces@domain hypertext and are copying that to send new messages to the list. Aside from repeatedly telling the users that they need to send to listname@domain, have any of you found a better solution? Thanks, -p -- Pat Hirayama Systems Engineer / 206.667.4856 / phira...@fredhutch.org / Fred Hutch / Cures Start Here CIT | Enterprise IT Services / Advancing IT and Data Services to Accelerate the Elimination of Disease -- 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] How do I prevent subscribers from sending to -bounces address instead of list address?
Sorry, I should add this salient point. Since the subscriber has sent to -bounces, it is going to the list admins, but there is no indication to the subscriber that this has happened. As far as they know, their message has been posted to the list. This seems bad, but it doesn't seem like a good idea to have the list admins forward the message, since that will change the sender. Thanks, -p -Original Message- From: Hirayama, Pat Sent: Friday, March 04, 2016 10:30 AM To: 'mailman-users@python.org' Subject: How do I prevent subscribers from sending to -bounces address instead of list address? Greetings, Apparently, many of my subscribers must be using Outlook, so they see the mailto:listname-bounces@domain hypertext and are copying that to send new messages to the list. Aside from repeatedly telling the users that they need to send to listname@domain, have any of you found a better solution? Thanks, -p -- Pat Hirayama Systems Engineer / 206.667.4856 / phira...@fredhutch.org / Fred Hutch / Cures Start Here CIT | Enterprise IT Services / Advancing IT and Data Services to Accelerate the Elimination of Disease -- 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
