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 784665 - Reply/Forward fails to pair account alias with recipient
Reply/Forward fails to pair account alias with recipient
Status: RESOLVED FIXED
Product: evolution
Classification: Applications
Component: Composer
3.24.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2017-07-07 18:43 UTC by Stephen
Modified: 2017-07-11 10:54 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Stephen 2017-07-07 18:43:13 UTC
When replying to an email, Evolution looks for an account with an address matching the original message's recipient, and selects that by default in the "From" field.

That's a very useful feature, and is currently a deficiency with the 3.24 alias feature relative to the old workaround of "create a send-only account".

With aliases, when replying to a message sent to the alias address, the From dropdown currently needs to be manually changed each time.

This can among other things result in inadvertently leaking the potentially more private primary address to the recipient for which an alias is being used. For instance, I create aliases for different companies I email, as many quite happily sell/share their customer email address lists with third parties, and don't want them to get hold of my primary address.

It would be great if aliases can inherit the same smart address selection behaviour as used with full accounts :)
Comment 1 Milan Crha 2017-07-11 08:50:06 UTC
Thanks for a bug report. It is supposed to preselect the alias, not the main/primary mail address. Interestingly, it works fine for me on my main machine, but fails to pair the alias with the To address on other two machines.
Comment 2 Milan Crha 2017-07-11 10:54:35 UTC
Okay, I realized that the working machine had also set Send Account Override, and it was for the same address, thus it seemed like working. When I unset that override it was not working too. A workaround is to define full address (with the name) for the alias, which was the part which had been failing (no name->no match->use the main address). I fixed it with the below change.

When I've been in it, I made also Forwards respect Send Account Override and this alias lookup, just like the Reply works.

Created commit 15ef0e2 in evo master (3.25.4+)
Created commit ccfc282 in evo gnome-3-24 (3.24.4+)