379670 - Sending message to e group using email address, bounce back to another email account

Status: RESOLVED INCOMPLETE

(Thunderbird :: Account Manager, defect)

Description

[Anton Sy]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.3) Gecko/20070309 Firefox/2.0.0.3
Build Identifier: 1.5.0.1

I am sending to an egroup account with an alternate email address included in the egroup.  The mail will be successfully sent under said alternate email address but later on, it will bounce the message back to my default email address.  I am sure I chose the alternate email address to send the email from.  

Reproducible: Always

Steps to Reproduce:
1. Set up a alternate email account with a alternate email address in the outgoing server
2. Compose an email 
3.  Choose the alternate email address to send from instead of default email address as defined in the Outgoing Server portion of the Account Settings menu
3. Send the message out

Actual Results:  
The message will be bounced back to the original default email address.  It seems that even if I chose the alternate email address to send from,  the message is sent out using the default address

Expected Results:  
It should have not bounced back since I used the email address included in the egroup

Comment 1

[Magnus Melin [:mkmelin]]

Maybe wrong Reply-To address set up for that identity? You can always try BCCing yourself and examining the message...

Comment 2

[Anton Sy]

I set it up and now it looks like it's working.  I presumed that when you set up the sender email address at the top portion of the message,  it will assume the same email address to reply to.  Does that mean I have to set it up for every email account I have?

Comment 3

[Magnus Melin [:mkmelin]]

I think it should... Can't really tell what the problem was without knowing your setup and seeing the message. Also, 2.0 is out.

Comment 4

[Wayne Mery (:wsmwk)]

Anton, this works for you now?

Comment 5

[Gary Kwong [:gkw] [:nth10sd] (NOT official MoCo now)]

No additional useful information since last comment -> resolving incomplete.

Please comment if the issue still occurs in the latest supported 2.0.0.14 / trunk nightlies.