[EMAIL PROTECTED] wrote on 01/19/2006 10:27:15 AM:
> > Content-Type: text/html; > > name*0="file:///C|/DOKUME%7E1/ANDRE/LOKALE%7E1/TEMP/nsmail-1.htm" > > Content-Transfer-Encoding: 7bit > > Content-Disposition: inline; > > > > filename*0="file:///C|/DOKUME%7E1/ANDRE/LOKALE%7E1/TEMP/nsmail-1.htm" > > > > In this particular sample, the path (well, the complete filename) is of > > no use at all, but in general: There is no real reason, why the filename > > spec should contain a path component, is it? > > That's not the only thing strange. Why does this have '*0=' for '=', > a pipe after 'C', and '~' (as %7E) in odd places? I would wonder what UMA created the message. The ~ (%7E) is Microsoft's coding long filenames into 8.3 namespace. I would guess the file to be a nonenglish (german?) equivalent to "C:\Documents and Settings\Andre\Local Settings\Temp\nsmail.htm" _______________________________________________ NOTE: If there is a disclaimer or other legal boilerplate in the above message, it is NULL AND VOID. You may ignore it. Visit http://www.mimedefang.org and http://www.roaringpenguin.com MIMEDefang mailing list MIMEDefang@lists.roaringpenguin.com http://lists.roaringpenguin.com/mailman/listinfo/mimedefang
