SMTP with OAuth in child portal attempting to use Global portal email address

[RockSolidSW]

We are running DNN Platform 9.13.3. We have moved to SMTP with OAuth for M365 to cover all of our client sites, however, we have one client who uses their individual portal's SMTP configuration. We previously had it setup with Basic authentication, but need to move it also to OAuth with the changes that MS is making for legacy auth and MFA. After doing so (and successfully authorizing the Azure app registration for the child portal), email calls from modules such as DNNGo Power Forms are trying to use the Global email address and therefore throwing "SendAsDenied" errors in the main log. This same issue used to occur in just the Server Settings area when trying to test SMTP, but it appears when shifting to OAuth that it then disrupts emails from modules. Was this fixed in a later 9.x.x release by chance? I believe at least the Basic settings used to check the Settings, Security, Login Settings, Basic Login Settings, Primary Administrator field value and use that. In this case, we still have that value set for the customer's admin account which has the same email address we authorized the OAuth configuration with.

Thanks in advance! Todd

[valadas]

What the email "from" address will depend a bit on the implementation. In theory from anything DNN, the email will go from the email of the portal owner if possible and if not (no portal context) then it falls back to the host email. But for individual modules the "from" is really up to how the module was coded or settings of the module...

[RockSolidSW]

Hey Daniel, thanks for the reply! Yea, that is how I understand it as well. The weird part is that while in "Basic" mode, it operated correctly with this one portal being set to use its settings vs. Global. I will revert it back and test that theory, to confirm!

[RockSolidSW]

Hey Daniel, I did some additional testing and I do think that this may be a defect in either DNN when SMTP (specifically using the site option vs. global) "OAuth" is in place. If I put this customer's settings back to Basic authentication, it does not work due to the new MFA requirement for M 365, however it is trying to send using their portal administrator's email and not the global super user's email. So for some reason it looks as if when you change to OAuth that it restore back to using the global super user's email, when it should still be using the sites primary administrator user's email if that makes sense?

[valadas]

I could not say as I don't use OAuth for that, it is possible... I like to use some service specialized for sending out emails like https://resend.com/ for low volume sites, they have a free plan, so great for less than 100 emails per day. https://sendgrid.com is another popular option but they no longer have a free tier, just a free trial...