Names get crossed between different profiles



MailNews: Message Display
13 years ago
12 years ago


(Reporter: Tony, Unassigned)


1.7 Branch
Windows 98

Firefox Tracking Flags

(Not tracked)





13 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.7.5) Gecko/20041217
Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.7.5) Gecko/20041217

If I set up two seperate profiles, after a few email are sent from or between
the two, eventually when sending an email or posting to a newsgroup, the second
profile will show the user name of the first profile in the headers or message

Reproducible: Always

Steps to Reproduce:
1.Setup 2 seperate email and newsgroup profiles.
2.Send a few test emails between the two profiles, and test emails to the same
profile you are using. 

Actual Results:  
Look in the "message source" of a test email from the second profile and you
will find the user name of the first profile along with that info.

Expected Results:  
It should have kept the two profiles seperate.

I reported this as critical since it deals with the anonimity of any mozilla
user with two or more profiles.  A second anonomous profile which you may not
want to contain your actual name (like for use in newsgroups) is being
comprimised.  Your actual identity can be seen through a supposed seperate profile.

I am not sure if this problem existed before upgrading to 1.7.5

Comment 1

13 years ago
Can you be more specific? Can you maybe attach the source of such two mails in
the bug here so we can see what you mean (and on what headers you see it's from
the first/second profile)?
Version: unspecified → 1.7 Branch


13 years ago
Assignee: sspitzer → mail
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.