This just has to do with securing SMTP communication. If you’re a Microsoft email user (or Google), they are making progressively more difficult/impossible to send email over unencrypted communication or using plain authentication even over secure port 465/587.
If you’re using web based email or Outlook or a modern email client, they all support Oauth or similar secure authentication mechanism. >From a practical perspective, the only thing this is breaking is the ability >to use older email clients or devices that don’t support modern secure SMTP >authentication. The place I see this in the real world is devices like >multifunction copiers that want to do scan to email. They almost all only >support plain authentication. They want you to put your credentials into their >Web UI and send email through plain authentication on port 25,465,587. >Microsoft and now Google as well, will not allow this kind of authentication >at all. My customers with these kinds of devices just can’t send email through >Google or Microsoft any more. We are using SMTP2GO to stand in the gap and provide a solution for sending email from these legacy devices. Chris Sent from my iPhone > On Sep 22, 2022, at 10:58 AM, Howard White <hwh...@vcch.com> wrote: > > We have a customer concerned that Microsoft is implementing a TFA > requirement for sending emails. A cursory web search points me to an article > from Microsoft Documentation > <https://learn.microsoft.com/en-us/exchange/clients-and-mobile-in-exchange-online/deprecation-of-basic-authentication-exchange-online>. > The gist of this post is that effective > > "In September 2021, we announced that effective October 1, 2022, we will > begin disabling Basic authentication for Outlook, EWS, RPS, POP, IMAP, and > EAS protocols in Exchange Online. SMTP Auth will also be disabled if it is > not being used. See full announcement: Basic Authentication and Exchange > Online – September 2021 Update." > > I guess I live under a rock as this is the first I have heard of this. We > have customers who send email via Exchange now asking "what are we gonna do?" > > Yikes > > Howard > > -- > -- > You received this message because you are subscribed to the Google Groups > "NLUG" group. > To post to this group, send email to nlug-talk@googlegroups.com > To unsubscribe from this group, send email to > nlug-talk+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/nlug-talk?hl=en > > --- You received this message because you are subscribed to the Google Groups > "NLUG" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to nlug-talk+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/nlug-talk/f8ee5ae6-3e05-5b97-502e-47c5608f6c03%40vcch.com. -- -- You received this message because you are subscribed to the Google Groups "NLUG" group. To post to this group, send email to nlug-talk@googlegroups.com To unsubscribe from this group, send email to nlug-talk+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nlug-talk?hl=en --- You received this message because you are subscribed to the Google Groups "NLUG" group. To unsubscribe from this group and stop receiving emails from it, send an email to nlug-talk+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/nlug-talk/B906A00C-01A7-47D6-96EE-DD021E2C501A%40gmail.com.
