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? Was this actually legit mail? Joseph Brennan Columbia University Information Technology _______________________________________________ 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
