- Mailman-users - lists.mailman3.org

exim4 + mailman3 lmtp failure
by Thomas Drillich 10 May '20

10 May '20

Hello, I tried to setup exim4 + mailman3 but it seems to stuck at lmtp delivery of mailman3. Could you give me a hint, to detect the reason of failure ? greetings Thomas ---- returned message --- This message was created automatically by mail delivery software. A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed: seebruecke(a)listen.td3.eu all hosts for 'listen.td3.eu' have been failing for a long time (and retry time not reached) Reporting-MTA: dns; detroit.drillich.net Action: failed Final-Recipient: rfc822;seebruecke(a)listen.td3.eu Status: 5.0.0 ----------------------------------------------------------- >exim -bv -d+all seebruecke(a)listen.td3.eu ... 19:45:02.715 32200 listen.td3.eu in "+mm_domains"? yes (matched "+mm_domains") 19:45:02.715 32200 checking require_files 19:45:02.715 32200 ┌considering: /var/lib/mailman3//lists/${local_part}.${domain} 19:45:02.715 32200 ├──expanding: /var/lib/mailman3//lists/${local_part}.${domain} 19:45:02.715 32200 └─────result: /var/lib/mailman3//lists/seebruecke.listen.td3.eu 19:45:02.715 32200 file check: /var/lib/mailman3//lists/${local_part}.${domain} 19:45:02.715 32200 expanded file: /var/lib/mailman3//lists/seebruecke.listen.td3.eu 19:45:02.715 32200 stat() yielded 0 19:45:02.715 32200 calling mailman3_router router 19:45:02.715 32200 mailman3_router router called for seebruecke(a)listen.td3.eu 19:45:02.715 32200 domain = listen.td3.eu 19:45:02.715 32200 set transport mailman3_transport 19:45:02.715 32200 queued for mailman3_transport transport: local_part = seebruecke 19:45:02.715 32200 domain = listen.td3.eu 19:45:02.715 32200 errors_to=NULL 19:45:02.715 32200 domain_data=NULL localpart_data=NULL 19:45:02.715 32200 routed by mailman3_router router 19:45:02.715 32200 envelope to: seebruecke(a)listen.td3.eu 19:45:02.715 32200 transport: mailman3_transport seebruecke(a)listen.td3.eu router = mailman3_router, 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 -- mit freundlichem Gruss -- regards Thomas Drillich Heugasse 4 / D-55116 Mainz / Germany fon +49-6131-570-2621 mobil +49-162-469-5875

3 6

Handling of Mail from non-subscribers
by Peter Adebahr 09 May '20

09 May '20

Hi *, I have a fresh setup of MM3 on Ubuntu 20, installed by apt-get. It seems to be running fine so far, except for some (to me) strange behaviour: When posting to the list as a non-subscriber, I see the mail coming in on mailman's smtp.log, then it vanishes. No notice of this mail being hold is sent to the sender, no notice to the moderator, and logging into Postorius as owner of the list, it is not showing up in "Held messages" "Hold for moderation" has been set. Any idea how to debug this will be welcome - thank you :) Best regards, Peter

2 7

PSA: Avoiding spam-scanning outgoing mailman3 mail
by Mark Dadgar 08 May '20

08 May '20

So I integrated SpamAssassin into my mailman3 server the other day, using the ubuntu packages which implement the “standard” SpamAssassin install with a filter on port 25 and re-injection using /usr/sbin/sendmail. From postfix/master.cf: # ========================================================================== # service type private unpriv chroot wakeup maxproc command + args # (yes) (yes) (yes) (never) (100) # ========================================================================== smtp inet n - n - 10 smtpd -o content_filter=spamassassin spamassassin unix - n n - - pipe user=debian-spamd argv=/usr/bin/spamc -f -e /usr/sbin/sendmail -oi -f ${sender} ${recipient} The problem there, of course, is that mailman3 traffic gets scanned twice: once on the way in from the original sender and once on the way out as mailman3 duplicates it to list recipients. This is because out-of-the-box mailman3 tends to be configured to re-inject list email via port 25, which is scanning for spam on incoming email. This is horribly inefficient, obviously, and gets worse the bigger your mailing list is. Given that it’s written in Perl, SpamAssassin isn’t the most efficient thing in the first place. Anyway, I got literally zero hits on solving this when I googled it, so here’s mine to save future mailman3+SpamAssassin users some grief. The easy fix was to edit the [mta] setting in mailman.cfg to deliver email via the submit port instead, which has no filtering applied to it: smtp_host: localhost # using the submit port bypasses spamassassin filtering on outgoing list email smtp_port: 587 smtp_user: mm3send <— I created this user for this purpose smtp_pass: <password-for-mm3send-user> This works great and can be applied to any email filtering. FYI. - Mark ----- mark(a)pdc-racing.net | 408-348-2878

2 2

Link in the top-left corner of Hyperkitty
by Seth Seeger 08 May '20

08 May '20

Hello, There is a link to the root of Hyperkitty in the top left corner of my Hyperkitty pages. It links to the correct domain, but the text isn’t right - it’s the first domain name I was using at the beginning of my install for testing. I’d like to update it, but can’t find what to change. Thanks, Seth

3 7

Can it work on FreebSD
by Peter Fraser 08 May '20

08 May '20

Hi All I would really be interested in getting this working of FreeBSD. I find the BSD’s to be very stable and easy to maintain. Please could anyone point me to any document or suggestions to get it working on FreeBSD? Much Appreciated. Regards SI Sent from [1]Mail for Windows 10 References 1. https://go.microsoft.com/fwlink/?LinkId=550986

3 2

Post log?
by Mark Dadgar 06 May '20

06 May '20

Is there the equivalent of the post log from mailman 2.x available? I see every logging option but that one listed here: https://mailman.readthedocs.io/en/latest/src/mailman/config/docs/config.htm… <https://mailman.readthedocs.io/en/latest/src/mailman/config/docs/config.htm…> That was a handy way to track list traffic statistics and I was hoping to munge up the old mm_stats script to use the mailman3 logging format. I am running the ubuntu 3.2.2-based package. Thanks, as always! - Mark ----- mark(a)pdc-racing.net | 408-348-2878

2 2

How to remove a nonmember from a list
by skenny＠scss.tcd.ie 05 May '20

05 May '20

Hi, I've been banging my head against the proverbial wall for more than a day trying to remove nonmembers from a list (I am a Mailman3 and Python novice so that might account for something, but anyway ...) According to https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…, it should be possible to do: MailingList.remove_role('nonmember', 'email_address(a)example.com') However I can't get this to work. I think I have manage to track down all the required imports. This is what I see: TypeError: remove_role() missing 1 required positional argument: 'address' More digging in the docs seems to indicate that a third parameter is required - "self". At this point though I am way out of my depth, and would appreciate any guidance. Thanks very much Stephen Kenny

4 26

HyperKitty Question
by Samir Faci 05 May '20

05 May '20

Okay, I have mailman3 working to allow me to send/receive emails. postorius seems to be working fine. My only issue seems to be with hyperkitty saving the archive. postorius seems to be working fine. Hyperkitty on the other hand is failing. I have nginx running with multiple website being serviced from the same server. I updated the config where port 80 gets redirected to SSL. I tried setting mailman3-hyperkitty.conf to both: base_url: http://localhost/hyperkitty/ base_url: https://lists.domain.com/hyperkitty/ But neither seem to be working. Does hyperkitty require traffic to be going over port 80? -- Thank you Samir Faci https://keybase.io/csgeek

2 2

Re: Installation Wooes
by Mark Sapiro 04 May '20

04 May '20

On 5/3/20 8:13 PM, Samir Faci wrote: > > Postfix Failed Logs. > > May 4 03:07:36 lists postfix/smtpd[1968155]: disconnect from > unknown[198.199.98.177] ehlo=1 mail=1 rcpt=0/1 rset=1 quit=1 commands=4/5 > May 4 03:07:36 lists postfix/smtpd[1968155]: connect from > unknown[198.199.98.177] > May 4 03:07:36 lists postfix/smtpd[1968155]: 745B31473C6: > client=unknown[198.199.98.177] > May 4 03:07:36 lists postfix/cleanup[1968158]: 745B31473C6: > message-id=<158856165549.136760.840427238489827082@lists> > May 4 03:07:36 lists postfix/qmgr[1964759]: 745B31473C6: > from=<booh-bounces(a)lists.domain.org So mailman and Postfix are on different machines. That may complicate things, but > <mailto:booh-bounces@lists.domain.org>>, size=5474, nrcpt=1 (queue active) > May 4 03:07:36 lists postfix/smtpd[1968155]: disconnect from > unknown[198.199.98.177] ehlo=1 mail=1 rcpt=1 data=1 quit=1 commands=5 > May 4 03:07:36 lists postfix/lmtp[1968159]: 745B31473C6: > to=<booh-owner(a)lists.domain.org <mailto:booh-owner@lists.domain.org>>, > relay=lists.domain.org <http://lists.domain.org>[198.199.98.177]:8024, > delay=0.03, delays=0/0/0/0.02, dsn=2.0.0, status=sent (250 Ok) This was a successful delivery. > May 4 03:07:36 lists postfix/qmgr[1964759]: 745B31473C6: removed > May 4 03:07:38 lists postfix/smtpd[1968155]: connect from > unknown[198.199.98.177] > May 4 03:07:38 lists postfix/smtpd[1968155]: NOQUEUE: reject: RCPT from > unknown[198.199.98.177]: 554 5.7.1 <csgeek(a)domain.com > <mailto:csgeek@domain.com>>: Relay access denied; > from=<booh-bounces+csgeek=domain.com(a)lists.domain.org > <mailto:domain.com@lists.domain.org>> to=<csgeek(a)domain.com > <mailto:csgeek@domain.com>> proto=ESMTP helo=<[127.0.1.1]> You are sending from a remote machine 198.199.98.177 to a presumably remote domain domain.com so relay access is denied as it should be. You need to add 198.199.98.177 to mynetworks in Postfix. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 6

Re: Installation Wooes
by Mark Sapiro 04 May '20

04 May '20

On 5/3/20 8:43 PM, Samir Faci wrote: > Inline. > > On Sun, May 3, 2020, 20:32 Mark Sapiro <mark(a)msapiro.net > <mailto:mark@msapiro.net>> wrote: > > You are sending from a remote machine 198.199.98.177 to a presumably > remote domain domain.com <http://domain.com> so relay access is > denied as it should be. > > You need to add 198.199.98.177 to mynetworks in Postfix. > > > I can but domain.com <http://domain.com> is basically my Gmail I just > regex-ed the logs. If that's the fix is have to add every recepients > domain to mynetworks. You absolutely don't want to do that. The log entry is confusing. Between your munging domains and my MUA adding mailto: links to every email address, it's a mess. Let's try again: May 4 03:07:38 lists postfix/smtpd[1968155]: NOQUEUE: reject: RCPT from unknown[198.199.98.177]: 554 5.7.1 <csgeek(a)domain.com>: Relay access denied; from=<booh-bounces+csgeek=domain.com(a)lists.domain.org> to=<csgeek(a)domain.com> proto=ESMTP helo=<[127.0.1.1]>. This says Postfix received a RCPT command from 98.199.98.177. It looks like it comes from Mailman, i.e., the envelope sender loogs like a Mailman VERPed address <booh-bounces+csgeek=domain.com(a)lists.domain.org> for a message to <csgeek(a)domain.com> and that is the envelope recipient and the sender identified itself in EHLO as [127.0.1.1]. So Postfix thinks it is asked to relay from 98.199.98.177 to domain.com. Note that 98.199.98.177 is a Comcast network IP. It has nothing to do with gmail. So is the connect comes from Mailman on the Postfix machine, why does Postfix think it comes from 98.199.98.177. That's the issue. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 0