4 messages in net.sourceforge.lists.courier-sqwebmailRe: [sqwebmail] Problem in attachment...
FromSent OnAttachments
Juan Enciso CondeñaNov 19, 2004 9:52 am 
Sam VarshavchikNov 19, 2004 3:45 pm 
Juan Enciso CondeñaNov 22, 2004 8:18 am 
Ricardo SantosNov 25, 2004 12: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:Re: [sqwebmail] Problem in attachment nameActions...
From:Ricardo Santos (ric@yahoo.com)
Date:Nov 25, 2004 12:51:16 pm
List:net.sourceforge.lists.courier-sqwebmail

Hi.

--- Sam Varshavchik <mrs@courier-mta.com> wrote:

Juan Enciso Condeña writes:

My mail server is running sqwebmail-4.0.7, i think that it is very fast than another php-webmail, but now I found a problem. When attempt to donwload a attachment that contains special characters in its name it show me any name different to original when I do click to download link.

For example My attach name is "Filtros-activos-diseño.pdf" In the page readmsg.html it shows this to me:

=?iso-8859-1?Q?filtrosactivos-dise=F1o.pdf?=

When I do click, the download menu of IE it show me this name for save:

CA0LMRKD document.

I would like that the IE shows me this:

filtros-activos-diseño.pdf document.pdf

Any help will be received

There's nothing that SqWebMail can do about IE's, or some other mail client's, failure to implement an Internet standard.

Hummmm I see there are still problems with atachments' name. Exactly, IE isn't the only client with problems, I have the same issue with Opera and Netscape. I've noticed this situation when somebody send an email with an atachment on WinXP (maybe other Win versions too) doing a "right buton clicking" on a file to "send to mail".

Still RFC 2231??

Months ago I wrote to ask for an idea to deal with this strict behaviour (not implementation) of SqWebMail and my houndreds Outlook clients (I don't know if a new SqWebMail version does something about it), no body told me anything but Jim Horner (thanks) who give [me|us] a more philosofic than technic answer:

---Quoting Jim Quoting another open source project (KMail):

--The golden rule of implementing standards is "Be strict in what you produce, but be tolerant in what you accept.". Being strict here means using RFC 2231 for filename encoding. Being tolerant means also to accept the broken attachment names Outlook produces.--

I don't know if sqwebmail accepts Outlook's broken attachment names or not but -certainly- I do not want it producing broken attachment names.

---End Quoting Jim