Closed
Bug 165069
Opened 22 years ago
Closed 21 years ago
Adding custom headers to email
Categories
(MailNews Core :: Backend, enhancement)
MailNews Core
Backend
Tracking
(Not tracked)
People
(Reporter: bertosmailbox, Assigned: mscott)
Details
I'm working on the ability to add custom headers to email. Since every time I ask a question about this, everyone tells me that custom header support is built in, the best way I can explain is using this page as the explanation: http://www.habeas.com/support/install.htm
Comment 1•22 years ago
|
||
my query: field: product; value: 'mailnews' field: summary; value: 'custom header' other fields: none time spent: ~1 minute reporter, please understand that ~35% of new bugs are duplicates. To help us respond to user feedbacks quickly, search Bugzilla for duplicates before filing a bug report. Thank you. *** This bug has been marked as a duplicate of 16925 ***
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
Mr. Wang: I think that bug #16925 is slightly different from what I'd like to setup. Basically the custom header support that is discussed there is to add headers, which you can fill in at compose time along with the to, cc, bcc, etc. Please take a look at comments #45 and #46 in that bug report. This is not what I'm trying to accomplish. The feature I want to add allows you to add a header, give it a value, and from then on it's added to every email you write. Make sense? Thanks.
Comment 3•21 years ago
|
||
Actually, this is a duplicate of bug 61520 which, fortunately, seems to be nearing completion. :) 16925 was fixed, but this wasn't. Wish I had rights to correct the error.
Comment 4•21 years ago
|
||
re-openning to remove dependacy and set correct dupe.
Comment 5•21 years ago
|
||
*** This bug has been marked as a duplicate of 61520 ***
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago → 21 years ago
Resolution: --- → DUPLICATE
Updated•20 years ago
|
Product: MailNews → Core
Updated•16 years ago
|
Product: Core → MailNews Core
You need to log in
before you can comment on or make changes to this bug.
Description
•