On 5/21/25 9:31 AM, Steve Bachinsky wrote:
Hi. We have noticed some posts being held for moderation (even though user has 
permission to post to list) and Mailman reports:

   moderation_reasons: ['Message has implicit destination’]

The lists are configured for “require_explicit_destination”. However, the email 
address of the list is clearly in the CC: header of the email (no alias or 
subdomain). Is there some other reason why Mailman would hold an email for 
moderation with the reason of “implicit destination”?


No. The rule looks at all the addresses in To:, Cc:, Resent-To: and Resent-Cc: headers using standard Python email library methods, lower cases them any if any lc address matches the list posting address or an acceptable_alias, the rule misses, i.e. doesn't hold the message.

There is no other reason.

This moderation is not consistent for same list and poster. The emails come 
from a large domain with multiple load-balancing email servers. I suspect that 
it may be something with one or more of the servers being misconfigured, but 
unable to see anything obvious from the headers and confused why Mailman states 
the reason to be implicit destination when that does not seem to be the cause.

I'm sorry, but I have no idea why this is happening. If the headers of the held message contain the explicit address, I have no clue as to why it is held for that reason. Maybe there is some other reason why the message is held, and the reason is misstated, but I don't know how that could happen.

--
Mark Sapiro <m...@msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan
_______________________________________________
Mailman-users mailing list -- mailman-users@mailman3.org
To unsubscribe send an email to mailman-users-le...@mailman3.org
https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
Archived at: 
https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/VXB5D3JY2LCTGETB6HOGQN3WOVNYMCJQ/

This message sent to arch...@mail-archive.com

Reply via email to