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