attachments and binary data

[Matthias Andree]

David Relson <relson at osagesoftware.com> writes:

> Thanks for the test case you sent me and the lexer_v3.c modification to
> show the problem.  
>
> It _is_ the case that this mime part:
>
> ------------791891673B6A210E
> Content-Type: application/x-zip-compressed; name="blablabla"
> Content-Disposition: attachment; filename="blablabla"
> Content-Transfer-Encoding: base64
>
>
> is causing the lexer to read in a big chunk (200K or so) of the
> attachment.  On my AMD 2800, it takes about 30 seconds to process the
> 448k attachment.  We'll have to see what we can do to prevent that
> happening.

Does the boundary match? If so, why doesn't bogofilter skip over this
quickly, forward to the next boundary, in the mime code?

-- 
Matthias Andree