This plugin implements the spamd protocol and will send messages to spamd for scoring.
spamd_socket = [host:port /path/to/socket] optional
Host or path to socket where spamd is running.
spamd_user = [user] optional
Username to pass to spamd. This is useful when you are running spamd with virtual users.
You can also pass this value in dynamically by setting:
connection.transaction.notes.spamd_userin another plugin.
The special username: first-recipient. The first envelope recipient will be used as the username.
the special username all-recipients may eventually be supported. See the get_spamd_username function in the plugin.
max_size = N optional
Maximum size of messages (in bytes) to send to spamd. Messages over this size will be skipped.
reject_threshold = N optional
Default: none (do not reject any mail)
SpamAssassin score at which the mail should be rejected.
relay_reject_threshold = N optional
As above, except this threshold only applies to connections that are relays (e.g. AUTH) where connection.relaying = true. This is used to set a lower thresold at which to reject mail from these hosts to prevent sending outbound spam.
If this is not set, then the
reject_thresoldvalue is used.
munge_subject_threshold = N optional
Default: none (do not munge the subject)
Score at which the subject should be munged (prefixed).
subject_prefix = [prefix] optional
Default: ** SPAM **
Prefix to use when munging the subject.
old_headers_action = [rename drop keep] optional
If old X-Spam-* headers are in the email, what do we do with them?
renamethem to X-Old-Spam-*.
dropwill delete them.
keepwill keep them (new X-Spam-* headers appear lower down in the headers then).
connect_timeout = N optional
Time in seconds to wait for a connection to spamd
results_timeout = N optional
Time in seconds to wait for results from spamd
The optional check section can allow skipping SpamAssassin check for remote connection meeting following criteria.
If true, messages from authenticated users will be scored.
If true, messages from private IPs will be scored.
If true, messages from localhost will be scored.
If true, messages that are to be relayed will be scored.
A SpamAssassin plugin can be found in the
Haraka.\[pm|cf\] files should be placed in the SpamAssassin local
site rules directory (/etc/mail/spamassassin on Linux), spamd should be
restarted and the plugin will make spamd output the Haraka UUID as part
of its log output to aid debugging when searching the mail logs.
This plugin now passes the X-Spam-* headers generated by SA through unaltered. You can control the presence and appearance of X-Spam-* headers by editing your SpamAssassin config.
The default headers added by SpamAssassin are:
add_header all Checker-Version SpamAssassin _VERSION_ (_SUBVERSION_) on _HOSTNAME_ add_header spam Flag _YESNOCAPS_ add_header all Level _STARS(\*)_ add_header all Status "_YESNO_, score=_SCORE_ required=_REQD_ tests=_TESTS_ autolearn=_AUTOLEARN_ version=_VERSION_"
Other headers options you might find interesting or useful are:
add_header all DCC _DCCB_: _DCCR_ add_header all Tests _TESTS_