Mailman 3 May 2014 - Mailman-Users

Mailman 2.1.18 final release
by Mark Sapiro May 6, 2014

May 6, 2014

I'm pleased to announce the final release for Mailman 2.1.18. This release has new features to help with mitigation of the impacts of DMARC on mailing lists as well as fixing several bugs. Python 2.4 is the minimum supported, but Python 2.7 is recommended. There are significant new i18n strings associated with the DMARC mitigation features. If you are interested in helping with the translations of these strings, see <http://wiki.list.org/x/MQ>. There is also a new dependency … [View More]

1 1

accessing relay mailman server from its own network
by Anne Wainwright May 4, 2014

May 4, 2014

Hello, My mailing lists run on a relay server installed as per FAQ 4.88 Accessing the web interface across the internet works fine but accessing while on the host network is not so fine. Instead of the DSL (dyndns) address I use the server name or IP address and all goes fine unless I query the mailing list addresses. Then i am returned to login again and so on ad infinitum. Same if I try to list them. I note that when I mouse-over the menu options the browser bottom line shows the server … [View More]

2 13

Parallel list question
by Rob Lingelbach May 3, 2014

May 3, 2014

I once set this up long ago on mailman but took it down and now need to do it again but forgot how: Want to have all subscribers to list A receive from, and be able to post to, list B. Purpose is to change the list title shown in the Subject: field, and have different admin options for list B. Thank you in advance. (And while I'm at it, thank you to those who have worked on the DMARC "enhancements.") Rob Lingelbach http://colorist.org

3 4

2.1.18 internal documentation suggestions
by Lindsay Haisley May 3, 2014

May 3, 2014

The internal documentation in the admin screens for 2.1.18 is a bit confusing with regard to Reply-To munging. In the doc for the from_is_list option we have "It replaces the poster's address in the From: header with the list address and adds the poster to the Reply-To: header, but the anonymous_list and Reply-To: header munging settings below take priority." Which Reply-To: header munging settings take priority, and how should one set them so that they don't override from_is_list? If … [View More]

7 29

Ignore DMARC bounces?
by Andrew Partan May 3, 2014

May 3, 2014

Is there some way of ignoring the DMCAC bounces? That way a message From: someone(a)yahoo.com will not not increase the bounce count of all Yahoo, AOL, Hotmail, ATT, MSN, and Comcast users. Yahoo & ATT say this: 554 5.7.9 Message not accepted for policy reasons. See http://postmaster.yahoo.com/errors/postmaster-28.html AOL says this: 521 5.2.1 : (DMARC) This message failed DMARC Evaluation and is being refused due to provided DMARC Policy Comcast says this: 550 5.2.0 … [View More]

3 2

Issue approving subscription requests
by Murray S. Kucherawy May 2, 2014

May 2, 2014

For a list I recently migrated from 2.1.14 on one machine to 2.1.17 on another, I'm unable to approve pending subscription requests. After making my choices and clicking "Submit all data", the radio buttons simply reset themselves with no changes made to the subscriber records. "check_perms -f" and "check_db" make no complaints about my configuration. Is this a bug? Could something have gotten botched in the migration? The lists seem to be operating fine otherwise. -MSK

2 9

Which file are Mailman's webpages build from?
by Henrik Rasmussen May 2, 2014

May 2, 2014

I am running Mailman version 2.1.12. I have not been able to find a list of pages where the different HTML templates are used. Having copied the HTML-templates, listed below, from /usr/lib/mailman/templates/da/ to /usr/lib/mailman/templates/site/da/ I would like to change the design of the web-pages. So far I am doing good a few templates, but I am not able to locate on which pages the second list of files are used Also some of the web-pages gets there information from various spurces such as … [View More]

2 1

DMARC From munging: Keep original sender
by Ralf Jung May 2, 2014

May 2, 2014

Dear all, I am currently experimenting with the From munging of Mailman (2.1.16) to make my lists DMARC-compliant. This is generally working, there is a problem though: I found no way so far to tell, from the mail that's ultimately delivered to the users, who was the original sender. No matter whether I set reply_goes_to_list to 0 or 1 (and unfortunately, many of my users request a 1 here :-/ ), the final mail contains no trace of the original sender except for its pretty-printed name. … [View More]

3 7

ht://Dig integration patches with Mailman 2.1.12/RHEL 6.5
by Greg Earle May 1, 2014

May 1, 2014

At work I'm dealing with migrating a legacy production system that uses Mailman 2.1.9 with ht://Dig integration on a RHEL 5.x box. I'm trying to migrate it to a RHEL 6.5 system with Mailman 2.1.12-18. I have the indexing and ht://Dig patches for 2.1.12 and I'm trying to integrate it into a custom RPM build, like its predecessor. Basing it on mailman-2.1.12-18.el6.src.rpm. Has anyone on the list done this before? It seems like no matter where I try to put the 2 patches in the .spec file, … [View More]there is a conflict between the htdig patch and some other patch (like the "cron" patch or the "FHS" patch). What's strange is that the patches for 2.1.9 seem not all that very different, and yet that rpmbuild worked perfectly for me! But no such luck with 2.1.12 so far. If I look in the old 2.1.9 version of the htdig patch file, I see this segment for "crontab.in.in", for example: -- diff -ruP --exclude=.DS_Store mailman-2.1.9-index/cron/crontab.in.in mailman-2.1 .9-htdig/cron/crontab.in.in --- mailman-2.1.9-index/cron/crontab.in.in 2002-01-06 06:28:12.000000000 +0 000 +++ mailman-2.1.9-htdig/cron/crontab.in.in 2006-09-20 16:06:17.000000000 +0 100 @@ -18,6 +18,11 @@ # or want to exclusively use a callback strategy instead of polling. 0,5,10,15,20,25,30,35,40,45,50,55 * * * * @PYTHON@ -S @prefix@/cron/gate_news # +# At 2:19am every night, regenerate htdig search files. Only +# turn this on if the internal archiver is used and htdig +# use enabled in mm_cfg.py with USE_HTDIG +19 2 * * * @PYTHON@ -S @prefix@/cron/nightly_htdig +# # At 3:27am every night, regenerate the gzip'd archive file. Only # turn this on if the internal archiver is used and # GZIP_ARCHIVE_TXT_FILES is false in mm_cfg.py -- which assumes that line 19 has "gate_news" and "@PYTHON@" in it. Yet if I look at the actual diffs after the 2.1.9 htdig patch was (successfully) applied, it's somehow not the same: -- [root@rushmore cron]# diff -u crontab.in.in.htdig crontab.in.in --- crontab.in.in.htdig 2009-04-02 01:45:29.000000000 -0700 +++ crontab.in.in 2009-04-02 01:45:29.000000000 -0700 @@ -41,6 +41,11 @@ # or want to exclusively use a callback strategy instead of polling. 0,5,10,15,20,25,30,35,40,45,50,55 * * * * @MAILMAN_USER@ @prefix@/cron/gate_news # +# At 2:19am every night, regenerate htdig search files. Only +# turn this on if the internal archiver is used and htdig +# use enabled in mm_cfg.py with USE_HTDIG +19 2 * * * @PYTHON@ -S @prefix@/cron/nightly_htdig +# # At 3:27am every night, regenerate the gzip'd archive file. Only # turn this on if the internal archiver is used and # GZIP_ARCHIVE_TXT_FILES is false in mm_cfg.py -- Note the "@MAILMAN_USER@" on the "gate_news" line (which is now line 42 after the "cron" patch had been applied). Plus, after the "cron" patch was applied, the line numbers in the "htdig" patch are no longer correct. In other words, shouldn't the 2.1.9 patch have choked as well, just as the 2.1.12 patch seems to be doing to me now? I tried changing the current 2.1.12 htdig patch and put in "@MAILMAN_USER@". Now the htdig patch works - but then I get an immediate .rej file from the FHS patch right afterwards. :-( The htdig patch assumes FHS hasn't been applied yet - but if htdig is applied before FHS, then FHS breaks because it doesn't know about the added "archives/htdig" entry in VAR_DIRS that the htdig patch put there. I re-ran the 2.1.9 rpmbuild and sure enough, it worked perfectly fine: -- [...] Patch #4 (mailman-cron.patch): + patch -p1 -b --suffix .cron -s + echo 'Patch #5 (indexing-2.1.9-0.1.patch):' Patch #5 (indexing-2.1.9-0.1.patch): + patch -p1 -b --suffix .indexing -s + echo 'Patch #6 (htdig-2.1.9-0.1.patch):' Patch #6 (htdig-2.1.9-0.1.patch): + patch -p1 -b --suffix .htdig -s + echo 'Patch #7 (mailman-FHS.patch):' Patch #7 (mailman-FHS.patch): + patch -p1 -b --suffix .FHS -s [...] -- At this point I'm more shocked that the 2.1.9 patches worked, given what I've seen with the 2.1.12 patches. Color me baffled at this point! If anyone has successfully done this integration and can offer any pointers (like what order to do the patching, and what patch number in the spec file to insert them into, or what obvious thing I'm doing wrong), feel free to respond or send me e-mail directly and take it off-line. Thanks, - Greg [View Less]

2 2

Mailman error (2.1.16): "low level unrecoverable exception"
by Robert Heller May 1, 2014

May 1, 2014

What does this error message mean? "low level unrecoverable exception" I just installed my own build of mailman 2.1.16 (built under CentOS 5 x84_64) as an upgrade over the stock 2.1.9 that comes with CentOS 5 and I am getting this error. What should I be looking for? -- Robert Heller -- 978-544-6933 / heller(a)deepsoft.com Deepwoods Software -- http://www.deepsoft.com/ () ascii ribbon campaign -- against html e-mail /\ www.asciiribbon.org -- against proprietary attachments

2 5