163701 - Switch from identity w/Reply-To: and/or BCC: fields to one without causes multiple addressing problems (send fails)

Status: RESOLVED DUPLICATE of bug 464448

(MailNews Core :: Composition, defect)

Description

[xolaware.llc]

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-US; rv:1.1b) Gecko/20020820
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-US; rv:1.1b) Gecko/20020820

i have multiple accounts.  one is set up with a Reply-To: and a BCC:, the other
is not.

when i start composing mail from the first acct (this can happen when i am in
that mailbox or if the mail window is not open but it was the last acct i
accessed), that acct will appear in the From: field.  if i then attempt to use
the menu to choose another acct from which to send the mail. the Reply-To:  &
BCC: fields appropriately disappear, but no matter what i attempt to place in
the To: field is not recognized as a proper address.  when i hit send, i get a
message that i no recipients have been specified.  it is also impossible to
attempt to enter a second recipient in such an e-mail.


Reproducible: Always

Steps to Reproduce:
1. create two accounts, one with auto Reply-To: & auto BCC: fields, one w/o
2. attempt to send mail starting by using the one with the auto-fields
3. attempt to change the From: to the acct w/o the auto-fields
4. address the mail to a valid address
5. attempt to address to another recipient (FAILS)
6. attempt to send (FAILS w/msg "no recipients specified")

Actual Results:  
5. attempt to address to another recipient (FAILS - unable to enter add'l fields)
6. attempt to send (FAILS w/msg "no recipients specified")


Expected Results:  
5. should have allowed other recipients
6. should have sent the mail to the expected recipient.

Comment 1

[Greg K.]

I can find the auto-BCC options, but where are the reply-to settings these days?

Comment 2

[xolaware.llc]

to set up the reply-to field for automatic usage:
1 - choose Edit->"Mail & Newsgroup Account Settings", then click on the name for
    the account for which you wish to set up the reply-to field.
    (or click on the name in the left tab for the account of interest, and
    from there, click on "View Settings for this Account"
2 - in the preferences, there will be a probably-empty "Reply-to" box.
    fill it in, hit ok.

now, it should be set up as you need.

Comment 3

[Greg K.]

Confirmed using FizzillaCFM/2002081416.

Comment 4

[Mike Cowperthwaite]

*** Bug 199582 has been marked as a duplicate of this bug. ***

Comment 5

[Mike Cowperthwaite]

Reproduced with TB 1.0, Win2K.

The duplicate notes that this problem also occurs when the first account has two 
BCC's (but no Reply-To) specified.  Also, if the switched-to account specifies a 
BCC of its own, multiple compose fields can be edited -- altho there are some 
issues there as well, such as: the third field will not autocomplete.

Comment 6

[Mike Cowperthwaite]

*** Bug 297640 has been marked as a duplicate of this bug. ***

Comment 7

[Max Waterman]

*** Bug 299093 has been marked as a duplicate of this bug. ***

Comment 8

[Mike Cowperthwaite]

I am not seeing this symptom any longer using TB 1.5b2/1.6a1.  The symptom 
described is similar to bug 276228 and bug 229880, which also have been solved 
in the recent builds.  => WFM

Comment 9

[xolaware.llc]

(In reply to comment #8)
> I am not seeing this symptom any longer using TB 1.5b2/1.6a1.  The symptom 
> described is similar to bug 276228 and bug 229880, which also have been solved 
> in the recent builds.  => WFM

did you try the steps to reproduce this exactly?  because this still fails
exactly as specified in the reproducible steps for me, and i'm using alpha 2
build version 1.6a1 (20051009).  i will accept "RESOLVED WFM" if you are
experiencing something different in a more recent nightly build.

Comment 10

[Mike Cowperthwaite]

(In reply to comment #9)
> did you try the steps to reproduce this exactly?  because this still fails
> exactly as specified in the reproducible steps for me

You're right -- I followed the steps but checked for the wrong symptom.

Comment 11

[Wayne Mery (:wsmwk)]

*** Bug 235116 has been marked as a duplicate of this bug. ***

Comment 12

[Michael Veit]

This bug is still present in Thunderbird 2.0.0.9, therfore existing more than 5 years.

Comment 13

[Sorin Adrian Savu]

Hi, I've submitted a patch to bug 464448,that will fix the issue above. (I should search more carefully before doing that, 464448 is a duplicate of this one )