Sam Varshavchik writes: 

> Can you try applying the following patch to mailbot, and see if it fixes 
> both problems. I'll need to document the fact that autoreplies in webmail 
> should be set up with a browser that supports utf-8. This patch transcodes 
> the original message to the character set specified in the autoreply text, 
> so the autoreply text should be specified in utf-8 in order to be able to 
> transcode any character set to it.

This patch cured both problems, thanks Sam. Content-Transfer-Encoding 
header, generated by Sqwebmail, indirectly proves that original message is 
in utf-8. And of course Firefox 3.6 supports utf-8. 

Meantime I've had to face another problem - OE cannot parse long attachment 
filenames, encoded by Sqwebmail, and replaces them by ATT00001.dat. 

Relevant headers are:
Content-Type: application/octet-stream; charset=utf-8; 
name*0*="iso-8859-1''Enterprise%20Content%20Management%20%D1%85%D0%B7%D1%87"
; name*1*="%D1%82%D0%BE.xls"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
  filename*0*=utf-8'en-us'Enterprise%20Content%20Management%20%D1%85%D0%B7;
  filename*1*=%D1%87%D1%82%D0%BE.xls

Note that "name" encoded differently than "filename", and specified charset 
(iso-8859-1) does not match real one (utf-8). Another difference, not so 
important in this case but potentially dangerous for very long encoded 
names, is that "name" tokens doesn't begin from new lines. 

I've tried to edit "name" manually and replace iso... by utf-8. OE still 
cannot recognize filename (Thunderbird have not any problems in both 
cases). Than I've tried to send the same file with Squirrelmail. OE 
successfully recognized filename, encoded as follows:
Content-Type: application/vnd.ms-excel; 
name="=?utf-8?B?RW50ZXJwcmlzZSBDb250ZW50IE1hbmFnZW1lbnQg0YXQt9GH0YLQvi54bHM=
?="
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
 
filename="=?utf-8?B?RW50ZXJwcmlzZSBDb250ZW50IE1hbmFnZW1lbnQg0YXQt9GH0YLQvi54
bHM=?="
(long lines are not wrapped) 

I've also noted headers added by Squirrelmail IMO useful for tracking 
purposes:
Received: from 192.168.2.3
        (SquirrelMail authenticated user lehel)
        by mail.* with HTTP;
        Mon, 20 Sep 2010 20:20:03 +0400
and
User-Agent: SquirrelMail/1.4.21 

-- 
Alexei.

------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
_______________________________________________
courier-users mailing list
[email protected]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users

Reply via email to