Closed
Bug 16499
Opened 25 years ago
Closed 22 years ago
Work around sendmail bug which reveals bcc recipients when all recipients are bcc
Categories
(MailNews Core :: Composition, enhancement, P3)
Tracking
(Not tracked)
VERIFIED
FIXED
mozilla1.3alpha
People
(Reporter: slschroe, Assigned: bugzilla)
References
Details
(Keywords: privacy)
Attachments
(1 file)
1.23 KB,
patch
|
cavin
:
review+
sspitzer
:
superreview+
|
Details | Diff | Splinter Review |
In Netscape Mail, I would love to be able to send an e-mail message without havi ng any addresses shown - I don't want to have to mail myself the message, then B CC the other people I would like to send it to. I realize the point of carbon co pying is to make a copy, but I would like there to be a way of witholding all ad dresses.
Assignee | ||
Updated•25 years ago
|
Status: NEW → ASSIGNED
Target Milestone: M15
Assignee | ||
Comment 1•25 years ago
|
||
slschroe, doesn't put all recipients in bcc isn't enough for you? If you do that, no address will be shown execpt the sender (FROM:).
What ducarroz suggests should do what you want: 1) New message 2) Change the recipient from To: to BCC: 3) Address your message and send Or are you talking about something else?
Updated•25 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → WORKSFORME
Updated•25 years ago
|
Severity: enhancement → critical
Status: RESOLVED → REOPENED
Comment 5•25 years ago
|
||
There is a more serious problem related to this: Although Mozilla does handle everything correctly, it triggers a stupid sendmail bug: When there's neither a To nor CC header, Sendmail will add an Apparently-To header revealing all envelope addresses! If the message has not yet been split up to individual recipients (eg at the smarthost though which Mozilla delivers the mail), this will reveal all BCC recipients. qmail-inject has implemented a workaround to this: It adds "CC: unlisted-recipients: ;" to the headers, which reportedly prevents sendmail from doing that very stupid and annoying thing. (BTW: This problem is also exploited by NS 4.x.)
Updated•25 years ago
|
Resolution: WORKSFORME → ---
Assignee | ||
Updated•25 years ago
|
Status: REOPENED → ASSIGNED
Updated•25 years ago
|
Summary: Undisclosed recipients in Mail possible? → Work around sendmail bug which reveals bcc recipients
Comment 6•25 years ago
|
||
Mass moving to M16 to get these off the M15 radar. Please let me know if this is really an M15 stopper.
Target Milestone: M15 → M16
Comment 7•25 years ago
|
||
This is not critical. It would be nice for us to implement this enhancement to workaround a server bug, but it isn't a high priority right now. Use a to: in your message to avoid the server bug.
Severity: critical → enhancement
Target Milestone: M16 → M20
Move enhancement to future target milestone for review in a later release. Adding helpwanted keyword.
Keywords: helpwanted
Target Milestone: M20 → Future
Assignee | ||
Comment 9•22 years ago
|
||
The solution of addressing the message to a empty address group named unlisted-recipient cause too much problem as some mail server doesn't not recognized it as a valid address. Therefore I choose to go the way Outlook did by addressing the message to the sender when no recipient are disclosed.
QA Contact: pmock → esther
Assignee | ||
Updated•22 years ago
|
Keywords: helpwanted
Whiteboard: have fix
Assignee | ||
Comment 10•22 years ago
|
||
If a message has only bcc recipients, the message will be addressed also to the sended (as to).
Comment 11•22 years ago
|
||
Comment on attachment 105343 [details] [diff] [review] Proposed fix, v1 r=cavin.
Attachment #105343 -
Flags: review+
Comment 12•22 years ago
|
||
Comment on attachment 105343 [details] [diff] [review] Proposed fix, v1 sr=sspitzer but won't this send mail the mail back to the person who sent it? (are we ok with that?) any thoughts about doing "Undisclosed Repients" that you sometimes see? or is that a spammer trick?
Attachment #105343 -
Flags: superreview+
Assignee | ||
Comment 13•22 years ago
|
||
As I said in comment #9, sending the message to an address group [Undisclosed Repients:;] or [unlisted-recipients:;] can cause trouble with some server and event some client as this kind of syntax (RFC822) doesn't to be fully supported! Some server might think it's an incomplete address and automatically add a domain to it which will result in a delivery error. That why I decided to choose the MS Outlook solution which is 100% safe. Sure the user will get the message back but that's a very small price to pay.
Comment 14•22 years ago
|
||
thanks for explaining it to me. sorry for not reading the whole bug first.
Assignee | ||
Comment 15•22 years ago
|
||
Fix checked in
Status: ASSIGNED → RESOLVED
Closed: 25 years ago → 22 years ago
Resolution: --- → FIXED
Whiteboard: have fix
Updated•22 years ago
|
Summary: Work around sendmail bug which reveals bcc recipients → Work around sendmail bug which reveals bcc recipients when all recipients are bcc
Comment 16•22 years ago
|
||
Using trunk build 20021121 on winxp, linux and max osx verifying that when the sender only puts BCC recipients, on Send we add the To: using the sender's email address. I viewed messages and they only show the To: in the addressing field, no one except the sender sees the BCC list (but only in the copy in the Sent folder).
Status: RESOLVED → VERIFIED
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
•