365 Modern Authentication

[ITGURU]

I have received notice that MS will be switching off basic authentication later this year and that there are a small number of users using the old protocols.

However, I also have helpdesk systems etc that pull mail from a mailbox using pop3 and IMAP.

If i enable modern authentication, but leave POP3 and IMAP enabled under the other procotols, will this mean that they will still get switched off later this year, or will they continue to work and just affect clients such as older versions on outlook?

Just looking for clarification.

thanks.

[chaplic]

Unless your helpdesk systems support IMAP via modern auth (exceptionally unlikely) they will stop working. They might have an option of using EWS and OAUTH which is probably the best bet of what to switch to.

[ITGURU]

Unless your helpdesk systems support IMAP via modern auth (exceptionally unlikely) they will stop working. They might have an option of using EWS and OAUTH which is probably the best bet of what to switch to.

 

I use OSticket so only does IMAP or POP3 pull?

[chaplic]

I use OSticket so only does IMAP or POP3 pull?

I'd normally say speak to your supplier as they will be aware.

 

I've never heard of it, but a quick google lead to here, looks like it's still WIP. There is also a link to something called davmail which looks basically like a basic auth to modern auth proxy which is either a horrible bodge or an elegant workaround depending on your point of view (I'll certainly have it in the back of my mind!)

 

 

Microsoft is retireing basic auth for POP & IMAP · Issue #5390 · osTicket/osTicket · GitHub

[psydii]

Perhaps a little on prem exchange server for this purpose? With firewall rules to prevent internet traffic (other than to/from 365).

[ITGURU]

Perhaps a little on prem exchange server for this purpose? With firewall rules to prevent internet traffic (other than to/from 365).

 

Wouldn't it have to be setup in hybrid mode though as this is for receiving emails, not sending.

[psydii]

Yes, its how our helpdesk picks up email, but also how it and the old photocopiers and other legacy devices send email.

[DaveTheTech]

Wouldn't an SMTP relay work better?

[Guest Guest]

I use OSticket so only does IMAP or POP3 pull?

A dev mentioned on their forums that support for modern Auth is in development

[free780]

https://techcommunity.microsoft.com/t5/exchange-team-blog/basic-authentication-and-exchange-online-september-2021-update/ba-p/2772210

 

All suppliers should now move to use modern authentication (OAUTH) for IMAP/POP. Or you have to pay for an SMTP sending service or an on prem mail relay as others have said.

 

In October legacy auth will start to be turned off for tenancies. If your a global admin you should get a monthly report of legacy auth use.

[ITGURU]

Wouldn't an SMTP relay work better?

 

For outbound yes, not inbound when on office 365?

[Cw2k]

I use OSticket so only does IMAP or POP3 pull?

 

The osticket devs are working on an oauth implementation for pop and imap as they will be supported by modern auth

[chaplic]

Wouldn't it have to be setup in hybrid mode though as this is for receiving emails, not sending.

 

 

 

No. Setup an exchange server, in it's own domain if you want, with domain of your choosing, does not even need to be a public name, let's say nonexistant.local . Setup firewall rules to listen to MS internet range on port 25. Setup a routed connection in O365 for nonexistant.local to point at your exchange server. Setup a mail enabled user object in O365 to receive email to the address you want and forward it to [email protected].

[free780]

No. Setup an exchange server, in it's own domain if you want, with domain of your choosing, does not even need to be a public name, let's say nonexistant.local . Setup firewall rules to listen to MS internet range on port 25. Setup a routed connection in O365 for nonexistant.local to point at your exchange server. Setup a mail enabled user object in O365 to receive email to the address you want and forward it to [email protected].

 

Ah but then you have the joy of Exchange updates [emoji1].

[3s-gtech]

You mentioned ‘little’ and ‘Exchange server’ together…the system requirements for 2019 still make me shudder. Will Exchange 2022 require as much RAM as the whole of Exchange Online?!

[Norphy]

No. Setup an exchange server, in it's own domain if you want, with domain of your choosing, does not even need to be a public name, let's say nonexistant.local . Setup firewall rules to listen to MS internet range on port 25. Setup a routed connection in O365 for nonexistant.local to point at your exchange server. Setup a mail enabled user object in O365 to receive email to the address you want and forward it to [email protected].

 

An entire Exchange server, just to be an SMTP relay? Isn’t that just a mite, well, excessive?

[chaplic]

An entire Exchange server, just to be an SMTP relay? Isn’t that just a mite, well, excessive?

 

 

More of a mailbox, but unquestionably, yes.

 

Coincidentally I was on a confcall today with a GLOBALMEGACORP beating up a supplier who doesn't yet have a working solution for this, and I'd suggest effort that way (or finding a service which is more on-the-ball if your IT budget isnt a telephone number) is more productive than reheating yesterdays tech. But if your organisation has an on prem exchange of some flavour it might be a plan B option.

[andy_b]

Having a look at this today as OSticket 1.17 RC supports OAUTH.

 

Seems a little complicated. Has anyone had a go yet?