Mailman 3 November 2015 - Mailman-Users

ANNOUNCING: GNU Mailman 3.0.1
by Barry Warsaw Nov. 15, 2015

Nov. 15, 2015

I'm happy to announce the first maintenance release of GNU Mailman 3. This version 3.0.1 release includes updates to the core, Postorius, HyperKitty, and mailman.client. The release matrix of versions is available here: http://wiki.list.org/Mailman3 You can find more information about the changes in each component by following the version links in that overview page. Enjoy, -Barry (on behalf of the entire Mailman development team)

1 0

Downgrade options/alternatives
by Montanez, Victor Nov. 13, 2015

Nov. 13, 2015

Hello, I have done a successful upgrade from Mailman version 2.1.16 to 2.1.20 successfully. I am now testing the downgrade (In case some issue comes up and I have to rollback) and it seemed to have gone okay for the most part. At the of the end of the downgrade I get the following message(which I have googled around but no real alternative given). Error: Compiling i18n.py ... Compiling versions.py ... Downgrade detected, from version 0x20114f0 to version 0x20110f0 This is probably not safe. Exiting. make: *** [update] Error 1 I understand is a downgrade, that is what I want to do. But it looks like "downgrading" isn't really supported in Mailman. What is a recommended alternative for having a way to go back to previous Mailman version? Thank you

2 4

Readonly admin access
by Peter Shute Nov. 13, 2015

Nov. 13, 2015

On our list, several of the moderators have admin access so that we can add and remove members. Has it ever been considered to add a third type of user who can perform those tasks without being able to modify the list configuration? I assume there isn't already a way to achieve this? A related idea is to have mailman keep a log of configuration changes so that's it's easy to see when and what changes have been made. Peter Shute

2 1

Part of moderated mails postponed to later digests
by Henrik Rasmussen Nov. 12, 2015

Nov. 12, 2015

One of my list administrators complains that digest mails now seems to be sent in fragmented chunks and instead of sending all moderated mails in a digest the same day, only some of the mails will be sent with a digest the same day, and the rest will be sent in a digest with the next moderated mails, half a week later. For instance, when moderating say 50 mails in week 1 and 50 mails in week 2, the digest mail in week 1 will contain say 30 mails in a digest, while the digest in week 2 will contain like 20 mails from week 1 and like 10 mails from week 2. There is no information about when the admin discovered the problem, but on August 20th 2015 Mailman has been upgraded from 3:2.1.12-18.el6 to 3:2.1.12-25.el6 and I wonder if the DMARC implementation in 3:2.1.12-22.el6 has something to do with it, as this is the only changes I can think of having any effect on the mail behavior. dmarc_quarantine_moderation_action is set to Yes on the list in particular and according to some discussions on the Internet, this strict action has been coursing bounces, so I suggested him to set this to No. But even being strict, I don't see why this would course parts of the digest being held half a week, so something else must interfere. Regards Henrik Rasmussen

2 7

listname@lists.domain does not work, listname@domain does
by Paw Nov. 11, 2015

Nov. 11, 2015

Hi Mailman community, I am using postfix with dovecot on a Debian server. I followed < http://wiki.list.org/x/ZoCj> for setting up mailman, but something is wrong with my postfix configuration. I can create new lists on http://lists.mydomain and when subscribing I get the subscription notification from mailman. But for sending to the list, I have to use listname@domain instead of listname(a)lists.domain. Mails sent to listname(a)lists.domain just seems to get lost(don't bounce or end up in /var/log/mail.log) I am sorry so disturb with such a question, but I am really stuck. This is the full log when sending a mail to test@mydomain. The mail is being delivered to local user tester's inbox. Nov 11 06:41:59 loki postfix/smtpd[4543]: connect from mail-lf0-f49.google.com[209.85.215.49] Nov 11 06:41:59 loki postfix/smtpd[4543]: 7F4E724C09B: client= mail-lf0-f49.google.com[209.85.215.49] Nov 11 06:41:59 loki postfix/cleanup[4914]: 7F4E724C09B: message-id=<CAP53jTxugaP79R=Uqr_1zipb2z_EVQRno= LXJJ7KUJAaOBgxZA(a)mail.gmail.com> Nov 11 06:41:59 loki postfix/qmgr[31085]: 7F4E724C09B: from=< pawses(a)gmail.com>, size=1680, nrcpt=1 (queue active) Nov 11 06:41:59 loki postfix/smtpd[4543]: disconnect from mail-lf0-f49.google.com[209.85.215.49] Nov 11 06:41:59 loki postfix/local[4915]: 7F4E724C09B: to=< test(a)studentergaarden.dk>, relay=local, delay=0.63, delays=0.49/0.01/0/0.13, dsn=2.0.0, status=sent (delivered to command: /var/lib/mailman/mail/mailman post test) Nov 11 06:41:59 loki postfix/qmgr[31085]: 7F4E724C09B: removed Nov 11 06:42:01 loki postfix/smtpd[4543]: connect from localhost[127.0.0.1] Nov 11 06:42:01 loki postfix/smtpd[4543]: 44A6324C0A7: client=localhost[127.0.0.1] Nov 11 06:42:01 loki postfix/cleanup[4914]: 44A6324C0A7: message-id=<CAP53jTxugaP79R=Uqr_1zipb2z_EVQRno= LXJJ7KUJAaOBgxZA(a)mail.gmail.com> Nov 11 06:42:01 loki postfix/qmgr[31085]: 44A6324C0A7: from=< test-bounces(a)lists.studentergaarden.dk>, size=3127, nrcpt=1 (queue active) Nov 11 06:42:01 loki postfix/smtpd[4543]: 5D5F124C0E1: client=localhost[127.0.0.1] Nov 11 06:42:01 loki postfix/cleanup[4914]: 5D5F124C0E1: message-id=<CAP53jTxugaP79R=Uqr_1zipb2z_EVQRno= LXJJ7KUJAaOBgxZA(a)mail.gmail.com> Nov 11 06:42:01 loki postfix/qmgr[31085]: 5D5F124C0E1: from=< test-bounces(a)lists.studentergaarden.dk>, size=3137, nrcpt=1 (queue active) Nov 11 06:42:01 loki postfix/smtpd[4543]: disconnect from localhost[127.0.0.1] Nov 11 06:42:01 loki dovecot: lda(tester): msgid=<CAP53jTxugaP79R=Uqr_1zipb2z_EVQRno=LXJJ7KUJAaOBgxZA(a)mail.gmail.com>: saved mail to INBOX Nov 11 06:42:01 loki postfix/local[4915]: 5D5F124C0E1: to=< tester(a)studentergaarden.dk>, relay=local, delay=0.19, delays=0.05/0/0/0.13, dsn=2.0.0, status=sent (delivered to command: /usr/lib/dovecot/deliver) Nov 11 06:42:01 loki postfix/qmgr[31085]: 5D5F124C0E1: removed Nov 11 06:42:01 loki postfix/smtp[4944]: 44A6324C0A7: to=<pawses(a)gmail.com>, relay=gmail-smtp-in.l.google.com[173.194.222.27]:25, delay=0.49, delays=0.1/0.01/0.26/0.12, dsn=2.0.0, status=sent (250 2.0.0 OK 1447220691 38si4916356lfq.17 - gsmtp) Nov 11 06:42:01 loki postfix/qmgr[31085]: 44A6324C0A7: removed My config is as follow: ----------------------------------------------- Dumps of postconf, mm_cfg.py virtual-mailman, virtual_to_transport and transport-mailman ----------------------------------------------- $ postconf -n alias_database = hash:/etc/aliases alias_maps = hash:/etc/aliases hash:/var/lib/mailman/data/aliases append_dot_mydomain = no biff = no body_checks = pcre:/etc/postfix/bodychecks config_directory = /etc/postfix dovecot_destination_recipient_limit = 1 header_checks = pcre:/etc/postfix/headerchecks inet_interfaces = mail.studentergaarden.dk, localhost inet_protocols = ipv4 mailbox_command = /usr/lib/dovecot/deliver mailbox_size_limit = 2048000000 message_size_limit = 40480000 mydestination = $mydomain, $myhostname, localhost.$mydomain, localhost myhostname = mail.studentergaarden.dk mynetworks = 130.226.169.128/26, 172.16.0.0/16, 127.0.0.0/8 myorigin = /etc/mailname recipient_delimiter = + relayhost = smtpd_banner = $myhostname ESMTP $mail_name smtpd_client_restrictions = permit_mynetworks, reject_unknown_client smtpd_hard_error_limit = 10 smtpd_helo_required = yes smtpd_helo_restrictions = reject_invalid_hostname smtpd_recipient_restrictions = permit_mynetworks, reject_rbl_client zen.spamhaus.org, reject_unauth_destination, reject_unauth_pipelining, smtpd_relay_restrictions = permit_mynetworks, reject_rbl_client zen.spamhaus.org, reject_unauth_destination, reject_unauth_pipelining, smtpd_sender_restrictions = reject_non_fqdn_sender, reject_unknown_sender_domain smtpd_soft_error_limit = 8 transport_maps = hash:/var/lib/mailman/data/transport-mailman virtual_mailbox_domains = mail.studentergaarden.dk virtual_transport = dovecot $ cat /etc/mailman/mm_cfg.py ... few irrelevant lines truncated ... DEFAULT_EMAIL_HOST = 'lists.studentergaarden.dk' DEFAULT_URL_HOST = 'lists.studentergaarden.dk' MTA='Postfix' POSTFIX_STYLE_VIRTUAL_DOMAINS = ['lists.studentergaarden.dk'] POSTFIX_MAP_CMD = '/var/lib/mailman/data/transport-mailman' --- Whether POSTFIX_MAP_CMD is commented out or not, does not seems to make a difference $ ll /var/lib/mailman/data total 80K -rw-r----- 1 root list 41 Oct 22 05:15 adm.pw -rw-rw---- 1 root list 5,6K Nov 11 06:13 aliases -rw-rw---- 1 list list 12K Nov 11 06:14 aliases.db -rw-r----- 1 root list 41 Nov 11 04:40 creator.pw -rw-rw-r-- 1 root list 10 Oct 22 03:11 last_mailman_version -rw-rw-r-- 1 root list 14K Apr 6 2015 sitelist.cfg -rwxrwxr-x 1 root list 0 Nov 11 03:53 transport-mailman -rw-r--r-- 1 root list 12K Nov 11 04:10 transport-mailman.db -rw-rw---- 1 www-data list 5,3K Nov 11 06:13 virtual-mailman -rw-rw---- 1 list list 12K Nov 11 06:14 virtual-mailman.db -rwxr-x--- 1 root list 153 Nov 11 04:00 virtual_to_transport $ cat /var/lib/mailman/data/virtual-mailman # STANZA START: test # CREATED: Wed Nov 11 05:55:30 2015 test(a)lists.studentergaarden.dk test test-admin(a)lists.studentergaarden.dk test-admin test-bounces(a)lists.studentergaarden.dk test-bounces test-confirm(a)lists.studentergaarden.dk test-confirm test-join(a)lists.studentergaarden.dk test-join test-leave(a)lists.studentergaarden.dk test-leave test-owner(a)lists.studentergaarden.dk test-owner test-request(a)lists.studentergaarden.dk test-request test-subscribe(a)lists.studentergaarden.dk test-subscribe test-unsubscribe(a)lists.studentergaarden.dk test-unsubscribe # STANZA END: test (the Mailman list is also included in the above file) $ cat /var/lib/mailman/data/virtual_to_transport sed -r -e 's/(^[^#]\S+\s+).+$/\1local:/' $1 > /var/lib/mailman/data/transport-mailman /usr/sbin/postmap /var/lib/mailman/data/transport-mailman $ cat /var/lib/mailman/data/transport-mailman <<<EOF (empty) There are no errors in relevant postfix/mailman logs. I do not use postfix-to-mailman.py. What have I done wrong with the postfix configuration? And where does the listname(a)list.domain maills go? $ uname -a Linux loki 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt11-1+deb8u5 (2015-10-09) x86_64 GNU/Linux $ /usr/sbin/check_perms No problems found $ /usr/lib/mailman/bin/version Using Mailman version: 2.1.18 Thanks in advance! /Paw

3 2

Re: [Mailman-Users] 64 bit encoding
by Mark Sapiro Nov. 10, 2015

Nov. 10, 2015

On November 9, 2015 6:56:56 PM EST, Mark Sapiro <mark(a)msapiro.net> wrote: > > >On November 9, 2015 6:49:53 PM EST, Ruben <mrbrklyn(a)panix.com> wrote: >> >> > >>I made this change and I think I'm getting no throughput through the >>list altogether :( >> >>I have the mail logs being tailed and all the mailman/logs but I'm not > >>spotting the problem >> >> >>==> /var/lib/mailman/logs/post <== >>Nov 09 18:34:12 2015 (28269) post to hangout from mrbrklyn(a)panix.com, >>size=6608, message-id=<563AE93A.2000208(a)panix.com>, 11 failures > > >What's in Mailman's smtp-failure log for these? > >Anything in Mailman's error log? > >What's in the mail log for these? -- Mark Sapiro <mark(a)msapiro.net> Sent from my Not_an_iThing with standards compliant, open source software.

3 5

64 bit encoding
by Ruben Safir Nov. 9, 2015

Nov. 9, 2015

I'm converting my mailing lists from majordomo to mailman using postfix. A lot of little issues have cropped up but the biggest problem I have currently is that it seems that mailman is converting files to 64 bit which is screwing up my home cooked archives but good. How you I stop it from doing this: <mailto:hangout-request@nylxs.com?subject=subscribe> Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Errors-To: hangout-bounces(a)nylxs.com Sender: "hangout" <hangout-bounces(a)nylxs.com> T24gMTEvMDMvMjAxNSAxMTozOCBBTSwgUnViZW4gU2FmaXIgd3JvdGU6Cj4gTG93IGxldmVsIGF1 dG9tYXRpb24gdG9vbHMgZGV2ZWxvcGVyCj4g16nXnNeXINen15XXqNeV16og15fXmdeZ150KPiDX lNeV16HXoyDXnNeh15wKPiBEZXZhbG9yZUV4cGVyaWVuY2VkIHdpdGggdG9vbHMgYW5kIGF1dG9t YXRpb24gZnJhbWV3b3JrIGRldmVsb3BtZW50IGZvcgo+IGxvdyBsZXZlbCBzb2Z0d2FyZSBGVy9k cml2ZXIKPiBFeGNlbGxlbnQgdW5kZXJzdGFuZGluZyBjb21wbGljYXRlZCBvZiBTVyBhcmNoaXRl Y3R1cmUgSFcvRHJpdmVyL1NXCj4gKEV4Y2VsbGVudCBrbm93bGVkZ2UgaW4gQysrICg0KyB5ZWFy cwo+IEdvb2Qga25vd2xlZGdlIGluIEMjIGFuZCBPT1AgLSBhZHZhbnRhZ2UgMisgeWVhcnMKPiBE ZWVwIHVuZGVyc3RhbmRpbmcgaW4gTGludXggaW50ZXJuYWxzCj4gSGFuZHMgb24gSmF2YSBwcm9n cmFtbWluZyBleHBlcmllbmNlCj4gQWR2YW50YWdlIDpGYW1pbGlhcml0eSB3aXRoIG5ldHdvcmtp bmcgc3lzdGVtL3Byb3RvY29scwo+IEFkdmFudGFnZSA6RXhwZXJpZW5jZSB3aXRoIE9iamVjdCBP cmllbnRlZCBtZXRob2RvbG9naWVzCj4gKEJpZyBBZHZhbnRhZ2UgOkZhbWlsaWFyaXR5IHdpdGgg V2ktRmkgdGVjaG5vbG9naWVzICg4MDIuMTEKPiBHb29kIGRlYnVnZ2luZyBhbmQgcHJvYmxlbSBz b2x2aW5nIHNraWxscwo+IEdvb2QgY29tbXVuaWNhdGlvbiBza2lsbHMgYW5kIGFiaWxpdHkgJiBk ZXNpcmUgdG8gd29yayBhcyBhIHRlYW0gcGxheWVyCj4gYXJlIGEgbXVzdAo+IFRoZXNlIHBvc2l0

4 6

Re: [Mailman-Users] Mailman only delivers inside server
by kapuzino＠web.de Nov. 9, 2015

Nov. 9, 2015

Hello >> Mailman had worked fine primarily. >> After a server-update it deliveres messages only to email-adresses hostet on the same server (my own adresses connected to two different tld's). (Gao) >I am having the same problem ... >... So I changed my main.cf: >mynetworks = 192.168.1.0/24, 127.0.0.0/8 localhost It is done, without bettering. (Mark Sapiro) >This is almost certainly a Postfix issue, not a Mailman issue. But what is the diffrence between sending with postfix using a distributor generated in plesk-email-panel and the connection of mailman to postfix ? If it is no internal mailman issue, though a special configuration issue needed for mailman, when postfix is sending everything well, but mailman tasks. What information could help to localize the failure ? regards Kapuzino

2 1

Delete Archive
by am Nov. 9, 2015

Nov. 9, 2015

I posted a similar q on 6th but did not see the post nor any responses. (I may be still in the newbie doghouse :-) ...) My question: Is there a way to reset the archive, or delete / restart it? Mailman 2.1.20 Thank you - C-L

2 1

Re: [Mailman-Users] 64 bit encoding
by Ruben Safir Nov. 6, 2015

Nov. 6, 2015

On 11/05/2015 12:24 PM, Mark Sapiro wrote: > On 11/05/2015 08:41 AM, Ruben Safir wrote: >> >> Which file am I patching? Is this a normal setup? I pulled it from >> opensuse. >> >> >> ruben@www:~> locate Mailman/Message.py >> /usr/lib/mailman/Mailman/Message.py >> /usr/lib/mailman/Mailman/Message.pyc > > The above two are probably what you want. > /usr/lib/mailman/Mailman/Message.py is the source to patch. After you > apply the patch and restart Mailman, Python will automatically detect > that the .py is newer and recompile it into the .pyc. > > >> /usr/local/apache/conf/mailman/Mailman/Message.py >> /usr/local/apache/conf/mailman/Mailman/Message.pyc > ohh. Maybe I did that because I didn't want my cgi-bin directory outside of my apache trunk. It is odd habit I picked up in the last 30 years is that I want my webservers restricted to the apache directory tree which is /usr/local/apache/ It didn't occur to be that mailing system binary and script libraries would also end up in the apache trunk. <VirtualHost *:80> ServerAdmin ruben(a)mrbrklyn.com DocumentRoot "/usr/local/apache/htdocs/nylxs" ScriptAlias /mailman/ /usr/local/apache/htdocs/mailman/cgi-bin/ Alias /mailmanicons/ /usr/local/apache/htdocs/mailman/icons/ Alias /pipermail/ /usr/local/apache/htdocs/mailman/archives/public/ ServerName www.nylxs.com DirectoryIndex index.html PerlModule Embperl Embperl_UseEnv on ErrorLog logs/nylxs_error_log CustomLog logs/nylxs_access_log common <Directory /usr/local/apache/htdocs/nylxs> Options Indexes ExecCGI DirectoryIndex index.html <Files *.html> SetHandler perl-script # PerlResponseHandler URL_BLOCK PerlHandler Embperl </Files> AllowOverride None Order allow,deny Allow from all </Directory> </VirtualHost> <VirtualHost *:80> ServerName lists.mrbrklyn.com DocumentRoot "/usr/local/apache/htdocs/mailman/" ScriptAlias /mailman/ /usr/local/apache/htdocs/mailman/cgi-bin/ Alias /mailmanicons/ /usr/local/apache/htdocs/mailman/icons/ Alias /pipermail/ /usr/local/apache/htdocs/mailman/archives/public/ " ErrorLog logs/mailman_error_log TransferLog logs/mailman_access_log <Directory /usr/local/apache/htdocs/mailman/cgi-bin> order allow,deny allow from all </Directory> <Directory /usr/local/apache/htdocs/mailman/icons> order allow,deny allow from all </Directory> <Directory /usr/local/apache/htdocs/mailman/archives/> Options +FollowSymLinks order allow,deny allow from all </Directory> </VirtualHost> > This is very strange. I've never seen anything like it. My best guess is > that for some reason, the openSUSE package installs a separate Mailman/ > directory for use by the web server. If that is the case, this one > doesn't need to be patched because the patch doesn't affect anything in > the web UI. > > To be sure, I'd need to see the apache configuration, the MTA > configuration and the contents of the directories. > > I did quickly look at > <https://build.opensuse.org/package/view_file/openSUSE:Leap:42.1/mailman/mai…>, > <https://build.opensuse.org/package/view_file/server:mail/mailman/mailman-ap…>, > etc. and they all refer to /usr/lib/mailman so I have no idea what > /usr/local/apache/conf/mailman/ is about. > > The bottom line is the Message.py you need to patch is the one that's > imported by the qrunners, IncomingRunner and OutgoingRunner in > particular. Is there even a > /usr/local/apache/conf/mailman/Mailman/Queue/ directory at all? > > If the two Message.py files are the same, it wouldn't hurt to patch both. >

2 5