Marcus Felipe Pereira writes:
Hi,
sqwebmail is not correctly interpreting the some attachment names sent by
Outlook Express.
May be it's an error on OE Mime but I've tested in many webmails and only
in sqwebmail I've got the error.
The test below I've done sending an attachement with the name:
"testão.txt".
- Sending the attachment with sqwebmail. The mime header of the file was:
**********************************
--=_0_29965_1119538165
Content-Disposition: attachment;
filename*0*=iso-8859-1'pt-br'Test%E3o.txt
Content-Type: text/plain; charset="iso-8859-1";
name*0*=iso-8859-1''Test%E3o.txt
Content-Transfer-Encoding: 7bit
**********************************
and sqwebmail correctly showed the attachament name: "Attachment:
Testão.txt (0.0K)"
- Sending the attachment with Outlook Express:
**********************************
--=_ieu-12670-1119538110-0001-2
Content-Type: text/plain; format=flowed;
name="=?iso-8859-1?Q?Test=E3o.txt?="; reply-type=original;
charset=iso-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
filename="=?iso-8859-1?Q?Test=E3o.txt?="
**********************************
and sqwebmail showed: "Attachment: =?iso-8859-1?Q?Test=E3o.txt?= (0.0K)"
There is clearly differences in the filename field of each message.
Do I miss any configuration?
No. You only missed the fact that Microsoft fails to follow an established
standard for encoding i18n attachment names.
SqWebMail uses the encoding convention defined by RFC 2231. Microsoft pulls
something out of thin air.
Is there any way I can fix this?
Call Microsoft, and ask them to fix it.
6 messages in net.sourceforge.lists.courier-sqwebmailRe: [sqwebmail] Wrong attachment name
