Yes, you can replace the default SMTP behavior in CMS 11 without relying on SendGrid.
In Optimizely CMS 11 (ASP.NET Framework), built-in messaging (forgot password, notifications, etc.) goes through the EPiServer mail abstraction. You can implement your own ISmtpClient (or override the mail service) and register it via DI.
This allows you to:
Use OAuth2-based SMTP authentication
Integrate with Microsoft Graph API instead of SMTP
Route mail through an internal relay
As long as your custom implementation is registered in the container, the built-in messaging features will use it automatically.
The key is to replace the mail implementation - not just the <mailSettings> configuration. That’s typically the cleanest way to handle basic auth deprecation in CMS 11 environments.
Hi.
On CMS 11, using host smtp.office365.com in mailSettings and with the deprecation of basic auth, what would be alternatives be, except using SendGrid?
Like Stefan Holm's article is there a way in CMS 11 (ASP.NET Framwork) to use my own EmailService that also works with the built-in messaging, such as forgot password, and notifications?!