This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Whitelist Options Missing after Update

Hello,

 

after Updating from SFOS 17.0.8 MR-8 to SFOS 17.1.1 MR-1 (Today I've Updatet to SFOS 17.1.2 MR-2 but still the same Issue)

I am missing the following Options:

Email > General Settings > Allowed IP Addresses/FQDNs list

Email > General Settings > Allowed E-Mail Addresses

 

Only the Blocked Senders list is still available.

 

Where can I find These Options or is it a bug?

We having trouble with some customers E-Mails because there are detected as Spam and I Need to whitelist them.

 

best regards,

Oliver A.



This thread was automatically locked due to age.
  • V17.1 introduced the Email Exceptions. Take a look at Email - Email Policies & Exceptions. 

     

    • Email Security - adds user management over individual SMTP block and allow lists via the User Portal.  Domains or email addresses added to the Allow list will bypass policies (except for malware or sandboxing enforcement) and adding domains or addresses to the block list will automatically quarantine emails from those senders.  In addition, more flexible SMTP policy exceptions are supported to provide parity with Sophos SG UTM.
  • Thanks.

     

    One more Question:

    I send a test spam mail from my gmx.de Account to our Domain.

    I've added "gmx.de" to our Whitelist "For This Source/Host". But my Mail was still blocked by the Spamfilter.

    After I put my full E-Mail Address Oliver.abc@gmx.de into the "Return Address" Field it works.

     

    But how Can I whitelist complete Domains? Or maybe just a Syntax Error?

    See Screenshot.

      

  • But how Can I whitelist complete Domains? Or maybe just a Syntax Error?

    You must put the domains with wildcard in this field:

    The whitelist "For these Sources/Hosts" or "Für diese Quellen/Hosts" is meant for whitelisting mailservers. For example you have to list all GMX mailservers there, which is not very usable in this case.

  • Works fine now. My mistake.

     

    Thanks!