[Mimedefang] Re: Problem on attachment name

[Ing. Andrea Vettori]

>
> Did you do an upgrade from MimeDefang 2.39 to 2.58 when this error
> occured?
>

No they are two different installations, one recent with the 2.58  
mimedefang and the other older with the 2.39 mimedefang. The  
antivirus version is the same for the two installations.

>
> Did you try to scan such a bad apple-message -and its parts- with
> your antivirus from the commandline (outside of MimeDefang)?
> That will probably show what is causing this trouble: the
> antivirus program (while scanning the raw message) or MimeDefang
> (while decoding the mime parts). But the _real_ cause is ofcourse
> a malformed mime header in the message.
>

Yes, if I save the message source from the sender email client and  
run the antivirus on that file,  it pass with no problem, even if as  
you said, the message does not conform to rfc specifications (but the  
filename and name paramteres of content-type and content-disposition  
are the same).

I've modified mimedefang to make a copy of the temp file on which the  
antivirus is run to have a backup to analyze since mimedefang will  
delete the temp file after running the antivirus. And in that backup  
file I can see that the unquoted filename is truncated.

Is mimedefang "rebuilding" the message from its parts or the source  
arrive at mimedefang already modified (i.e. with the filename  
truncated?). I don't know how to check this.

I've sent a bug report to Apple but I don't know if they respond  
quickly and certainly it can pass a lot of time before all Apple Mail  
users upgrade. Before this every mimedefang/f-secure server that  
receives AppleMail mail with spaces on attachment name will fail...

Do you know if some workaround can solve the problem waiting for  
Apple patch ???

Many thanks for your help.

--
Ing. Andrea Vettori
Consulente per l'Information Technology