Open
Bug 169990
Opened 22 years ago
Updated 2 years ago
news: saving a news mesg as template doesnt work.
Categories
(MailNews Core :: Backend, defect)
MailNews Core
Backend
Tracking
(Not tracked)
NEW
People
(Reporter: grylchan, Unassigned)
References
Details
Using commercial trunk
2002-09-19-08-trunk/ NT 4.0
2002-09-20-08-trunk/ Mac 10.1.5, mac 9.2.2
2002-09-20-08-trunk/ linux 2.2, red hat 7.0
was trying to test bug 159988.
I'm not sure if the fix for bug 167538 or bug 167382
should have fixed this?
Anways, either online or offline, if you select a News mesg
and go to file|save as|template, the mesg will not be
saved to 'Template' folder under Local folders.
I can save a imap mail mesg to either the online or Local Folders
template folder fine. Just with News I can't.
Comment 2•22 years ago
|
||
I don't think my copyService changes are responsible here. I don't know if it
ever worked. From what I have found, basically the url listener is never
informed when url stops running. over to default owner.
Assignee: naving → sspitzer
Hardware: PC → All
Note to self: be sure to test Save as Template when this is fixed, since I
couldn't test that when I verified bug 159988.
Updated•20 years ago
|
Product: MailNews → Core
Comment 5•16 years ago
|
||
I doubt bienvenu is still looking at this.
Assignee: bienvenu → nobody
QA Contact: stephend → networking.news
Assignee | ||
Updated•16 years ago
|
Product: Core → MailNews Core
Saving mails as templates via File menu fails too.
Handling templates should be similar to handling drafts. Drafts could only be
saved from the composing window. This window has a different File - Save As sub
menu.
The code for saving templates is announced as 'obscured', and perhaps not needed any more, see
http://mxr.mozilla.org/mozilla/source/mailnews/base/src/nsMessenger.cpp#231
Existing messages can be saved as templates the usual way via Message - Copy To
- <Target Selection>.
Component: Networking: NNTP → Backend
QA Contact: networking.nntp → backend
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•