[Mailman-Users] log errors after restart

[Mark Sapiro]

On 12/24/2012 7:48 AM, Con Wieland wrote:
> More issues.  I had several of these messages:
> 
> Dec 24 06:57:23 2012 (17125) Ignoring unparseable message: 1354049125.0870931+f5e280e91f2ed298fb5
> 62d3690311d1e47d24dee
> 
> I found them in the bounce directory and removed them. I then restarted mailman with no errors but I noticed that I now have a lot of qfiles that don't seem to be getting processed.


So they were bounces that were unparseable for some reason. Possibly a
spam post gets rejected or held and a notice is sent to the probably
spoofed sender and that bounces. Except that the above message id is not
a Mailman generated ID as would be found in a reject or held message
notice. Also, you shouldn't find any queue entry corresponding the above
log message, because that message says the queue entry was removed and
ignored.


> /usr/local/mailman/qfiles/archive 153


Is ArchRunner running? What are the extensions on the names of these 153
entries.


> /usr/local/mailman/qfiles/bad	542


The 'bad' queue does not get processed. This is where unparseable
messages are preserved for inspection (with a .psv extension) and where
messages with no content after content filtering are saved if the list's
filter_action = Preserve.

See the documention of settings QRUNNER_SAVE_BAD_MESSAGES,
BAD_SHUNT_STALE_AFTER and BAD_SHUNT_ARCHIVE_DIRECTORY in the "Qrunner
defaults" section of Defaults.py for more info, although if yours is an
older Mailman, you may not have all these features/settings.

-- 
Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan