Closed
Bug 3901
Opened 26 years ago
Closed 19 years ago
want ability to forward message/rfc822 attachments
Categories
(SeaMonkey :: MailNews: Message Display, enhancement, P3)
Tracking
(Not tracked)
RESOLVED
FIXED
Future
People
(Reporter: jgmyers, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: helpwanted)
Consider a message, for example a bounce message, which has an imbedded
message/rfc822. The user can click on the paperclip button, then double-click
on the imbedded message/rfc822 to display the imbedded message. Unfortunately,
the imbedded message cannot be forwarded.
There should be some way to forward the imbedded message/rfc822, as if it were a
top-level message.
Reporter | ||
Comment 1•26 years ago
|
||
Being able to do most of the other operations on the "Message" menu make sense.
Reply, Edit as new, Copy, and Add to Addressbook. Move, Mark, and the Thread
items would not make sense.
Updated•26 years ago
|
Assignee: phil → rhp
Comment 2•26 years ago
|
||
Hmm. Maybe a libmime issue? -> rhp
Updated•26 years ago
|
Status: NEW → ASSIGNED
Comment 3•26 years ago
|
||
I'll put this on the list...could be a libmime issue, but I will have to
investigate.
- rhp
Updated•26 years ago
|
Target Milestone: M5
Updated•25 years ago
|
Target Milestone: M5 → M6
Comment 4•25 years ago
|
||
Won't get here before M5.
Updated•25 years ago
|
Target Milestone: M6 → M9
Comment 5•25 years ago
|
||
Enhancements will probably be later in the cycle.
Updated•25 years ago
|
Target Milestone: M9 → M12
Comment 6•25 years ago
|
||
Pushing enhancements out past B1.
- rhp
Updated•25 years ago
|
Target Milestone: M16 → M20
Comment 8•25 years ago
|
||
Moving to the helpwanted list
Moving target milestone to "future" to be reviewed at a later time
Target Milestone: M20 → Future
Comment 13•24 years ago
|
||
See also bug 69359.
Comment 14•23 years ago
|
||
Do we seriously have to detach attachments from the incoming message and
manually attach them to a forwarded message to include attachments in the
forwarded message?? This is way annoying. Since we are nearing 1.0 can the
importance of this "enhancement" be reconsidered?
Comment 15•23 years ago
|
||
QA Contact: trix → stephend
Updated•21 years ago
|
Flags: blocking1.6b+
Updated•21 years ago
|
Flags: blocking1.6b+
Updated•20 years ago
|
Product: Browser → Seamonkey
Updated•20 years ago
|
Updated•20 years ago
|
Comment 16•19 years ago
|
||
This has been fixed by the patch for bug 204350.
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
Comment 17•19 years ago
|
||
(In reply to comment #16)
> This has been fixed by the patch for bug 204350.
If this is fully fixed by 204350, then shouldn't bug 34150 be removed as blocker?
Also, does Bug 11013 factor in?
Comment 18•19 years ago
|
||
(In reply to comment #17)
> (In reply to comment #16)
> > This has been fixed by the patch for bug 204350.
>
> If this is fully fixed by 204350, then shouldn't bug 34150 be removed as
> blocker?
Yep.
> Also, does Bug 11013 factor in?
No, that's unrelated.
No longer depends on: 34150
You need to log in
before you can comment on or make changes to this bug.
Description
•