diff options
Diffstat (limited to 'mail/mailscanner/files/patch-docs:man:MailScanner.conf.5.html')
| -rw-r--r-- | mail/mailscanner/files/patch-docs:man:MailScanner.conf.5.html | 1036 |
1 files changed, 0 insertions, 1036 deletions
diff --git a/mail/mailscanner/files/patch-docs:man:MailScanner.conf.5.html b/mail/mailscanner/files/patch-docs:man:MailScanner.conf.5.html deleted file mode 100644 index a712926fb1fb..000000000000 --- a/mail/mailscanner/files/patch-docs:man:MailScanner.conf.5.html +++ /dev/null @@ -1,1036 +0,0 @@ ---- ../MailScanner-4.30.3.orig/docs/man/MailScanner.conf.5.html Mon May 3 10:48:25 2004 -+++ docs/man/MailScanner.conf.5.html Mon May 3 10:48:42 2004 -@@ -1,5 +1,5 @@ - <!-- Creator : groff version 1.19 --> --<!-- CreationDate: Fri Apr 2 12:23:58 2004 --> -+<!-- CreationDate: Mon May 3 10:47:48 2004 --> - <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" - "http://www.w3.org/TR/html4/loose.dtd"> - <html> -@@ -331,17 +331,85 @@ - <!-- INDENTATION --> - <p>Directory in which MailScanner should find e−mail - messages for scanning. This can be any of the following:</p> -+</td> -+</table> -+<!-- TABS --> -+<table width="100%" border=0 rules="none" frame="void" -+ cols="5" cellspacing="0" cellpadding="0"> -+<tr valign="top" align="left"> -+<td width="22%"></td> -+<td width="3%"> -+ -+<p>1.</p> -+</td> -+<td width="3%"></td> -+<td width="26%"> -+ -+<p>a directory name.</p> -+</td> -+<td width="46%"> -+</td> -+</table> - <!-- INDENTATION --> --<p>1. a directory name. Example: /var/spool/mqueue.in</p> --<!-- INDENTATION --> --<p>2. a wildcard giving directory names. Example: --/var/spool/mqueue.in/*</p> -+<table width="100%" border=0 rules="none" frame="void" -+ cols="2" cellspacing="0" cellpadding="0"> -+<tr valign="top" align="left"> -+<td width="28%"></td> -+<td width="72%"> -+<p>Example: /var/spool/mqueue.in</p> -+</td> -+</table> -+<!-- TABS --> -+<table width="100%" border=0 rules="none" frame="void" -+ cols="5" cellspacing="0" cellpadding="0"> -+<tr valign="top" align="left"> -+<td width="22%"></td> -+<td width="3%"> -+ -+<p>2.</p> -+</td> -+<td width="3%"></td> -+<td width="52%"> -+ -+<p>a wildcard giving directory names.</p> -+</td> -+<td width="20%"> -+</td> -+</table> - <!-- INDENTATION --> --<p>3. the name of a file containing a list of directory --names, which can in turn contain wildcards. Example: --/usr/local/etc/MailScanner/mqueue.in.list.conf</p> -+<table width="100%" border=0 rules="none" frame="void" -+ cols="2" cellspacing="0" cellpadding="0"> -+<tr valign="top" align="left"> -+<td width="28%"></td> -+<td width="72%"> -+<p>Example: /var/spool/mqueue.in/*</p> - </td> - </table> -+<!-- TABS --> -+<table width="100%" border=0 rules="none" frame="void" -+ cols="4" cellspacing="0" cellpadding="0"> -+<tr valign="top" align="left"> -+<td width="22%"></td> -+<td width="3%"> -+ -+<p>3.</p> -+</td> -+<td width="3%"></td> -+<td width="72%"> -+ -+<p>the name of a file containing a list of directory names, -+which can in turn contain wildcards.</p> -+</td> -+</table> -+<!-- INDENTATION --> -+<table width="100%" border=0 rules="none" frame="void" -+ cols="2" cellspacing="0" cellpadding="0"> -+<tr valign="top" align="left"> -+<td width="28%"></td> -+<td width="72%"> -+<p>Example: -+/usr/local/etc/MailScanner/mqueue.in.list.conf</p></td> -+</table> - <!-- INDENTATION --> - <table width="100%" border=0 rules="none" frame="void" - cols="2" cellspacing="0" cellpadding="0"> -@@ -1403,29 +1471,79 @@ - fake addresses on messages they send, so there is no point - informing the sender of the message, as it won’t - actually be them who sent it anyway. Other words that can be --put in this list are the 5 special keywords<br> --HTML−IFrame: inserting this will stop senders being --warned about HTML Iframe tags, when they are not --allowed.<br> --HTML−Codebase: inserting this will stop senders being --warned about HTML Object Codebase tags, when they are not --allowed.<br> --Zip−Password: inserting this will stop senders being --warned about password−protected zip files when they --are not allowd. This keyword is not needed if you include --All−Viruses.<br> --All−Viruses: inserting this will stop senders being --warned about any virus, while still allowing you to warn --senders about HTML−based attacks. This includes -+put in this list are the 5 special keywords</p> -+</td> -+</table> -+<!-- TABS --> -+<table width="100%" border=0 rules="none" frame="void" -+ cols="4" cellspacing="0" cellpadding="0"> -+<tr valign="top" align="left"> -+<td width="22%"></td> -+<td width="1%"> -+ -+<p>•</p> -+</td> -+<td width="5%"></td> -+<td width="72%"> -+ -+<p>HTML−IFrame: inserting this will stop senders -+being warned about HTML Iframe tags, when they are not -+allowed.</p> -+</td> -+<tr valign="top" align="left"> -+<td width="22%"></td> -+<td width="1%"> -+ -+<p>•</p> -+</td> -+<td width="5%"></td> -+<td width="72%"> -+ -+<p>HTML−Codebase: inserting this will stop senders -+being warned about HTML Object Codebase tags, when they are -+not allowed.</p> -+</td> -+<tr valign="top" align="left"> -+<td width="22%"></td> -+<td width="1%"> -+ -+<p>•</p> -+</td> -+<td width="5%"></td> -+<td width="72%"> -+ -+<p>Zip−Password: inserting this will stop senders -+being warned about password−protected zip files when -+they are not allowd. This keyword is not needed if you -+include All−Viruses.</p> -+</td> -+<tr valign="top" align="left"> -+<td width="22%"></td> -+<td width="1%"> -+ -+<p>•</p> -+</td> -+<td width="5%"></td> -+<td width="72%"> -+ -+<p>All−Viruses: inserting this will stop senders -+being warned about any virus, while still allowing you to -+warn senders about HTML−based attacks. This includes - Zip−Password so you don’t need to include - both.</p> -+</td> -+</table> - <!-- INDENTATION --> -+<table width="100%" border=0 rules="none" frame="void" -+ cols="2" cellspacing="0" cellpadding="0"> -+<tr valign="top" align="left"> -+<td width="28%"></td> -+<td width="72%"> - <p>The default of "All−Viruses" means that - no senders of viruses will be notified (as the sender - address is always forged these days anyway), but anyone who - sends a message that is blocked for other reasons will still --be notified.</p> --</td> -+be notified.</p></td> - </table> - <!-- INDENTATION --> - <table width="100%" border=0 rules="none" frame="void" -@@ -1590,15 +1708,47 @@ - Microsoft Outlook security vulnerabilities to go - unprotected, but if you have a load of mailing lists sending - them, then you will want to allow them to keep your users --happy. Possible Values:</p> --<!-- INDENTATION --> --<p>yes => Allow these tags to be in the message no => --Ban messages containing these tags disarm => Allow these --tags, but stop these tags from working</p> --<!-- INDENTATION --> --<p>This can also be the filename of a ruleset, so you can --allow them from known mailing lists but ban them from --everywhere else.</p> -+happy. This can also be the filename of a ruleset, so you -+can allow them from known mailing lists but ban them from -+everywhere else. Possible Values:</p> -+</td> -+</table> -+<!-- TABS --> -+<table width="100%" border=0 rules="none" frame="void" -+ cols="4" cellspacing="0" cellpadding="0"> -+<tr valign="top" align="left"> -+<td width="22%"></td> -+<td width="1%"> -+ -+<p>•</p> -+</td> -+<td width="5%"></td> -+<td width="72%"> -+ -+<p>yes => Allow these tags to be in the message</p> -+</td> -+<tr valign="top" align="left"> -+<td width="22%"></td> -+<td width="1%"> -+ -+<p>•</p> -+</td> -+<td width="5%"></td> -+<td width="72%"> -+ -+<p>no => Ban messages containing these tags</p> -+</td> -+<tr valign="top" align="left"> -+<td width="22%"></td> -+<td width="1%"> -+ -+<p>•</p> -+</td> -+<td width="5%"></td> -+<td width="72%"> -+ -+<p>disarm => Allow these tags, but stop these tags from -+working</p> - </td> - </table> - <!-- INDENTATION --> -@@ -1615,8 +1765,14 @@ - <tr valign="top" align="left"> - <td width="22%"></td> - <td width="78%"> --<p>Default: no</p> -+<p>Default: no</p></td> -+</table> - <!-- INDENTATION --> -+<table width="100%" border=0 rules="none" frame="void" -+ cols="2" cellspacing="0" cellpadding="0"> -+<tr valign="top" align="left"> -+<td width="28%"></td> -+<td width="72%"> - <p>You may receive complaints from your users that HTML - mailing lists they subscribe to have been stopped by the - "Allow IFrame Tags" option above. So before you -@@ -1649,10 +1805,44 @@ - people to part with credit card information and other - personal data. This can also be the filename of a ruleset. - Possible values:</p> --<!-- INDENTATION --> --<p>yes => Allow these tags to be in the message no => --Ban messages containing these tags disarm => Allow these --tags, but stop these tags from working</p> -+</td> -+</table> -+<!-- TABS --> -+<table width="100%" border=0 rules="none" frame="void" -+ cols="4" cellspacing="0" cellpadding="0"> -+<tr valign="top" align="left"> -+<td width="22%"></td> -+<td width="1%"> -+ -+<p>•</p> -+</td> -+<td width="5%"></td> -+<td width="72%"> -+ -+<p>yes => Allow these tags to be in the message</p> -+</td> -+<tr valign="top" align="left"> -+<td width="22%"></td> -+<td width="1%"> -+ -+<p>•</p> -+</td> -+<td width="5%"></td> -+<td width="72%"> -+ -+<p>no => Ban messages containing these tags</p> -+</td> -+<tr valign="top" align="left"> -+<td width="22%"></td> -+<td width="1%"> -+ -+<p>•</p> -+</td> -+<td width="5%"></td> -+<td width="72%"> -+ -+<p>disarm => Allow these tags, but stop these tags from -+working</p> - </td> - </table> - <!-- INDENTATION --> -@@ -1669,18 +1859,57 @@ - <tr valign="top" align="left"> - <td width="22%"></td> - <td width="78%"> --<p>Default: no</p> -+<p>Default: no</p></td> -+</table> - <!-- INDENTATION --> -+<table width="100%" border=0 rules="none" frame="void" -+ cols="2" cellspacing="0" cellpadding="0"> -+<tr valign="top" align="left"> -+<td width="28%"></td> -+<td width="72%"> - <p>Do you want to allow <Object Codebase=...> tags in - email messages? This is a bad idea as it leaves you - unprotected against various Microsoft−specific - security vulnerabilities. But if your users demand it, you - can do it. This can also be the filename of a ruleset. --Possible values:</p> --<!-- INDENTATION --> --<p>yes => Allow these tags to be in the message no => --Ban messages containing these tags disarm => Allow these --tags, but stop these tags from working</p> -+Possible values:</p></td> -+</table> -+<!-- TABS --> -+<table width="100%" border=0 rules="none" frame="void" -+ cols="4" cellspacing="0" cellpadding="0"> -+<tr valign="top" align="left"> -+<td width="22%"></td> -+<td width="1%"> -+ -+<p>•</p> -+</td> -+<td width="5%"></td> -+<td width="72%"> -+ -+<p>yes => Allow these tags to be in the message</p> -+</td> -+<tr valign="top" align="left"> -+<td width="22%"></td> -+<td width="1%"> -+ -+<p>•</p> -+</td> -+<td width="5%"></td> -+<td width="72%"> -+ -+<p>no => Ban messages containing these tags</p> -+</td> -+<tr valign="top" align="left"> -+<td width="22%"></td> -+<td width="1%"> -+ -+<p>•</p> -+</td> -+<td width="5%"></td> -+<td width="72%"> -+ -+<p>disarm => Allow these tags, but stop these tags from -+working</p> - </td> - </table> - <!-- INDENTATION --> -@@ -1697,8 +1926,14 @@ - <tr valign="top" align="left"> - <td width="22%"></td> - <td width="78%"> --<p>Default: no</p> -+<p>Default: no</p></td> -+</table> - <!-- INDENTATION --> -+<table width="100%" border=0 rules="none" frame="void" -+ cols="2" cellspacing="0" cellpadding="0"> -+<tr valign="top" align="left"> -+<td width="28%"></td> -+<td width="72%"> - <p>This option interacts with the "Allow ... Tags" - options above like this:</p> - <!-- INDENTATION --> -@@ -3670,6 +3905,32 @@ - <tr valign="top" align="left"> - <td width="11%"></td> - <td width="89%"> -+<p><b>Spam List Timeouts History</b></p></td> -+</table> -+<!-- INDENTATION --> -+<table width="100%" border=0 rules="none" frame="void" -+ cols="2" cellspacing="0" cellpadding="0"> -+<tr valign="top" align="left"> -+<td width="22%"></td> -+<td width="78%"> -+<p>Default: 10</p> -+<!-- INDENTATION --> -+<p>The total number of Spam List attempts during which -+"Max Spam List Timeouts" will cause the spam list -+fo be marked as "unavailable". See the previous -+comment for more information. The default values of 5 and 10 -+mean that 5 timeouts in any sequence of 10 attempts will -+cause the list to be marked as "unavailable" until -+the next periodic restart (see "Restart -+Every").</p> -+</td> -+</table> -+<!-- INDENTATION --> -+<table width="100%" border=0 rules="none" frame="void" -+ cols="2" cellspacing="0" cellpadding="0"> -+<tr valign="top" align="left"> -+<td width="11%"></td> -+<td width="89%"> - <p><b>Is Definitely Not Spam</b></p></td> - </table> - <!-- INDENTATION --> -@@ -3733,6 +3994,31 @@ - This can also be the filename of a ruleset.</p> - </td> - </table> -+<!-- INDENTATION --> -+<table width="100%" border=0 rules="none" frame="void" -+ cols="2" cellspacing="0" cellpadding="0"> -+<tr valign="top" align="left"> -+<td width="11%"></td> -+<td width="89%"> -+<p><b>Ignore Spam Whitelist If Recipients -+Exceed</b></p></td> -+</table> -+<!-- INDENTATION --> -+<table width="100%" border=0 rules="none" frame="void" -+ cols="2" cellspacing="0" cellpadding="0"> -+<tr valign="top" align="left"> -+<td width="22%"></td> -+<td width="78%"> -+<p>Default: 20</p> -+<!-- INDENTATION --> -+<p>Spammers have learnt that they can get their message -+through by sending a message with lots of recipients, one of -+which chooses to whitelist everything coming to them, -+including the spammer. So if a message arrives with more -+than this number of recipients, ignore the "Is -+Definitely Not Spam" whitelist.</p> -+</td> -+</table> - <a name="SpamAssassin"></a> - <h2>SpamAssassin</h2> - <!-- INDENTATION --> -@@ -3868,11 +4154,7 @@ - <tr valign="top" align="left"> - <td width="22%"></td> - <td width="78%"> --<p>Default: --/opt/MailScanner/etc/spam.assassin.prefs.conf<br> --Default Linux: /etc/MailScanner/spam.assassin.prefs.conf<br> --Default FreeBSD: --/usr/local/etc/MailScanner/spam.assassin.prefs.conf</p> -+<p>Default: %etc−dir%/spam.assassin.prefs.conf</p> - <!-- INDENTATION --> - <p>SpamAssassin uses a "user preferences" file - which can be used to set the values of various SpamAssassin -@@ -3934,6 +4216,32 @@ - <tr valign="top" align="left"> - <td width="11%"></td> - <td width="89%"> -+<p><b>SpamAssassin Timeouts History</b></p></td> -+</table> -+<!-- INDENTATION --> -+<table width="100%" border=0 rules="none" frame="void" -+ cols="2" cellspacing="0" cellpadding="0"> -+<tr valign="top" align="left"> -+<td width="22%"></td> -+<td width="78%"> -+<p>Default: 30</p> -+<!-- INDENTATION --> -+<p>The total number of SpamAssassin attempts during which -+"Max SpamAssassin Timeouts" will cause -+SpamAssassin to be marked as "unavailable". See -+the previous comment for more information. The default -+values of 10 and 20 mean that 10 timeouts in any sequence of -+20 attempts will trigger the behaviour described above, -+until the next periodic restart (see "Restart -+Every").</p> -+</td> -+</table> -+<!-- INDENTATION --> -+<table width="100%" border=0 rules="none" frame="void" -+ cols="2" cellspacing="0" cellpadding="0"> -+<tr valign="top" align="left"> -+<td width="11%"></td> -+<td width="89%"> - <p><b>Check SpamAssassin If On Spam List</b></p></td> - </table> - <!-- INDENTATION --> -@@ -4063,23 +4371,81 @@ - <p>This can be any combination of 1 or more of the following - keywords, and these actions are applied to any message which - is spam.</p> --<!-- INDENTATION --> -+</td> -+</table> -+<!-- TABS --> -+<table width="100%" border=0 rules="none" frame="void" -+ cols="4" cellspacing="0" cellpadding="0"> -+<tr valign="top" align="left"> -+<td width="22%"></td> -+<td width="1%"> -+ -+<p>•</p> -+</td> -+<td width="5%"></td> -+<td width="72%"> -+ - <p>"deliver" − the message is delivered to - the recipient as normal</p> --<!-- INDENTATION --> -+</td> -+<tr valign="top" align="left"> -+<td width="22%"></td> -+<td width="1%"> -+ -+<p>•</p> -+</td> -+<td width="5%"></td> -+<td width="72%"> -+ - <p>"delete" − the message is deleted</p> --<!-- INDENTATION --> -+</td> -+<tr valign="top" align="left"> -+<td width="22%"></td> -+<td width="1%"> -+ -+<p>•</p> -+</td> -+<td width="5%"></td> -+<td width="72%"> -+ - <p>"store" − the message is stored in the - quarantine</p> --<!-- INDENTATION --> --<p>"forward" − an email address is supplied, --to which the message is forwarded</p> --<!-- INDENTATION --> -+</td> -+<tr valign="top" align="left"> -+<td width="22%"></td> -+<td width="1%"> -+ -+<p>•</p> -+</td> -+<td width="5%"></td> -+<td width="72%"> -+ -+<p>"forward" − an email address is -+supplied, to which the message is forwarded</p> -+</td> -+<tr valign="top" align="left"> -+<td width="22%"></td> -+<td width="1%"> -+ -+<p>•</p> -+</td> -+<td width="5%"></td> -+<td width="72%"> -+ - <p>"notify" − Send the recipients a short - notification that spam addressed to them was not delivered. - They can then take action to request retrieval of the - orginal message if they think it was not spam.</p> --<!-- INDENTATION --> -+</td> -+<tr valign="top" align="left"> -+<td width="22%"></td> -+<td width="1%"> -+ -+<p>•</p> -+</td> -+<td width="5%"></td> -+<td width="72%"> -+ - <p>"striphtml" − convert all in−line - HTML content in the message to be stripped to plain text, - which removes all images and scripts and so can be used to -@@ -4087,12 +4453,30 @@ - action on its own does not imply that the message will be - delivered, you will need to specify "deliver" or - "forward" to actually deliver the message.</p> --<!-- INDENTATION --> -+</td> -+<tr valign="top" align="left"> -+<td width="22%"></td> -+<td width="1%"> -+ -+<p>•</p> -+</td> -+<td width="5%"></td> -+<td width="72%"> -+ - <p>"attachment" − Convert the original - message into an attachment of the message. This means the - user has to take an extra step to open the spam, and stops - "web bugs" very effectively.</p> --<!-- INDENTATION --> -+</td> -+<tr valign="top" align="left"> -+<td width="22%"></td> -+<td width="1%"> -+ -+<p>•</p> -+</td> -+<td width="5%"></td> -+<td width="72%"> -+ - <p>"bounce" − bounce the spam message. This - option should not be used and must be enabled with the - "Enable Spam Bounce" option first.</p> -@@ -4112,8 +4496,14 @@ - <tr valign="top" align="left"> - <td width="22%"></td> - <td width="78%"> --<p>Default: deliver</p> -+<p>Default: deliver</p></td> -+</table> - <!-- INDENTATION --> -+<table width="100%" border=0 rules="none" frame="void" -+ cols="2" cellspacing="0" cellpadding="0"> -+<tr valign="top" align="left"> -+<td width="28%"></td> -+<td width="72%"> - <p>This is the same as the "Spam Actions" option - above, but it gives the actions to apply to any message - whose SpamAssassin score is above the "High -@@ -4452,24 +4842,18 @@ - Note the files are mutable. If this is unset then no extra - places are searched for. If using Postfix, you probably want - to set this to /var/spool/MailScanner/spamassassin and --do</p></td> -+do</p> -+</td> - </table> --<!-- TABS --> -+<!-- INDENTATION --> - <table width="100%" border=0 rules="none" frame="void" - cols="2" cellspacing="0" cellpadding="0"> - <tr valign="top" align="left"> --<td width="29%"></td> --<td width="71%"> -- --<p>mkdir /var/spool/MailScanner/spamassassin</p> --</td> --<tr valign="top" align="left"> --<td width="29%"></td> --<td width="71%"> -- --<p>chown postfix.postfix --/var/spool/MailScanner/spamassassin</p> --</td> -+<td width="26%"></td> -+<td width="74%"> -+<p>mkdir /var/spool/MailScanner/spamassassin<br> -+chown postfix.postfix -+/var/spool/MailScanner/spamassassin</p></td> - </table> - <!-- INDENTATION --> - <table width="100%" border=0 rules="none" frame="void" -@@ -4511,12 +4895,92 @@ - <td width="78%"> - <p>Default:</p> - <!-- INDENTATION --> --<p>The site−local rules are searched for here, and in --prefix /etc/spamassassin, prefix/etc/mail/spamassassin, --/usr/local/etc/spamassassin, /etc/spamassassin, --/etc/mail/spamassassin, and maybe others. If this is set --then it adds to the list of places that are searched; --otherwise it has no effect.</p> -+<p>This tells MailScanner where to look for the -+site−local rules. If this is set it adds to the list -+of places that are searched. MailScanner will always look at -+the following places (even if this option is not set):</p> -+</td> -+</table> -+<!-- TABS --> -+<table width="100%" border=0 rules="none" frame="void" -+ cols="5" cellspacing="0" cellpadding="0"> -+<tr valign="top" align="left"> -+<td width="22%"></td> -+<td width="1%"> -+ -+<p>•</p> -+</td> -+<td width="5%"></td> -+<td width="43%"> -+ -+<p>prefix/etc/spamassassin</p> -+</td> -+<td width="29%"> -+</td> -+<tr valign="top" align="left"> -+<td width="22%"></td> -+<td width="1%"> -+ -+<p>•</p> -+</td> -+<td width="5%"></td> -+<td width="43%"> -+ -+<p>prefix/etc/mail/spamassassin</p> -+</td> -+<td width="29%"> -+</td> -+<tr valign="top" align="left"> -+<td width="22%"></td> -+<td width="1%"> -+ -+<p>•</p> -+</td> -+<td width="5%"></td> -+<td width="43%"> -+ -+<p>/usr/local/etc/spamassassin</p> -+</td> -+<td width="29%"> -+</td> -+<tr valign="top" align="left"> -+<td width="22%"></td> -+<td width="1%"> -+ -+<p>•</p> -+</td> -+<td width="5%"></td> -+<td width="43%"> -+ -+<p>/etc/spamassassin</p> -+</td> -+<td width="29%"> -+</td> -+<tr valign="top" align="left"> -+<td width="22%"></td> -+<td width="1%"> -+ -+<p>•</p> -+</td> -+<td width="5%"></td> -+<td width="43%"> -+ -+<p>/etc/mail/spamassassin</p> -+</td> -+<td width="29%"> -+</td> -+<tr valign="top" align="left"> -+<td width="22%"></td> -+<td width="1%"> -+ -+<p>•</p> -+</td> -+<td width="5%"></td> -+<td width="43%"> -+ -+<p>maybe others as well</p> -+</td> -+<td width="29%"> - </td> - </table> - <!-- INDENTATION --> -@@ -4533,13 +4997,73 @@ - <tr valign="top" align="left"> - <td width="22%"></td> - <td width="78%"> --<p>Default:</p> -+<p>Default:</p></td> -+</table> - <!-- INDENTATION --> --<p>The default rules are searched for here, and in --prefix/share/spamassassin, /usr/local/share/spamassassin, --/usr/share/spamassassin, and maybe others. If this is set --then it adds to the list of places that are searched; --otherwise it has no effect.</p> -+<table width="100%" border=0 rules="none" frame="void" -+ cols="2" cellspacing="0" cellpadding="0"> -+<tr valign="top" align="left"> -+<td width="28%"></td> -+<td width="72%"> -+<p>This tells MailScanner where to look for the default -+rules. If this is set it adds to the list of places that are -+searched. MailScanner will always look at the following -+places (even if this option is not set):</p></td> -+</table> -+<!-- TABS --> -+<table width="100%" border=0 rules="none" frame="void" -+ cols="5" cellspacing="0" cellpadding="0"> -+<tr valign="top" align="left"> -+<td width="22%"></td> -+<td width="1%"> -+ -+<p>•</p> -+</td> -+<td width="5%"></td> -+<td width="44%"> -+ -+<p>prefix/share/spamassassin</p> -+</td> -+<td width="28%"> -+</td> -+<tr valign="top" align="left"> -+<td width="22%"></td> -+<td width="1%"> -+ -+<p>•</p> -+</td> -+<td width="5%"></td> -+<td width="44%"> -+ -+<p>/usr/local/share/spamassassin</p> -+</td> -+<td width="28%"> -+</td> -+<tr valign="top" align="left"> -+<td width="22%"></td> -+<td width="1%"> -+ -+<p>•</p> -+</td> -+<td width="5%"></td> -+<td width="44%"> -+ -+<p>/usr/share/spamassassin</p> -+</td> -+<td width="28%"> -+</td> -+<tr valign="top" align="left"> -+<td width="22%"></td> -+<td width="1%"> -+ -+<p>•</p> -+</td> -+<td width="5%"></td> -+<td width="44%"> -+ -+<p>maybe others as well</p> -+</td> -+<td width="28%"> - </td> - </table> - <a name="Advanced Settings"></a> -@@ -4797,15 +5321,78 @@ - <td width="78%"> - <p>Default: supported</p> - <!-- INDENTATION --> --<p>Some of the virus scanners are not supported by the --authors of MailScanner, and they may use code contributed by --another user. If this option is set to the wrong value for --your virus scanners, then you will get an error message in --your maillog (syslog) telling you tha# Are you using Exim --with split spool directories? If you don’t understand --# this, the answer is probably "no". Refer to the --Exim documentation for # more information about split spool --directories. Split Exim Spool = yes</p> -+<p>Minimum acceptable code stability status −− -+if we come across code that’s not at least as stable -+as this, we barf. This is currently only used to check that -+you don’t end up using untested virus scanner support -+code without realising it. Don’t even *think* about -+setting this to anything other than "beta" or -+"supported" on a system that receives real mail -+until you have tested it yourself and are happy that it is -+all working as you expect it to. Don’t set it to -+anything other than "supported" on a system that -+could ever receive important mail. Levels used are:</p> -+</td> -+</table> -+<!-- TABS --> -+<table width="100%" border=0 rules="none" frame="void" -+ cols="4" cellspacing="0" cellpadding="0"> -+<tr valign="top" align="left"> -+<td width="22%"></td> -+<td width="1%"> -+ -+<p>•</p> -+</td> -+<td width="5%"></td> -+<td width="72%"> -+ -+<p>none − there may not even be any code.</p> -+</td> -+<tr valign="top" align="left"> -+<td width="22%"></td> -+<td width="1%"> -+ -+<p>•</p> -+</td> -+<td width="5%"></td> -+<td width="72%"> -+ -+<p>unsupported − code may be completely untested, a -+contributed dirty hack, anything, really.</p> -+</td> -+<tr valign="top" align="left"> -+<td width="22%"></td> -+<td width="1%"> -+ -+<p>•</p> -+</td> -+<td width="5%"></td> -+<td width="72%"> -+ -+<p>alpha − code is pretty well untested. Don’t -+assume it will work.</p> -+</td> -+<tr valign="top" align="left"> -+<td width="22%"></td> -+<td width="1%"> -+ -+<p>•</p> -+</td> -+<td width="5%"></td> -+<td width="72%"> -+ -+<p>beta − code is tested a bit. It should work.</p> -+</td> -+<tr valign="top" align="left"> -+<td width="22%"></td> -+<td width="1%"> -+ -+<p>•</p> -+</td> -+<td width="5%"></td> -+<td width="72%"> -+ -+<p>supported − code *should* be reliable.</p> - </td> - </table> - <!-- INDENTATION --> -@@ -4822,8 +5409,14 @@ - <tr valign="top" align="left"> - <td width="22%"></td> - <td width="78%"> --<p>Default: yes</p> -+<p>Default: yes</p></td> -+</table> - <!-- INDENTATION --> -+<table width="100%" border=0 rules="none" frame="void" -+ cols="2" cellspacing="0" cellpadding="0"> -+<tr valign="top" align="left"> -+<td width="28%"></td> -+<td width="72%"> - <p>Are you using Exim with split spool directories? If you - don’t understand this, the answer is probably - "no". Refer to the Exim documentation for more -@@ -4850,22 +5443,55 @@ - <p>When trying to work out the value of configuration - parameters which are using a ruleset, this controls the - behaviour when a rule is checking the "To:" --addresses. If this option is set to "yes", then --the following happens when checking the ruleset:</p> --<!-- INDENTATION --> --<p>a) 1 recipient. Same behaviour as normal.<br> --b) Several recipients, but all in the same domain -+addresses. If this option is set to "no", then -+some rules will use the result they get from the first -+matching rule for any of the recipients of a message, so the -+exact value cannot be predicted for messages with more than -+1 recipient. This value *cannot* be the filename of a -+ruleset.<br> -+If this option is set to "yes", then the following -+happens when checking the ruleset:</p> -+</td> -+</table> -+<!-- TABS --> -+<table width="100%" border=0 rules="none" frame="void" -+ cols="4" cellspacing="0" cellpadding="0"> -+<tr valign="top" align="left"> -+<td width="22%"></td> -+<td width="3%"> -+ -+<p>a)</p> -+</td> -+<td width="3%"></td> -+<td width="72%"> -+ -+<p>1 recipient. Same behaviour as normal.</p> -+</td> -+<tr valign="top" align="left"> -+<td width="22%"></td> -+<td width="3%"> -+ -+<p>b)</p> -+</td> -+<td width="3%"></td> -+<td width="72%"> -+ -+<p>Several recipients, but all in the same domain - (domain.com for example). The rules are checked for one that --matches the string "*@domain.com".<br> --c) Several recipients, not all in the same domain. The rules --are checked for one that matches the string -+matches the string "*@domain.com".</p> -+</td> -+<tr valign="top" align="left"> -+<td width="22%"></td> -+<td width="3%"> -+ -+<p>c)</p> -+</td> -+<td width="3%"></td> -+<td width="72%"> -+ -+<p>Several recipients, not all in the same domain. The -+rules are checked for one that matches the string - "*@*".</p> --<!-- INDENTATION --> --<p>If this option is set to "no", then some rules --will use the result they get from the first matching rule --for any of the recipients of a message, so the exact value --cannot be predicted for messages with more than 1 recipient. --This value *cannot* be the filename of a ruleset.</p> - </td> - </table> - <a name="RULESETS"></a> |