Launchpad has imported 20 comments from the remote bug at https://bugzilla.mozilla.org/show_bug.cgi?id=11013.
If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. ------------------------------------------------------------------------ On 1999-07-31T22:06:50+00:00 Endico wrote: When you send a mail message that bounces, the mailer daemon's bounce message is generally a multipart mime message where your original message is enclosed as a message/rfc822 attachment. It would be nice to have an easy way get at this attachment so you can re-address, edit and resend it. Being able to drag an attachment from the bounce message window to the Drafts folder would allow this. Reply at: https://bugs.launchpad.net/thunderbird/+bug/848183/comments/0 ------------------------------------------------------------------------ On 1999-07-31T22:29:59+00:00 Endico wrote: Marking this RFE HELP WANTED. See http://www.mozilla.org/mailnews/jobs.html for info on submitting features to the mail/news team. This requires drag&drop to be implemented.(RSN i think) Reply at: https://bugs.launchpad.net/thunderbird/+bug/848183/comments/1 ------------------------------------------------------------------------ On 1999-08-01T13:32:59+00:00 Rhp-8 wrote: This is sort of similar to Bug #3901. Bascially, I'm pushing feature requests past B1 for now. - rhp Reply at: https://bugs.launchpad.net/thunderbird/+bug/848183/comments/2 ------------------------------------------------------------------------ On 1999-08-01T20:50:59+00:00 Sspitzer wrote: marking M15. Reply at: https://bugs.launchpad.net/thunderbird/+bug/848183/comments/3 ------------------------------------------------------------------------ On 1999-08-24T17:29:59+00:00 Phil-formerly-netscape wrote: Bulk-resolving requests for enhancement as "later" to get them off the Seamonkey bug tracking radar. Even though these bugs are not "open" in bugzilla, we welcome fixes and improvements in these areas at any time. Mail/news RFEs continue to be tracked on http://www.mozilla.org/mailnews/jobs.html Reply at: https://bugs.launchpad.net/thunderbird/+bug/848183/comments/4 ------------------------------------------------------------------------ On 1999-09-01T00:35:59+00:00 Phil-formerly-netscape wrote: Reopen mail/news HELP WANTED bugs and reassign to nob...@mozilla.org Reply at: https://bugs.launchpad.net/thunderbird/+bug/848183/comments/5 ------------------------------------------------------------------------ On 1999-11-30T18:39:59+00:00 Pmock wrote: changing qa assigned to pm...@netscape.com Reply at: https://bugs.launchpad.net/thunderbird/+bug/848183/comments/6 ------------------------------------------------------------------------ On 2001-01-31T00:13:13+00:00 Fenella wrote: Change QA-assign to fenella Reply at: https://bugs.launchpad.net/thunderbird/+bug/848183/comments/7 ------------------------------------------------------------------------ On 2001-02-16T21:20:42+00:00 Fenella wrote: To Esther.. Reply at: https://bugs.launchpad.net/thunderbird/+bug/848183/comments/8 ------------------------------------------------------------------------ On 2004-01-16T23:33:05+00:00 Mcow wrote: xref bug 204612. See also bug 204350. Reply at: https://bugs.launchpad.net/thunderbird/+bug/848183/comments/9 ------------------------------------------------------------------------ On 2004-12-19T01:55:33+00:00 Ekoontz wrote: Made a web page to help myself learn about mozilla programming and to think out loud about this bug : http://hiro-tan.org/~ekoontz/bug11013/ Reply at: https://bugs.launchpad.net/thunderbird/+bug/848183/comments/10 ------------------------------------------------------------------------ On 2009-06-14T13:47:27+00:00 Kairo-kairo wrote: This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state. If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way. If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar). If no action happens within the next few months, we move this bug report to an EXPIRED state. Query tag for this change: mass-UNCONFIRM-20090614 Reply at: https://bugs.launchpad.net/thunderbird/+bug/848183/comments/11 ------------------------------------------------------------------------ On 2009-06-14T13:52:31+00:00 Kairo-kairo wrote: This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state. If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way. If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar). If no action happens within the next few months, we move this bug report to an EXPIRED state. Query tag for this change: mass-UNCONFIRM-20090614 Reply at: https://bugs.launchpad.net/thunderbird/+bug/848183/comments/12 ------------------------------------------------------------------------ On 2009-06-14T16:53:17+00:00 8-gil wrote: This bug applies to Thunderbird. Should it be re-registered in MailNews Core instead of Seamonkey? Reply at: https://bugs.launchpad.net/thunderbird/+bug/848183/comments/13 ------------------------------------------------------------------------ On 2009-06-14T17:56:47+00:00 Kairo-kairo wrote: This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state. If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way. If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar). If no action happens within the next few months, we move this bug report to an EXPIRED state. Query tag for this change: mass-UNCONFIRM-20090614 Reply at: https://bugs.launchpad.net/thunderbird/+bug/848183/comments/14 ------------------------------------------------------------------------ On 2009-06-14T19:56:11+00:00 Kairo-kairo wrote: This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state. If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way. If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar). If no action happens within the next few months, we move this bug report to an EXPIRED state. Query tag for this change: mass-UNCONFIRM-20090614 Reply at: https://bugs.launchpad.net/thunderbird/+bug/848183/comments/15 ------------------------------------------------------------------------ On 2009-06-14T20:13:06+00:00 Kairo-kairo wrote: This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state. If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way. If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar). If no action happens within the next few months, we move this bug report to an EXPIRED state. Query tag for this change: mass-UNCONFIRM-20090614 Reply at: https://bugs.launchpad.net/thunderbird/+bug/848183/comments/16 ------------------------------------------------------------------------ On 2009-06-14T20:20:10+00:00 Kairo-kairo wrote: This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state. If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way. If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar). If no action happens within the next few months, we move this bug report to an EXPIRED state. Query tag for this change: mass-UNCONFIRM-20090614 Reply at: https://bugs.launchpad.net/thunderbird/+bug/848183/comments/17 ------------------------------------------------------------------------ On 2009-06-15T05:18:18+00:00 Mkmelin+mozilla wrote: Let's move it to mn-core. (The front-end part shouldn't be that large / different.) Reply at: https://bugs.launchpad.net/thunderbird/+bug/848183/comments/18 ------------------------------------------------------------------------ On 2011-02-25T13:04:50+00:00 Brian J. Murrell wrote: Has this ticket gone moribund for a new ticket covering the same general features? Reply at: https://bugs.launchpad.net/thunderbird/+bug/848183/comments/19 ** Changed in: thunderbird Status: Unknown => Confirmed ** Changed in: thunderbird Importance: Unknown => Wishlist -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/848183 Title: RFC822 Attachments and .EML files cannot be moved to folders To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/848183/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs