FYI the 2FA for an outlook email was going to spam. Not sure if there is a way to add a reminder for them to check spam or resend a new 2FA
Is there 2FA with fluent products ?
Rosvaldas Nudas I think he refers to the FluentAuth plugin?
Florian,I don't use FluentAuth. This was just regular trouble shooting. I'm sure it is connected to the tight spam rules from microsoft since it was outlook. Once I white listed my email address no issue.
Unfortunately, I experience the same with FluentAuth. The emails land in my spam folder every single time, no matter what I do.
That's the thing which prevents me using it for all users
Florian, Have you created the proper SPF, DKIM and DMARC records in your DNS settings for the domain?
Email deliverability is a bigger subject so it is hard to give a simple answer.
I assume your spam issue is not related to your IP/Domain/Hosting neighborhood because when you use the same SMTP server (credentials) with other SMTP plugin then you dont have any spam issue. Hard to believe but this might happen (lot of factors).
If the spam issue is related to only 2FA emails sent with FluentAuth plugin then the only difference in this case is the email body content (FluentAuth use Rich/HTML formatting).
Your other SMTP plugin ("not spammy one") might not have the same body html content (Plain text without external links, buttons, pictures etc) with 2FA emails then.
It is not obvious that all emails (not related to 2FA emails only) from a good hosting/IP cause such a difference (for using two different SMTP plugins). If you use external email provider (shared IP) then other factors matter too (warm up, volume, timing, email content, data center, ISP, transactional vs marketing emails, verified email list, spam reported by M365/gmail users etc).
That's interesting. So, I haven't had the problem with all just the outlook email. Everything else seems to work fine. With the other person, I thought maybe Yahoo.ca But their mcafee was listing the site as potential phishing, giving them a warning. So that may have been creating the issue for that person. I was able to get mcafee to clean up that error, which was good to catch before growing it past this initial 10 people