288615 - "Recepient not specified" while it IS, when using a non default account

Status: RESOLVED WORKSFORME

(Thunderbird :: Message Compose Window, defect)

Description

[Erik de Bruijn]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050317 Firefox/1.0.2
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050317 Firefox/1.0.2

A particular use case that fails:
In firefox, ctrl-L for forwarding an e-mail. The compose window opens. I select
a different account to send from (2nd out of 4 acccounts, not the default one).
Then I type an address in the TO field. Normally when you press enter you can
fill in the next recepient, but this just selects the entire address I just
filled in (it was auto completed from my address book). Clicking on a second
recepient line (which is empty, one below the first one I've just entered),
doesn't do anything, while the usual behavoir is opening this line for typing
another recepient.

Completing the message. A subject and message is entered. When I try to send
(either ctrl-enter, send button, alt-s) I get two popups: 
1. one is a status indication with title "Sending messages - [subject]" and
contents:
"Status: Assembling mail information...
Progress: [bar keeps running]"

2nd popup: title "Send Message Error"
"Sending of message failed.
No recepients were specified. Please enter..."

This is exactly the same message you'll get when leaving out the recepients (doh!).
Extra info:
- non autocompleted addresses ([e-mail]) give the same problem
- I also got this problem using a debian packaged thunderbird on linux, and a
custom install (mozilla.org binary packaged), also under linux. The BUG is
platform independent!
- I have 4 accounts in "Accounts" --> "Manage Identities" with different
reply-to and auto-BCC addresses added to them. No vcards attached.
Account 1: (always works)
- BCC address set
- reply-to address set
Account 2: (has problem)
- BCC address NOT set
- reply-to address NOT set
Account 3:
- BCC address NOT set
- reply-to address set
Account 4: works fine
- BCC address NOT set
- reply-to address set

They are all attached/under the same IMAP account.

Another way it fails:
When adding a recepient under the default account and AFTER THAT switching to
the 2nd account/identity, the addresses are emptied.
When I click on the drop-down menu to choose another account (after the odd
behaviour), I see every account twice. 1,2,3,4,1,2,3,4.

I've sometimes managed to get this 4 times, giving me a dropdown covering the
entire screen with my four accounts. None of the account 2's work.

Sometime I seriously need to send a message via a particular account, and I
simply can't get it sent. I often need a very elaborate workaround (via saving
to drafts and then using another mail client to acutally send the e-mail). 

Reproducible: Sometimes

Steps to Reproduce:
1. Compose, select 2nd non-default account
2. Type in recepient (doesn't commit to next line)
3. Try to send (will fail)

Actual Results:  
I get two popups: 
1. one is a status indication with title "Sending messages - [subject]" and
contents:
"Status: Assembling mail information...
Progress: [bar keeps running]"

2nd popup: title "Send Message Error"
"Sending of message failed.
No recepients were specified. Please enter..."

Expected Results:  
Step 2 desired result: just go to the next recepient line
Step 3 desired result: use the address that was entered

It fails with version 1.0.2 (20050317), but also with others (e.g. Linux,
Thunderbird version 1.0) trying to use my setup.

Note: I have serious usability problems (while I'm very computer savvy and use
FF en TB all the time), so I believe it is a 'major bug' compared to many others
I found to see if I was the first submitting this.

Comment 1

[Erik de Bruijn]

Addition to the failing use case: 
I do not need to forward a message, simply composing (ctrl-M) gives similar
problems.

Comment 2

[Mike Cowperthwaite]

This sounds similar to the problems in bug 282645, which was fixed not long ago.
Please check a current trunk build to see if your problem still exists; if it 
does not, please mark this bug:   Resolved | WorksForMe

You should always check a current build *before* reporting a bug, especially an 
obvious regression such as this one.

Comment 3

[Erik de Bruijn]

I've just checked and I can confirm that the build
mozilla.org/thunderbird/nightly/2005-04-04-05-aviary1.0.1/ (help --> about:
version 1.0.2 (20050404)) fails similarly. It was on a windows XP SP2 box,
however I'm quite sure it will also fail under linux. It's behavior I'm seeing
for a long time now, I thought I'd submit it now, since it didn't get fixed
while thunderbird was maturing :)

It's not just with replies or forwards, also with composing a new message.

-- 
Kind regards,

Erik de Bruijn
BudgetDedicated

www.BudgetDedicated.com | Tel. [phone] | Fax. [phone] | Mob. +31 6
21856715 | Adres: Adelaarshorst 9 | Zipcode NL-5042 XE Tilburg

Comment 4

[Mike Cowperthwaite]

By "current build" I didn't mean 1.0.anything -- most fixes filed since 1.0 was 
released will not end up in the 1.0 stream.

Comment 5

[Mike Cowperthwaite]

No response from reporter, => WFM