Clay Dowling writes:
After nosing around in rfc2231, and playing with a few problematic
clients, I have found that the rfcs permit (by means of omission) both
filename* and filename attributes to the Content-Disposition header.
Are you positively sure about that logic?
A better solution is to use encoded parameters only for non-USASCII content. Which is what's going to happen.Doing so causes file attachments to retain their filenames in both good, rfc2231 compliant clients such as Netscape, and non-compliant clients such as Microsoft Outlook. I have modified attachments.c to include both of these attributes to that header. Diffs for this are included in the attachment. This patch is sub-optimal, and shouldn't be considered anything but a temporary workaround. Specifically, for plain text attachments two filename
-------------------------------------------------------
This sf.net email is sponsored by:
With Great Power, Comes Great Responsibility Learn to use your power at OSDN's High Performance Computing Channel
http://hpc.devchannel.org/
_______________________________________________
courier-users mailing list
[EMAIL PROTECTED]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
