[MM3-users] Re: All messages to a new list/domain shunted from "in" queue with no logged exceptions

25 Nov 2023

      I was able to resolve this by going to the "List Settings"->"DMARC Mitigations" config page for the affected list, making no changes, and then clicking "Save Changes".
This suggests that new lists in 3.3.9 may be getting mlist.dmarc_addresses set to None rather than an empty list (which seems to be expected).
--Jered
----- On Nov 25, 2023, at 10:53 AM, Jered Floyd jered@convivian.com wrote:
...
I added this to my config:
[logging.error]
level: DEBUG
path: debug-errors.log
That got me the traceback (I'll investigate why they weren't logging earlier),
which is a bit curious; looking into the code now:
Nov 25 15:49:26 2023 (90) Uncaught runner exception: 'NoneType' object is not
iterable
Nov 25 15:49:26 2023 (90) Traceback (most recent call last):
File
"/opt/app-root/src/.local/lib/python3.9/site-packages/mailman/core/runner.py",
line 179, in _one_iteration
self._process_one_file(msg, msgdata)
File
"/opt/app-root/src/.local/lib/python3.9/site-packages/mailman/core/runner.py",
line 272, in _process_one_file
keepqueued = self._dispose(mlist, msg, msgdata)
File
"/opt/app-root/src/.local/lib/python3.9/site-packages/mailman/runners/incoming.py",
line 80, in _dispose
process(mlist, msg, msgdata, start_chain)
File
"/opt/app-root/src/.local/lib/python3.9/site-packages/mailman/core/chains.py",
line 57, in process
if link.rule.check(mlist, msg, msgdata):
File
"/opt/app-root/src/.local/lib/python3.9/site-packages/mailman/rules/dmarc.py",
line 324, in check
if maybe_mitigate(mlist, address):
File
"/opt/app-root/src/.local/lib/python3.9/site-packages/mailman/rules/dmarc.py",
line 284, in maybe_mitigate
for address in mlist.dmarc_addresses:
TypeError: 'NoneType' object is not iterable
Nov 25 15:49:26 2023 (90) SHUNTING:
1700927366.81852+6d2f84a8eb97e64c3ee93662f1744a2a756c7ca9
[...]
--Jered
----- On Nov 25, 2023, at 10:44 AM, Jered Floyd jered@convivian.com wrote:
...
...
When Mailman shunts a message, it always attempts to log the exception
to its error.log which by default is written to mailman.log. If you
can't find these messages, either you aren't looking in the right place
or Mailman doesn't have permission to write the log.
I've had them appear in my mailman.log previously, but I'll increase the logging
level (and try a different file name for good measure) just to check.
...
Actually, the message is moved back to the in queue and shunted again.
Fair; I was using "no effect" as shorthand for that the operation was
idempotent. :-)
--Jered

Mailman-users mailing list -- mailman-users@mailman3.org
To unsubscribe send an email to mailman-users-leave@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/...
This message sent to jered@convivian.com