[Mailman-Users] cannot rebuild archives

[Mark Sapiro]

Jeff DeReus wrote:
>
>and there are no entries in the shunt queue.  here is the error log entry
>
>  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 240, in
>_parsebody
>    msgobj = self.parsestr(part)
>  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 265, in
>_parsebody
>    msg = self.parse(fp)
>  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 206, in
>_parsebody
>    raise Errors.BoundaryError(
>BoundaryError: No terminating boundary and no trailing empty line
>
>Jun 23 02:45:24 2006 (4473) Ignoring unparseable message:
>1151048724.4360731+1e264a285361f87ce3a55bc965c303a3f65881d4


This is not related to your archive issue. It is an unparseable email
message (i.e. a message with defective MIME structure - most likely
spam) that was totally ignored.

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