We're having a problem with the CMDSPACE test flagging email from our own hosting accounts. Scott has recommended we whitelist our own clients, but that's not so easy....So this becomes a management nightmare.
The easiest way to handle this is to use "WHITELIST AUTH", if you are using IMail v8. If you are using a previous version of IMail, however, you can't automatically whitelist E-mails from authenticated users (as those versions do not report this information) -- and need to resort to other means (listing IP ranges, not scanning outgoing E-mail, disabling the test, etc.).
Actually, I'm not quite sure why this problem occurs. We didn't have this with the older version of Declude, and I'm assuming this is because the test wasn't used then? If so, what does this does actually look for? And, more to the point, why does it get stuck on our own clients?
It was added recently, as it typically catches over 50% of spam, while catching a very small amount of legitimate E-mail, making it an excellent test. It looks for one specific technical violation of the RFCs. The drawback, though, is that there are some mail clients that have this technical violation (so whitelisting your own users fixes the problem).
-Scott
---
Declude JunkMail: The advanced anti-spam solution for IMail mailservers since 2000.
Declude Virus: Ultra reliable virus detection and the leader in mailserver vulnerability detection.
Find out what you've been missing: Ask for a free 30-day evaluation.
--- [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)]
To Unsubscribe: http://www.ipswitch.com/support/mailing-lists.html List Archive: http://www.mail-archive.com/imail_forum%40list.ipswitch.com/ Knowledge Base/FAQ: http://www.ipswitch.com/support/IMail/
