Mailman 3 December 2015 - Mailman-Users

accept_these_nonmembers from address encoding problem
by Kapetanakis Giannis 11 Dec '15

11 Dec '15

Hi, I have a problem in accept_these_nonmembers option. The system is not recognizing sender's address cause it contains an iso-8859-7 encoded name inside From: header. As a result it does not much user's email which is included in accept_these_nonmembers. The From: header is like this: From: =?iso-8859-7?B?1C7FLskuIMrRx9TH0ywg0NHPxcTRz9MgxS4gyuHw5fTh7dzq5/I=?=<user(a)example.com> The system sees only a sender as ?.?.? instead of user(a)example.com Can I force the use of envelope address instead of from address? I've tried setting SENDER_HEADERS = (None,) SENDER_HEADERS = ('from',) without any luck. Any other option to try? System is Centos 5 with mailman-2.1.9 Thanks in advance, Giannis

2 2

What's the /var/spool/mailman/virgin for?
by Tony Bibbs 11 Dec '15

11 Dec '15

I've got an instance of mailman where the contents of /var/spool/mailman/virgin holds 1.4G of data. I'm just curious what this directory is for to determine what is putting the data there and what's responsible for sending it along. The same directory is empty for most other mailman instances I have access to. Thanks in advance, --Tony

2 1

Re: [Mailman-Users] View a user's subscription options
by Adrian Pepper 10 Dec '15

10 Dec '15

I see https://www.msapiro.net/scripts/user_options lists subscribed topics. Which is something of interest. But it must be run from the server. I ended up taking my own approach, building on little things I'd written before, to do an assessment of topic subscriptions from a web client machine. Does the following mimic some standard utility somewhere? # # tag-filter # From HTML input, output lines of only text or a single tags. # I.e. it will produce... (e.g. from output of curl -s -b cookiefile https://mailman/mailman/options/test-aharper-subset/aharper--at--dt.uwaterl… ) <html> <head> <link rel="SHORTCUT ICON" href="/icons/mm-icon.png"> <title> aharper at dt.uwaterloo.ca membership configuration for test-aharper-subset </title> </head> <BODY BGCOLOR="#ffffff"> <TABLE WIDTH="100%" BORDER="0" CELLSPACING="0" CELLPADDING="5"> <TR> <TD WIDTH="100%" BGCOLOR="#99CCFF"> test-aharper-subset mailing list membership configuration for aharper at dt.uwaterloo.ca [...] <tr> <td colspan="2"> [...] That can simplify rudimentary parsing. After tag-filter, I can use my "form-filter", which from output such as the above can produce... aharper(a)dt.uwaterloo.ca.disablemail="0"(CHECKED) aharper(a)dt.uwaterloo.ca.disablemail="1"(notchecked) aharper(a)dt.uwaterloo.ca.deliver-globally="1"(notchecked) aharper(a)dt.uwaterloo.ca.digest="0"(CHECKED) aharper(a)dt.uwaterloo.ca.digest="1"(notchecked) aharper(a)dt.uwaterloo.ca.mime="0"(notchecked) aharper(a)dt.uwaterloo.ca.mime="1"(CHECKED) aharper(a)dt.uwaterloo.ca.mime-globally="1"(notchecked) aharper(a)dt.uwaterloo.ca.dontreceive="1"(notchecked) aharper(a)dt.uwaterloo.ca.dontreceive="0"(CHECKED) aharper(a)dt.uwaterloo.ca.ackposts="0"(CHECKED) aharper(a)dt.uwaterloo.ca.ackposts="1"(notchecked) aharper(a)dt.uwaterloo.ca.remind="1"(notchecked) aharper(a)dt.uwaterloo.ca.remind="0"(CHECKED) aharper(a)dt.uwaterloo.ca.remind-globally="1"(notchecked) aharper(a)dt.uwaterloo.ca.conceal="0"(notchecked) aharper(a)dt.uwaterloo.ca.conceal="1"(CHECKED) aharper(a)dt.uwaterloo.ca.usertopic="Newsletter%2C"(notchecked) aharper(a)dt.uwaterloo.ca.usertopic="Test+Topic+2%2C"(notchecked) aharper(a)dt.uwaterloo.ca.usertopic="Any+Topic%2C"(notchecked) aharper(a)dt.uwaterloo.ca.usertopic="This+Topic+Should+Match+Nothing%2C"(notchecked) aharper(a)dt.uwaterloo.ca.usertopic="This+Topic+Should+Match+Everything%2C"(notchecked) aharper(a)dt.uwaterloo.ca.usertopic="Farmers+Institute+Newsletters+1%2C"(notchecked) aharper(a)dt.uwaterloo.ca.usertopic="Farmers+Institute+Newsletters+2%2C"(notchecked) aharper(a)dt.uwaterloo.ca.usertopic="Farmers+Institute+Newsletters+3%2C"(notchecked) aharper(a)dt.uwaterloo.ca.usertopic="Farmers+Institute+Newsletters+4%2C"(notchecked) aharper(a)dt.uwaterloo.ca.usertopic="Farmers+Institute+Newsletters+5%2C"(notchecked) aharper(a)dt.uwaterloo.ca.usertopic="Farmers+Institute+Newsletters+6%2C"(notchecked) aharper(a)dt.uwaterloo.ca.usertopic="NothingPythonOrg%2C"(notchecked) aharper(a)dt.uwaterloo.ca.usertopic="NothingMine%2C"(notchecked) aharper(a)dt.uwaterloo.ca.rcvtopic="0"(CHECKED) aharper(a)dt.uwaterloo.ca.rcvtopic="1"(notchecked) aharper(a)dt.uwaterloo.ca.nodupes="0"(CHECKED) aharper(a)dt.uwaterloo.ca.nodupes="1"(notchecked) aharper(a)dt.uwaterloo.ca.nodupes-globally="1"(notchecked) aharper(a)dt.uwaterloo.ca.options-submit="Submit My Changes" (Both tag-filter and form-filter may make simplifying assumptions based on what has and has never been seen as mailman HTML, e.g. on what to use as "form name"). After turning a simple pipeline like that into "mailman-get-member-options" and writing something to do: get-member-list $listname | \ xargs -n 1 mailman-get-member-options $listname I added that to what I run in my standard list dumps. Allowing me to assess... (relevant output is distributed into */members.optioned) cs-xh-admin% grep topic= */*optioned | sed 's/^[^:]*:.*[.]//' | sort | uniq -c | sort -nr 1063 rcvtopic="1"(notchecked) 1063 rcvtopic="0"(CHECKED) 104 usertopic="Topic+Which+Gets+No+Posts"(notchecked) 102 usertopic="Farmers+Institute+Newsletters"(notchecked) 4 usertopic="This+Topic+Should+Match+Nothing%2C"(notchecked) 4 usertopic="This+Topic+Should+Match+Everything%2C"(notchecked) 4 usertopic="Test+Topic+2%2C"(notchecked) 4 usertopic="SCS+Newsletter%2C"(notchecked) 4 usertopic="NothingPythonOrg%2C"(notchecked) 4 usertopic="NothingMine%2C"(notchecked) 4 usertopic="Farmers+Institute+Newsletters+6%2C"(notchecked) 4 usertopic="Farmers+Institute+Newsletters+5%2C"(notchecked) 4 usertopic="Farmers+Institute+Newsletters+4%2C"(notchecked) 4 usertopic="Farmers+Institute+Newsletters+3%2C"(notchecked) 4 usertopic="Farmers+Institute+Newsletters+2%2C"(notchecked) 4 usertopic="Farmers+Institute+Newsletters+1%2C"(notchecked) 4 usertopic="Any+Topic%2C"(notchecked) 2 usertopic="Farmers+Institute+Newsletters"(CHECKED) 1 rcvtopic="1"(CHECKED) 1 rcvtopic="0"(notchecked) cs-xh-admin% (Not a lot of interest is selecting based on topic (yet)). (The only use so far is my own testing). Adrian. On 12/03/2015 1:57 PM -0800 Mark Sapiro wrote: > > On 12/03/2015 01:09 PM, Adrian Pepper wrote: > > > > I wrote something (really ugly[*], incrementally developed over a period [...] > > > You might be interested in looking at > <https://www.msapiro.net/scripts/mailman-subscribers.py> which is > another web admin membership screenscraper which when run with the --csv > option produces output like > > > > "Full name","email address","mod","hide","nomail","ack","not metoo","nodupes","digest","plain" > > "Mark Sapiro","mark(a)msapiro.net","off","off","off","off","off","on","off","off" > > "Mark","another@address","off","off","[A]","off","off","on","off","off" > > "Mark","yet@another","off","off","[A]","off","on","on","off","off" > > > It uses Python's cookielib to deal with cookies and only requires the > hostname, listname and admin password for input. > > -- > Mark Sapiro >

1 0

feature request
by Steven Jones 09 Dec '15

09 Dec '15

"Should administrator get notices of subscribes and unsubscribes? " Would it be possible to split these as our list admins would like to see unsubscribes but not subscribes. <http://lists.vuw.ac.nz/mailman/admin/all_active_students/?VARHELP=general/a…> <http://lists.vuw.ac.nz/mailman/admin/all_active_students/?VARHELP=general/a…> regards Steven

4 5

List posts sent to AOL list subscribers bounce as undeliverable (v. 2.1.20)
by Woody Mon 05 Dec '15

05 Dec '15

Hello, I'm assisting a small non-profit organization with their informational news listserv which is running on Mailman version 2.1.20. The issue is that list posts sent to AOL subscriber addresses are now bouncing as undeliverable with the bounce code: "521 5.2.1 : AOL will not accept delivery of this message." This issue just began several days ago and 200+ subscribers with AOL email addresses are now identified as bouncing in Mailman admin. I understand last year AOL (and Yahoo) made changes to their email systems which might contribute to this issue. However it didn't seem to impact our list subscribers with AOL email addresses until just now. The bounce email message for each subscriber appears as: ---- A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed: EmailAccountHere(a)aol.com host mailin-03.mx.aol.com [64.12.91.196] SMTP error from remote mail server after end of data: 521 5.2.1 : AOL will not accept delivery of this message. ---- Unfortunately the list server runs on a host machine maintained by another non-profit, which in turn contacts with a small local hosting provider. And we don't have access to changing any list server configuration parameters, beyond what is available in the list owner admin. And unfortunately the hosting provider will not make any changes to the server for specific lists. We are just grateful the free listserv service and that they keep the version of Mailman up-to-date. And we are unable to setup a white list or feedback loop (FBL) with AOL as we don't have access to the postmaster or abuse email accounts for the list server domain. We have sent an email to http://postmaster.info.aol.com/SupportRequest.php to request unblocking out list email address and/or the list server IP (assuming one or the other is actually "blocked", we have no idea at this point), but have yet to receive a response from AOL. The error codes page at https://postmaster.info.aol.com/error-codes says this about the bounce error noted above: AOL will not accept delivery of this message This is a permanent bounce due to: * RFC2822 From domain does not match the rDNS of sending server. * RFC 2822 FROM address does not have an A record and is not a valid domain. * IP has a poor reputation and mail is sent to multiple recipients. * There are multiple From address in the mail headers and the IP reputation is poor. Before I dive into the details above and the info within the document at https://postmaster.info.aol.com/tech-requirements, I'm hoping to hear some potential simple solutions that may be applied to our particular solution. I can post the content of the list email a headers, but I wish to avoid posting the info in a public forum, Thank you for any advice.

6 5

Re: [Mailman-Users] List posts sent to AOL list subscribers bounce as undeliverable (v. 2.1.20)
by Woody Mon 04 Dec '15

04 Dec '15

The Mailman version is in both the subject line and the OP ;-) I'll investigate those DEMARC settings. Thanks.

1 0

Re: [Mailman-Users] List posts sent to AOL list subscribers bounce as undeliverable (v. 2.1.20)
by Woody Mon 04 Dec '15

04 Dec '15

RE: "Error: The form lifetime has expired. (request forgery check)" Never mind on that. Just let the admin form idle too long. So just changed to 'Munge' and unchecked the 'No Mail' box for several AOL subscribers which were bouncing. Will see if this has any impact.

1 0

Re: [Mailman-Users] List posts sent to AOL list subscribers bounce as undeliverable (v. 2.1.20)
by Woody Mon 04 Dec '15

04 Dec '15

FYI, I'm just using a Yahoo email account (via web interface) to post to the Mailman-users list. I don't use this account for much anything else. All posts to the list in question are moderated and almost all are sent from a Mozilla Thunderbird email client. And almost all subscribers (including AOL subscribers) are set for digest mode. In the list mail the from line always shows the listname(a)subdomain.domain1.org (not an individual email address or freemail domain) How do I find these DMARC workarounds which you speak? -------------------------------------------- On Fri, 12/4/15, John wrote: I see that you have a yahoo.com address. If there's a yahoo.com address on the From: line of the list mail, AOL and Yahoo's well documented abuse of DMARC will cause the failure you're seeing. If you're running a recent version of Mailman, there are some DMARC workarounds you can use. Other than that, I'd find a different address to mail from, not at Yahoo, not at AOL, and preferably not at Gmail.

2 1

Re: [Mailman-Users] List posts sent to AOL list subscribers bounce as undeliverable (v. 2.1.20)
by Woody Mon 04 Dec '15

04 Dec '15

Somehow a sentence above was cut off, Should be: I've checked and every list subscriber has the 'not metoo' and 'dupe' boxes checked.

1 0

Re: [Mailman-Users] List posts sent to AOL list subscribers bounce as undeliverable (v. 2.1.20)
by Woody Mon 04 Dec '15

04 Dec '15

I just attempted to change "from_is_list" from "No" to "Munge From" but observed the following error in Mailman admin "Error: The form lifetime has expired. (request forgery check)" Reading VARHELP=general/from_is_list it appears that changing to "Munge From" or "Wrap Message" would not provide any benefit when sending list digests..

1 0