Closed Bug 165069 Opened 22 years ago Closed 21 years ago

Adding custom headers to email

Categories

(MailNews Core :: Backend, enhancement)

enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 61520

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
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.
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.
Depends on: 61520
re-openning to remove dependacy and set correct dupe.
Status: RESOLVED → UNCONFIRMED
No longer depends on: 61520
Resolution: DUPLICATE → ---

*** This bug has been marked as a duplicate of 61520 ***
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago21 years ago
Resolution: --- → DUPLICATE
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.