Filename corruption -cont.

From: Mgr. Peter Tuharsky (
Date: Wed 26 Jul 2006 - 12:29:49 GMT

I see that codepage is michmatched when sent the message in UTF-8. I'll
try not to use UTF-8. I re-sent the previous message using the ISO8859-2

we use ANOMY sanitizer 1.70-1 (Debian Sarge). The same behaviour I face
with the fresh new 1.76 from Your website.
It is configured to "accept" several file types, including .doc
Quite often, the filename of the attached doc file is corrupted. I don't
understand, why even does the ANOMY bother with the file -it should just
"accept" it and let it go. However, it seems that mostly corrupted are
filenames with diacritics.

For example, I have sent myself the file "Informaèná bro¾úra-koneèná

And what I get is:

This message has been 'sanitized'. This means that potentially
dangerous content has been rewritten or removed. The following
log describes which actions were taken.

Sanitizer (start="1153750036"):
Part (pos="1233"):
SanitizeFile (filename="unnamed.txt", mimetype="text/plain"):
Match (names="unnamed.txt", rule="2"):
Enforced policy: accept

Part (pos="1370"):
Informae`ná bro3/4úra-konee`ná verzia., Informae`ná bro3/4úra-konee`ná
verzia.doc, doc", mimetype="application/msword"):
Informae`ná bro3/4úra-konee`ná verzia.doc", rule="2"):
Enforced policy: accept

Replaced file name with:

Total modifications so far: 1

Anomy 0.0.0 :
$Id:,v 1.90 2005/01/04 20:30:13 bre Exp $

In effect, the attachment is named

This is problem, since my users usually cannot open such a file
directly. Saving it under different (correct) name works, file is not
corrupted itself.

Please, what could I do to get rid of this?


hosted by