Diana von Bidder writes:
I have several entries in /var/lib/mailman3/queue/shunt/ with Aug 21 timestamps,
Evidence! Preserve it!
You can look at those using "mailman qfile <file>", where the specification for <file> needs to be a regular path. the 'qfile' command does not assume a prefix of /var/lib/mailman3/queue/, unfortunately. Look for non-ASCII characters in headers, very long lines, a line with no indentation that doesn't match the "name: content" pattern that header follow (indented lines are considered to be "logically" part of the previous line so that's not a problem), and empty lines in the header. (There is always an empty line between the message header and the message body, but an empty line in the middle of the header will often cause problems.)
Check the size of the files; probably all these messages were short test messages and it won't matter but in real life you might have a huge attachment which I think would be printed out. Start with the short ones. :-)
and several entries in /var/lib/mailman3/queue/shunt/ with current timestamp (i.e. everytime I ls -l there is a new timestamp with the current time).
I'm not sure what's going on with that. The point of the shunt queue is that Mailman doesn't know what to do and it's putting the messages there to wait for human intervention. So timestamps shouldn't be changing.
My output looks exactly the same.
Good!
If you want you can send me one of those entries in shunt (assuming you're satisfied with my assurance of privacy of any identifying information such as IP addresses, domain names, and mailbox names).
Steve