This is part of a much bigger problem which can only be addressed by
rewriting a major portion of the sanitizer (yes, this is on my TODO
list, but nowhere near the top).
Basically, the filename is incorrectly encoded in the example below
- Anomy parses it correctly as "3333", but some email clients may
incorrectly parse it as "3333 et.scr".
In cases like these Anomy should consider *both* possibilities and
respond based on the "more dangerous". Implementing such logic will
take me a while...
Thanks for the bug report though. :)
On 2002-04-19, 16:24:46 (+0200), a2k wrote:
> name=3333 et.scr
-- Bjarni R. Einarsson PGP: 02764305, B7A3AB89 firstname.lastname@example.org -><- http://bre.klaki.net/
Check out my open-source email sanitizer: http://mailtools.anomy.net/ Spammers, please send plenty of email to: email@example.com