Mailman 3 November 2015 - Mailman-Users

Fwd: Fwd: [Spip-Ann] Discover UAE National Day Deals
by Fil Nov. 22, 2015

Nov. 22, 2015

Hello, a spam went through a moderated list today, and the story is weird. Here's what I understand/ (mailman version 2.1.20) First, the message was received and rejected by the list moderators logs/vette.log:Nov 22 14:56:45 2015 (10257) Message rejected, msgid: < 20151122135632.C128E412040(a)mst135.mdreg-mstnew.qlc.co.in> Then, the (rejected!) message was sent to the list members; logs/post.log:Nov 22 17:05:41 2015 (15369) post to spip-ann from mails(a)clovertourism.com, size=4374, message-id=< 20151122135632.C128E412040(a)mst135.mdreg-mstnew.qlc.co.in>, success logs/smtp.log:Nov 22 17:05:41 2015 (15369) < 20151122135632.C128E412040(a)mst135.mdreg-mstnew.qlc.co.in> smtp to spip-ann for 2880 recips, completed in 2.228 seconds The "reason" why this went through at 17+ is that I have a cron job that tries to unshunt messages each day at that hour. So the (discarded then shunted) message was unshunt and sent to the list. logs/error.log:Nov 22 14:56:44 2015 (10257) IOError reading list extension: [Errno 12] Cannot allocate memory: '/var/local/mailman/lists/spip-ann/extend.py' logs/error.log:Nov 22 14:56:45 2015 (10257) Uncaught runner exception: [Errno 12] Cannot allocate memory: '/var/local/mailman/qfiles/virgin' logs/error.log:Nov 22 14:56:45 2015 (10257) Traceback (most recent call last): logs/error.log:Nov 22 14:56:45 2015 (10257) SHUNTING: 1448200600.413774+c9883eaaeaec5a744cfe6a49237d51c2c0373b98 -- Fil

2 3

Old chestnut: List integration with forum
by Andrew Hodgson Nov. 22, 2015

Nov. 22, 2015

Hi, I have a list which is working well at the moment, but want to introduce a forum that gates to and from the list. Which forum software currently in people's opinion has the best integration with Mailman 2.x? Thanks. Andrew.

1 0

Problem with this list archive
by Alain Williams Nov. 22, 2015

Nov. 22, 2015

It seems to have recently gone to HTTPS and is generating a 404 for HTTP URLs. This causes a problem with archives email that contains a link to old messages. Eg: https://mail.python.org/pipermail/mailman-users/2005-January/042243.html contains a link to: http://mail.python.org/pipermail/mailman-users/2005-January/041697.html which comes up 404. However, if you manually convert ''http:'' to ''https:'' the URL then works. Could you persuade Apache to do that redirect ? Regards -- Alain Williams Linux/GNU Consultant - Mail systems, Web sites, Networking, Programmer, IT Lecturer. +44 (0) 787 668 0256 http://www.phcomp.co.uk/ Parliament Hill Computers Ltd. Registration Information: http://www.phcomp.co.uk/contact.php #include <std_disclaimer.h>

2 2

Can the list prefix placed at the end of the subject line?
by Nicola Caon Nov. 20, 2015

Nov. 20, 2015

Hi, here at my workplace several users have suggested that the list prefix be removed from the email subject, as the list prefix takes up precious space in the subject line and makes it more difficult to see what the email is about without opening it (especially on mobile or small screens). In our case the problem is magnified by the fact that our main lists are actually made up of sublists, so that the email subject might go like [postdocs][researchers] Seminar tomorrow on ... Other users strongly object to removing the list prefix altogether from the email subject. Perhaps the best compromise would be moving the list prefix at the end of the subject line, however it seems that there is no such option in mailman (we are running version 2.1.15). Are there any hidden settings or some simple change to the code that can enable this option? Or could it be implemented in a future release? Thanks! Nicola Caon

3 3

Re: [Mailman-Users] Can the list prefix placed at the end of the subject line?
by Adrian Pepper Nov. 19, 2015

Nov. 19, 2015

On 11/19/15 9:25 AM, Nicola Caon wrote: > > Hi, > > here at my workplace several users have suggested that the list prefix be > removed from the email subject, as the list prefix takes up precious space > in the subject line and makes it more difficult to see what the email is > about without opening it (especially on mobile or small screens). > > In our case the problem is magnified by the fact that our main lists are > actually made up of sublists, so that the email subject might go like > [postdocs][researchers] Seminar tomorrow on ... > > Other users strongly object to removing the list prefix altogether from the > email subject. > > Perhaps the best compromise would be moving the list prefix at the end of > the subject line, however it seems that there is no such option in mailman > (we are running version 2.1.15). > > Are there any hidden settings or some simple change to the code that can > enable this option? Or could it be implemented in a future release? > > Thanks! > > Nicola Caon > ------------------------------------------------------ > Mailman-Users mailing list Mailman-Users(a)python.org > https://mail.python.org/mailman/listinfo/mailman-users > Mailman FAQ: http://wiki.list.org/x/AgA3 > Security Policy: http://wiki.list.org/x/QIA9 > Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ > Unsubscribe: https://mail.python.org/mailman/options/mailman-users/arpepper%40uwaterloo.… > I see, you are talking about your own prefixes, not [Mailman-Users] specifically. What is in [] doesn't need to match the list name exactly (or at all, although obviously it is better if it matches somewhat). So you could shorten to e.g. "[pdoc][rsrch] Seminar tomorrow on ..." Perhaps some of the top lists don't need a tag? Adrian Pepper arpepper(a)uwaterloo.ca

1 0

Files able to remove
by Marino, Dominic Nov. 19, 2015

Nov. 19, 2015

I need to remove some files to free up some space on my server and I am new to Mailman aspects. So my question is what files are save to remove where I can get the most bang from my buck so to say. ________________________________ Dominic Marino

2 1

Re: [Mailman-Users] Reverse chronological date order for archives
by Mark Sapiro Nov. 19, 2015

Nov. 19, 2015

On 11/18/15 7:03 PM, ListGnome ProtonMail wrote: > Hi Mark, > > I was referring to the date.html page - but it would also apply to all > the other views - whereby the most recent post is always at the top > rather than the bottom. > > I found another post (from 2004) where the author modified the > HyperDatabase.py file and says that managed to reverse the chronological > date order. > > https://www.mail-archive.com/mailman-users%40python.org/msg28944.html > > I had a look at the HyperDatabase.py file in my version (2.1.20) and the > code that he shows doesn't exist in my file. ... The patch in that post is against Mailman 2.1.5. The reason you can't find that code in any HyperDatabase.py is the patch is 'reversed' and the lines that show as deleted were actually added. A proper context diff for that patch is $ diff -u HyperDatabase.py.old HyperDatabase.py --- HyperDatabase.py.old 2015-11-18 22:15:25.000000000 -0800 +++ HyperDatabase.py 2015-11-18 22:20:43.000000000 -0800 @@ -291,9 +291,14 @@ def first(self, archive, index): self.__openIndices(archive) + if index == 'date': dateIndex = 1 + else: dateIndex = 0 index = getattr(self, index + 'Index') try: key, msgid = index.first() + if dateIndex == 1: + index.sorted.reverse() + key, msgid = index.first() return msgid except KeyError: return None And the patch refactored for style against 2.1.20 is $ diff -u 2.1/Mailman/Archiver/HyperDatabase.py 21/Mailman/Archiver/HyperDatabase.py --- 2.1/Mailman/Archiver/HyperDatabase.py 2013-05-31 14:44:32.000000000 -0700 +++ 21/Mailman/Archiver/HyperDatabase.py 2015-11-18 22:32:14.000000000 -0800 @@ -297,8 +297,14 @@ def first(self, archive, index): self.__openIndices(archive) + if index == 'date': + dateIndex = 1 + else: + dateIndex = 0 index = getattr(self, index + 'Index') try: + if dateIndex == 1: + index.sorted.reverse() key, msgid = index.first() return msgid except KeyError: I note three things. 1) I have not tested the patch. It looks like it might work, but no guarantees. 2) The patch only affects the date index. 3) After installing the patch and restarting Mailman, the current period date index for a list should be reordered with the next post to that list, but older date index files will not be unless you rebuild the archive with bin/arch --wipe. See the section "NOTE ON MBOX ANOMALIES:" in the FAQ at <http://wiki.list.org/x/4030681> for caveats before doing this. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 0

Reverse chronological date order for archives
by ListGnome ProtonMail Nov. 18, 2015

Nov. 18, 2015

Hi, Has anyone been able to order their archive messages in reverse chronological date order - so the most recent post is at the top of the page. (Version 2.1.20) I found a related thread in the Mailman-Users archive (dated 2002) but it didn't explain how it was done. https://mail.python.org/pipermail/mailman-users/2002-February/017906.html Any clues greatly appreciated. Cheers, Mark

2 1

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

Nov. 15, 2015

(Mark Sapiro) >If I had to guess, my guess would be that 'localhost' or it's equivalent >IP (possibly IPv6 - see /etc/hosts) is not in Postfix mynetworks in >main.cf Following the advice of "Gao" and netfound tips it was defined already: mynetworks = 127.0.0.0/8, 89.163.212.5/32 but no change of behaviour. Below the complete main.cf and master.cf. Maybe, someone can see abscent or unmatching entries. Kapuzino ______________________________________________________________ main.cf # See /usr/share/postfix/main.cf.dist for a commented, more complete version # Debian specific: Specifying a file name will cause the first # line of that file to be used as the name. The Debian default # is /etc/mailname. #myorigin = /etc/mailname smtpd_banner = $myhostname ESMTP $mail_name (Debian/GNU) biff = no # appending .domain is the MUA's job. append_dot_mydomain = no # Uncomment the next line to generate "delayed mail" warnings #delay_warning_time = 4h readme_directory = no # TLS parameters smtpd_tls_cert_file = /etc/postfix/postfix_default.pem smtpd_tls_key_file = $smtpd_tls_cert_file smtpd_use_tls = yes smtpd_tls_session_cache_database = btree:${data_directory}/smtpd_scache smtp_tls_session_cache_database = btree:${data_directory}/smtp_scache # See /usr/share/doc/postfix/TLS_README.gz in the postfix-doc package for # information on enabling SSL in the smtp client. smtpd_relay_restrictions = permit_mynetworks permit_sasl_authenticated defer_unauth_destination myhostname = f632.fuchsia.scp-manager.com alias_maps = hash:/etc/aliases, hash:/var/spool/postfix/plesk/aliases alias_database = hash:/etc/aliases myorigin = /etc/mailname mydestination = localhost.fuchsia.scp-manager.com, localhost, localhost.localdomain relayhost = mynetworks = 127.0.0.0/8, 89.163.212.5/32 mailbox_size_limit = 0 recipient_delimiter = + inet_interfaces = all inet_protocols = all virtual_mailbox_domains = $virtual_mailbox_maps, hash:/var/spool/postfix/plesk/virtual_domains virtual_alias_maps = $virtual_maps, hash:/var/spool/postfix/plesk/virtual virtual_mailbox_maps = , hash:/var/spool/postfix/plesk/vmailbox transport_maps = , hash:/var/spool/postfix/plesk/transport smtpd_tls_security_level = may smtp_tls_security_level = may smtp_use_tls = no smtpd_timeout = 3600s smtpd_proxy_timeout = 3600s disable_vrfy_command = yes smtpd_sender_restrictions = check_sender_access hash:/var/spool/postfix/plesk/blacklists, permit_sasl_authenticated smtpd_client_restrictions = permit_mynetworks, permit_sasl_authenticated smtp_send_xforward_command = yes smtpd_authorized_xforward_hosts = 127.0.0.0/8 [::1]/128 smtpd_sasl_auth_enable = yes smtpd_recipient_restrictions = permit_mynetworks, permit_sasl_authenticated, reject_unauth_destination virtual_mailbox_base = /var/qmail/mailnames virtual_uid_maps = static:30 virtual_gid_maps = static:31 smtpd_milters = , inet:127.0.0.1:12768 inet:127.0.0.1:12345 sender_dependent_default_transport_maps = hash:/var/spool/postfix/plesk/sdd_transport_maps virtual_transport = plesk_virtual plesk_virtual_destination_recipient_limit = 1 mailman_destination_recipient_limit = 1 virtual_mailbox_limit = 0 smtpd_tls_mandatory_protocols = TLSv1 TLSv1.1 TLSv1.2 smtpd_tls_protocols = TLSv1 TLSv1.1 TLSv1.2 smtpd_tls_ciphers = medium smtpd_tls_mandatory_ciphers = medium tls_medium_cipherlist = HIGH:!aNULL:!MD5 message_size_limit = 102400000 milter_connect_macros = j {daemon_name} {client_connections} {client_addr} {client_ptr} v milter_default_action = accept ______________________________________________________________ master.cf # # Postfix master process configuration file. For details on the format # of the file, see the master(5) manual page (command: "man 5 master" or # on-line: http://www.postfix.org/master.5.html). # # Do not forget to execute "postfix reload" after editing this file. # # ========================================================================== # service type private unpriv chroot wakeup maxproc command + args # (yes) (yes) (yes) (never) (100) # ========================================================================== smtp inet n - - - - smtpd #smtp inet n - - - 1 postscreen #smtpd pass - - - - - smtpd #dnsblog unix - - - - 0 dnsblog #tlsproxy unix - - - - 0 tlsproxy #submission inet n - - - - smtpd # -o syslog_name=postfix/submission # -o smtpd_tls_security_level=encrypt # -o smtpd_sasl_auth_enable=yes # -o smtpd_reject_unlisted_recipient=no # -o smtpd_client_restrictions=$mua_client_restrictions # -o smtpd_helo_restrictions=$mua_helo_restrictions # -o smtpd_sender_restrictions=$mua_sender_restrictions # -o smtpd_recipient_restrictions= # -o smtpd_relay_restrictions=permit_sasl_authenticated,reject # -o milter_macro_daemon_name=ORIGINATING #smtps inet n - - - - smtpd # -o syslog_name=postfix/smtps # -o smtpd_tls_wrappermode=yes # -o smtpd_sasl_auth_enable=yes # -o smtpd_reject_unlisted_recipient=no # -o smtpd_client_restrictions=$mua_client_restrictions # -o smtpd_helo_restrictions=$mua_helo_restrictions # -o smtpd_sender_restrictions=$mua_sender_restrictions # -o smtpd_recipient_restrictions= # -o smtpd_relay_restrictions=permit_sasl_authenticated,reject # -o milter_macro_daemon_name=ORIGINATING #628 inet n - - - - qmqpd cleanup unix n - - - 0 cleanup #qmgr unix n - n 300 1 oqmgr tlsmgr unix - - - 1000? 1 tlsmgr rewrite unix - - - - - trivial-rewrite bounce unix - - - - 0 bounce defer unix - - - - 0 bounce trace unix - - - - 0 bounce verify unix - - - - 1 verify flush unix n - - 1000? 0 flush proxymap unix - - n - - proxymap proxywrite unix - - n - 1 proxymap smtp unix - - - - - smtp relay unix - - - - - smtp # -o smtp_helo_timeout=5 -o smtp_connect_timeout=5 showq unix n - - - - showq error unix - - - - - error retry unix - - - - - error discard unix - - - - - discard local unix - n n - - local virtual unix - n n - - virtual lmtp unix - - - - - lmtp anvil unix - - - - 1 anvil scache unix - - - - 1 scache # # ==================================================================== # Interfaces to non-Postfix software. Be sure to examine the manual # pages of the non-Postfix software to find out what options it wants. # # Many of the following services use the Postfix pipe(8) delivery # agent. See the pipe(8) man page for information about ${recipient} # and other message envelope options. # ==================================================================== # # maildrop. See the Postfix MAILDROP_README file for details. # Also specify in main.cf: maildrop_destination_recipient_limit=1 # maildrop unix - n n - - pipe flags=DRhu user=vmail argv=/usr/bin/maildrop -d ${recipient} # # ==================================================================== # # Recent Cyrus versions can use the existing "lmtp" master.cf entry. # # Specify in cyrus.conf: # lmtp cmd="lmtpd -a" listen="localhost:lmtp" proto=tcp4 # # Specify in main.cf one or more of the following: # mailbox_transport = lmtp:inet:localhost # virtual_transport = lmtp:inet:localhost # # ==================================================================== # # Cyrus 2.1.5 (Amos Gouaux) # Also specify in main.cf: cyrus_destination_recipient_limit=1 # #cyrus unix - n n - - pipe # user=cyrus argv=/cyrus/bin/deliver -e -r ${sender} -m ${extension} ${user} # # ==================================================================== # Old example of delivery via Cyrus. # #old-cyrus unix - n n - - pipe # flags=R user=cyrus argv=/cyrus/bin/deliver -e -m ${extension} ${user} # # ==================================================================== # # See the Postfix UUCP_README file for configuration details. # uucp unix - n n - - pipe flags=Fqhu user=uucp argv=uux -r -n -z -a$sender - $nexthop!rmail ($recipient) # # Other external delivery methods. # ifmail unix - n n - - pipe flags=F user=ftn argv=/usr/lib/ifmail/ifmail -r $nexthop ($recipient) bsmtp unix - n n - - pipe flags=Fq. user=bsmtp argv=/usr/lib/bsmtp/bsmtp -t$nexthop -f$sender $recipient scalemail-backend unix - n n - 2 pipe flags=R user=scalemail argv=/usr/lib/scalemail/bin/scalemail-store ${nexthop} ${user} ${extension} mailman unix - n n - - pipe flags=R user=list:list argv=/usr/lib/plesk-9.0/postfix-mailman ${nexthop} ${user} ${recipient} plesk_virtual unix - n n - - pipe flags=DORhu user=popuser:popuser argv=/usr/lib/plesk-9.0/postfix-local -f ${sender} -d ${recipient} -p /var/qmail/mailnames pickup fifo n - - 60 1 pickup plesk_saslauthd unix y y y - 1 plesk_saslauthd status=5 listen=6 dbpath=/plesk/passwd.db qmgr fifo n - n 1 1 qmgr smtps inet n - - - - smtpd -o smtpd_tls_wrappermode=yes plesk-89.163.212.5- unix - n n - - smtp -o smtp_bind_address=89.163.212.5 -o smtp_bind_address6= -o smtp_address_preference=ipv4 plesk-89.163.142.29- unix - n n - - smtp -o smtp_bind_address=89.163.142.29 -o smtp_bind_address6= -o smtp_address_preference=ipv4 plesk-89.163.142.28- unix - n n - - smtp -o smtp_bind_address=89.163.142.28 -o smtp_bind_address6= -o smtp_address_preference=ipv4

2 1

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