Closed Bug 294221 Opened 20 years ago Closed 17 years ago

"Undisclosed-recipients" shown contrary to setting

Categories

(Thunderbird :: General, defect)

Product:
Thunderbird
Component:
General
Platform:
x86
Windows 2000
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WORKSFORME

People

(Reporter: bugzilla, Unassigned)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4

As I already stated in the title, mail I send only to Bcc: shows "To:
undisclosed-recipients:;".

I've checked user.js and it does contain the code:
// E-mail without anything in the To: field
user_pref("mail.compose.add_undisclosed_recipients", false);

This code is also copied to prefs.js (without the comment).

Specifications:
W2K SP4 completely up to date
Thunderbird 1.0.2 (English)
Tiny Personal Firewall
AVG 

Reproducible: Always

Steps to Reproduce:
1.New Message
2.All addressees (at least one and one being an alternate address to yourself)
in "Bcc:"
3.Any message
4.Send it

Actual Results:  
The mail is sent. On reception, it shows "To: undisclosed-recipients:;".


Expected Results:  
That line should not have been visible with the settings used.
only as note: 
To: Undisclosed Recipients was added to prevent certain sendmail servers from
adding their own version of a to: line that revealed the entire bcc: list. Your
own immediate server may not do this, but I don't know what happens when your
message passes through other SMTP servers on its way to its final destinations.
I suppose no one is served by revealing a bcc: list. So if the potential for
unintended disclosure doesn't bother you, set the pref
mail.compose.add_undisclosed_recipients to false.
Version: unspecified → 1.0
(In reply to comment #1)
> only as note: 
> To: Undisclosed Recipients was added to prevent certain sendmail servers from
> adding their own version of a to: line that revealed the entire bcc: list. Your
> own immediate server may not do this, but I don't know what happens when your
> message passes through other SMTP servers on its way to its final destinations.
> I suppose no one is served by revealing a bcc: list. So if the potential for
> unintended disclosure doesn't bother you, set the pref
> mail.compose.add_undisclosed_recipients to false.

Please read the reporter's comments. Setting
mail.compose.add_undisclosed_recipients to false does not remove the appearance
of "To: undisclosed-recipients:;"

I can also verify this and have checked the setting with the Advanced
Preferences extension to Thunderbird.
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:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

"Auto-resolve?" "Not confirmed in three months?" 

This bug was confirmed in less than **14**hours**.

If you're going to knock a bug off the list for cause, please give us a better
reason than that. A little research would reveal the two users who reported and
confirmed this bug to be more than just ad hoc users. We've combined spent a lot
of time supporting other users. 

We can not only confirm the existence of the problem, but have provided steps to
reproduce.

I know the developers are busy, but please take a bit of time to at least look
at this one. If more information is necessary, at least let us know what you need.
This bug was found in version 1.0.2 and is still present in version 1.0.6. I
don't know if it is still present in version 1.0.7 because that version contains
a bug that prevents me from running it at all.
(In reply to comment #5)
> This bug was found in version 1.0.2 and is still present in version 1.0.6. I
> don't know if it is still present in version 1.0.7 because that version contains
> a bug that prevents me from running it at all.

I can confirm it is still present in 1.0.7.


WFM - setting mail.compose.add_undisclosed_recipients to false results in a
message w/o a To header. If you look in your sent folder, does it have the
"undisclosed recipients" To: header, or is it only when you receive the message?
If the latter, then it's your mail server doing it.
(In reply to comment #7)
> WFM - setting mail.compose.add_undisclosed_recipients to false results in a
> message w/o a To header. If you look in your sent folder, does it have the
> "undisclosed recipients" To: header, or is it only when you receive the message?
> If the latter, then it's your mail server doing it.

From the sent message:

Subject: Test
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
To: undisclosed-recipients:;
(In reply to comment #7)
> WFM - setting mail.compose.add_undisclosed_recipients to false results in a
> message w/o a To header. If you look in your sent folder, does it have the
> "undisclosed recipients" To: header, or is it only when you receive the message?
> If the latter, then it's your mail server doing it.

It seems indeed to be a server artifact. If I send it out through my primary
e-mail account, the "undisclosed recipient" gets added. If I send it out through
my GMail account, it doesn't. (And yes, in both cases I sent it to the same
Hotmail account.)

Thanks for pointing this out to me.
If it *is* a server artifact, it happens a lot. I have been testing with my ISP
(Charter Communications) as well as Free SMTP Server from www.softstack.com.

Sending through either to the same destination accounts gives the same result.

Given that, I am reluctant to jump on the "It's the Server!" bandwagon.

Besides, I can confirm that the message contains the "To: undisclosed
recipients" in my Sent folder. How can it then be a server artifact?
(In reply to comment #10)
> If it *is* a server artifact, it happens a lot. I have been testing with my ISP
> (Charter Communications) as well as Free SMTP Server from www.softstack.com.
> 
> Sending through either to the same destination accounts gives the same result.
> 
> Given that, I am reluctant to jump on the "It's the Server!" bandwagon.
> 
> Besides, I can confirm that the message contains the "To: undisclosed
> recipients" in my Sent folder. How can it then be a server artifact?

I verified the source in my Sent folder and there was no "To: undisclosed
recipients". Maybe this bug was reintroduced in version 1.0.7?
(In reply to comment #11)
> (In reply to comment #10)
> > If it *is* a server artifact, it happens a lot. I have been testing with my ISP
> > (Charter Communications) as well as Free SMTP Server from www.softstack.com.
> > 
> > Sending through either to the same destination accounts gives the same result.
> > 
> > Given that, I am reluctant to jump on the "It's the Server!" bandwagon.
> > 
> > Besides, I can confirm that the message contains the "To: undisclosed
> > recipients" in my Sent folder. How can it then be a server artifact?
> 
> I verified the source in my Sent folder and there was no "To: undisclosed
> recipients". Maybe this bug was reintroduced in version 1.0.7?

It hasn't changed for me since you before the initial bug report.
QA Contact: general
confirm, version 3.0a1pre (2008050203)
Status: UNCONFIRMED → NEW
Ever confirmed: true
While my received test message got the To: undisclosed-recipients:; added, the one in my Sent folder doesn't have it, so I'm pretty sure it's the server that adds it. 

Nikolay: did you check the copy in your Sent folder?
Anyone else seeing it added on the copy in their Sent folder? (And Gmail might not count... though I didn't try.)
version 3.0a2pre (2008051203) 

sent copy has
To: undisclosed-recipients:;
(imap, sent=inbox)
Magnus this is depends on SMTP server, worksforme TB3a1, behavior is correct. I'm using IMAP sent contain message w/o To: field. If there no TO: most SMTP servers add it as To: undisclosed-recipients:;.
Wayne: you did set the pref?

If this is only a server issue it should be closed, nothing we can do after the message leaves thunderbird.
Assignee: mscott → nobody
~ mail.compose.add_undisclosed_recipients=true
Wayne, TRUE is default change it to false.
with mail.compose.add_undisclosed_recipients=false, no To:
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.