<!--%%INCLUDE "i_defaulthead.incl"-->
   <title>PolluStop Advanced settings and tweaks</title>
</head>
<body>
   <h1>PolluStop Advanced settings and tweaks<br />
   <span class="h2">%%domainname%%</span></h1>
   <!--%%INCLUDE "i_statuscodes.incl"-->
   <form action="advanced" method="post">

   <fieldset><legend>Coherent header information</legend>
      <p><select name="m_fromcheckenabled"><!--%%BOOLMENU settings.m_fromcheckenabled DEFAULT defaultsettings.m_fromcheckenabled DISPLAY yesno--></select>
      Try to match From: header with the Sender and
      add <select name="m_fromnomatchadd"><!--%%ENUMMENU settings.m_fromnomatchadd DEFAULT defaultsettings.m_fromnomatchadd in Scores--></select> when they don't match</p>

      <p><select name="m_tocccheckenabled"><!--%%BOOLMENU settings.m_tocccheckenabled DEFAULT defaultsettings.m_tocccheckenabled DISPLAY yesno--></select>
      Try to match To/CC headers with the Recipient and
      add <select name="m_toccnomatchadd"><!--%%ENUMMENU settings.m_toccnomatchadd DEFAULT defaultsettings.m_toccnomatchadd in Scores--></select> when there's no match</p>

      <p class="explain">It is not recommended to enable To/CC matching if you use forwarders, rpop or external accounts forwarded to local accounts.</p>
   </fieldset>

   <fieldset><legend>
   <select name="m_checkmorethanreturnpath"><!--%%BOOLMENU settings.m_checkmorethanreturnpath DEFAULT defaultsettings.m_checkmorethanreturnpath DISPLAY yesno--></select>
   Check more than return-path</legend>
   <p class="explain">The filter uses Return-Path information to determine if the message is coming
      from a local or a non-local user. This information can be forged; however, if you use SMTP-AUTH
      on your server, a non-local user cannot forge his or her return-path to be that of a local user.</p>
   <p class="explain">This setting is for those who DON'T use SMTP-AUTH. When this option is enabled, the filter
   will guess the Return-Path instead of relying only on the CGP Envelope information.
   Enable this setting only if you DON'T use SMTP-AUTH.</p>
   </fieldset>

   <fieldset><legend>Good Tokens Importance <select name="m_goodimportance" class="nw"> <!--%%ENUMMENU settings.m_goodimportance DEFAULT defaultsettings.m_goodimportance in Importances DISPLAY percentages--></select></legend>
   <p class="explain">Importance given to the Good corpus over the Spam corpus.</p>
   </fieldset>

   <fieldset><legend><select class="ed" name="m_messageidenabled"><!--%%BOOLMENU settings.m_messageidenabled DEFAULT defaultsettings.m_messageidenabled DISPLAY enabledisable--></select> Message-ID History</legend>
      <p class="explain">Remember all sent message IDs. All received messages which have a known message ID in Reference or In-Reply-To fields will automatically receive a score of 0.00. Whether or not this database is in memory, it takes about 8 bytes per sent message. So if you send 10k messages per day, the database will increase in size by about 80kB per day. The memory-resident database is faster.</p>
      <p><input type="radio" name="m_usediskdatabase" %%CHECKED(NOT(settings.m_usediskdatabase))%% value="0" /> Keep all in memory</p>
      <p><input type="radio" name="m_usediskdatabase" %%CHECKED(settings.m_usediskdatabase)%% value="1" /> Store on disk when <select name="m_maxmemsize" class="nw"><!--%%NUMERICMENU settings.m_maxmemsize DEFAULT defaultsettings.m_maxmemsize in (64, 128, 256, 512, 1024, 2048) DISPLAY memorysizes--></select> in memory are reached</p>
      <p>Keep <select name="m_historydays" class="nw"><!--%%NUMERICMENU settings.m_historydays DEFAULT defaultsettings.m_historydays in (30, 61, 91, 122, 182, 274, 365, 731, 99999)  DISPLAY historytimes--></select> of history.</p>
   </fieldset>


   <fieldset><legend><select name="m_htmlcommentcountenabled"><!--%%BOOLMENU settings.m_htmlcommentcountenabled DEFAULT defaultsettings.m_htmlcommentcountenabled DISPLAY yesno--></select> Count HTML Comments in messages</legend>
      <p class="explain">Count HTML comments in messages &lt;!--something--&gt;.</p>
      If the count exceeds <select name="m_htmlcommentscountmax" class="nw"><!--%%NUMERICMENU settings.m_htmlcommentscountmax DEFAULT defaultsettings.m_htmlcommentscountmax in (1,2,3,4,5,7,10,15,20,25,30)--></select>,
      increase the message score by <select name="m_htmlcommentcountadd"><!--%%ENUMMENU settings.m_htmlcommentcountadd DEFAULT defaultsettings.m_htmlcommentcountadd in Scores--></select>
   </fieldset>


   <fieldset><legend>Interesting Tokens</legend>
      <p class="explain">The "interest" of a token is <span style="font-style:normal">0.5 - score(token)</span>, i.e. the "distance" between 0.5 and its score. A token is more "interesting" when this value is near 0.5.</p>
      <p><input type="radio" name="m_interestingthresholdenabled" %%CHECKED(settings.m_interestingthresholdenabled)%% value="1" /> Use all tokens with a "distance" of <select name="m_interestingthreshold"><!--%%ENUMMENU settings.m_interestingthreshold DEFAULT defaultsettings.m_interestingthreshold in interests--></select> or higher.</p>
      <p><input type="radio" name="m_interestingthresholdenabled" %%CHECKED(NOT(settings.m_interestingthresholdenabled))%% value="0" /> Use the <select name="m_interestingcount" class="nw"><!--%%NUMERICMENU settings.m_interestingcount DEFAULT defaultsettings.m_interestingcount in (5,10,15,20,25,30,40,50,75,100,150,200,1000)--></select> most interesting tokens</p>
   </fieldset>


   <fieldset><legend><select class="ed" name="m_multipleweightenabled"><!--%%BOOLMENU settings.m_multipleweightenabled DEFAULT defaultsettings.m_multipleweightenabled DISPLAY enabledisable--></select> Multiple Token Weight</legend>
   <span class="explain">Tokens are used once in final calculations, even if they are present more than once in the message.
   With this option enabled, tokens found more than once will be used twice in final calculations.</span>
   </fieldset>


   <fieldset><legend><select name="m_newwordscountenabled"><!--%%BOOLMENU settings.m_newwordscountenabled DEFAULT defaultsettings.m_newwordscountenabled DISPLAY yesno--></select> Count New Words (words not in the database)</legend>
   If the count exceeds <select name="m_newwordsminimum" class="nw"><!--%%NUMERICMENU settings.m_newwordsminimum DEFAULT defaultsettings.m_newwordsminimum in (1,3,5,10,15,20,25,30,40,50)--></select>
   and <select name="m_newwordsminratio"><!--%%ENUMMENU settings.m_newwordsminratio DEFAULT defaultsettings.m_newwordsminratio in ratios DISPLAY percentages--></select> of the total,
   increase message score by <select name="m_newwordsadd"><!--%%ENUMMENU settings.m_newwordsadd DEFAULT defaultsettings.m_newwordsadd in Scores--></select>
   </fieldset>

   <fieldset><legend>Known Sources</legend>
      <p class="explain">Messages coming from known sources can have their score decreased by:</p>
      <p><select name="m_trustedsourcesub"><!--%%ENUMMENU settings.m_trustedsourcesub DEFAULT defaultsettings.m_trustedsourcesub in Scores--></select> when the message is received through a Trusted source</p>
      <p><select name="m_authenticatedsourcesub"><!--%%ENUMMENU settings.m_authenticatedsourcesub DEFAULT defaultsettings.m_authenticatedsourcesub in Scores--></select> when the message is received through an Authenticated source</p>
      <p><select name="m_scannedsourcesub"><!--%%ENUMMENU settings.m_scannedsourcesub DEFAULT defaultsettings.m_scannedsourcesub in Scores--></select> when the real sender is in a local domain</p>
      <p><select name="m_localsourcesub"><!--%%ENUMMENU settings.m_localsourcesub DEFAULT defaultsettings.m_localsourcesub in Scores--></select> when the real sender is scanned</p>
      <fieldset><legend><select name="m_pipeistrustable"><!--%%BOOLMENU settings.m_pipeistrustable DEFAULT defaultsettings.m_pipeistrustable DISPLAY yesno--></select> PIPE is trusted</legend>
         <p class="explain">The PIPE module is a Trusted source. If messages from the outside are processed in a way that requires the use of the PIPE module, you should unckeck this option.</p>
         <p class="explain">Trusted Sources may include your backup MX or secondary MXes. If these servers are not spam-protected and you make PolluStop decrease the score of messages received through a Trusted source, you may end up receiving a lot of spam through these servers that won't get caught. Testing &amp; monitoring are required.</p>
         <p class="explain">While multiple parameters may apply to one message, only the greater value will be used.</p>
      </fieldset>
   </fieldset>


   <fieldset><legend><select class="ed" name="m_contextualtokentagsenabled"><!--%%BOOLMENU settings.m_contextualtokentagsenabled DEFAULT defaultsettings.m_contextualtokentagsenabled DISPLAY enabledisable--></select> Contextual Tokens</legend>
      <p class="explain">When splitting the message into Tokens, the filter can remember in which part of the message it found each token (Subject, To/CC, From, or an URL in the message). This normally gives more accuracy when giving a score. Finding "Dick" (short for Richard) in a From: field is not the same thing as finding the same word a few times in a message...</p>
      <p class="explain"><b>WARNING:</b> This value affects training. If you change this value, you must recreate your database as well.</p>
      <fieldset><legend><select name="m_onlyallowhightocctokens"><!--%%BOOLMENU settings.m_onlyallowhightocctokens DEFAULT defaultsettings.m_onlyallowhightocctokens DISPLAY yesno--></select> Only allow To/CC-contextual tokens to increase the score</legend>
         <p class="explain">Since most of the time the Spam database has been trained from a set of mail sent to a reduced set of people, the To and CC headers will bias (quite significantly) targeted spam to a lower score. To reduce this effect, the To and CC headers tokens will be used only if they increase the score. This feature should be enabled if you didn't train both parts of the database with untampered spam and good mail coming from the same set of accounts. This feature is internally automatically enabled when Niversoft's spam database is used.</p>
      </fieldset>
   </fieldset>


   <fieldset><legend><select name="m_keeptokencase"><!--%%BOOLMENU settings.m_keeptokencase DEFAULT defaultsettings.m_keeptokencase DISPLAY yesno--></select> Case-sensitive tokens</legend>
   <p class="explain">Keep the token's case when storing it in the database. This results in a larger database which takes more memory but gives better results.</p>
   <p class="explain"><b>WARNING:</b> This value affects training. If you change this value, you must recreate your database as well.</p>
   </fieldset>


   <!--%%IF zzz--><fieldset><legend><select name="m_chainedtokensenabled"><!--%%BOOLMENU settings.m_chainedtokensenabled DEFAULT defaultsettings.m_chainedtokensenabled DISPLAY yesno--></select> Use Chained Tokens</legend>
   <p class="explain">PolluStop normally uses single tokens in its bayesian algorithms; it can also use sequences of two tokens. This increase the accuracy of the filter and doesn't affect the processing time, but it does increase the size of the database.</p>
   <p class="explain"><b>WARNING:</b> This value affects training. If you enable this value, you must recreate your database as well to use it. If you disable this value, ou should recreate your
   database to decrease its size in memory.</p>
   </fieldset>
<!--%%ENDIF-->

   <fieldset><legend><select name="m_polymorphictokensenabled"><!--%%BOOLMENU settings.m_polymorphictokensenabled DEFAULT defaultsettings.m_polymorphictokensenabled DISPLAY yesno--></select> Use polymorphic tokens</legend>
   <p class="explain">The filter can try to match a token with its other forms if it can't find it as is in the database. Other forms may include different case, different or no Contextual Token Tag, etc. This setting is recommended if you use contextual or case-sensitive tokens.</p>
   </fieldset>


   <fieldset><legend><select name="m_doublecheckwithoutaccents"><!--%%BOOLMENU settings.m_doublecheckwithoutaccents DEFAULT defaultsettings.m_doublecheckwithoutaccents DISPLAY yesno--></select> Use token ascii-fication</legend>
   <p class="explain">The filter can try to remove all accented characters from a word and check the score for the newly created word. If the score of this new word is higher than the original, this new score is used. This is a protection against the "accented words" attack. For instance, the word "m&oacute;rtg&agrave;ge" would be mapped to "mortgage" and would probably get a higher score. Also, zeros and ones are mapped to the letters "l" and "o".</p>
   </fieldset>


   <fieldset><legend>Message length</legend>
   <p>When a message is shorter than <select name="m_veryshortemail" class="nw"><!--%%NUMERICMENU settings.m_veryshortemail DEFAULT defaultsettings.m_veryshortemail in (5,10,15,20,25,30,40,50,75,100,150)--></select>,
   and no attachment with a type other than
   <!--%%FORALL att in settings.m_veryshortemailspamext--><input name="m_veryshortemailspamext" type="text" size="2" maxlength="4" value="%%att[]%%" />,<!--%%ENDFOR att--><input name="m_veryshortemailspamext" type="text" size="2" maxlength="4" value="" />
   is found in it, add <select name="m_veryshortemailadd"><!--%%ENUMMENU settings.m_veryshortemailadd DEFAULT defaultsettings.m_veryshortemailadd in Scores--></select> to the score.</p>
   <p class="explain">Messages with almost no text and no attachments other than specified types will be considered as short. Types should contain image types like jpg or gif. This way your users will likely not get explicit pornographic spam directly in their INBOX.</p>
   </fieldset>


   <fieldset><legend>Score of new and not well-known tokens</legend>
      <p>A token not in the database receives an initial score of <select name="m_newwordinitialscore"><!--%%ENUMMENU settings.m_newwordinitialscore DEFAULT defaultsettings.m_newwordinitialscore in Scores--></select>.</p>
      <p>If the token contains both letters and digits, the score is increased by <select name="m_letterdigitmixedadd"><!--%%ENUMMENU settings.m_letterdigitmixedadd DEFAULT defaultsettings.m_letterdigitmixedadd in Scores--></select>.</p>
      <p>If the token contains only consonants or only vowels, the score is increased by <select name="m_vowelsorconsonantsonlyadd"><!--%%ENUMMENU settings.m_vowelsorconsonantsonlyadd DEFAULT defaultsettings.m_vowelsorconsonantsonlyadd in Scores--></select>.</p>
      <p>If the token is longer than <select name="m_verylongtoken" class="nw"><!--%%NUMERICMENU settings.m_verylongtoken DEFAULT defaultsettings.m_verylongtoken in (7,8,9,10,11,12,13,14,15,16,17,18,19,20)--></select> characters, the score is increased by <select name="m_verylongtokenadd"><!--%%ENUMMENU settings.m_verylongtokenadd DEFAULT defaultsettings.m_verylongtokenadd in Scores--></select>.</p>
   <fieldset><legend><select class="ed" name="m_confidenceonrareenabled"><!--%%BOOLMENU settings.m_confidenceonrareenabled DEFAULT defaultsettings.m_confidenceonrareenabled DISPLAY enabledisable--></select> Confidence bias</legend>
   <p class="explain">Token score is biased in the direction of the initial score when we have little data on it.</p>
   We have a confidence of <select name="m_newwordconfidenceonrare"><!--%%ENUMMENU settings.m_newwordconfidenceonrare DEFAULT defaultsettings.m_newwordconfidenceonrare in Scores display percentages--></select> that a new word really has this score.
   </fieldset></fieldset>


   <fieldset><legend><select class="ed" name="m_pgptweak"><!--%%BOOLMENU settings.m_pgptweak DEFAULT defaultsettings.m_pgptweak DISPLAY enabledisable--></select> PGP signature detection</legend>
   <p class="explain">PolluStop is bound to generate false positive when an inline PGP signature or encryption is used. This setting reduces the risk of false positives, and could be extended to other types of signatures in further versions if required.</p>
   The filter can also subtract <select name="m_pgpsub"><!--%%ENUMMENU settings.m_pgpsub DEFAULT defaultsettings.m_pgpsub in Scores--></select> from the message when it contains a PGP signature,
   <p class="explain">however this is not recommended since a spam could contain a PGP signature only to mislead the filter.</p>
   </fieldset>


   <fieldset><legend><select class="ed" name="m_longtokensequencesenabled"><!--%%BOOLMENU settings.m_longtokensequencesenabled DEFAULT defaultsettings.m_longtokensequencesenabled DISPLAY enabledisable--></select> Long Tokens Sequence detection</legend>
   <p class="explain">Some spammers include a block of random words in the message to mislead bayesian-type spam filters. PolluStop can try to detect them by checking punctuation.</p>
   Allow a maximum of <select name="m_longtokensequencesmax" class="nw"><!--%%NUMERICMENU settings.m_longtokensequencesmax DEFAULT defaultsettings.m_longtokensequencesmax in (5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26,27,28,29,30)--></select> subsequent words without
   punctuation, and add <select name="m_longtokensequencesadd"><!--%%ENUMMENU settings.m_longtokensequencesadd DEFAULT defaultsettings.m_longtokensequencesadd in Scores--></select> to the message score when it breaks this rule.
   </fieldset>


   <fieldset><legend><select name="m_savefulltokens"><!--%%BOOLMENU settings.m_savefulltokens DEFAULT defaultsettings.m_savefulltokens DISPLAY yesno--></select> Save full tokens</legend>
   <p class="explain">The PolluStop database contains hashes of the tokens, not the full tokens, and, while you can query if a single token is in the database, there's no way to get a list. You may want to have a list of which tokens are in the database; PolluStop can save this list on disk as they are added to the database. This list is kept in memory until the database is saved (once per hour if modified), and is appended to a text file (pollustop/db/tokens.list). PolluStop will never try to reload the list, if you don't need it you can delete it and disable this function, but once deleted it is NOT recoverable.</p>
   </fieldset>


   <fieldset><legend><select class="ed" name="m_invisibilitydetection"><!--%%BOOLMENU settings.m_invisibilitydetection DEFAULT defaultsettings.m_invisibilitydetection DISPLAY enabledisable--></select> Invisibility detection</legend>
   <p class="explain">PolluStop can detect "invisible" text, such as white text (or pale yellow text) on white background. When such "invisible" text is found, the probability of spam is very high.</p>
   <p>When "invisible" text is detected, add <select name="m_invisibilityadd"><!--%%ENUMMENU settings.m_invisibilityadd DEFAULT defaultsettings.m_invisibilityadd in Scores--></select> to the message's score</p>
   </fieldset>


   <fieldset><legend><select class="ed" name="m_inlinejisenabled"><!--%%BOOLMENU settings.m_inlinejisenabled DEFAULT defaultsettings.m_inlinejisenabled DISPLAY enabledisable--></select> Inline JIS encoding detection</legend>
   <p class="explain">Some spam is sent in japanese and is often illegible, even for japanese readers, since it's send with inline JIS encoding, which is not supported by most mail clients. UTF-8 or Unicode should be used to send messages with non-ASCII characters.</p>
   <p class="explain">You can easily identify such mails, they contains a lot of illegible characters, often beginning by &larr;$B (ESC $ B).  For instance: &larr;$B$*Aj&lt;j$O%-%c%j%&quot;%&amp;!&lt;%^%s$N$_$G$9&larr;</p>
   <p class="errors">You should disable this feature if you send or receive legitimate mail with inline JIS encoding, but it's recommended to switch to UTF-8 or Unicode as soon as possible.</p>
   <p>When inline JIS encoding text is detected, add <select name="m_inlinejisadd"><!--%%ENUMMENU settings.m_inlinejisadd DEFAULT defaultsettings.m_inlinejisadd in Scores--></select> to the message's score.</p>
   </fieldset>



   <fieldset><legend>Single-letters tokens detection</legend>
      <p class="explain">The spammer can try to hide some words from the spam filter by i&nbsp;n&nbsp;s&nbsp;e&nbsp;r&nbsp;t&nbsp;i&nbsp;n&nbsp;g &nbsp; s&nbsp;p&nbsp;a&nbsp;c&nbsp;e&nbsp;s &nbsp; in it or using html/css float tricks. PolluStop can detect these attempts.</p>
      <p class="explain">While PolluStop is not able to reconstruct the word to give it a score, the simple attempt to obfuscate a word with this technique is a good sign of spam.</p>

      <fieldset><legend><select name="m_singlelettertokenscountenabled"><!--%%BOOLMENU settings.m_singlelettertokenscountenabled DEFAULT defaultsettings.m_singlelettertokenscountenabled DISPLAY yesno--></select> Count Single-letter words</legend>
         <p>If the message contains more than <select name="m_singlelettertokensratio"><!--%%ENUMMENU settings.m_singlelettertokensratio DEFAULT defaultsettings.m_singlelettertokensratio in lowratios DISPLAY lowpercentages--></select> of such words, add <select name="m_singlelettertokensadd"><!--%%ENUMMENU settings.m_singlelettertokensadd DEFAULT defaultsettings.m_singlelettertokensadd in Scores--></select> to the message score;</p>
      </fieldset>


      <fieldset><legend><select class="ed" name="m_singleletterseqenabled"><!--%%BOOLMENU settings.m_singleletterseqenabled DEFAULT defaultsettings.m_singleletterseqenabled DISPLAY enabledisable--></select> Check for several single-letter characters in a row</legend>
        <p>If more than <select name="m_singlelettersequencemax"><!--%%NUMERICMENU settings.m_singlelettersequencemax DEFAULT defaultsettings.m_singlelettersequencemax in (1,2,3,4,5,6)--></select> single-letter words are found in a row, add <select name="m_singlelettersequenceadd"><!--%%ENUMMENU settings.m_singlelettersequenceadd DEFAULT defaultsettings.m_singlelettersequenceadd in Scores--></select> to the message score;</p>
      </fieldset>
   </fieldset>

   <fieldset><legend><select class="ed" name="m_checkabusivelinkedimages"><!--%%BOOLMENU settings.m_checkabusivelinkedimages DEFAULT defaultsettings.m_checkabusivelinkedimages DISPLAY enabledisable--></select> Detect linked-image spam</legend>
      <p class="explain">PolluStop can detect spam formed by one or two linked images in a short message.</p>
      <p>When such linked images are found, add <select name="m_abusivelinkedimagesadd"><!--%%ENUMMENU settings.m_abusivelinkedimagesadd DEFAULT defaultsettings.m_abusivelinkedimagesadd in Scores--></select> to the message's score.
   </fieldset>

   <fieldset><legend><select class="ed" name="m_checkheaderpattern"><!--%%BOOLMENU settings.m_checkheaderpattern DEFAULT defaultsettings.m_checkheaderpattern DISPLAY enabledisable--></select> Detect header pattern</legend>
      <p class="explain">PolluStop can detect spam containing several spaces at the beginning of the From: and the Date: headers. This pattern has been found in many spam messages but no good mail yet</p>
      <p>When such a pattern is found, add <select name="m_headerpatternadd"><!--%%ENUMMENU settings.m_headerpatternadd DEFAULT defaultsettings.m_headerpatternadd in Scores--></select> to the message's score.
   </fieldset>

   <fieldset><legend><select class="ed" name="m_checkmessagedate"><!--%%BOOLMENU settings.m_checkmessagedate DEFAULT defaultsettings.m_checkmessagedate DISPLAY enabledisable--></select> Check Message date</legend>
      <p class="explain">Several spam is sent with a very old date or a date in the far future. Good messages with an incorrect date are usually off by a few days to a few months. PolluStop will add 0.3 to a message with a date off by two years or more.</p>
      <p>When such a date is found, add <select name="m_messagedateadd"><!--%%ENUMMENU settings.m_messagedateadd DEFAULT defaultsettings.m_messagedateadd in Scores--></select> to the message's score.
   </fieldset>

   <fieldset><legend><select class="ed" name="m_attachmentspam"><!--%%BOOLMENU settings.m_attachmentspam DEFAULT defaultsettings.m_attachmentspam DISPLAY enabledisable--></select> Detect attachment spam</legend>
      <p class="explain">PolluStop can detect spam formed by one attachment (an image file, a pdf or a zip file) and no text at all in the body.</p>
      <p>When such message is found, add <select name="m_attachmentspamadd"><!--%%ENUMMENU settings.m_attachmentspamadd DEFAULT defaultsettings.m_attachmentspamadd in Scores--></select> to the message's score.
   </fieldset>

   <!--%%IF (zzz)-->
   <fieldset><legend><select class="ed" name="m_checkspamurl"><!--%%BOOLMENU settings.m_checkspamurl DEFAULT defaultsettings.m_checkspamurl DISPLAY enabledisable--></select> Detect spam url</legend>
      <p class="explain">EXPERIMENTAL FEATURE. PolluStop can detect messages formed by a link pointing to a search engine, link whose parameters will make the search engine automatically open a particular page, which most likely is an advertisement for the spammer's product.</p>
      <p>Such a link will cause PolluStop to consider the message as spam. Currently only google links using the "I'm feeling lucky" or adwords are detected. More will likely be added in future versions
   </fieldset>

   <fieldset><legend><select name=m_experimentalfeaturesenabled><!--%%BOOLMENU settings.m_experimentalfeaturesenabled DEFAULT defaultsettings.m_experimentalfeaturesenabled DISPLAY yesno--></select> Enable Experimental Features</legend>
   <p class=explain>PolluStop can include other experimental features that may increase its accuracy. These features haven't been tested over a large amount of emails, and the results and implications may not be completely known.</p>
   </fieldset>
   <!--%%ENDIF-->

   <br><br>

   <p><input type="submit" class="btn" name="Apply" value="Save settings" /><input type="reset" class="btn" value="Reset" /></p>
   </form>
<!--%%INCLUDE "i_defaultfoot.incl"-->

