Re: Pyzor breaks when doing report --mbox

[Kelson <ke...@sp...>]

Johan Segern=E4s wrote:
> I get the following error when I do pyzor report --mbox almost every ti=
me I
> do report on a big mbox, how come? Something wrong here or known bug in
> pyzor? Fix? Workaround?
<snip>
> ValueError: unknown Content-Transfer-Encoding: binary

Known bug.  Apparently Python doesn't deal well with invalid content=20
transfer encodings, and Pyzor doesn't include enough exception handling=20
to recover.

There's no way to submit the broken messages, but it is possible to pick=20
up the mbox submission where it left off.  What I do is search for the=20
offending line, then remove any messages that match it.  I also remove=20
any messages before the first match, because those have already been=20
submitted.  Then I submit the mbox again.

--=20
Kelson Vibber
SpeedGate Communications <www.speed.net>