I am terribly sorry.
First:
Because Thunderbird add a new mime-part with delete comment like:
--------------B9BFA3413B08F1FAB3A2AAC0
Content-Type: text/plain; charset=UTF-8; x-mac-type="0"; x-mac-creator="0";
name="=?UTF-8?B?44OG44K544OILnR4dA==?="
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
filename*=utf-8''%E3%83%86%E3%82%B9%E3%83%88%2E%74%78%74
44OG44K544OI
--------------B9BFA3413B08F1FAB3A2AAC0--
is original message. Not problematic one.
On 2018/12/02 12:58, Hideki SAKAMOTO wrote:
Hi,
On 2018/12/01 7:34, Sam Varshavchik wrote:
I don't see anything wrong here.
Oh sorry, I copied error-part from Thunderbird's view screen.
I checked raw file in the server and it's fileneme field changed raw UTF-8
even if original message did not.
I test a Email with two attachfile, 'test.txt' and '[test in Japanese].txt'
with patched version.
First loading is ok:
mail_original.txt / imaplog_reload_folder.txt
Remove 'test.txt' also ok:
mail_englishfile_removed.txt / imaplog_remove_EnglishFile.txt
Remove '[test in Japanese].txt' got warning(Error with 5.0.4 version):
mail_japanesefile_removed.txt / imaplog_remove_Japanesefile.txt
So error occured when Thunderbird try to save message just remove attachment
file named in Japanese.
On 2018/12/01 7:34, Sam Varshavchik wrote:
Hideki SAKAMOTO writes:
Hi,
Thank you for your quick release of 5.0.4.
Now there was another claim that Thunderbird users could not delete attachments
with UTF-8 filenames.
Because Thunderbird add a new mime-part with delete comment like:
--------------B9BFA3413B08F1FAB3A2AAC0
Content-Type: text/plain; charset=UTF-8; x-mac-type="0"; x-mac-creator="0";
name="=?UTF-8?B?44OG44K544OILnR4dA==?="
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
filename*=utf-8''%E3%83%86%E3%82%B9%E3%83%88%2E%74%78%74
44OG44K544OI
--------------B9BFA3413B08F1FAB3A2AAC0--
I'm not sure this part is violate RFC or not, but this error seemed to be
avoidable with the attached patch(I reffered to libs/imap/fetch.c).
I don't see anything wrong here. I'm guessing that Thunderbird takes an
existing message with 8-bit headers, and preserves them when APPENDing a new
one. There is no IMAP function to detach attachments. This is done by adding a
new message without the attachment, in place of the old one.
So, Thunderbird is preserving 8-bit headers, and the current code rejects the
message for that reason.
_______________________________________________
Courier-imap mailing list
[email protected]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-imap
_______________________________________________
Courier-imap mailing list
[email protected]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-imap
--
有限会社つくばセキュアネットワークリサーチ 坂元 英紀
E-mail: [email protected]
Tel: 029-850-5250, Fax: 029-850-5251
_______________________________________________
Courier-imap mailing list
[email protected]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-imap
