byterazor/qpsmtpd
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

update documentation (issue #26)

Browse Source 
git-svn-id: https://svn.perl.org/qpsmtpd/trunk@935 958fd67b-6ff1-0310-b445-bb7760255be9
This commit is contained in:
Ask Bjørn Hansen 2008-07-31 20:32:32 +00:00
parent 29ea951680
commit 3c8766f683
1 changed files with 5 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
plugins/spamassassin
View File

@ -28,19 +28,20 @@ the options. Confused yet? :-)
=item reject_threshold [threshold] =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 mail servers are so useless that they ignore 55x responses not coming
after RCPT TO, so they might just keep retrying and retrying and after RCPT TO, so they might just keep retrying and retrying and
retrying until the mail expires from their queue. 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. The default is to never reject mail based on the SpamAssassin score.
=item munge_subject_threshold [threshold] =item munge_subject_threshold [threshold]
Set the threshold over which we will prefix the subject with Set the threshold where the plugin will prefix the subject with
'***SPAM***'. A messed up subject is easier to filter on than the '***SPAM***'. A modified subject is easier to filter on than the
other headers for many people with not so clever mail clients. You 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. might want to make another plugin that does this on a per user basis.