Hi All,
we have moved to Mailman3 from Mailman2 recently, and have a quite strange problem:
Every message sent to owners is forwarded to the lists instead of the owner's mail address.
So for example if a non-member sends a message to MYLIST@MYDOMAIN.COM, then a notification appears on MYLIST (and all members receive it, the message also appears in the archive) instead of sending it to the private address of the owner set on the web interface. I found no obvious error either in mailman.log, smtp.log or the MTA's logs. This problem can cause a storm of mails as per default the owner is not allowed to send a message to a member-only list so each notifications generates a new notification. This storm is mitigated temporarily by accepting everything from the owner in a non-member setting, but it is only a workaround. I want mails sent to MYLIST-owner@MYDOMAIN.COM to be forwarded to the real owner instead of the list. The same is true for MYLIST-admin@MYDOMAIN.COM, and probably for the other administrative addresses.
We are using GNU Mailman 3.2.1 (La Villa Strangiato) from the Debian Buster repo. As MTA we use exim4 (running on the same machine as Mailman), and have Amavisd on a separate machine for spam filtering.
How can I test what happens to mails sent to the owner inside Mailman? Any help or tips on debugging this issue would be highly appreciated.
Best regards,
Tamas
Here is an anonymized header for such a message:
From MYLIST-bounces@MYDOMAIN.COM Mon Oct 21 21:13:59 2019 Return-path: <MYLIST-bounces@MYDOMAIN.COM> Envelope-to: MYADDRESS@MYDOMAIN.COM Delivery-date: Mon, 21 Oct 2019 21:13:59 +0200 Received: from [SPAMFILTER] (helo=localhost) by MAILSERVER.MYDOMAIN.COM with esmtp (Exim 4.92) (envelope-from <MYLIST-bounces@MYDOMAIN.COM>) id 1iMd7u-0007pv-VR; Mon, 21 Oct 2019 21:13:59 +0200 X-Virus-Scanned: by amavis-dc Received: from MAILSERVER.MYDOMAIN.COM ([MAILSERVER-LOCAL-IP]) by localhost (spamfilter.MYDOMAIN.COM [SPAMFILTER]) (amavisd-new, port 10023) with ESMTP id Pe6CPG7d_0VR; Mon, 21 Oct 2019 21:13:57 +0200 (CEST) Received: from MAILSERVER2.MYDOMAIN.COM ([MAILSERVER-PUBLIC-IP] helo=MAILSERVER.MYDOMAIN.COM) by MAILSERVER.MYDOMAIN.COM with esmtp (Exim 4.92) (envelope-from <MYLIST-bounces@MYDOMAIN.COM>) id 1iMd7t-0007pn-Mu; Mon, 21 Oct 2019 21:13:57 +0200 Received: from MAILSERVER2.MYDOMAIN.COM ([MAILSERVER-PUBLIC-IP] helo=MAILSERVER.MYDOMAIN.COM) by MAILSERVER.MYDOMAIN.COM with esmtp (Exim 4.92) (envelope-from <MYLIST-bounces@MYDOMAIN.COM>) id 1iMd7r-0007pR-JZ for MYLIST-owner@MYDOMAIN.COM; Mon, 21 Oct 2019 21:13:55 +0200 From: MYLIST-owner@MYDOMAIN.COM To: MYLIST-owner@MYDOMAIN.COM MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1338746665924884909==" Message-ID: <157168523467.30989.13607822853875106726@MAILSERVER.MYDOMAIN.COM> Date: Mon, 21 Oct 2019 21:13:54 +0200 Precedence: bulk X-Mailman-Version: 3.2.1 Message-ID-Hash: UWYSMZDJO3ZXNBKY6GE6AS6FBLCZL6BG X-Message-ID-Hash: UWYSMZDJO3ZXNBKY6GE6AS6FBLCZL6BG X-MailFrom: MYLIST-bounces@MYDOMAIN.COM X-Mailman-Rule-Hits: nonmember-moderation X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation Subject: [MYLIST] MYLIST@MYDOMAIN.COM post from ... requires approval List-Id: Name of the List <MYLIST.MYDOMAIN.COM> Archived-At: <https://MYDOMAIN.COM/hyperkitty/list/MYLIST@MYDOMAIN.COM/message/UWYSMZDJO3ZXNBKY6GE6AS6FBLCZL6BG/> List-Archive: <https://MYDOMAIN.COM/hyperkitty/list/MYLIST@MYDOMAIN.COM/> List-Help: <mailto:MYLIST-request@MYDOMAIN.COM?subject=help> List-Post: <mailto:MYLIST@MYDOMAIN.COM> List-Subscribe: <mailto:MYLIST-join@MYDOMAIN.COM> List-Unsubscribe: <mailto:MYLIST-leave@MYDOMAIN.COM>
--===============1338746665924884909== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit
As list administrator, your authorization is requested for the following mailing list posting:
List: MYLIST@MYDOMAIN.COM
From: ...
Subject: ...The message is being held because:
The message is not from a list memberAt your convenience, visit your dashboard to approve or deny the request. ...
On 10/22/19 2:20 AM, Tamas HOLCZER via Mailman-users wrote:
Hi All,
we have moved to Mailman3 from Mailman2 recently, and have a quite strange problem:
Every message sent to owners is forwarded to the lists instead of the owner's mail address. ... We are using GNU Mailman 3.2.1 (La Villa Strangiato) from the Debian Buster repo. As MTA we use exim4 (running on the same machine as Mailman), and have Amavisd on a separate machine for spam filtering.
This may be an exim configuration issue. You can stop the mail from being delivered to the list by ensuring the Postorius Settings - Message Acceptance -> Acceptable aliases is empty and Settings - Message Acceptance -> Require Explicit Destination is Yes. This will cause the messages to -owner, etc to be held.
First ensure exim, particularly the router for list messages is configured as in <https://mailman.readthedocs.io/en/latest/src/mailman/docs/mta.html#exim4-configuration>.
From MYLIST-bounces@MYDOMAIN.COM Mon Oct 21 21:13:59 2019 Return-path: <MYLIST-bounces@MYDOMAIN.COM> Envelope-to: MYADDRESS@MYDOMAIN.COM Delivery-date: Mon, 21 Oct 2019 21:13:59 +0200 Received: from [SPAMFILTER] (helo=localhost) by MAILSERVER.MYDOMAIN.COM with esmtp (Exim 4.92) (envelope-from <MYLIST-bounces@MYDOMAIN.COM>) id 1iMd7u-0007pv-VR; Mon, 21 Oct 2019 21:13:59 +0200 X-Virus-Scanned: by amavis-dc Received: from MAILSERVER.MYDOMAIN.COM ([MAILSERVER-LOCAL-IP]) by localhost (spamfilter.MYDOMAIN.COM [SPAMFILTER]) (amavisd-new, port 10023) with ESMTP id Pe6CPG7d_0VR; Mon, 21 Oct 2019 21:13:57 +0200 (CEST) Received: from MAILSERVER2.MYDOMAIN.COM ([MAILSERVER-PUBLIC-IP] helo=MAILSERVER.MYDOMAIN.COM) by MAILSERVER.MYDOMAIN.COM with esmtp (Exim 4.92) (envelope-from <MYLIST-bounces@MYDOMAIN.COM>) id 1iMd7t-0007pn-Mu; Mon, 21 Oct 2019 21:13:57 +0200
It seems the issue occurs here. The Received: header below is the receipt of the message from Mailman to MYLIST-owner. That header clearly says the envelope recipient is MYLIST-owner@MYDOMAIN.COM.
Then the header above looks like the delivery of the message from the Mailman list to one or more list members. What we don't see is the intermediate step of LMTP delivery of the message to Mailman's LMTP server. That delivery must have had envelope recipient MYLIST@MYDOMAIN.COM rather than MYLIST-owner@MYDOMAIN.COM
I think what's missing is rcpt_include_affixes = true in the exim
transport for Mailman.
Received: from MAILSERVER2.MYDOMAIN.COM ([MAILSERVER-PUBLIC-IP] helo=MAILSERVER.MYDOMAIN.COM) by MAILSERVER.MYDOMAIN.COM with esmtp (Exim 4.92) (envelope-from <MYLIST-bounces@MYDOMAIN.COM>) id 1iMd7r-0007pR-JZ for MYLIST-owner@MYDOMAIN.COM; Mon, 21 Oct 2019 21:13:55 +0200 From: MYLIST-owner@MYDOMAIN.COM To: MYLIST-owner@MYDOMAIN.COM
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (2)
-
Mark Sapiro -
Tamas HOLCZER