11013, 11076, 22878, 35587, 56908, 160141, 166541, 199995, 204612, 219240, 227360, 227720, 227994, 241216, 270068, 271094, 326303, 333074, 333880, 387061, 463129, 531354, 549078, 634860, 715845, 867538, 927640, 3901, 26201, 58950, 141364, 144359, 154332, 169090, 171907, 174692, 188108, 193281, 201881, 201895, 203524, 203570, 204350, 206278, 206421, 218912, 220646, 223801, 226877, 231282, 234450, 236397, 238271, 241212, 241213, 242959, 246042, 252320, 258570, 259522, 261559, 267428, 268746, 270139, 270772, 272988, 273793, 277076, 284381, 293475, 294495, 309931, 310341, 313457, 314349, 314351, 320496, 324954, 339595, 351064, 358121, 366482, 380354, 380812, 383361, 389650, 392585, 425455, 449220, 489001, 489416, 516240, 523796, 548070, 549903, 550478, 559532, 612621, 673049, 700899, 736798, 867539
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8a5) Gecko/20041113 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8a5) Gecko/20041113 I'd like to open meta bug in order to track problems relate to message/rfc822 attachment(forwarded mail) and ".eml" file, and in order to close many dup bugs which makes a complaint about forwarded mail(=message/rfc822 part of multipart mail). Forwarding mail as messeage/rfc822 attachment is usual useage in business use, bugs related messeage/rfc822 will become very serious, I think, if Thunderbird 1.0 will be shipped. I set product="Thunderbird" although this bug points to Mozilla mail&News bug also, since Thunderbird will be main stream of mailer of Mozilla family. Reproducible: Always Steps to Reproduce: Following is current summary based on bug 268746 comment #4 From Mike Cowperthwaite and my bug 203570 Comment #22. Seamonkey Thunderbird (1) Nested message/rfc822 part in multipart/mixed etc. is not processed properly (parent's attachment is used as child mail's attachment) Both bug 203570 bug 241267 (2) Commands(reply, forward, viewsource and so on) are disabled message/rfc822 bug 204350 bug 224967 .EML files bug 241213 bug 268746 (Note: Opposite request to these exists : bug 201881) (3) Envelope panel message/rfc822 ? ? .EML files bug 241212 ? (4) Images in HTML message/rfc822 part in Mail message/rfc822 bug 206278 ? (5) Images in HTML message/rfc822 part in News post message/rfc822 bug 203524 ?
Current open bugs who has 'rfc822' or '.eml' or 'forwarded attachment' in summary fields. - Search condition : Product = mail&new || thunderbird Status = UNCONFIRMED || NEW || ASSIGNED || REOPEND Resolution = --- Sumary contains = ('822') || ('eml') || ( 'foward" && 'attach' ) - Bugs already listed in comment #0 are omitted. - This bug is also omitted. - Summary is shortened to fit into 80 bytes line. *KEYWORD* *BUG-No.* *SUMARY* 822, (fwd&att) bug 3901 want ability to forward message/rfc822 attachmen 822 bug 11013 add drag message/rfc822 type mime attachments to eml bug 11076 *.eml, news://host/article or imap:// should open foward&attach bug 17479 Multi-forward (N messages each with 1 attachment) eml bug 22878 Import eml from clipboard eml bug 26201 Doubleclicking on an .eml file opens Outlook Exp foward&attach bug 35587 Attachments in forwarded mails should be shown ne eml bug 38109 Eml attachment with non-ascii in the header shows 822 bug 46502 Fetch of RFC822.SIZE is redundant eml bug 56908 Non-ascii file name is displayed incorrectly in foward&attach bug 58950 Non-ascii chars in the mail body forwarded as an foward&attach bug 65159 multipart/alternative :: text/enriched message bo foward&attach bug 82016 Non-ascii file name and Subject in the body of No foward&attach bug 83018 forwarding attachment problem when orginal msg wa 822 bug 83521 Use RFC822 "groups" for Mozilla's "lists" during foward&attach bug 91515 Unable to Edit message as new/from Drafts when fo 822 bug 97073 Message "Save As..." should resemble RFC 822 he foward&attach bug 109288 Icon for attached forwarded mail should not be 822 bug 110605 Viewer doesn't support recipient "groups"(RFC822) foward&attach bug 114046 Ability to send/forward address book card by e-m foward&attach bug 115163 Apple double attachment not correctly supported foward&attach bug 128848 Forwarding forwarded attached mail: Text missing 822 bug 141364 embedded rfc822 message doesn't show up when me eml bug 144359 Mac: Saving a mail as eml type generates an empty foward&attach bug 149111 MDN receipt: need to reload the message in case eml, (fwd&att) bug 154332 Forwarding a ".EML" attachment adds additional foward&attach bug 157640 forwarding or replying to a message with an atta foward&attach bug 161391 Forward as attachment broken on OSX eml bug 166541 Add support for X-Unsent property in .eml files foward&attach bug 169090 'From' field not indented in 'Forwarded As Attac 822 bug 169493 incorrect parsing of (non-RFCx822) list of mail eml bug 171907 drag & drop an eml file into a mailbox folder eml bug 174692 gif, bmp, and jpg-format attachments are not disp eml, (fwd&att) bug 188108 Forwarding an AOL forwarded message shows forward foward&attach bug 189206 Attachment of forwarded message not readable by eml bug 193281 Ability to import e-mail messages from .eml text foward&attach bug 198551 cpu usage 100% and mozilla not responding if I fo foward&attach bug 199982 Mac: the forward as attachment mail body charset 822 bug 201895 heed the mailnews.reuse_message_window pref, when foward&attach bug 204612 Facility of saving forwarded attached messages to foward&attach bug 215252 move "Forward" preference (inline/attachment) to foward&attach bug 217979 S/MIME encrypted msg forwarded as smime.p7m atta eml bug 219240 File/Attachments/1 Count on Us.eml/Open -> progr eml, (fwd&att) bug 220646 Forward as attachment: Attachment name is subject foward&attach bug 224986 unable to change forwarding type from "As Attach 822 bug 226877 Cannot move (drag) attached mail (message/rfc822) 822 bug 227360 Wrong character encoding when viewing message/rfc eml, (fwd&att) bug 227720 attachments shown as "ForwardedMessage.eml" when eml bug 227870 Save as EML can corrupt HTML attachment's CSS sty foward&attach bug 227994 Forward inline should grab all text, including te foward&attach bug 228058 Encoded attachment(s) not identified/shown in a foward&attach bug 230448 Change default forwarding preference to inline in 822 bug 231282 Opening RFC822 attachment into its window throws foward&attach bug 234449 UUencode'd attachment handled as text when inline 822 bug 234450 Protocol Error RFC822.peek should be BODY.peek eml bug 238271 Save message As Text (or HTML), file gets double 822, (fwd&att) bug 238465 Forwarded message (message/rfc822 attachment) reo eml bug 239685 non accessible attachments in .eml foward&attach bug 239698 Unable to edit HTML attachments when forwarding foward&attach bug 239909 Cannot forward mail with attachments eml bug 241216 Integrate support for opening .EML files to brows eml bug 242959 Thunderbird should open .eml files from command l eml bug 246042 Saving Mail als EML doesn't work on Network Drive foward&attach bug 249236 Error message appears when trying to forward an e foward&attach bug 252320 Previewing attached forwarded message fails on IM eml bug 253216 Opening .eml file shows message source, rather th foward&attach bug 254931 Shift-click on Forward: toggles plain/HTML for As eml bug 256183 Extremly slow saving of attachements if one messa eml bug 258570 Add ability to export multiple messages to .eml f 822 bug 259522 "Filing" message/rfc822 attachment to folder disa eml bug 261395 improved eml import and export for multiple .eml- eml bug 261559 Thunderbird should register *.eml file type assoc 822 bug 263854 Crash while viewing message/rfc822 with attachmen foward&attach bug 269351 can't forward special message as attachment *KEYWORD* *BUG-No.* *SUMARY*
Status: UNCONFIRMED → NEW
Ever confirmed: true
Linklify bug 270772 for ease of access.
822&eml Bug 271094 Opening message/rfc822 or eml attachment from compose window: incorrectly handled
WADA, do you have any plan in which sequence and when will you fix these bugs?
(In reply to comment #5) > WADA, > do you have any plan in which sequence and when will you fix these bugs? There is no plan to "fix bugs", because this bug's obejective is to close many DUP bugs, as I said in comment #0. First fruit of this bug is finding that Bug 238417 & Bug 270772 are DUP. - Bug 238417 has been closed as DUP of Bug 270772, because newer Bug 270772 has better description on problem, as Bug 238417 comment #9 says. Second fruit is Bug 223801 which has been placed in "Depends on:" field recently. - Bug 223801 can be closed as DUP of one of bugs listed in this bug, or some bugs listed in this bug can be closed as DUP of Bug 223801.
I've opened Bug 279650 as work area for using "Show dependency tree" in order to overlook related bugs. Bug 279650's "Depends on:" has bugs listed in comment #0 and comment #4 initially. See "Show dependency tree" of Bug 279650.
First approach for closing DUPs is ; In order to make "search with 'Summary contains 822 or eml'" effective, add "rfc822" or ".eml" to summary(and whiteboard if required) which has "attach & foward" but doesn't have "822" nor "eml", if the bug has relation to "rfc822" or ".eml",
I've done comment #8 work from 169090 to 269351 in list of comment #1, although I don't think perfect work.
Cc: ing to Mike, expecting your co-operation :-)
eml Bug 264167 In browser view of messages (.EML files), output links to attachments
I've done comment #8 work from 3901 to 166541 in list of comment #1, then finished all. Second approach for closing DUPs is ; In order to make "search with 'Summary contains .eml'" effective, ("Summary contains eml" hits "*emly" too, then '.eml' is better.) change 'eml' in summary to '.eml' if ".eml" related bug.
I've finished second work. I've also changed 'rfc/822' to 'message/rfc822' in a few bugs opened by Seth. I think many of related bugs can now be searched by "Summary contains rfc822 or .eml'.
As of today, 67 open bugs are found by "Summary contains any of word/string of 'rfc822 .eml'". (Product=any,Component=any,Staus=any,Resolution=---)
Puting all found bugs to "Blocks:" of this bug. I think that this bug can now be used as meta bug for tracking "rfc822 / .eml" related bugs.
Blocks: 224967, 226877, 227360, 227720, 227870, 227994, 231282, 234450, 236397, 238271, 239685, 241212, 241213, 241216, 242959, 246042, 252320, 253216, 258570, 259522, 261559, 264167, 267428, 268746, 270068, 270115, 270139, 270772, 271094, 272988, 277076, 3901, 11013, 11076, 22878, 26201, 35587, 46502, 56908, 58950, 83521, 110605, 141364, 144359, 154332, 160141, 166541, 169090, 171907, 174692, 188108, 193281, 201881, 201895, 203524, 203570, 204350, 204612, 206278, 206421, 218912, 219240, 220646, 223801
No longer depends on: 223801
Whiteboard: rfc822 .eml
Correction. Bug numbers should be placed in "Depends on:" of this bug("Blocks:" of each bug). Sorry for spam.
No longer blocks: 224967, 226877, 227360, 227720, 227870, 227994, 231282, 234450, 236397, 238271, 239685, 241212, 241213, 241216, 242959, 246042, 252320, 253216, 258570, 259522, 261559, 264167, 267428, 268746, 270068, 270115, 270139, 270772, 271094, 272988, 277076, 3901, 11013, 11076, 22878, 26201, 35587, 46502, 56908, 58950, 83521, 110605, 141364, 144359, 154332, 160141, 166541, 169090, 171907, 174692, 188108, 193281, 201881, 201895, 203524, 203570, 204350, 204612, 206278, 206421, 218912, 219240, 220646, 223801
Depends on: 224967, 226877, 227360, 227720, 227870, 227994, 231282, 234450, 236397, 238271, 239685, 241212, 241213, 241216, 242959, 246042, 252320, 253216, 258570, 259522, 261559, 264167, 267428, 268746, 270068, 270115, 270139, 270772, 271094, 272988, 277076, 3901, 11013, 11076, 22878, 26201, 35587, 46502, 56908, 58950, 83521, 110605, 141364, 144359, 154332, 160141, 166541, 169090, 171907, 174692, 188108, 193281, 201881, 201895, 203524, 203570, 204350, 204612, 206278, 206421, 218912, 219240, 220646, 223801
Second approach for closing DUPs is ; Pick up important bugs which should closed ASAP in addition to bugs listed in comment #0, from the dependency tree. Third approach for closing DUPs is ; Close DUP bugs as many as possible.
Summary: [Meta bug] Problems relate to message/rfc822 attachment(forwarded mail) and '.eml' file → [Meta bug] Problems relate to message/rfc822 attachment(forwarded mail) in a mail and '.eml' file
(In reply to comment #11) > eml Bug 264167 In browser view of messages (.EML files), output links to > attachments I'd like to hilight my suggested code for a possible solution. https://bugzilla.mozilla.org/show_bug.cgi?id=264167#c4 <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=264167#c4">bug264167 comment #4</a> regards, A21. ps: nice job, wada!
Adding next bugs in "Depends on:" of this meta bug. Bug 273793 : "Attached" message/rfc822 not shown in attachment panel, when Inline Display is off Bug 309931 : message/rfc822 attachments dropped when importing from Outlook Bug 313457 : Alert popup if open a saved .eml file Bug 314349 : Reply/Forward/Edit with .EML or message/rfc822: fails if no Message-Id Bug 314351 : Reply to .EML or message/rfc822: problems with MIME-encoded headers
Bugzilla Bug 324954 HTML Reply to .EML/rfc822 attachment without Message-ID results in HTML source within compose body
Adding Bug 328324 to dependency tree because it involves problem in attachment display of nested message/rfc822 part. > Bug 328324 : Display attachments inline causes incorrect number of attachments to display Current 3 major issues when message/rfc822 part or .eml is involved. (1) Display of main mail : Bug 35587 Bug 328324 (2) Display of attached mail : Bug 203570 (3-a) Action on attached mail : Bug 204350 (3-b) Action on .eml file : Bug 241213(Seamonkey) Bug 268746(Thunderbird)
Depends on: 328324
Bugzilla Bug 338536 Errors in JS console on opening .EML file
Bugzilla Bug 339595 Saving as .EML removes starting dot in all lines
.MSG messages cannot be opened too.
Using .eml extensions on the file names of attached e-mail messages causes some virus scanners to reject e-mail or flag it as suspicious. I started seeing this problem as soon as I upgraded to TB 2. It's not reasonable to expect sysadmins to change this behavior in their virus scanners; some will, but some simply won't consider it and won't listen to any reasons. The use, or non-use, of the .eml extension on attachments needs to be under control of the individual TB user, depending on his/her environment and the behavior of the e-mail systems he/she needs to contend with. To me, this issue is a blocker to my using TB 2. I've gone back to TB 1.5 and cannot use or recommend TB 2 until / unless the .eml extension is made optional or configurable. I assume I'm probably not alone on this. See bug 220646 and bug 380354 for more details.
Looking into bug 11013, it seems related to just the MailNews component of the Mozilla Suite. Besides, part of the functionality that's being asked for there is already present in Thunderbird (i.e. treating message/rfc822 attachments as if they were real messages). I therefore propose to remove bug 11013 from the bugs being tracked here.
Also, bug 11076 does not seem to apply to Thunderbird.
(In reply to comment #26) To Mauro Cicognini: Main reasons why Product=Thunderbird are; 1. There is no Product=Thunderbird-and-Mail&News 2. For ease of search by both Thunderbird users and Seamonkey users - Tb users don't usually search Seamonkey bugs - Sm users searches Tb bugs because they know many common issues exist Please don't remove Seamonkey(App-Suite) only bugs.
When forwarding or attaching a message we should set the Content-Disposition filename suggestion without adding any extension, or even remove any extension if it is already part of the filename. As described in part 2.1, 2.2, and 2.3 of the RFC 2183 “the sender may want to suggest a filename” AND when “the receiving MUA writes the entity to a file, the suggested filename should be used as a basis for the actual filename.” Please note that filename extension serves as a file-system specific way to identify actual type of a file which is stored in the same file-system. Email system is using MIME Content-Type for that purpose and the file extension is irrelevant and even unwanted because the file in question may be saved to a file-system that does not use filename extensions at all. MUA should add the extension, or set the creator code, or set the Type code, as appropriate for the target file-system at the time of writing to the specific file-system. The MIME content-type concept is invented to solve the problem of transferring files between different systems. Translation between MIME content-type and file-system specific file type is OS specific. Any MUA that is relying on the filename extension from the Content-Disposition filename field to recognize content-type is non-conforming non-interoperable and should not be used. We should not try to fix the problems of deficient substandard mailers. So, when forwarding or attaching a message we should set the Content-Type: message/rfc822 and Content-Disposition filename suggestion without adding any extension, or even remove any extension if it is already part of the filename.
Above comment #29 sounds to be for Bug 220646 ... To Milan Kupcevic: This bug is "Meta bug", for ease of tracking bugs.
See Bug 391503 Someone got an email. He now forwards this mail to me as an .eml attachment. I open his mail, click on the .eml attachment and TB opens a new mail window which looks like I got this mail from the attachment. Now I click on "reply", type some text, and then do file->save. TB now says: "unable to save your message as draft" So it seems that TB has problems with replies to forwarded mails.
This bug persists on Thunderbird 3.0b2 (niglty from 22 january , 2009 ) David Ascher Be welcome !
Component: General → Backend
Product: Thunderbird → MailNews Core
Version: unspecified → Trunk
Still getting unusable winmail.dat on Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:188.8.131.52pre) Gecko/20110307 Lightning/1.0b2 Lanikai/3.1.10pre
... that's bug 77811 though and not related to message/rfc822 attachments (proprietary Microsoft TNEF content type). Also, as was stated in comment #30, this is a meta bug, thus no specifics here please but in the respective bugs.
Subscribing. Still valid for TB 8.0 under linux.
You need to log in before you can comment on or make changes to this bug.