AquaMail Forum

English - Android => Bug reports => Topic started by: maddogmdd on July 25, 2018, 10:13:01 am

Title: Default Identity Not Working on Certain Replies
Post by: maddogmdd on July 25, 2018, 10:13:01 am
Hello,

Having a problem with default identity in replies.

I have A@gmail.com with 1@domain.com set up as the default identity.

When I compose a new e-mail, or when I reply to an e-mail sent to 1@domain.com, 1@domain.com is used as the sender, as expected.

However, when I reply to an e-mail that was not addressed explicitly to A@gmail.com or 1@domain.com, A@gmail.com is used as the sender, which is not what I want given that I selected 1@domain.com as the default identity.

This seems like a bug, unless I'm missing something.  Thoughts?

Thanks.  Loving my purchase of Aquamail otherwise.
Title: Re: Default Identity Not Working on Certain Replies
Post by: Kostya Vasilyev on July 27, 2018, 09:59:18 pm
No not a bug - since you're replying to a message addressed to the account's email, the reply uses that automatically.
Title: Re: Default Identity Not Working on Certain Replies
Post by: maddogmdd on August 03, 2018, 02:13:52 am
The e-mail was not actually addressed to the A@gmail.com address though.  It was sent to a group e-mail (let's call it group@company.com) that distributes to a handful of addresses, my 1@domain.com address being one of them.  In the absence of A@gmail.com in the to/cc/bcc fields, shouldn't it use my default identity in the reply, 1@domain.com, even if 1@domain.com is not explicitly in the to/cc/bcc?

Thanks
Title: Re: Default Identity Not Working on Certain Replies
Post by: Kostya Vasilyev on August 03, 2018, 10:23:51 pm
Quote
In the absence of A@gmail.com in the to/cc/bcc fields, shouldn't it use my default identity in the reply, 1@domain.com, even if 1@domain.com is not explicitly in the to/cc/bcc?

Well I'd have to check the code - it has one or two special cases base on past user feedback.

Did this message have either of "account" address (a@gmail) or "identity" address (1@domain.com) in its TO / CC / BCC at all?

Or was it a distribution list that hides actual recipients?

Title: Re: Default Identity Not Working on Certain Replies
Post by: maddogmdd on August 04, 2018, 12:40:47 am
It did not have either the "account" or "identity" address in those fields, just a distribution list address in the TO field and nothing else.  Thanks for checking into it.
Title: Re: Default Identity Not Working on Certain Replies
Post by: Kostya Vasilyev on August 07, 2018, 08:53:01 pm
Ah OK.

Well the logic (in the code) is like this:

1 - If a message has an identity's email address in its To / CC / BCC -> replying will use the identity

2 - If it didn't -> replying (or forwarding) will use the account itself

It doesn't look at "default account / identity for sending" at all.

We could make it do that (i.e. change the fallback for point 2 above from "use the account iself" to "if there is a default send from, and it's an identity, use that") - but I'm afraid it would be a bad change for "some" existing users out there, and we'd only find out when we released this change to Google Play.
Title: Re: Default Identity Not Working on Certain Replies
Post by: maddogmdd on August 07, 2018, 10:57:19 pm
To me, the cleanest logic would be that composing, replying, and forwarding all act the same way (use default send-from identity) unless something overrides it in the TO/CC/BCC or the user overrides.  But I hear your concern.

What about making it a toggle under "Composing and Sending" settings?  Something like: "Use default account when replying or forwarding if TO/CC/BCC do not specify" and leave it as OFF by default.  That way the logic doesn't change unexpectedly for anyone, but the option is there.

In my case, I'd rather people not know my personal gmail address, but it gets used inadvertently if I don't remember to change to my default identity every time I reply to a distribution, so it would be a very useful option.

Thanks again.
Title: Re: Default Identity Not Working on Certain Replies
Post by: Kostya Vasilyev on August 08, 2018, 09:26:19 pm
Re: What about making it a toggle under "Composing and Sending" settings? 

Um a new setting...

Re: In my case, I'd rather people not know my personal gmail address

But you can switch accounts / identities on the compose screen before sending.

Is this too much of a hassle because you get messages like that rather often?
Title: Re: Default Identity Not Working on Certain Replies
Post by: maddogmdd on August 08, 2018, 11:12:58 pm
Yeah, I get them often, and it's easy to forget to change it every time.  The Gmail web interface does it automatically based on my default identity, so it's not "habit" to have to do it manually in Aquamail.
Title: Re: Default Identity Not Working on Certain Replies
Post by: Kostya Vasilyev on August 11, 2018, 12:56:29 am
Quote
Yeah, I get them often, and it's easy to forget to change it every time.  The Gmail web interface does it automatically based on my default identity, so it's not "habit" to have to do it manually in Aquamail.

OK got it. I will file this as an idea for future versions.
Title: Re: Default Identity Not Working on Certain Replies
Post by: maddogmdd on August 11, 2018, 01:32:19 am
Thanks, much appreciated
Title: Re: Default Identity Not Working on Certain Replies
Post by: alexmay on September 10, 2022, 09:37:28 pm
What ever happened to this? There seem to be a number of threads that are very similar where users want to know how to set a default identity per account which is different from the account email address. I am one of those. My use case is as follows. I have a gmail account set up and then attached a domain to it. That means my account email is the gmail address that I don't use. When I am replying, this works fine as the email will have been sent to my domain. When I compose a new email though, it is really annoying to have to remember every time to switch to the identity when I actually NEVER want to send from the account email address. That is really no more than my login. Despite numerous users asking about this over a period of four years, I am unsure as to why this still seems to be an issue. Surely this would be a relatively simple setting to add.