After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 603398 - Replies use default email address instead of To: address
Replies use default email address instead of To: address
Status: RESOLVED DUPLICATE of bug 588833
Product: evolution
Classification: Applications
Component: Mailer
2.28.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2009-11-30 18:33 UTC by Biscuits McCree
Modified: 2009-12-21 19:14 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Biscuits McCree 2009-11-30 18:33:48 UTC 
I have multiple accounts and previous versions of evolution would use the

"To:" address from the email in the reply.  So if it was "To" my second email account, that's what would be used in a reply.

However, since upgrading to 2.28, it now uses my default account no matter what, and I have to manually change it to the correct one every time.  

Is there a workaround till this is fixed?
Comment 1 Akhil Laddha 2009-12-01 04:24:30 UTC 
looks related to bug 597473
Comment 2 Biscuits McCree 2009-12-02 19:45:07 UTC 
Akhil,

I seem some reference on that page to being fixed in 2.29, but what can I do with 2.28?  The to: is specified in all these cases, so I'm not sure what the problem is.
Comment 3 Biscuits McCree 2009-12-18 10:24:40 UTC 
I can confirm this bug has not been fixed in 2.28.2.

Basically, if you have 3 email addresses, and someone writes to #3 in the to:, when you hit reply, it defaults to #1 for your from:.  

This is not the way it used to work.  I think this bug was introduced in 2.28.
Comment 4 Milan Crha 2009-12-21 09:50:03 UTC 
I guess it's the same as bug #588833
Comment 5 Biscuits McCree 2009-12-21 19:14:13 UTC 

*** This bug has been marked as a duplicate of bug 588833 ***