Moved this over from the 1.9 thread:
I’ve been playing around with the setup and think I figured out some things (please correct me if I am wrong on any points)
NodeWorx Main Email Setup
If you turn on “Enable SpamAssassin” this does two things:
You are enabling the SMTP level scanning. The SMTP level scanning drops messages based on the “SMTP Spam Score” below. This scans the mail before local delivery and if it is higher than the “SMTP Spam Score” you set it will drop the email (never reaching the inbox of the user[s]). So I would set this to at least 15 or above so your clients don’t complain about missing emails.
You turned on all SiteWorx account to scan on local delivery based on the spam preferences (see below for more on spam preferences) even if “SpamAssassin Status” is off in the SiteWorx Account.
NodeWorx Spam Preferences
This is the default global settings for local delivery (basically this overrides the SpamAssassins default settings for all SiteWorx Accounts).
*NOTE: These settings are active even if you have “Enable SpamAssassin” turned off in the NodeWorx Main Email Setup
SiteWorx Spam Preferences
These settings override any default SpamAssassins or NodeWorx preferences. For example if you set “required_score 10” in the NodeWorx Spam Preferences and the SiteWorx account sets “required_score 5” the 5 will take precedence for that domain.
Force all SiteWorx accounts to scan and make the default local spam level set to 10 without dropping any messages at the SMTP level.
- Set the NodeWorx Main Email Setup ON to FORCE (even if turned off at the SiteWorx level) all the SiteWorx account to scan for Spam.
[I]*Note: SiteWorx Spam Preferecnes are still active and override the Global preference even if SpamAssassin status is off in SiteWorx
FOR THE IWORX TEAM
Could you just have the SiteWorx SpamAssassins status to ON and have it greyed out (radio buttons disabled) if it is on by default in Nodeworx[/I]
- We don’t want to drop any messages at the SMTP level so we will set the SMTP Spam Score very high (ie. 999999).
FOR THE IWORX TEAM
Even tough it won’t drop at STMP if set to 99999, it will still take CPU time to scan, maybe you can have a way in NodeWorx to force all SiteWorx account to turn on without scanning SMTP.
- Then we go to NodeWorx Spam Preferences and add an entry for " required_score 10"
And were done.
Questions, comments, correction please!!!
Just noticed a White/Black list setting in horde, what is this tied to?
Question that I am not sure about
Does the SMTP scan at the NodeWorx level just use some default SpamAssassins settings or does it also take into account the NodeWorx Spam Preferences (SiteWorx Spam Preferences can’t be use as Paul explained above: “The bad thing about SpamAssassin scanning at the SMTP level is that if the e-mail that comes in has multiple recipients, there is no way to determine which recipient’s Spam Preferences should be used when scanning.”?
So if you have an email black listed on the NodeWorx Spam Preferences would this drop the email so it doesn’t even reach the inbox?
On this same note one bad thing is if you have a white list in SiteWorx Spam Preferences becasue this would be ignored at the SMTP level.