Nominating a forum post submits a request to create a new Knowledge Article based on the forum post topic. Please ensure your nomination includes a solution within the reply.
Okay so this is normal, the appliance has a reputation scoring and the client MailServer has a poor score.You can double check the sender score via the cli diagnose fortiguard rating ip x.x.x.x
So that mans you need to do one of a few things if you trust this sender.
1: have the client improve there score by being a better player in the email world ( fix any spam issues, spf creation, etc...)
2: or remove the AS checks for this client
3: or eliminate the sender reputation checks in your AS policy and just for this client address
4: or whitelist it , if it' a good trusted sender
Item #1, you can't do from your end of things. So only 2-thru-4 are your only options.
I bet if you use the http://www.anti-abuse.org/multi-rbl-check-results/?host=x.x.x.x ( replace x.x.x.x with the client address that's being delayed ) and you will find they are probably listed elsewhere. As side note, you can use the ironport senderbase scoring to see if the fortiguard is rating the client fairly. Both are extreme good at Reputational scoring. I would even say the senderbase is probably better due to more ESA from IronPort are use than let's say Fortimail.
BTW, the fortimail is doing it's job ;)
PCNSE
NSE
StrongSwan
Select Forum Responses to become Knowledge Articles!
Select the “Nominate to Knowledge Base” button to recommend a forum post to become a knowledge article.
User | Count |
---|---|
1660 | |
1077 | |
752 | |
443 | |
220 |
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2024 Fortinet, Inc. All Rights Reserved.