4 messages in net.sourceforge.lists.courier-sqwebmailRe: [sqwebmail] attachment name problems
FromSent OnAttachments
Ricardo SantosSep 3, 2004 3:26 pm 
Sam VarshavchikSep 3, 2004 4:31 pm 
Ricardo SantosSep 6, 2004 9:26 am 
Jim HornerSep 6, 2004 10:56 am 
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:Re: [sqwebmail] attachment name problemsActions...
From:Sam Varshavchik (mrs@courier-mta.com)
Date:Sep 3, 2004 4:31:41 pm
List:net.sourceforge.lists.courier-sqwebmail

Ricardo Santos writes:

Hi.

I have sqwebmail-4.0.7 (problem also with sqwebmail-4.0.6). When I send an email with an attachment with spaces in its name and read that email on Outlook (any version) the attachment name es

Looks like it isn't a sqwebmail problem code but maybe from a prerequisite or dependency program or library in the host system or even an elaborated ./configure or use of an especific auth-module.

No. Outlook does not implement RFC 2231-formatted mail headers.

I used to work with sqwebmail-3.3.2 on Suse 7.1 and vpopmail-5.2.1 without any problem, a couple of months

RFC 2231 was implemented in sqwebmail 3.4.0, which was released about two years ago.

RFC 2231 was standardized seven years ago. If you would like to know why Microsoft's software does not implement a seven year old standard for formatting mail headers, only Microsoft can answer that question for you.

The mail file inside the maildir with a problematic attachment looks like:

--=_0_13980_1094247328 Content-Disposition: attachment; filename*0*=utf-8'en-us'Friends%20Theme.mp3 Content-Type: audio/mpeg; name*0*=iso-8859-1''Friends%20Theme.mp3 Content-Transfer-Encoding: base64

Right. See RFC 2231.