Thank you everybody for your input. My problem is now solve. In my case, 8.1 was not the culprit. Here are my final configuration and working great going through the anti-spam cloud service in both directions. Line with the (MODIFIED) are the corrections to my original configuration. To find out what was wrong, I had created an any-to-any temporary (5 minutes max) rule with the risk (i know). So I got the information in the trafic log. Logging is not enabled in the default 2 security rules. As a documentation, my physical configuration is like that: My MX records points to the ANTISPAM-CLOUD service. INBOUND EMAILS ---> ANTISPAM-CLOUD ---> FW ---> MAIL-SERVER (Trueted Zone( MAIL-SERVER (Trusted Zone) ---> FW ---> ANTISPAM-CLOUD ---> OUTBOUD EMAILS I have the following NAT rule for outgoing mails. src-zone : Servers-Zone dst-zone : Internet-Zone dst-interface : Internet1/1 src-addr : PRV-MAIL-SERVER dest-addr : outbound-mail-to antispam solution (MODIFIED) Service : any (MODIFIED) Src-translation: static-ip: PUB-MAIL-SERVER, bidirectional : no (Bidirectional=NO) and the following NAT rule for then incoming mails src-zone : Internet-Zone dst-zone : Internet-Zone (MODIFIED) dst-interface : Internet1/1 (MODIFIED) src-addr : ANTISPAM-ADDR-GROUP (MODIFIED) dest-addr : PUB-Mail-Server (MODIFIED) Service : any (MODIFIED) Src-translation: static-ip: PRV-MAIL-SERVER, bidirectional : no (Bidirectoional=NO) The Security Rules are (Outgoing email): src Zone : Servers-Zone src Address : PRV-MAIL-SERVER dst Zone : Internet-Zone dst-Addr : outbound-mail-to antispam solution (MODIFIED to go through the ANTISPAM) application : smtp and Service : application-default Action : Allow The Security Rules are (Incoming email): src Zone : Internet-Zone src Address : ANTISPAM-ADDR_GROUP dst Zone : Server-Zone dst-Addr : PUB-MAIL-SERVER (MODIFIED) application : smtp and Service : application-default Action : Allow Thank you again, Michel
... View more