[BlueOnyx:25622] Re: Mail server problem with Outlook

[Ken Hohhof]

We actually host mail on a separate mailserver not using BlueOnyx, but in
general it seems like bad practice to use bare usernames on a shared hosting
server.

What if we host mail for domains foo.com and bar.com, and we have a mail
account for john at foo.com, what if there is also a john at bar.com.  Sorry,
there can only be one "john" on the entire server.  So the second john has
to be john2?

Almost all modern mail systems use the full email address as the username
for login.  This is not the same as stripping the domain name.  Most
companies with their own domains will have a convention for email addresses,
like firstname at domain.com or initial.lastname at domain.com, and will not be
happy with the explanation they can't have their preferred email address
because someone at another domain has that username.


-----Original Message-----
From: Blueonyx <blueonyx-bounces at mail.blueonyx.it> On Behalf Of Larry Smith
Sent: Tuesday, September 20, 2022 10:29 AM
To: blueonyx at mail.blueonyx.it
Cc: Darren Shea <darrens at ecpi.com>
Subject: [BlueOnyx:25619] Re: Mail server problem with Outlook


Sorry, resulting line should read

auth_username_format = %Ln

(no leading #).

--
Larry Smith
lesmith at ecsis.net

On Tue September 20 2022 10:16, Larry Smith wrote:
> Darren,
>
>   On a 5208R box you would edit the /etc/dovecot/10-auth.conf file and 
> uncomment (remove leading #) from
>
> #auth_username_format = %Lu
>
> and change that line to read
>
> #auth_username_format = %Ln
>
> Note the ending n versus u.  This drops the domain from a login that 
> has user at domain format.
>
> Save and then restart dovecot.
_______________________________________________
Blueonyx mailing list
Blueonyx at mail.blueonyx.it
http://mail.blueonyx.it/mailman/listinfo/blueonyx