Some quirks with the Red Condor spam filter:
1. The Red Condor does not play well with text mail clients and web browsers. It’s heavily javascripted and requires web browsers that support it. The email messages are HTML’d and while they can be set to text mode (from a gui browser), that consists basically of a very long link to the web interface that would need to be cut/pasted — you wouldn’t want to type it!
2. Before users can login directly to the RC, you have to go to http://redcondor1.peak.org/console/ and click on the “Signup” link. This asks for an initial password (twice), then sends a confirmation message.
3. When users get a quarantine message, then click on the Personal Dashboard link, the default view is for “messages quarantined today” whereas the email message will have “messages quarantined yesterday”. You have to click on the Time Range button to get the slider control that allows changing that.
4. When you “Release” a message, it will prompt you as to whether or not you want to tell Red Condor they goofed and whether or not you want to whitelist the sender (”modify friends list”).
5. You can’t adjust the sensitivity, only adjust how the different categories are handled (this is done in the Policies tab):
Green (Junk): “legitimate” business/newsletter/mail list etc
Yellow (Suspicious): blank, forged, foreign, attachments
Red (Dangerous): everything else that doesn’t look good
It’s pretty flexible on how you deal with the various types (for example, you can handle messages in specific languages differently), but you can’t adjust *how* it categorizes messages.
6. If you tell it to send a periodic digest, it *will* send you a digest. You can tell it to limit the zones it reports, but all that does is change it so it gives you a count instead of listing them out.
7. All domains were switched to the Red Condor at once by changing the dns for barracuda.peak.org to point to the Red Condor systems. An unfortunate side effect of this was that the links in the Barracuda spam digests that went out today (and previously) go to the Red Condor instead of the Barracuda. There are two aspects to this:
A. To get to the Barracuda, edit the url to barracuda1.peak.org instead of barracuda.peak.org. The Barracudas have been reconfigured to use that in the links in the messages sent out from now on.
B. The Barracuda redirects users to http://barracuda.peak.org/login This url does *not* have the signup link. Only /console has the link (e.g. http://barracuda.peak.org/console/ orhttp://redcondor1.peak.org/console/)
8. We are still working an issue to get SSL working on the Red Condor; at the moment, if you go to https://redcondor1.peak.org, you will get an untrusted certificate error, then after you connect, it will redirect you to the non SSL url anyhow. This should be fixed in the next couple of days.