On Oct 21, 2004, at 07:11, Steve Hostnik wrote:
Matteo,
This was explained to me when I had the same issue as sqwebmail supporting a
new RFC that older e-mail programs don't understand. If your file
attachment has spaces or special characters it uses the new RFC that Outlook
can't understand. You need to rename the file attachment something without
spaces or special characters and resend it. I'm not sure why sqwebmail
isn't backwards compliant.
Thanks, Steve
-----Original Message----- From: Matteo Tempia [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 20, 2004 6:39 AM To: [EMAIL PROTECTED] Subject: [sqwebmail] attachments problems
Hello everybody,
i have a problem with the way sqwebmail attaches files.
The problem is when I download the email with a client like outlook the file
appears like "ATT000011.dat" and people doesn't know what file it is..
I'm sure there's a simple solution for this thing.
Please help me.
Matteo
I might be mistaken, as I haven't had to discuss it recently nor deal with the problem much... But I don't think it's that SqWebMail complies with a "new" RFC exactly, or that it's in any way "not backwards compliant."
If I remember the details properly, it's simply that Outlook doesn't follow the long-standing rules for naming attachments that all mail systems are supposed to follow, and SqWebMail (and actually the entire Courier system in general, for that matter) is unforgiving about other systems that are slack about supporting standards.
[Editorial note]
Personally, I think other programmers should always behave this way... And *NEVER* give Microsoft (in particular, and other lame programmers in general) the slack that they often get, whereby so many so-called "bugs" in good programs are fixed by adding hacks to support the stupid programs.
But then, that's me. [Steps off soap box.]
-jab
smime.p7s
Description: S/MIME cryptographic signature
