From 3c8766f68390610e76d4d0a1f7db525fd9d84df8 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ask=20Bj=C3=B8rn=20Hansen?= Date: Thu, 31 Jul 2008 20:32:32 +0000 Subject: [PATCH] update documentation (issue #26) git-svn-id: https://svn.perl.org/qpsmtpd/trunk@935 958fd67b-6ff1-0310-b445-bb7760255be9 --- plugins/spamassassin | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/plugins/spamassassin b/plugins/spamassassin index 468b84a..7355c8b 100644 --- a/plugins/spamassassin +++ b/plugins/spamassassin @@ -28,19 +28,20 @@ the options. Confused yet? :-) =item reject_threshold [threshold] -Set the threshold over which the plugin will reject the mail. Some +Set the threshold where the plugin will reject the mail. Some mail servers are so useless that they ignore 55x responses not coming after RCPT TO, so they might just keep retrying and retrying and retrying until the mail expires from their queue. -I like to configure this with 15 or 20 as the threshold. +Depending on your spamassassin configuration a reasonable setting is +typically somewhere between 12 to 20. The default is to never reject mail based on the SpamAssassin score. =item munge_subject_threshold [threshold] -Set the threshold over which we will prefix the subject with -'***SPAM***'. A messed up subject is easier to filter on than the +Set the threshold where the plugin will prefix the subject with +'***SPAM***'. A modified subject is easier to filter on than the other headers for many people with not so clever mail clients. You might want to make another plugin that does this on a per user basis.