- Mailman-users - lists.mailman3.org

Mailman only send some release messages to the subscribers
by Henrik Rasmussen 28 Sep '17

28 Sep '17

I have three list admins each maintaining one list, thus three lists: E, H and S. All reports that some mails they release from Held messages are sent, some isn't. In the logs (Mailman smtp.log and postfix log I can confirm that at least one of the lists (E) sent out another message to 559 recips at Sep 26 09:31:12 201 (UTC+2) so something is working. The admin of list E explains that she have released mails that came out, but some mails isn't sent when she reases them. Among others a mail she released Sep 26 09:38. I can also see in the Mailman Postfix log that Mailman received a mail from the Admin's e-mail address sender(a)foo.bar. Sep 26 09:38:49 postfix postfix/smtpd[5527]: D8E6D1109026: client=gateway[172.19.199.1] Sep 26 09:38:49 postfix postfix/cleanup[6076]: D8E6D1109026: message-id=<E7657360D6CFE64DBAC4E5D158511918873690FB(a)mailserver.foo.bar> Sep 26 09:38:49 postfix postfix/qmgr[139]: D8E6D1109026: from=<sender(a)foo.bar>, size=19589, nrcpt=1 (queue active) Sep 26 09:38:49 postfix postfix/lmtp[6077]: D8E6D1109026: to=<s(a)listserver.foo.bar>, relay=172.19.199.2[172.19.199.2]:8024, delay=0.03, delays=0.01/0.01/0/0.01, dsn=2.0.0, status=sent (250 Ok) Sep 26 09:38:49 postfix postfix/qmgr[139]: D8E6D1109026: removed I cannot find the mail-id in the Mailman smtp.log, however in the smtp.log I found that the mail was received Sep 26 09:38:49 2017 (32) Peer: ('172.19.199.5', 49238) Sep 26 09:38:49 2017 (32) ('172.19.199.5', 49238) handling connection Sep 26 09:38:49 2017 (32) ('172.19.199.5', 49238) Data: b'LHLO mailgateway.foo.bar' Sep 26 09:38:49 2017 (32) ('172.19.199.5', 49238) Data: b'MAIL FROM:<sender(a)foo.bar>' Sep 26 09:38:49 2017 (32) ('172.19.199.5', 49238) sender: sender(a)foo.bar Sep 26 09:38:49 2017 (32) ('172.19.199.5', 49238) Data: b'RCPT TO:<s(a)listserver.foo.bar>' Sep 26 09:38:49 2017 (32) ('172.19.199.5', 49238) recip: s(a)listserver.foo.bar Sep 26 09:38:49 2017 (32) ('172.19.199.5', 49238) Data: b'DATA' Sep 26 09:38:49 2017 (32) ('172.19.199.5', 49238) Data: b'QUIT' Sep 26 09:38:49 2017 (32) ('172.19.199.5', 49238) connection lost Sep 26 09:38:49 2017 (32) Connection lost during _handle_client() I don't see any release of the held mail not that it was sent out. Two hours later I see a a log message about a notification mail to the admin that another mail had been held, but not anything about the released mail neither in thge smtp.log nor the postfix log. I don't know why it only works sometimes. -- Henrik Rasmussen <her(a)adm.ku.dk<mailto:her@adm.ku.dk>> University of Copenhagen, Danmark

1 2

mailman-cli tools
by Dmitry Makovey 27 Sep '17

27 Sep '17

I've come across mailman-cli docs: http://mailman-cli.readthedocs.io/en/latest/src/mailmanclient/cli/docs/usin… yet I cannot figure out what's the official source for the installation. Rabbit hole of links lead me to https://github.com/rajeevs1992/mailmancli which suggests: sudo pip install mailman.client and that doesn't work. I also did: pip install mailmanclient in hopes that it comes with CLI tools, but it looks like it is only the library. Am I looking in wrong places or is it that mailman3 cli tools are "not there"? -- Sr System and DevOps Engineer SoM IRT

3 5

HyperKitty: Thread matching query does not exist
by C. R. Oldham 26 Sep '17

26 Sep '17

Greetings, I have an active list for which I am trying to debug some deliverability issues. When a user tells me that folks aren't getting their postings, I check the archives first. In this case, I am getting a traceback saying "thread matching query does not exist" when I try to go to the HyperKitty page for the list. How can I debug this? I am using Mailman 3 via the Docker containers documented here: https://asynchronous.in/docker-mailman/ The container versions appear to be 0.1. --cro

3 3

Upgrade path
by David Krantz 23 Sep '17

23 Sep '17

Hi. I currently run MM3.0 based on the old bundle installation. It seems to work just fine although with a number of minor and major annoyances that probably have been fixed now. What is the rekommended way to upgrade to the newest version? (newest _usable_ version, of course)? Is it docker-only with a migration from the current solution to a docker based? If so, any ideas or pointers on how to go about this? Cheers // David

2 2

mailman 3 adding extraneous /var/ to pid path?
by Andrew Hodder 21 Sep '17

21 Sep '17

I'm not sure if this is a bug, or if I've configured something I'm unable to find doing this. But when I'm attempting to stop my mailman3 process, I keep getting an extra /var/ appending into the pid path, so it never finds the PID to terminate. Here are some examples, run at different times, some with different -C configs to launch, all worked successfully to start, this is only a problem on the stop.: (venv3) [root@mailman3(on1) venv3]# mailman stop Shutting down Mailman's master runner PID unreadable in: /opt/mailman/venv3/var/master.pid [Errno 2] No such file or directory: '/opt/mailman/venv3/var/master.pid' Is the master even running? (venv3) [root@mailman3(on1) var]# mailman stop Shutting down Mailman's master runner PID unreadable in: /opt/mailman/var/var/master.pid [Errno 2] No such file or directory: '/opt/mailman/var/var/master.pid' (venv3) [root@mailman3(on1) var]# mailman stop Shutting down Mailman's master runner PID unreadable in: /opt/mailman/var/etc/var/var/master.pid [Errno 2] No such file or directory: '/opt/mailman/var/etc/var/var/master.pid' I keep getting around this by creating symlinks to the pid file and then the stop works, but it's getting silly. It seems like mailman just assumes CWD + /var/ + master.pid must be the location. Once I realized this, I found I can do "mailman stop" so long as I'm only in /opt/mailman/ (since it'd then add /var/master.pid). But that seems a little nonsensical. Going to try my hand at using the environment variables MAILMAN_CONFIG_FILE and MAILMAN_VAR_DIR, maybe that will sort this out. But if anyone can explain further, it'd be appreciated. Sincerely, Andrew Hodder Systems Administrator Support Operations, Afilias E-mail: drew(a)afilias.info Phone: +1 416.673.4164 Fax: +1 416.646.1541

4 3

Change Base URI for Mailman 3.1
by Dmitry Makovey 21 Sep '17

21 Sep '17

I'm tinkering with docker container of mailman 3.1 however I'm trying to utilize existing nginx server thus I need to map "/mailman" to mailman-web docker container vs default "/" mapping. Where do I configure base URI for mailman-web ? (quick search of archives and googling didn't yield any positive results thus far) -- Sr System and DevOps Engineer SoM IRT

2 1

Mailman List Lost on URL transfer
by heartsandbones＠zoho.com 20 Sep '17

20 Sep '17

Hello Mailman Forum! I hope you all can help me. I have been banging my head against this issue for weeks. Here’s the scoop: I did a web site redesign for a non-profit. They didn’t mention to me that they had a mailman list associated with the site. When we transferred the url to Squarespace their list quakers(a)sbfriends.org stopped functioning and the administration login link: http://mail.sbfriends.org/mailman/admin/quakers_sbfriends.org results in a “server not found” error. I don’t know how to set up the site so that their mailman list works again. Please tell me exactly what to do to make this work. Let me know if I can provide any additional information to help you help me. This is my first post to this forum, so I hope I’ve done so correctly. Thanks so much! Licity

2 1

Log for outgoing e-mails
by Henrik Rasmussen 20 Sep '17

20 Sep '17

Docker mailman 0.1.1 Where is outgoing e-mails logged? Where can I see who it was sent to? On my test list I subscribed a new member (say recipient(a)hotmail.com) using Mass operation subscription. From another e-mail, not subscribed to the list (say sender(a)example.ku.dk) I sent a mail to the list which was held as expected. The message was logged in /opt/mailman/core/var/logs/smtp.log. When I released the mail, the newcoming member recipient(a)hotmail.com received the mail as expected, but I don’t see any log messages that the mail was sent other than: Sep 20 11:50:52 2017 (34) <6DCC3E5DA06FE346B4DE4876C4F2713D019BB70E39(a)foo.bar> smtp to testlist(a)mailman3.ku.dk for 1 recips, completed in 0.052258968353271484 seconds Sep 20 11:50:52 2017 (34) <6DCC3E5DA06FE346B4DE4876C4F2713D019BB70E39(a)foo.bar> post to testlist(a)mailman3.ku.dk from sender(a)example.ku.dk, 13041 bytes -- Henrik Rasmussen <her(a)adm.ku.dk> University of Copenhagen, Danmark

2 1

restrict sending to owner/moderator
by m.dohmen＠xconnect.de 20 Sep '17

20 Sep '17

Hello, I'd like to restrict message acceptance on a per-list basis to the owner or moderator, so that simple subscribers cannot send messages to the list. But I don't want the owner/moderator having to moderate own messages, so the member setting "hold for moderation" in Postorius isn't applicable. Is there a way to do this?

3 2

Deleting archives
by Henrik Rasmussen 14 Sep '17

14 Sep '17

Docker-mailman 0.1: I have deleted some lists that I used for testing, but Hyperkitty seems to preserve the archives in the Available lists. Clicking on a list archive gets me to the archive of that list (with no posts because I haven't posted anything to the list). The URL is https://[WEBSITE]/hyperkitty/list/[LISTNAME](a)[LISTDOMAIN]/<https://[WEBSITE]/hyperkitty/list/%5bLISTNAME%5d(a)%5bLISTDOMAIN%5d/> (with a (a)), but when I click Manage subscription, the URI changes to https://[WEBSITE]/postorius/lists/[LISTNAME].[LIST<https://[WEBSITE]/postorius/lists/%5bLISTNAME%5d.%5bLIST>DOMAIN/ (with a dot instead of (a) which seems normal behavior) and I get a "Not Found The requested URL /postorius/lists/[LISTNAME]DOT[LISTDOMAIN]/ was not found on this server. " error. Of course I can't manage the subscription for a list I have deleted, but shouldn't the archive for a list be deleted along deleting the list. Henrik Rasmussen

1 1