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 778764 - Cannot select From email
Cannot select From email
Status: RESOLVED OBSOLETE
Product: geary
Classification: Other
Component: ux
master
Other Linux
: Normal normal
: ---
Assigned To: Geary Maintainers
Geary Maintainers
Depends on: 791230
Blocks:
 
 
Reported: 2017-02-16 14:46 UTC by Gautier Pelloux-Prayer
Modified: 2021-07-05 13:24 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Gautier Pelloux-Prayer 2017-02-16 14:46:27 UTC
Since Bug 778364 has been fixed, I am now able to add some addresses but I cannot actually select them when I am replying to some mail. 
See the following scenario:

1) from my gmail account I send an email to user+alias1@domain.com and user+alias2@domain.com
2) I receive both mails to user@domain.com (and in the same conversation). If I hit reply, (I believe) my From: address used will be the receiver of the most recent message

3 issues:

1) The From: address is not displayed so I cannot be 100% sure what address is actually used
2) If I'd like to answer with another address for any reason, I cannot. Maybe this point is invalid because "reply" tends to mean "use the receiver To: address that was used by the original email's From: emitter". 
3) If I hit "reply to all", my own addresses are removed from the copies. Eg. if I reply with user+alias1@domain.com, user+alias2@domain.com is also removed from the list of recipients.
Comment 1 Michael Gratton 2017-02-16 23:15:32 UTC
This sounds like Bug 738902, except that is more about changing accounts, rather than changing alises from within the same account.

You can work around (1) & (2) by detaching the composer - it will display the From combobox, but will only let you choose aliases from the current account.

I'm not sure about (3) - it sounds like a feature? It's there so that you don't end up emailing yourself, but maybe it should be limited to just the from address? I have a feeling that Bug 772631 might help out here, also.
Comment 2 Gautier Pelloux-Prayer 2017-02-17 20:30:05 UTC
> You can work around (1) & (2) by detaching the composer
OK for the workaround: but why the detached composer actually shows the From: entry but not the embedded composer? I believe both should show it, shouldn't they?

> It's there so that you don't end up emailing yourself, but maybe it should be limited to just the from address? 
Hm, I don't know. For me except the sender address (user+alias1@domain.com), none of the other addresses should be removed. Moreover, only my declared alias are removed from the list, but user+alias3@domain.com won't be removed from the list. But maybe it makes sense. At least I don't mind keeping it that way.
Comment 3 Michael Gratton 2017-02-23 05:27:51 UTC
(In reply to Gautier Pelloux-Prayer from comment #2)
> OK for the workaround: but why the detached composer actually shows the
> From: entry but not the embedded composer? I believe both should show it,
> shouldn't they?

Because it's compact? :) The idea is that when replying to a conversation, Geary should just do the right thing in selecting the correct from address to use, so you don't need to worry about it. That works fine when the recipients don't contain multiple aliases (which is the common case), but it's hard to guess 100% accurately if not.

How about this approach?

1. For accounts with no aliases, or when replying to a message that was sent to only the primary address or a single alias, keep the current behaviour and UI.
2. Otherwise, when the reply's recipients do contain more than one address for the account:
  2.1 Display the From: address in the address button tooltip, along with the reply's recipients as currently shown. This lets you easily discover who it is being sent as by default 
  2.2 When clicking the address button, ensure the From combobox is also shown

This will address (1) and (2) in the original description, without having to resort to detaching the composer first.

> > It's there so that you don't end up emailing yourself, but maybe it should be limited to just the from address? 
> Hm, I don't know. For me except the sender address (user+alias1@domain.com),
> none of the other addresses should be removed. Moreover, only my declared
> alias are removed from the list, but user+alias3@domain.com won't be removed
> from the list. But maybe it makes sense. At least I don't mind keeping it
> that way.

Well it's saved me a few times from emailing myself, and I think it's a nice bit of polish. However it probably is good to let the user know when addresses are dropped like that, even if it does happen by default.

On that basis, I have a feeling the correct solution is probably Bug 772631 Comment 2 - indicating when addresses have been removed from the reply (either automatically or by the user) and providing an easy way to restore them.
Comment 4 Gautier Pelloux-Prayer 2017-02-26 21:40:11 UTC
> Because it's compact? :)
Got the point, makes sense!

> How about this approach?
Sounds good, yes.

> On that basis, I have a feeling the correct solution is probably Bug 772631 Comment 2 - indicating when addresses have been removed from the reply (either automatically or by the user) and providing an easy way to restore them.
Yeah, it is a good solution. This is a minor issue actually, so I believe this would definitely solve it!
Comment 5 Michael Gratton 2018-01-26 04:56:51 UTC
NB: Bug 791230 is implementing (1) and a workaround as long as we don't have (2) implemented, so marking this as depending on that.
Comment 6 GNOME Infrastructure Team 2021-07-05 13:24:19 UTC
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org.
As part of that, we are mass-closing older open tickets in bugzilla.gnome.org
which have not seen updates for a longer time (resources are unfortunately
quite limited so not every ticket can get handled).

If you can still reproduce the situation described in this ticket in a recent
and supported software version, then please follow
  https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines
and create a new ticket at
  https://gitlab.gnome.org/GNOME/geary/-/issues/

Thank you for your understanding and your help.