Hi,
On Wed, Jan 10, 2018, at 9:21 AM, Dmitry Makovey wrote:
I'm using docker-based deployment of mailman.
things appear to be functioning for the most part, but recently I've started getting reports from users stating that mail from *some* subscribers to the list gets queued for moderation with reason "n/a".
This could be an unrelated issue. Until 3.1 release, not all the rules set a reason, so most probably those emails hit one or more of the rules and thus is held for moderation. If you look at the raw email and look for X-Rule-Hits: header, I think you will find the exact rule responsible.
Mark fixed this and made sure that rules always set a reason, it should be a part of next release.
Not sure if that's related, but I've also noticed that my logs are filling up with
Connection to HyperKitty failed: ("Connection broken: ConnectionResetError(104, 'Connection reset by peer')", ConnectionResetError(104, 'Connection reset by peer'))
(full dump: https://gist.github.com/droopy4096/1538d34ed7b6709252e8c3e82aaca69d )
what's the best angle to troubleshoot this situation?
I have read other bugs around this issue and found that most of these issues are because of wrong Content-Length header set, which causes the receiver to close connection pre-maturely.
In case of Django, I am not 100% sure how to debug this issue yet though.
Hope that was was a bit helpful.
-- Abhilash Raj maxking@asynchronous.in