Skip to main content
NeoRant
NeoRant
Explorer III
May 17, 2024
Solved

Fortimail 7.4.1 - Create exceptions for blocked domains/emails

  • May 17, 2024
  • 1 reply
  • 4999 views

Hi guys,

 

Fortimail is POWERFUL.

 

Been getting some calls now from staff, that some of their mails are being blocked, required for work. Fortimail is working great i tell you, spam is being caught well, anything looks off, it is snatched for quarantined or blocked. I used an antispam inbound profile that is not so robust, but it seems like it is STILL kinda robust lol.

 

However, i would like to create some exceptions for certain email domains so these mails can pass via. Some mails are not even being quarantined; they are just blocked totally.

 

How can i set these exceptions and where specifically?blocked mail..jpg

 

 

Best answer by AEK

Hi NeoRant

I don't know what exactly means "Sender domain check failed", but I think this means like if FortiMail couldn't resolve the sending domain of the sender (in your screenshot you hid the domain). However as per the FML check execution sequence it seems you can't allow just by adding to safelist.

Personally to allow this I'd first investigate why FML can't resolve this domain (probably DNS issue). Then if I'm sure of what I'm doing (sender is 100% legitimate), I'd do as follows:

  1. create a new IP policy with the sender IP as source
  2. clone the inbound session profile
  3. in the newly created inbound session profile, under "Unauthenticated Session Settings" section, disable the "Check sender domain"
  4. leave all other profiles as the ones used for your 0.0.0.0 inbound IP policy
  5. put the newly created IP policy at top so it is matched before the 0.0.0.0 IP policy

Hope it helps

1 reply

AEK
SuperUser
AEKAnswer
SuperUser
May 17, 2024

Hi NeoRant

I don't know what exactly means "Sender domain check failed", but I think this means like if FortiMail couldn't resolve the sending domain of the sender (in your screenshot you hid the domain). However as per the FML check execution sequence it seems you can't allow just by adding to safelist.

Personally to allow this I'd first investigate why FML can't resolve this domain (probably DNS issue). Then if I'm sure of what I'm doing (sender is 100% legitimate), I'd do as follows:

  1. create a new IP policy with the sender IP as source
  2. clone the inbound session profile
  3. in the newly created inbound session profile, under "Unauthenticated Session Settings" section, disable the "Check sender domain"
  4. leave all other profiles as the ones used for your 0.0.0.0 inbound IP policy
  5. put the newly created IP policy at top so it is matched before the 0.0.0.0 IP policy

Hope it helps

AEK
    NeoRant
    NeoRantAuthor
    Explorer III
    May 17, 2024

    Hi AEK, 

     

    Thanks or your response. I am actually using the Recipient Policy for mail inspection.

     

    Regards

    AEK
    SuperUser
    AEK
    SuperUser
    May 17, 2024

    Hi NeoRant

    It doesn't matter since the specific session profile is set in the IP policy.

    AEK
      Terms & ConditionsAccessibility statement