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 597442 - [regression] Identities are not used when the user replies an email
[regression] Identities are not used when the user replies an email
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-10-05 16:57 UTC by Germán Poo-Caamaño
Modified: 2010-02-16 10:01 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Germán Poo-Caamaño 2009-10-05 16:57:53 UTC
I manage multiples accounts and identities.

Let us say as accounts:
1. foo@domain_1.com - IMAP
2. goo@domain_2.com - IMAP

Let us say as identities only (set under accounts)
3. foo@other_domain.com - None
4. support@domain_2.com - None

foo@other_domain.com is an alias pointing to foo@domain_1.com, and
support@domain_2.com is an alias pointing to goo@domain_2.com.

All of them have different signatures set.

Behaviour expected (and as it worked until 2.26):
- When I replied an email sent to foo@other_domain.com, the 
  remitent (From) was automatically set with the proper identity,
  which is foo@other_domain.com.

Current behaviour (2.28):
- When I replied an email sent to foo@other_domain.com, the 
  remitent (From) is automatically set with the main account,
  which is foo@domain_1.com.

As user, I would to reply with the same address when the email 
was received.  In special cases I would want to change, but those 
are exceptions, not the rule.
Comment 1 Peter Williams 2009-11-23 18:44:31 UTC
I see this too, on Fedora 12.
Comment 2 Akhil Laddha 2010-02-16 10:01:45 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

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