I'm curious about the future of my SMTP services since we're using an on-prem server (IIS 6.0) that connects to O365 for sending emails. Currently, we don't have any authentication set up and only have the option for "Basic authentication" in IIS. Will we still be able to use our setup as is? We primarily rely on it for scan-to-email from our printers. If this changes, I'm considering switching to SMTP2Go, but I'd prefer not to have to set that up for all my clients if we can maintain our internal SMTP service.
6 Answers
I migrated my printers to use SMTP2Go recently. Now, emails are sent from a subdomain like [email protected] and so far, so good with no issues!
If you’re looking for an even more robust solution, consider Amazon SES. The setup is fairly inexpensive, and you'll likely have an easier time in the long run without worrying about new authentication methods.
We handle our emails using Mimecast, which helps connect our devices through the firewall without complications. If you're reluctant to set things up with O365 right now, consider adding DNS records to keep your internal server authorized. Just ensure it's secure to avoid spam issues later.
Honestly, it's 2023, and using Basic authentication isn't the best practice anymore. If you're facing OAuth2 changes and lack security configurations, using a third-party service for scanning emails is a solid backup plan. SMTP2Go is a good choice if you want to simplify things.
I just switched to SMTP2Go, and it was super easy! I recommend it if you're worried about the incoming changes.
I'm in the same boat! As of now, there's still uncertainty about when/if the current setup will stop working. Transitioning to an SMTP relay could be an effective way to enhance your email security while adapting to OAuth2 changes.
That’s what I’m afraid of! It feels like I need to make a move, but I still hope to linger on my current setup.
Just a note, SMTP AUTH changes won’t affect SMTP relay or direct send methods for O365 until March 2026. Your on-prem server should still work since it doesn’t use username/password for authentication, as per our CSP consultation.
Thanks! I'm leaning towards SMTP2Go for now, mainly to avoid spam problems since O365 does help with that.