Re: Pyzor breaks when doing report --mbox

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

Johan Segern=E4s wrote:
> On 2005-04-15 10:27 -0700 or thereabouts, Kelson wrote:
>=20
>>There's no way to submit the broken messages, but it is possible to pic=
k=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
> How do I find the offending line? Anyone who has a nice script for doin=
g this=20
> before doing pyzor report?=20

Some variation on grep "Content-Transfer-Encoding: binary"?

Maybe formail?

I only do mbox submissions when I have a chance to check the mailbox, so=20
I just manage it using pine.  If Pyzor fails, I look at the last line of=20
the trace for the actual error, search for messages containing that=20
phrase, and delete them all.

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