[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug-mailutils] (no subject)
From: |
djh |
Subject: |
[bug-mailutils] (no subject) |
Date: |
Thu, 06 Jul 2006 14:17:49 +0900 |
MH-E's K-a (save all mime parts) command is really a usefull one.
It can save a lot of time. Sometime you just want to save all files for now
and maybe look at them later.
I have run into a problem however. I didn't have any problems with all ascii
filesnames with no spaces in them. (Still didn't test any with spaces.)
I did some testing showing what happens in various situations, i.e., using
MH-E, gmail, and Becky (a mua) and compared the results.
Looks like two problems which confounds the issue.
(1) One is that using
filename*=
(filename with an * appended causes output to not use the given
filename.
(2) When filename=".......japanese characters in it like ..." (double quoates)
filename="=?ISO-2022-JP........ "
is used the name isn't converted back to a natual iso-2022 string,
before
creating and writing the file.
Please see the inlined test data file below. In the test data the MH-E, ';'
command was used to see the mime part headers.
Please take a look at these and give me some opinions and ideas on how to solve
this. Becuase I really like the K-a command.
Note, that K-o or output of a single mimi part works fine. But, its takes time
to jump between mime parts and K-o for each one if there are a lot
of them or you're in a hurry.
Regards,
Darel Henman
--------------------------------
With Japanese characters in the filename:
MH-E with Mailutils MH uses:
filename*=
* and no double quotes, ".
Without Japanese characters in the filenames:
MH-E with Mailutils MH uses:
filename=
* and no double quotes, ".
With Japanese characters in the filename
GMAIL mail used:
filename=
* with double quotes, ".
With Japanese characters in the filename
X-Mailer:Becky! v7.04
filename=
* with double quotes, ".
Note: I didn't test filenames with spaces in them.
I don't like them but they exist.
Here are the results of a few of my tests, below:
-------------------------------------------------
(1) Sent and rcvd by: MH-E & Mailutils MH (Japanese chars in filename)
--=-=-=
Content-Type: application/octet-stream
Content-Disposition: attachment;
filename*=iso-2022-jp''tfn1_%1b$B%3d%2a%1b%28B..doc
Content-Description: tfn1
test msg#1 filename data...
--=-=-=
Content-Type: application/octet-stream
Content-Disposition: attachment;
filename*=iso-2022-jp''tfn2_%1b$B!J%1b%28Bweb%1b$B!K%1b%28B.doc
Content-Description: tfn2
test msg#2 filename data...
--=-=-=--
==> Result from the MH-E command to save all mime parts above:
storing message 5 part 1 as file 5.1.plain
storing message 5 part 2 as file 5.2.octet-stream
storing message 5 part 3 as file 5.3.octet-stream
N.B. Not storing as the filename given by sender.
(2) Sent and rcvd by: MH-E & Mailutils MH (Only ascii chars in filename)
--=-=-=
Content-Disposition: attachment; filename=tfn1-ascii.doc
Content-Description: ascii name1
test msg#1 filename data...
--=-=-=
Content-Disposition: attachment; filename=tfn2-ascii.doc
Content-Description: ascii name2
test msg#2 filename data...
--=-=-=
==> Result from the MH-E command to save all mime parts above:
storing message 7 part 1 as file 7.1.plain
storing message 7 part 2 as file /cygdrive/c/tfn/tfn1-ascii.doc
storing message 7 part 3 as file /cygdrive/c/tfn/tfn2-ascii.doc
storing message 7 part 4 as file 7.4.plain
N.B. Stored as the filename given by the sender.
(3) Sent by mozilla via gmail and
Rcvd by Mailutils MH and MH-E (Japanese chars in filename<)
------=_Part_5754_2712772.1152158735400
Content-Type: application/msword;
name="=?ISO-2022-JP?B?dGZuMV8bJEI9KhsoQi4uZG9j?="
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
filename="=?ISO-2022-JP?B?dGZuMV8bJEI9KhsoQi4uZG9j?="
X-Attachment-Id: f_epaljmeo
dGVzdCBtc2cjMSBmaWxlbmFtZSBkYXRhLi4uCg==
------=_Part_5754_2712772.1152158735400
Content-Type: application/msword;
name="=?ISO-2022-JP?B?dGZuMl8bJEIhShsoQndlYhskQiFLGyhCLmRvYw==?="
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
filename="=?ISO-2022-JP?B?dGZuMl8bJEIhShsoQndlYhskQiFLGyhCLmRvYw==?="
X-Attachment-Id: f_epaljzev
dGVzdCBtc2cjMiBmaWxlbmFtZSBkYXRhLi4uCg==
==> Result from the MH-E command to save all mime parts above:
mhn: Cannot open output stream (file
/cygdrive/c/tfn/=?ISO-2022-JP?B?dGZuMV8bJEI9KhsoQi4uZG9j?=): No such file or
directory
mhn: Cannot open output stream (file
/cygdrive/c/tfn/=?ISO-2022-JP?B?dGZuMl8bJEIhShsoQndlYhskQiFLGyhCLmRvYw==?=): No
such file or directory
storing message 6 part 1.1 as file 6.1.1.plain
storing message 6 part 1.2 as file 6.1.2.html
storing message 6 part 2 as file
/cygdrive/c/tfn/=?ISO-2022-JP?B?dGZuMV8bJEI9KhsoQi4uZG9j?=
storing message 6 part 3 as file
/cygdrive/c/tfn/=?ISO-2022-JP?B?dGZuMl8bJEIhShsoQndlYhskQiFLGyhCLmRvYw==?=
N.B. Tried to store as filename given, but failed.
(4) Sent by X-Mailer:Becky! v7.04 [ja] over LAN
Rcvd by Mailutils MH and MH-E (Japanese chars in filename)
--------_449A4BF7B5CB05A784C8_MULTIPART_MIXED_
Content-Type: application/octet-stream;
name="FuncTechSpec_I0007-00_Delivery data
=?ISO-2022-JP?B?ZG93bmxvYWQbJEIhShsoQndlYhskQiFLGyhCXw==?=
=?ISO-2022-JP?B?cjMuMl8wNTExMjhwbV9FbmcuZG9j?="
Content-Disposition: attachment;
filename="FuncTechSpec_I0007-00_Delivery data
=?ISO-2022-JP?B?ZG93bmxvYWQbJEIhShsoQndlYhskQiFLGyhCXw==?=
=?ISO-2022-JP?B?cjMuMl8wNTExMjhwbV9FbmcuZG9j?="
Content-Transfer-Encoding: base64
==> Result from the MH-E command to save all mime parts above:
mhn: Cannot open output stream (file
/cygdrive/c/sys-tmp/FuncTechSpec_I0007-00_Delivery data
=?ISO-2022-JP?B?ZG93bmxvYWQbJEIhShsoQndlYhskQiFLGyhCXw==?=
=?ISO-2022-JP?B?cjMuMl8wNTExMjhwbV9FbmcuZG9j?=): No such file or directory
storing message 13 part 1 as file 13.1.plain
storing message 13 part 2 as file
/cygdrive/c/sys-tmp/FuncTechSpec_I0007-00_Delivery data
=?ISO-2022-JP?B?ZG93bmxvYWQbJEIhShsoQndlYhskQiFLGyhCXw==?=
=?ISO-2022-JP?B?cjMuMl8wNTExMjhwbV9FbmcuZG9j?=
N.B. Tried to store as filename given, but failed.
;;
;; end of test data
;;
- [bug-mailutils] (no subject),
djh <=