2 messages in net.sourceforge.lists.courier-users[courier-users] Re: A "fix" for broke...
FromSent OnAttachments
Clay DowlingDec 13, 2002 10:27 am.diff
Sam VarshavchikDec 13, 2002 2:51 pm 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:[courier-users] Re: A "fix" for broken Outlook attachment filenamesActions...
From:Sam Varshavchik (mrs@courier-mta.com)
Date:Dec 13, 2002 2:51:42 pm
List:net.sourceforge.lists.courier-users

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?

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

A better solution is to use encoded parameters only for non-USASCII content. Which is what's going to happen.