English
Chinese (Simplified)
French
German
Italian
Japanese
Russian
Spanish
Vietnamese
Sonicwall Comprehensive Anti-Spam Service (CASS)
-
Hello,
We adquired a new sonicwall NSA appliance which include anti-spam system.
The documentation says that the Junk Store only works with Exchange servers, but I read that it might work with any other email server if they use port 25 as default port.
Do you know if it will work with Mdaemon? We already have Outbreak Protection and Data Query Service, but we would like to test Sonicwall's anti spam.
Thank you!
-
The research I've done suggests that it is possible to use it with any mail server, however, I am not experienced with it. I'd suggest asking Sonicwall, they will be able to better guide you on how to use their products in your environment.
-
Hello, good day.
We make working the CASS with our server, but we are fighting with the new headers created for the new Anti-Spam, the main issue is with SPF, MDaemon wants to compare SPF again the CASS IP using the original email sender. Look this example:
(p=none sampling=55 pct=100);
iprev=pass policy.iprev=52.37.12.168 (PTR ec2-52-37-12-168.us-west-2.compute.amazonaws.com);
iprev=fail reason="does not exist" policy.iprev=52.37.12.168 (HELO na2caws-cassra3.colo.sonicwall.com);
iprev=fail reason="does not match" policy.iprev=52.37.12.168 (MAIL bounces-908f204df583d645@emailom.email.stevemadden.com)
Received-SPF: neutral (motivatingraphics.com: 52.37.12.168 is neither permitted
nor denied by domain emailom.email.stevemadden.com)
receiver=motivatingraphics.com; client-ip=52.37.12.168;
mechanism=default; envelope-from="bounces-908f204df583d645@emailom.email.stevemadden.com";
helo=na2caws-cassra3.colo.sonicwall.com;
Received: from na2caws-cassra3.colo.sonicwall.com (ec2-52-37-12-168.us-west-2.compute.amazonaws.com [52.37.12.168])The IP 52.37.12.168 is the IP for CASS, not my IP or the sender IP.
I already added the IP to Trusted IP, SPF verification, and still the server says SPF fail because of this.
If you have any idea how to fix it or a workaround, I would appreciate it.
Thank you!
-
You should be able to add the IP address for CASS to the SPF exempt list to exempt the inbound sessions from SPF verification. (Security | Sender Authentication | SPF Verification | Exempt list)
But It sounds like you've already done this, in which case, please confirm that the IP was entered correctly, and that the inbound SMTP log shows the connecting IP address is the same IP address added to the SPF exempt list.
If the IPs are all matching, try restarting the MDaemon server. If the problem continues after the restart, please post or upload to us, an inbound SMTP session that shows the issue occurring. You can upload your log file at https://mdaemon.sharefile.com/r-rc3922c1eed334d4dbf5e34f0bd04ccd6
