July 2019 - Mailman-users - lists.mailman3.org

Mailman shell tutorial
by andrew.bernard＠gmail.com 15 Jan '20

15 Jan '20

is there a tutorial or some examples for using the mailman shell? Is there detailed documentation on it? Anything I try to do such as the following fails: $ mailman shell Welcome to the GNU Mailman shell >>> command('mailman shell --details') Traceback (most recent call last): File "<console>", line 1, in <module> NameError: name 'command' is not defined >>> I execute the shell as user mailman and from within the same venv that all the programs run under.

4 5

Default values for new lists
by Sten Aus 11 Jan '20

11 Jan '20

Hi I haven't found out where I could choose or edit default list values (when creating new list). For example I would like that all new lists would be with *private archive* (and change this when it is needed). This is great that I can choose not to advertise list in Index (which I can choose from list creation interface) but I would like to choose other options too. Right now only solution is to create list and then choose Archiving and then select "private archives". Another thing is that I would like to choose default subscription policy to "Moderate". If anyone has encountered this problem, let me know! All the best Sten

4 5

MM3 shunting mails
by Anders Nilsson 03 Jan '20

03 Jan '20

I'm running a Mailman 3.1.0 installation on a CentOS 7 machine. Using RPMs from https://repos.fedorapeople.org/repos/abompard/hyperkitty/el-7/x86_64/ I do have problems with some lists occasionally going into some kind of shunt mode, where alla mails sent to them gets shunted. In the Mailman log I get entries for each shunted email: Mar 17 11:54:11 2017 (6217) Uncaught runner exception: Multiple rows were found for one_or_none() Mar 17 11:54:11 2017 (6217) Traceback (most recent call last): File "/usr/lib/python3.4/site-packages/mailman/core/runner.py", line 171, in _one_iteration self._process_one_file(msg, msgdata) File "/usr/lib/python3.4/site-packages/mailman/core/runner.py", line 264, in _process_one_file keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/lib/python3.4/site-packages/mailman/runners/pipeline.py", line 37, in _dispose process(mlist, msg, msgdata, pipeline) File "/usr/lib/python3.4/site-packages/mailman/core/pipelines.py", line 53, in process handler.process(mlist, msg, msgdata) File "/usr/lib/python3.4/site-packages/mailman/handlers/rfc_2369.py", line 121, in process process(mlist, msg, msgdata) File "/usr/lib/python3.4/site-packages/mailman/handlers/rfc_2369.py", line 70, in process archiver_set = IListArchiverSet(mlist) File "/usr/lib/python3.4/site-packages/zope/component/hookable.py", line 33, in __call__ return self.__implementation(*args, **kw) File "/usr/lib/python3.4/site-packages/zope/component/_api.py", line 156, in adapter_hook return sitemanager.queryAdapter(object, interface, name, default) File "/usr/lib64/python3.4/site-packages/zope/interface/registry.py", line 348, in queryAdapter return self.adapters.queryAdapter(object, interface, name, default) File "/usr/lib/python3.4/site-packages/mailman/database/transaction.py", line 85, in wrapper return function(args[0], config.db.store, *args[1:], **kws) File "/usr/lib/python3.4/site-packages/mailman/model/mailinglist.py", line 607, in __init__ ListArchiver.name == archiver_name).one_or_none() File "/usr/lib64/python3.4/site-packages/sqlalchemy/orm/query.py", line 2733, in one_or_none "Multiple rows were found for one_or_none()") sqlalchemy.orm.exc.MultipleResultsFound: Multiple rows were found for one_or_none() Mar 17 11:54:11 2017 (6217) SHUNTING: 1489748051.1949184+7a59df19c81493cb419306d620376efc0e381819 And so far my Google-fu hasn't been good enough to give me any useful answers to why this happens. If I dump one of the pickles using qfile I cannot see any complaints. Most of the times, if I remove and recreate a failing list and run unshunt the shunted emails get processed and sent. Anyone seen something similar? Regards, Anders Nilsson -- Anders Nilsson, Ph.D. <andersn(a)control.lth.se> Dep. of Automatic Control, Lund University Phone: +46 (0)46 222 87 94, Fax: +46 (0)46 13 81 18 Mob: +46 (0)703 22 57 67

4 4

bounces with empty message-id
by Peter Münster 12 Dec '19

12 Dec '19

Hi, It seems, that mailman bounces the bounces, so that the list-owner never sees them: --8<---------------cut here---------------start------------->8--- postfix/smtpd[12002]: connect from out04.smtpout.orange.fr[193.252.22.213] postfix/smtpd[12002]: 879D6F12E8: client=out04.smtpout.orange.fr[193.252.22.213] postfix/cleanup[11841]: 879D6F12E8: message-id=<> postfix/qmgr[10092]: 879D6F12E8: from=<>, size=4048, nrcpt=1 (queue active) postfix/smtpd[12002]: disconnect from out04.smtpout.orange.fr[193.252.22.213] ehlo=1 mail=1 rcpt=1 data=1 quit=1 commands=5 postfix/lmtp[11846]: 879D6F12E8: to=<test-bounces(a)my-domain.org>, relay=127.0.0.1[127.0.0.1]:8024, delay=0.05, delays=0.04/0/0/0.01, dsn=5.0.0, status=bounced (host 127.0.0.1[127.0.0.1] said: 550 No Message-ID header provided (in reply to end of DATA command)) postfix/qmgr[10092]: 879D6F12E8: removed --8<---------------cut here---------------end--------------->8--- What could I do please, to get the bounces? I would like to use VERP to identify wrong addresses... TIA for any hints, -- Peter

3 8

confirm mail rejected
by Marc Sluiter 29 Sep '19

29 Sep '19

Hi, im trying to setup mailman and have an issue: first my environment: - I’m running postfix etc with "mailcow-dockerized": https://mailcow.github.io/mailcow-dockerized-docs/ - I’m running mailman with "docker-mailman": https://asynchronous.in/docker-mailman/ I got almost everything working (with some configuration modifications, see other mail). The only thing which doesn’t work is conformation mails, they are rejected: In the logs I see that postfix is trying both "liste-confirm+extension@domain" and "liste-confirm@domain" for another lookup map of type mysql (so "recipient_delimiter" is working), but not for the mailman map of type regexp. Just a wild guess, I didn't find anything about it: can it be that “recipient_delimiter" doesn't work for “regexp" maps? For now I worked around this issue by manually modifying the confirm regex in "postfix_lmtp” to /^liste-confirm\+.*(a)domain\.tld$/ Does anyone have an idea why the regexp map isn’t working for me and at least 1 other user (see https://gitlab.com/mailman/mailman/issues/401)? Would my workaround be a long term solution which could be implemented in mailman? That would mean that mailman could work independent of the “recipient_delimiter” setting (or do I oversee something?) Thanks and greetings, Marc

4 4

Hyperkitty reply indent
by Andrew Bernard 16 Aug '19

16 Aug '19

Is there any way the indent in the thread view can be reduced or set to zero? My users are complaining that by the time you have a reply four or five deep the view on a mobile phone leaves only one or two words, because it does not wrap responsively correctly (have I set something wrongly?) Andrew

3 8

exposing Mailman3 API securely
by dancab＠caltech.edu 05 Aug '19

05 Aug '19

I'm working on a container based Mailman3 solution for my university. We have a help desk tool which needs to access the API remotely for creating and deleting Mailman lists. The API will be restricted to a private network, behind a firewall, etc. What is the simplest way to expose the API to an external host? At the moment, I seem to have this partially working via an Apache virtual host configuration which simply proxies via api.example.edu:80 to localhost:8001 on the container. I'm able to remotely use the mailmanclient module for the client.lists, client.system and client.members commands. However running client.domains generates an API connection error. So it seems unstable. Any thoughts or suggestions? Thanks. ---- Dan Caballero Systems Administrator Academic Computing Solutions IMSS - Caltech https://imss.caltech.edu

4 10

Replies unthreading
by Andrew Bernard 01 Aug '19

01 Aug '19

In my new list, I have a user - one of the foundation members, so an important use case - who will not be talked out of using a very old version of Eudora (!) for mail. Replies to threads from that mailer keep sometimes being properly threaded in Hyperkitty and then randomly jumping out into a new thread. This messes up the web view of the threads, and it's not right. Yet the threading appears to be correct in mail programs such as Thunderbird, using the email based interface to the list. Have others seen such behaviour with ancient mailers? Is it the mailer, or is there a known issue with threading the web interface? Looking carefully at message ID's and how they are threaded to examine the behaviour, I can't see what is causing this. Possibly some interaction with other RFC-822 headers? Andrew

3 3

Authenticating against Hyperkitty's DB
by Marvin Gülker 29 Jul '19

29 Jul '19

Hi, inspired by the question about LDAP, I want to ask a related question. We're currently thinking about adding a wiki to our small OSS project, and requiring users to have multiple accounts for the same project is nonsense. We don't have LDAP set up yet, but we do have a running Mailman 3 installation, including Hyperkitty. Thus I thought about whether it's possible to just write some glue script that authenticates against the user information in Hyperkitty's database. Creating an account for Hyperkitty would then be sufficient to get access to the wiki. Could someone give me a hint where and in what format Hyperkitty stores the user information into its database? Marvin -- Blog: https://mg.guelker.eu

2 6

Exim, Mailman3 and missing Message-ID:
by Robert Lister 29 Jul '19

29 Jul '19

Just a note that may help some people. After a bit of a learning curve, managed to get Mailman3 working in Debian 10 using the Debian package. I have mailman3-full + exim4 + apache2 setup: I did quite a lot of testing and getting it working, then when all seemed well, declared success and made it live. As (bad) luck would have it, the very first real message bounced: :-( 2019-07-25 20:53:09 1hqjnY-0005ms-RD <= xxxxxxx(a)ntlworld.com H=cloudi.spamtitan.com [52.26.55.167] P=esmtps X=TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256 CV=no S=7854 DKIM=ntlworld.com 2019-07-25 20:53:09 1hqjnY-0005ms-RD ** mylist(a)lentil.org R=mailman3_router T=mailman3_t H=127.0.0.1 [127.0.0.1]: LMTP error after DATA: 550 No Message-ID header provided 2019-07-25 20:53:09 1hqjnZ-0005mx-3F <= <> R=1hqjnY-0005ms-RD U=Debian-exim P=local S=9222 The user forwarded me the bounce, which contained the original message and headers, and indeed the original message did not contain a Message-ID: header. (Oddly, his message to me reporting the error using the same mail client DID contain a Message-ID: header.) Mail client: X-Mailer: Microsoft Outlook 16.0 So it seems in certain circumstances, Outlook doesn't put a Message-ID: header in its messages. The change from Mailman2.x to Mailman3 means it's now using LMTP to deliver to mailman instead of a local submission seems to have exposed this issue. Exim tries to be helpful for "locally submitted" messages: <https://www.exim.org/exim-html-current/doc/html/spec_html/ch-message_proces…> "12. The Message-ID: header line If a locally-generated or submission-mode incoming message does not contain a Message-ID: or Resent-Message-ID: header line, and the suppress_local_fixups control is not set, Exim adds a suitable header line to the message. If there are any Resent-: headers in the message, it creates Resent-Message-ID:. The id is constructed from Exim's internal message id, preceded by the letter E to ensure it starts with a letter, and followed by @ and the primary host name." However: "Note: Messages received over TCP/IP on the loopback interface (127.0.0.1 or ::1) are not considered to be locally-originated. Exim does not treat the loopback interface specially in any way." Therefore, Mailman3 using LMTP means exim will NOT "fix up" this problem before mailman3 receives the message. My solution for now (apart from telling people not to use old broken Outlook!) is to modify the exim mailman3_transport so that any message with a missing Message-ID: will have one generated by exim before it's passed to LMTP. This reproduces the same behaviour exim uses for locally submitted messages. (headers_remove ensures that we end up only with one Message-ID: header and not two, then we put back either the original Message-ID, or if that's not there, use Exim's ID to generate a new Message-ID header.) Here's an updated version of the example at: https://mailman.readthedocs.io/en/latest/src/mailman/docs/mta.html#exim # /etc/exim4/conf.d/main/25_mm3_macros # The colon-separated list of domains served by Mailman. domainlist mm_domains=list.example.net MM3_LMTP_PORT=8024 # MM3_HOME must be set to mailman's var directory, wherever it is # according to your installation. # debian default is /var/lib/mailman3 MM3_HOME=/opt/mailman/var MM3_UID=list MM3_GID=list ################################################################ # The configuration below is boilerplate: # you should not need to change it. # The path to the list receipt (used as the required file when # matching list addresses) MM3_LISTCHK=MM3_HOME/lists/${local_part}.${domain} # /etc/exim4/conf.d/router/455_mm3_router mailman3_router: driver = accept domains = +mm_domains require_files = MM3_LISTCHK local_part_suffix_optional local_part_suffix = \ -bounces : -bounces+* : \ -confirm : -confirm+* : \ -join : -leave : \ -owner : -request : \ -subscribe : -unsubscribe transport = mailman3_transport # /etc/exim4/conf.d/transport/55_mm3_transport mailman3_transport: driver = smtp protocol = lmtp allow_localhost hosts = localhost port = MM3_LMTP_PORT rcpt_include_affixes = true mailman3_transport: driver = smtp protocol = lmtp allow_localhost hosts = localhost port = MM3_LMTP_PORT rcpt_include_affixes = true headers_remove = message-id headers_add = "Message-ID: ${if def:header_message-id:{$h_message-id:}{<E${message_exim_id}@${qualify_domain}>}}"

4 6