Handling of Mail from non-subscribers
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
On 5/8/20 4:42 PM, Peter Adebahr via Mailman-users wrote:
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.
Set in "Default action to take when a non-member posts to the list"?
If that is the case, find the non-member in Users -> Non-Members and look at the Non-member Options link. What is the "Administration options Moderation" setting? for that non-member?
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On 5/9/20 1:55 AM, Mark Sapiro wrote:
"Hold for moderation" has been set.
Set in "Default action to take when a non-member posts to the list"?
yep
If that is the case, find the non-member in Users -> Non-Members and
it does'nt show up there, "list has no nonmembers"
On 5/8/20 5:08 PM, Peter Adebahr via Mailman-users wrote:
On 5/9/20 1:55 AM, Mark Sapiro wrote:
"Hold for moderation" has been set.
Set in "Default action to take when a non-member posts to the list"?
yep
If that is the case, find the non-member in Users -> Non-Members and
it does'nt show up there, "list has no nonmembers"
Look is var/logs/mailman.log for an error message with a SHUNTING notation and a Traceback.
Also look in var/queue/shunt. You can examine messages you find there
with mailman qfile.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On 5/9/20 2:13 AM, Mark Sapiro wrote:
On 5/8/20 5:08 PM, Peter Adebahr via Mailman-users wrote:
On 5/9/20 1:55 AM, Mark Sapiro wrote:
"Hold for moderation" has been set.
Set in "Default action to take when a non-member posts to the list"?
yep
If that is the case, find the non-member in Users -> Non-Members and
it does'nt show up there, "list has no nonmembers"
Look is var/logs/mailman.log for an error message with a SHUNTING notation and a Traceback.
Shunting seems to be ok:
May 09 01:22:38 2020 (1235) SHUNTING: 1588980158.3151......
But immediately before I find the "module 'time' has no attribute 'clock'" which I remember from a thread a couple of days ago, though I cannot remember a solution when mm3 has not been installed from source but via apt-get.
My core is V 3.2.2, core python 3.8.2, by the way.
Also look in var/queue/shunt. You can examine messages you find there with
mailman qfile.
ah, learnt how to use that now:
... X-Mailman-Rule-Hits: nonmember-moderation X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation ...
<----- start object 2 -----> { '_parsemsg': False, 'dmarc': True, 'envsender': 'noreply@xyzzy-listen.de', 'lang': 'de', 'listid': 'xyzzy-listen.de', 'member_moderation_action': 'hold', 'moderation_reasons': ['The message is not from a list member'], 'moderation_sender': 'peter@xyzzy.de', 'original_size': 7640, 'received_time': datetime.datetime(2020, 5, 8, 23, 22, 37, 976364), 'rule_hits': ['nonmember-moderation'], 'rule_misses': [ 'dmarc-mitigation', 'no-senders', 'approved', 'emergency', 'loop', 'banned-address', 'member-moderation'], 'to_list': True, 'version': 3, 'whichq': 'in'} [----- end pickle -----]
Does that help?
On 5/8/20 5:32 PM, Peter Adebahr via Mailman-users wrote:
May 09 01:22:38 2020 (1235) SHUNTING: 1588980158.3151......
But immediately before I find the "module 'time' has no attribute 'clock'" which I remember from a thread a couple of days ago, though I cannot remember a solution when mm3 has not been installed from source but via apt-get.
My core is V 3.2.2, core python 3.8.2, by the way.
That is exactly the issue. Mailman 3.2.2 is not compatible with Python 3.8. This is a Debian/Ubuntu packaging bug.
What has happened is the post encountered the exception shown in the Traceback that preceded the SHUNTING message and the message that triggered the exception was placed in the shunt queue.
The thread you remember is <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/K65RN3YNZ42T7Z6EOWJIGG6E4AK2YXLK/>
The fix is to patch your Mailman installation with the changes at <https://gitlab.com/mailman/mailman/-/merge_requests/552/diffs?commit_id=ea05bdd0f74ba06d85adad1f7d190a62e1bd4439>.
Or, at the very least change
x = random.random() + right_now % 1.0 + time.clock() % 1.0to
x = random.random() + right_now % 1.0 + time.process_time() % 1.0in mailman/utilities/uid.py.
After doing that and restarting Mailman core you can do
mailman unshunt to reprocess the message or if you prefer, mailman unshunt --discard (or just remove it from the shunt queue) to discard it.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On 5/8/20 7:39 PM, Mark Sapiro wrote:
That is exactly the issue. Mailman 3.2.2 is not compatible with Python 3.8. This is a Debian/Ubuntu packaging bug.
I have reported this to both Debian and Ubuntu.
<https://bugs.launchpad.net/ubuntu/+source/mailman3/+bug/1877701> and <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960072>
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On 5/9/20 4:39 AM, Mark Sapiro wrote:
The fix is to patch your Mailman installation with the changes at <https://gitlab.com/mailman/mailman/-/merge_requests/552/diffs?commit_id=ea05bdd0f74ba06d85adad1f7d190a62e1bd4439>.
As Ubuntu's version is 3.2.2, not 3.3, the full patch did no apply cleanly, but
x = random.random() + right_now % 1.0 + time.clock() % 1.0to x = random.random() + right_now % 1.0 + time.process_time() % 1.0
in mailman/utilities/uid.py.
this was the solution :))))))))))
Great support, Mark - Thank you very much!
Best regards, Peter
participants (2)
-
Mark Sapiro -
Peter Adebahr