...
Notification emails appearing in the Communication History have been sent from FastTrack360 however they may not have been received in the recipients Inbox recipient's Inbox or may be received later than expected due to:
- The email automatically being put in the recipient’s Spam/Junk email folder due to their spam filters. Please confirm with the recipient that the notification email isn’t in their Spam/Junk email folder.
- Email providers treating treat the email as spam if your Sender Policy Framework (SPF) record hasn’t been updated with FastTrack’s details. Please contact your IT Team to confirm your SPF record has been updated with FastTrack’s details as per our Sender Policy Framework (SPF) Record Update.
| Tip |
|---|
| If only the IP address, 13.55.19.10/32, has been added to your SPF record, delays will still occur. Your SPF record must also have “include:spf.messagelabs.com ~all” to ensure emails sent from FastTrack360 aren't treated as spam. |
If the email has gone to a junk or comes with a warning advising the sender is outside your organisation, please also review your Safe Senders list and if required include FastTrack360 and any other domains that will have emails sent. For steps on this, please refer to Microsoft support article, Safe Sender List.
If the email isn’t in the Spam/Junk folder and your SPF record has been updated with FastTrack's details but you are still experiencing issues with notifications not being received, please have your FastTrack Administrator (FTA) lodge a request via our Service Desk portal and provide the following details for each notification that wasn’t received:
...