Mailman 3 December 2015 - Mailman-Users

Re: [Mailman-Users] Moderated approval via email
by Adrian Pepper Dec. 22, 2015

Dec. 22, 2015

I struggled with this problem until I unearthed this gem from the archive. In addition we were using aliases as moderators, so I thought that was the key problem, but subsequent testing suggests there is no such restriction. Is that correct? So it is alright to use an alias as list administrator or moderator, but moderator recipients must simply know the "trick" of replying to the contained message, not the overall message. I usually use an "heirloom-mailx"-like MUA and I assumed it was not smart enough to generate correct headers. But now I'm reasonably sure I could create a working response to the sub-message in a number of ways. I have a means to save a message into a mailbox where I can view it with Thunderbird on my workstation. But I don't really use Thunderbird much, mostly just to look at messages heavy with graphics and other noise. Took me a while to work out that you need to "Open all attachments" (somewhat hidden in a non-obvious menu, and there didn't seem to be a selective option) which would give you a window you could reply to. And voila! I finally managed to get that pending posting to disappear! And after I removed my email address from both owner and moderator boxes, I still seemed to be able to dicard another pending posting. I struggled so long with this I thought I'd post my dumpster diving and added observations in case it helped anyone else. I didn't find anything like the following in a FAQ. Note also, that this moderation message is a multipart/mixed message and the part that says "If you reply to this message, keeping the Subject: header intact ..." is it's own message/rfc822 part and it's that message part you must reply to with the Approved: <password> line, not the "outer" message. Perhaps mention of this should be added. My apologies if it's already there and my web and keyword searches overlooked it. Now I know what to look for, I find more recent coverage on the list. https://www.mail-archive.com/mailman-users@python.org/msg64564.html (May 2014) Adrian. Mark Sapiro msapiro at value.net wrote Thu Feb 10 01:58:46 CET 2005 > > Previous message: [Mailman-Users] Moderated approval via email > Next message: [Mailman-Users] Auto Subscriptions to Mailman list > Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] > > Pantejo, Barbara FTL wrote: > > > >As the list admin/moderator, I received an email to approve a posting to a > >particular mailing list, but the instructions on approving via a reply email > >is confusing: > > > >"If you reply to this message and include an Approved: header with the list > >password in it, the message will be approved for posting to the list. The > >Approved: header can also appear in the first line of the body of the > >reply." > > > >What does "header" mean and where on a reply email does it exist? Does > >"header" mean the Subject line? > > > >Does this mean one of the following?: > >1) Clear out the Subject line of the email and place "Approved:{list > >password}" > > No. > > >2) Reply with the Subject line intact and place "Approved:{list password}" > >as the first line of the reply message. > > Yes > > >3) Something else... > > If your MUA allows it, you can actually add the Approved: <password> > line in the headers of the reply as a separate header, not in the > Subject:. > > >I tried option 1 and 2 and it did not work. Should there be a space between > >the colon and {list password}? > > > 2) should work. A space is conventional, but not required. The password > must be the list admin password or the list moderator password. The > site password is explicitly not accepted to discourage sending it in > plain text e-mail. > > Note also, that this moderation message is a multipart/mixed message > and the part that says "If you reply to this message, keeping the > Subject: header intact ..." is it's own message/rfc822 part and it's > that message part you must reply to with the Approved: <password> > line, not the "outer" message. > > I.e. the reply must be to the <listname>-request address, not the > <listname>-owner address, and the subject must be the "confirm > long-string-of-hex-digits" subject, not the "<listname> post from > <poster> requires approval" subject. > > -- > Mark Sapiro <msapiro at value.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan

2 1

Using mailman output in web page documentation
by Adrian Pepper Dec. 19, 2015

Dec. 19, 2015

I found it convenient to use mechanical dumps of mailman pages in attempting to create some moderator documentation, intended primarily for local use at the university where I work. Such dumped pages do not contain any formal copyright/left statement beyond alt="GNU's NOT Unix" 1. Is there a suitable comment one could/should (should not?) add to attribute the source of such excerpts to GNU (GFDL?). I use HTML dumps rather than screenshots so that I can modify them to create a mockup of a page which refers to a particular mailing list by name, and actually links variously to the real mailman server links, or further mockups as seems appropriate (to me). In addition, form items such as radio buttons will tend to appear in the manner the particular browser will display them on the real page. Adrian Pepper P.S. That's enough to start. Further analysis and tangential questions "2. and 3." exist already, perhaps in response to followups.

3 2

Encoding problem with 2.15 to 2.18 upgrade with Finnish
by Eva Isaksson Dec. 14, 2015

Dec. 14, 2015

Hi, I have a charset encoding problem that I'm unable to solve. I've been reading FAQs and list archives with little success. Our lists are in Finnish. The setup: our mailman installation uses its own translation file that is different from the Finnish translation that comes with the release. Because of that, mailman is on hold, and gets upgraded manually so that we can msfmt our own mailman.po. We have been running 2.15, on Debian, but because of the DMARC situation it's time to upgrade to 2.18.. Our upgrades have been rather routine so far, but this time we ran into problems. Suddenly, the character encoding was producing quite unreadable interfaces. Believing that the translation file was now supposed to be in utf-8 instead of iso-8859-1 I tried to re-encode all relevant files and change the mm_cfg.py values accordingly. This did not help at all. I've tried to check whether there have been any changes to mailman that could explain this, but no luck. - Eva Isaksson

2 1

Many users unsubscribed at once (not by me)
by Hal Dec. 14, 2015

Dec. 14, 2015

Today I received 18 unsubscribe notification mesages, each one telling me that "name(a)addr.ess has been removed from my_list_name". They all appear to have been sent simultaneously, and since I (the list adminisistrator) haven't performed the unsubscribe request myself I suspect either some sort of automated request by the Mailman software or someone hacking into the system. I've had this happen to me once before, several months ago. The only thing I can think of apart from someone hacking into the list-server is that Mailman automatically removes members who have non-working addresses after a certain amount of list postings. Could this be it, or am I right to be worried and should contact the server owner to ask if an intrusion has shown up on the logs? Logging into the Mailman admin page for my list tells me I'm using Mailman 2.1.12. Hal

7 18

accept_these_nonmembers from address encoding problem
by Kapetanakis Giannis Dec. 11, 2015

Dec. 11, 2015

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 Dec. 11, 2015

Dec. 11, 2015

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 Dec. 10, 2015

Dec. 10, 2015

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 Dec. 9, 2015

Dec. 9, 2015

"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 Dec. 5, 2015

Dec. 5, 2015

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 Dec. 4, 2015

Dec. 4, 2015

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

1 0