InterWorx uses SpamAssassin to help keep levels of email spam reasonable. The page in NodeWorx deals with settings that are global across the entire server.
SpamAssassin can be configured to block spam at the SMTP level before the message is even processed by the mail delivery system and sent to a local mailbox. SpamAssassin will refer to a rules database when checking incoming messages and assign a score to each message based on how likely it thinks a message is spam. A message with a higher spam score then a user-configurable threshold will automatically be refused by the SMTP service.
You may not want to enable this setting. It has no bearing on the SpamAssassin setting in SiteWorx, so e-mail messages may be scanned twice if this setting is enabled.
This option will scan all e-mail using the SpamAssassin content filter as the e-mail enters the server. The SMTP connection will be dropped only if the Spam Score is higher than the SMTP Spam Score option below. Otherwise, the e-mail will still be delivered to the recipient.
This is the SpamAssassin score threshold at which the SMTP server will reject a message before local delivery begins. If you don't want to block any spam at the SMTP level, use a very high number.
E-mails marked as SPAM will have the email subject rewritten with what is entered here. Corresponds to a server-wide spam preference setting of "rewrite_header subject
This option sets the method of delivering the actual e-mail spam message. The email can be sent unchanged but with the subject rewritten, it can be attached to an email from SpamAssassin, or it can be attached as plain text to an email from SpamAssassin. Corresponds to a server-wide spam preference setting of "report_safe" with a value of 0, 1, or 2 respectively.
Enable or disable the SpamAssassin AutoWhitelist functionality. See related documentation for details.