Outlook 2019 doesn't allow custom username for IMAP/SMTP account

Outlook►File►Account Settings►Manage Profiles►Email Accounts►double click email account►change Your Name►Test Account Settings...►Finish

bro67 said:

Too easy for your own self. Of course there are always Policies for the Mail Transport Agent, specifically Exchange.

Yeah, just disregard my post! After re-reading it all, I'm not sure what the OP specifically wants!!!

From Outlook 2019 navigate as follows -

File => Account Settings => Account Settings => Select 'Email' Tab => Select 'Change' . . . . .





and enter the persons name in the 'Your Name' field for the specified 'Account Name'

IanMosley is closer, but... when i firstly started Outlook 2019, it begins with some configuration wizard and didn't allow me to do anything else. See first screenshot - it is one part of this.

And that is the problem - it allows set only email address, not username. This configuration wizard is unusable for me and without finishing it, Outlook 2019 did not continue further.

Yes, i already got it. I can use virtual users and maintain another database (or table in textfile) of this alternative usernames (in other word aliases) for my MTA. Fine, but i really don't want to do it just because only one MUA from many needs it.

If only one application need something unusual without really good reason i must consider it error. Ok?

But fortunatelly, there is way around.

As i linked before, i can run Outlook 2019 with parameter "outlook.exe /manageprofiles". It will start similar dialog to one IanMosley uploaded.

It looks little retro, it is little chaotic, but it allows set everything i needs, especially username.

Thanks again, even if we did not understand each other exactly. Now, problem is solved.

Hi there @swec
Easier get around for others who have this problem with outlook

Just use the applet in the control panel -- it's labelled outlook 2016 (or mail 2016) - even for 2019. That will get you back into those old screens that allow manual config.

I do hate those wretched auto config wizards when they don't work or give you options you need but more and more email clients seem to be doing this now - including thunderbird.

Note - control panel still exists in W10 even in the latest insider builds.

Cheers
jimbo

You my friend understand what the OP is talking about.
The other guys haven't a clue as to what a Linux/Apache server does or they would have understood. They were a tad condescending in my opinion. Maybe Microsoft bubbleboys.
The autodiscover doesn't always work and we require more than what is given in the account setup process.
Thank you for pointing us in the right direction.
Maybe a reference to the Control Panel app in the Add Account process would be nice.

jimbo45 said:

Hi there @swec
Easier get around for others who have this problem with outlook

Just use the applet in the control panel -- it's labelled outlook 2016 (or mail 2016) - even for 2019. That will get you back into those old screens that allow manual config.

I do hate those wretched auto config wizards when they don't work or give you options you need but more and more email clients seem to be doing this now - including thunderbird.

Note - control panel still exists in W10 even in the latest insider builds.

Cheers
jimbo

I have found this option in Control Panel.

However I credits to swec for this comment;

swec said:

As i linked before, i can run Outlook 2019 with parameter "outlook.exe /manageprofiles". It will start similar dialog to one IanMosley uploaded.

I encountered the same problem that swec described. As he said, it's very common for the user name ("johnsmith") to differ from the email address ("john.smith@company.com"). This is a standard feature of the POP/IMAP protocols, established decades ago.

Omitting the user name from the Outlook 2019 setup wizard was a mistake on Microsoft's part. It's not an acceptable to tell people to use a legacy UI, after half an hour of frustration.

Outlook is probably the only mail client in the world with this design flaw. It's any easy fix. Microsoft should fix it. Period.