Yes, that is correct @yerch82, and the whole point I have tried to make in this thread.
As you say, a possible solution is to change the sender’s details in the account setting to the address you want to be default, rather than the ones used to login to the account.
You set an account as default.
Then you change the sender’s details to what you want to be default.
They don’t have to be the same as the details used to login to the server.
Some servers will not let you login with credentials (3) different to the address you want to send from (2). Some will, but the sent message will include the Sent-from: header which will be the login address (3).
I have a mailing list where I’m subbed as my alias on my Gmail account, I’ve put my alias into my Accounts setting for that account, but all my replies to list mail start with my Gmail address, not the alias. There’s an official reply above that makes me believe this should not be the case.
And count me as a vote for being able to set an alias as the main address. As my alias is on a Gmail account, the setup process completely bypassed my making any choices, and set the account up as a Gmail account, even though I had started with my alias as the email address.
As to Gary’s contention that “aliases aren’t meant to be primary addresses”, you’re just so brain-bogglingly wrong it’s hard to speak to it. The entire history of email has been replete with aliases used as primary addresses, by individuals and orgs of all sizes. Gary, if you can point me to the RFC that says aliases are not to be used for primary addresses, I’d appreciate it. RFC 5321 has bad things to say about local aliases, but FQDN aliases are just fine. Sorry you don’t like them so much.
In any case, it is certainly possible for an email client to set an alias as the primary address to send from, so I’m wondering why there appears to be a reluctance to do so with eM Client.
Is it possible to move Gary’s post from Dec '20 at the top of this thread, as a SOLUTION?
Granted it does not solve the problem as described at the beginning of the thread. However, it does outline such a PERFECT WORKAROUND, that it might as well be a solution. I assume the fact that the thread drops off after that is evidence of this.
I visited this thread months ago looking for this solution, got exasperated and missed it. I actually let my trial version of eMClient expire as a result of this feature not being available (I have several Gmail accounts, all with aliases, so without this feature I was constantly sending emails from an address I did not want to use).
However, I was unable to find a better alternative, revisited eMClient and this thread, implemented the workaround for all my accounts, and now eMClient does everything I want it to. Clearly the best application of many I tried.
In my opinion, eMClient Tech Support should describe this workaround when the issue of defaulting to aliases comes up. When I was in touch with them, they said the feature would be available at some indefinite time in the future, at which point I abandoned eM Client.
I’m glad I came back and discovered this workaround. Moving Gary’s post to the top of this thread might prevent others from missing it first time around like I did.
For Gmail users apart from changing the email address or alias email address in eM Client accounts, you also need to mirror that in Gmail online as I found out previously.
You need to change both your default “From” and “Reply-to” address in Gmail online.
If you only change the “From” address, replies will go to your original Gmail address by default.
See the following Gmail support page.
