Diana von Bidder writes:
You can look at those using "mailman qfile <file>" [..]
These files looked pretty normal...
Are they addressed to the problematic list? What's in them?
Do you actually know what's normal for email, that is, RFC 822 conformance? Do you know how to find out what characters are producing the whitespace you see? Do you know how to find non-printing characters?
What then happens is the following:
- I see the connection in /var/log/mailman3/smtp.log and a bak-file in /var/lib/mailman3/in.
- I see an ACCEPT in /var/log/mailman3/mailman.log and the bak-file in /var/lib/mailman3/pipeline
- I get the following error once a second in
The only reason I can think of at the moment for this to happen so frequently is that you have the list owner set to the list's posting address, or perhaps one of the list's administrative addresses, and each error sends a mail which triggers another error, etc. Please check that.
/var/log/mailman3/mailman.log
Aug 29 11:35:06 2022 (936) HyperKitty failure on http://localhost/mailman3/hyperkitty/api/mailman/urls: <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>404 Not Found</title> </head><body> <h1>Not Found</h1> <p>The requested URL was not found on this server.</p> <hr> <address>Apache/2.4.54 (Debian) Server at localhost Port 80</address> </body></html> (404)
suggests you have mailman-hyperkitty installed but HyperKitty is either not running, or running on a different host, or Apache doesn't know how to proxy for HyperKitty, or HyperKitty is configured to serve a different base URL (ie, other than http://localhost/mailman3/hyperkitty/).
Are the other lists that seem to be working configured to archive posts? Can you access the archives of the working lists from that URL? If not, mailman-hyperkitty is misconfigured. If you can, I can't think of a reason for this offhand. The relevant configurations are