Mailman 3 December 2015 - Mailman-Users

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

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

Thank you for everyone's ideas and recommends. I've checked and every list subscriber has the As Mark suggested trying, I'll change "from_is_list" to "Munge From" to see if that has any effect. And if not will try "Wrap Message". Note that almost all list subscribers are set to receive Digests, so hoping this doesn't mess with the format of the digests any (the list is text only, no html or attachments).. As Mark related, I suspect the issue is DNS related, and AOL is just finally cracking down on mail sent from this particular list server. A free web based DNS checker reports the following for the listserver domain: 1. FAIL - SOA record check. "No nameservers provided an SOA record for the zone". 2. FAIL - MX records check. "No MX records exist within the zone. This is legal, but if you want to receive E-mail on this domain, you should have MX record(s)." 3. PTR record for the domain "Error: Invalid IP address" I'm not privy to the details but I suspect the list server runs within a virtual host environment. >From the header of a list digest email I received yesterday ----- Return-Path: Listname-bounces(a)lsubdomain.domain1.org X-RC-FROM: <Listname(a)lsubdomain.domain1.org> Received: from localhost ([127.0.0.1]:obfuscated-port# helo=hostname.domain2.org) by hostname.domain2.org with esmtp (Exim 4.85) (envelope-from <Listname(a)lsubdomain.domain1.org>) id obfuscated date & timestamp X-AntiAbuse: Primary Hostname - hostname.domain2.org X-AntiAbuse: Original Domain - domain3.org X-AntiAbuse: Sender Address Domain - subdomain.domain1.org From: Listname-request(a)subdomain.domain1.org Subject: Listname Digest, Vol ##, Issue ### To: Listname(a)subdomain.domain1.org Reply-To: Listname(a)subdomain.domain1.org ------- It appears the listserver domain (domain1) runs on the domain2.org host and which is responsible for sending mail for domain1. Whereas the 'abuse' domain (domain3) is the domain name of the parent organization which hosts domain2, which the domain1 listserver runs upon. I'm considering sending a direct email to all the list subscribers with AOL addresses, recommending they either contact AOL to request a whitelist solution or to send us an alternative (freemail) email address which we'll change their list subscription to. Besides the list provider repairing their DNS configuration, is the above a recommended solution? If I was a network administrator I likely could phrase all this in better terms. ;-)

3 2

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

03 Dec '15

On 12/01/2015 17:23:58 -0800, Mark Sapiro wrote: > On 12/01/2015 08:51 AM, Gretchen R Beck wrote: > > Is there a command line script that can be used to view an individual user's subscription options for a specific list? > > > I'm not aware of one, but it is fairly simple to do. I'm willing to add > it to the collection at <https://www.msapiro.net/scripts/>, but what do > you want in the way of output. Presumably the input would be something like > > get_user_options listname user(a)example.com > > but what kind of output are you looking for? What fields and in what format? > I wrote something (really ugly[*], incrementally developed over a period of weeks) that produced, based on the main "membership" page(s) that produced via web access, e.g. apepper(a)pytone.org smHxanudP "Adrian Pepper" apepper(a)pyttwo.org smHxAnuDP "Adrian Pepper again" empty(a)pytone.org smHxanudP "Empty Recipient List" mshapiro(a)pytone.org smHxanudP "Mark Shapiro" onafees(a)pytthree.org smHXanudP "Oscar Nafees" those letter options correspond to reading across on https://SERVER/mailman/admin/LISTNAME/members sort of like "ls gone a little crazy". s/S - subscribe/unsubscribe (not actually implemented, for "safety") (though I did once in a test version when it would be useful) m/M - moderation off/ON h/H - hidden off/ON x/X - nomail off/ON (reason lost) a/A - ack off/ON n/N - not metoo off/ON u/U - nodUpes off/ON (ahem!) d/D - digest off/ON p/P - plaintext off/ON (applies to digest only) Needs a cookie file for access. Vulnerable to formatting changes in the web page output, of course. I actually have something to take that output as input and "make it so". But with at least one bug. (Omitted option letters are turned off, not left unchanged). But my main goal was to monitor changes, especially "nomail", and the email address which was supposed to conform to a standard. Though the "make it so" script is actually used for doing remote (web) subscriptions, setting desired options and a standard name field. And much later I realized that that output includes only some of the options available to the user on the user options page. https://SERVER/mailman/options/LISTNAME I guess you're talking about running the command on the server? I don't know if you want to contemplate something like my "ls gone a little crazy", or not. Adrian. [*] Lots of analysis done in csh in the top-level csh script

2 1

utf-8 subjects; extended "." regexp really necessary?
by Adrian Pepper 03 Dec '15

03 Dec '15

(Mailman 2.1.12, some local mods, but not around topics...) I had a utf-8 subject I was having difficulty matching with a topic regexp. Eventually I concluded the subject still had newlines in it when it was matched against the regexp. (That is the continuation lines were not joined before matching). And "." would not match the newline character(s)). So, for test purposes... Farmers[_ ]Weekly[\s\S\n\r]*Ac seemed to match my particular test subject. While the following did not. Farmers[_ ]Weekly.*Ac Am I correct in my conclusion that .* won't match newline characters, but <space-chars><not-space-chars><linefeed><carriage-return> will ? (And also, that that is the character class I created). For production I might need to put [\s\S\n\r]* between every pair of characters after a reasonable point in the expression. Unless I can enumerate the possibilities more precisely. (Which will probably result in an even longer looking character class). Empirically I see ?=\n =?utf-8?q?_ after "Weekly" and before "Ac". (And it seems the matching is done on the incoming subject, not the one formatted for resending, which, with my tag, and the utf-8 of an incoming tag pushes the expression entirely onto the second line where I think the ".*" variant (or even [_ ]) would match. More generally, my question applies to any potentially long subject, but utf-8 subjects seem to get longer more easily. There is no header-equivalent line in the body (it's mime anyway). Adrian Pepper

3 2

View a user's subscription options
by Gretchen R Beck 03 Dec '15

03 Dec '15

Is there a command line script that can be used to view an individual user's subscription options for a specific list? Gretchen Beck Carnegie Mellon

3 4

strange interaction between mailman and google docs
by Ottoson Webmaster 01 Dec '15

01 Dec '15

I am seeing a strange problem and I am wondering if someone has any idea. I am using google docs to create a newsletter which I then send to a mailman mailing list. Within google docs I use the feature "Email as attachment" to send to the list. The mailman list has about 1000 addresses some of which are gmail addresses and some are not (yahoo, hotmail, etc.) Well, the email from google docs is *only* received by the gmail addresses in the mailing list but *not* by any of the other addresses. If I send the email with the attachment from google docs to a *single* non-google email, then I see no problems. If I send the email with the attachment from gmail (outside of google docs) to the entire list I see no problems. The problem is only *from google docs to non-google email in mailman list* Ideas? Thank you! Antonella

3 2

List messages showing as attachments
by Lindsay Graham 01 Dec '15

01 Dec '15

I hope this is the right place to ask this question -- if not, please direct me to the right place. I'm a subscriber to 2 Mailman lists, Ger-Poland-Volhynia list at sggee.org and TSS list at surname-society.org. I joined the former (with Individual messages) several years ago and it has always worked as expected. The TSS list is new and, as a member of TSS (The Surname Society), I was subscribed automatically to Digest mode, but very soon switched to Individual mode. All email messages that come from the list (both Digest and Individual) are blank except for the list footer and the real message is an attachment to that blank message. I always have to open that attachment to read the message but to reply, I have to reply to the blank message. It's my impression that very few other TSS list subscribers receive their messages in this way, and I've not so far been able to get any explanation form the TSS webmaster. I've checked the Mailman subscription options for both lists and the settings appear to be identical. My email client is Thunderbird 31.7 (not quite the latest version) running under Windows 8.1 64-bit. The problem with the TSS list exists whether I view the email in Thunderbird or my ISP's webmail. If anybody has any clues why the TSS messages should appear in this way, I'd be very grateful for your help/advice. Lindsay Graham Canberra, Australia

2 1