Moderation requests flood after migrating from MM2 to MM3 on Debian
Dear all,
this may be of course related to Debian version of Mailman3 (currently 3.3.3, Debian 11 Bullseye), but I hope someone may point me towards a direction in which i should start digging in order to resolve this issue.
I have recently migrated two lists from perfectly working MM2 to MM3 using the migration approach outlines in the documentation (https://docs.mailman3.org/en/latest/migration.html), i.e.
a) mailman create foo-list@example.com b) mailman import21 foo-list@example.com /path/to/mailman2/foo-list/config.pck c) python manage.py hyperkitty_import -l foo-list@example.com $var_prefix/archives/private/foo-list.mbox/foo-list.mbox d) python manage.py update_index_one_list foo-list@example.com
I do not have the hyperkitty working properly, but that is not important as for now. What is however important, is that for both lists mailman3 generates approximately every minute a message that it tries to send to the list and the message is catched by the mailman and requires moderation. As a result, I have some 1000 moderation requests for each of the list every day. The requests are mostly of the type
Sender: foo-list-owner@example.com
Subject: foo-list@example.com_post_from_foo-list-owner@example.com_requires_approval
Reason: The message is not from a list memberI can see also some weird handling of bounced messages (if we try to send an e-mail that bounces, in my opinion it should be silently discarded or sent to foo-list-owner@example.com).
Sender: microsoftexchange329e71ec88ae4615bbc36ab6ce41109e@exampledomain.onmicrosoft.com
Subject: Undeliverable:_[FOO]_Meeting
Reason: The message is not from a list memberI have a strong feeling that I misconfigured MM3 somewhere or that I did not do my homework properly and failed to read relevant parts of the documentation. Any ideas where to start?
Thanks a lot!
Jan
On 10/13/22 13:33, grmpf@mm.st wrote:
What is however important, is that for both lists mailman3 generates approximately every minute a message that it tries to send to the list and the message is catched by the mailman and requires moderation. As a result, I have some 1000 moderation requests for each of the list every day. The requests are mostly of the type
Sender: foo-list-owner@example.com Subject: foo-list@example.com_post_from_foo-list-owner@example.com_requires_approval Reason: The message is not from a list member
There is something misconfigured here. What are the settings for the list's owners and moderators?
The above message is a notice to the owners and moderators about the held post. It should not be sent to the list.
I can see also some weird handling of bounced messages (if we try to send an e-mail that bounces, in my opinion it should be silently discarded or sent to foo-list-owner@example.com).
There have been some small changes in bounce processing since 3.3.3 (see https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/NEWS.h...), but they shouldn't affect this.
The envelope sender of messages from a list is listname-bounces@list.domain. Thus bounces should be returned to that address and processed by Mailman's bounce runner. There are several list settings that control this that are similar to MM 2.1. If the list's process_bounces setting is False, the bounce is ignored. If true, bounces are scored and delivery to the bouncing user is ultimately disabled and the user ultimately unsubscribed as in MM 2.1
I'm just guessing here, but your issues could be explained if your MTA
is somehow dropping the -xxx part of the recipient when delivering a
message to listname-xxx@example.com so all messages get delivered to the
list. This can happen for example if your MTA is exim and your exim
mailman transport does not have rcpt_include_affixes = true.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (2)
-
grmpf＠mm.st -
Mark Sapiro