FML cloud mail delivery

Tell Exchange admin to do the following and he should understand:

• Set MTA relay for external delivery to FortiMail_IP
• Set incoming SMTP Host to FortiMail_IP

If you want your domain not flagged as SPAM by remote MTAs, you need to have delivrability score 10/10. Before you put in prod always check with mail-tester.com or equivalent. You need to have score 10/10.

Thank you @AEK 

Dealing with emails that get stuck in spam folders is annoying, especially when you think everything is set up right.

It usually comes down to small mistakes in your SPF or DKIM records that are hard to spot just by looking at the raw code. Testing your setup before sending out a big batch is the only way to know for sure if those technical bits are actually working.

You should check this tool https://unspam.email/ to see how your mail looks to filters. It gives a good breakdown of what might be tripping up the sensors. Getting that green light early saves you from a lot of trial and error later on.

Thank you @Andrianv 

Setting up the mail flow for FortiMail Cloud can be a bit of a head-scratcher at first, especially when you're trying to make sure all the MX records and SPF entries align perfectly. I’ve found that the trickiest part is usually ensuring the 'Internal Hosts' are defined correctly so you don't accidentally end up with an open relay or blocked outbound mail.

One thing that helped me was double-checking the receive connectors on the Microsoft 365 or Google Workspace side to make sure they’re specifically trusting the FortiMail IP ranges. If those aren't locked down, you might see some intermittent 'Access Denied' errors. It’s definitely worth a quick audit of those connector settings just to be safe.