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

2022-09-20 Thread Michael Stauber
Hi Ken, On a server that just does email, there's no reason that a username can't be pretty much whatever you want, @ is just another character. All authentication services on an RHEL box (and clones) use PAM (Pluggable Authentication Mechanism). Which ties into the user and password

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

2022-09-20 Thread Ken Hohhof
Probably because all the way back to the Cobalt RaQ this is a hosting appliance that provides web, mail, FTP and other services. Most people using BlueOnyx are probably hosting at least web and email and maybe other services on the same server. On a server that just does email, there's no

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

2022-09-20 Thread Michael Aronoff
Michael Stauber wrote: > There is another benefit: If the email address is also one part of the login > credentials (and the remaining part being the password), then you're > already exposing half of the login credentials to the whole world. If you look at the attempted logins to hack email

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

2022-09-20 Thread Michael Stauber
Hi Ken, What if we host mail for domains foo.com and bar.com, and we have a mail account for j...@foo.com, what if there is also a j...@bar.com. Sorry, there can only be one "john" on the entire server. So the second john has to be john2? That's what "Email Aliases" are for and every user

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

2022-09-20 Thread 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 j...@foo.com, what if there is also a j...@bar.com.

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

2022-09-20 Thread Larry Smith
Darren, My reading of the docs is that it accepts either form (the %Ln) -- Larry Smith lesm...@ecsis.net On Tue September 20 2022 10:43, Darren Shea wrote: > Larry, > Thank you for the info - would the %Ln setting allow either form of > the username to work, or would it break

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

2022-09-20 Thread Michael Aronoff
Darren wrote: > newer versions of Outlook which do not allow the user to modify the username Microsoft is horrible but they have simply moved and hidden the correct screen for this. It is easy to do when you know where to look. Close Outlook and go to the Control Panel and Look for Mail.

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

2022-09-20 Thread Larry Smith
Sorry, resulting line should read auth_username_format = %Ln (no leading #). -- Larry Smith lesm...@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 > >

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

2022-09-20 Thread Larry Smith
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@domain format.

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

2022-09-20 Thread Darren Shea
All, We are running an older (5208) system, and we're running into an issue with newer versions of Outlook which do not allow the user to modify the username when logging in. Is there a way to permit the system to accept u...@domain.com usernames in addition to the bare "user" version?