[Mailman-Users] mailman error file grows & disk going out of space

[Mark Sapiro]

kk CHN wrote:
>
>/mailman/logs/error says the follows      ,  how can I fix this  ?
>did anyone face this earlier ? please give me  your valuable  comments
>  to fix this .
>
>
># tail -50  error
>    self._parsebody(root, fp, firstbodyline)
>  File "/usr/local/mailman/pythonlib/email/Parser.py", line 246, in _parsebody
>    raise Errors.BoundaryError(
>BoundaryError: multipart message with no defined boundary
>
>Apr 22 11:51:35 2008 (35739) Ignoring unparseable message:
>1186840687.951453+8a33be62beafbb6e10e55ebae32cfa03ed596313
>Apr 22 11:51:35 2008 (35739) Uncaught runner exception: multipart
>message with no defined boundary
>Apr 22 11:51:35 2008 (35739) Traceback (most recent call last):
>  File "/usr/local/mailman/Mailman/Queue/Runner.py", line 100, in _oneloop
>    msg, msgdata = self._switchboard.dequeue(filebase)
>  File "/usr/local/mailman/Mailman/Queue/Switchboard.py", line 164, in dequeue
>    msg = email.message_from_string(msg, Message.Message)
>  File "/usr/local/mailman/pythonlib/email/__init__.py", line 51, in
>message_from_string
>    return Parser(_class, strict=strict).parsestr(s)
>  File "/usr/local/mailman/pythonlib/email/Parser.py", line 75, in parsestr
>    return self.parse(StringIO(text), headersonly=headersonly)
>  File "/usr/local/mailman/pythonlib/email/Parser.py", line 64, in parse
>    self._parsebody(root, fp, firstbodyline)
>  File "/usr/local/mailman/pythonlib/email/Parser.py", line 246, in _parsebody
>    raise Errors.BoundaryError(
>BoundaryError: multipart message with no defined boundary
>
>Apr 22 11:51:35 2008 (35739) Ignoring unparseable message:
>1186840687.951453+8a33be62beafbb6e10e55ebae32cfa03ed596313
>Apr 22 11:51:35 2008 (35739) Uncaught runner exception: multipart
>message with no defined boundary
>Apr 22 11:51:35 2008 (35739) Traceback (most recent call last):
>
>
>
>
>I tried to find where this message
># find  / -name  1186840687.951453+8a33be62beafbb6e10e55ebae32cfa03ed596313
>
>but no result ,


In 2.1.9, the file you are looking for is
qfiles/in/1186840687.951453+8a33be62beafbb6e10e55ebae32cfa03ed596313.bak.
Each one of these errors is caused by a separate message being
received. This may be just a flood of malformed spam at your site or
some kind of DOS attack. I expect you have many .bak files in
qfiles/in/, one for each of these messages.

Note in general, log messages about queue entries don't contian the
extension, so you need 

# find  / -name 
1186840687.951453+8a33be62beafbb6e10e55ebae32cfa03ed596313\*

Actually, leaving these .bak files in the queue was an error in 2.1.9.
In Mailman 2.1.10, this was changed to preserve the queue entry that
contained the unparseable message in the shunt queue with a .psv
extension.

In any case, examining these qfiles/in/*.bak files with 'bin/dumpdb -p'
will tell you where the messages are coming from.

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