Reply to BCC'd mail adds `undisclosed-recipients:;`

RESOLVED WORKSFORME

Status

Thunderbird
Message Compose Window
RESOLVED WORKSFORME
3 years ago
2 years ago

People

(Reporter: kandel3, Unassigned)

Tracking

({regression})

31 Branch
regression

Thunderbird Tracking Flags

(thunderbird34 unaffected, thunderbird_esr31? affected)

Details

(Reporter)

Description

3 years ago
User Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:31.0) Gecko/20100101 Firefox/31.0 (Beta/Release)
Build ID: 20140716183446

Steps to reproduce:

1. Send email to `undisclosed-recipients:;` (For example, only Bcc)
2. Reply to that email (For example, check sent folder use 'Reply' button)


Actual results:

Attempt to send email to `undisclosed-recipients:;`


Expected results:

Shouldn't add anything in the `to` field, undisclosed-recipients:; is not a real email and it will fail to send.

Also this bug: https://bugzilla.mozilla.org/show_bug.cgi?id=189263

Updated

3 years ago
Component: Mail Window Front End → Message Compose Window

Comment 1

3 years ago
Confirmed on 31, not a problem on trunk though. 
Joshua, do you recall what fixed this? That should probably go into 31 I think.
Status: UNCONFIRMED → NEW
status-thunderbird34: --- → unaffected
status-thunderbird_esr31: --- → affected
tracking-thunderbird_esr31: --- → ?
Ever confirmed: true
Flags: needinfo?(Pidgeot18)
Keywords: regression
OS: Windows 8.1 → All
Hardware: x86_64 → All
Summary: Reply adds `undisclosed-recipients:;` → Reply to BCC'd mail adds `undisclosed-recipients:;`
Version: 34 → 31
(In reply to Magnus Melin from comment #1)
> Confirmed on 31, not a problem on trunk though. 
> Joshua, do you recall what fixed this? That should probably go into 31 I
> think.

The only bug that I can consider potentially regressing it didn't make it into 31, so I can't say.
Flags: needinfo?(Pidgeot18)

Comment 3

3 years ago
2014-06-04 broken
2014-06-06 ok

-> http://hg.mozilla.org/comm-central/pushloghtml?startdate=2014-06-04&enddate=2014-06-06

So fixed by bug 790855 as a side effect?

Comment 4

3 years ago
For the record: This still exists in 31.2.0.

Comment 5

2 years ago
-> WFM as it's working for 38.
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.