Hi All,
I was going through the archives for sqwebmail on the discussion about
attachments and certain mail clients renaming them. The archive below
explains what sqwebmail does for punctuation and non-English characters (
uses RFC 2231 to encode attachment filename) but
what about when there are spaces in the attachment (ie. 2004 Cap
Letter.doc)? It seems that any attachment with spaces in it get's renamed
by hotmail, yahoo, outlook express, incredimail, and probably more. Taking
the spaces out of an attachment filename works fine for those 4 mail
clients. Is sqwebmail using RFC 2231 for spaces in attachment names also?
I read RFC 2231 and I am still confused if sqwebmail is going by the rules
and the 4 mail clients are not or vice-vera. Archive is below. Any
information or help would be very much appreciated. Thank you in advance.
Chet
a.. From: Sam Varshavchik
a.. Subject: [sqwebmail] Re: Attachment name
a.. Date: Fri, 26 Sep 2003 17:23:04 -0700
Martin Kos writes:
when i send attachments through outlook or outlook express its
fine. when i send the attachment through sqwebmail web
interface then the attachments are renamed as .dat .
sqwebmail does not rename any attachment as .dat.
See the headers of the sent message.
i have the same problem over here. as far as i have found out,
the problem exists only if the attached filename has special
characters in it, e.g. space or the german "umlaut"s. the
received mail is shown right in sqwebmail but if i look at it in
outlook express (haven't tested other apps) only the filenames
that have no special characters are displayed right, the other
have filenames like "ATTxxxxxx.ext" with "ext = the right
extension".
i remember in some other cases (perhaps an earlier version of
sqwebmail?) i have had the same problem as you that showed the
filenames with .dat instead the right file extension... okay the
whole filename is still wrong :-(
sam, any idea what the problem could be?
When the filename contains any non-English characters, or if it contains
punctuation, sqwebmail uses RFC 2231 to encode the attachment filename. RFC
2231 defines attachment filename encoding for international and special
characters.
If the receiving mail client does not implement RFC 2231, it will not be
able to determine the attachment filename, and then it will do whatever it
does when it cannot determine the attachment filename. Using whatever.dat
seems like a reasonable default.
