Pegasus Mail & Mercury

Welcome to the Community for Pegasus Mail and
The Mercury Mail Transport System, the Internet's longest-serving PC e-mail system!
Welcome to Pegasus Mail & Mercury Sign in | Join | Help
in
Home Blogs Forums Downloads Pegasus Mail Overview Mercury Overview

Content Control definitions and rule files

Last post 02-05-2008, 12:02 by billinghurst. 1 replies.
Sort Posts: Previous Next
  •  01-30-2008, 15:45

    • pmerik is not online. Last active: 2008-12-10, 17:42 pmerik
    • Top 25 Contributor
    • Joined on 01-24-2008
    • Member
    • Points 760

    Content Control definitions and rule files

    I suggest that Content Control should accumulate weights from all rule sets. Possibly as an option with an associated threshold, in addition to the per file thresholds.

    Rationale: Content Control is a valuable spam fighting tool because it can catch tricks that would fool Bayesian filters, e.g concatenation like ArbitraryWordViagraArbitraryFemaleName. This suggestion would make it possible to update/replace SPAMBUST.DAT (as part of the Pegasus install package) without overwriting user additions. Plus it would encourage a more fine-grained rule structure.

    If my primary suggestion is not feasible, then I suggest either

    1. that the file-size limit of the internal editor be removed, or
    2. that the internal editor be disabled and an external editor be launched when the limit is exceeded
    Erik
  •  02-05-2008, 12:02

    Re: Content Control definitions and rule files

    pmerik:

    I suggest that Content Control should accumulate weights from all rule sets. Possibly as an option with an associated threshold, in addition to the per file thresholds.

    Rationale: Content Control is a valuable spam fighting tool because it can catch tricks that would fool Bayesian filters, e.g concatenation like ArbitraryWordViagraArbitraryFemaleName. This suggestion would make it possible to update/replace SPAMBUST.DAT (as part of the Pegasus install package) without overwriting user additions. Plus it would encourage a more fine-grained rule structure.

    If my primary suggestion is not feasible, then I suggest either

    1. that the file-size limit of the internal editor be removed, or
    2. that the internal editor be disabled and an external editor be launched when the limit is exceeded

    Erik

    I would have to agree.  When building my own filters, I prefer to have a variety of smaller sets of filters so that I can order, and apply fine control.  One file for RECEIVED headers, another for pharmacy type spam, another for enormous appendages, etc.  Even if there is the capacity to identify the active filters so that they are able to be strung together.  

    It would also be useful to be able to apply a global set of filters (uneditable), and then apply user-based filters.

    [Having changed ISP's and they're not having as a good set of spam filtering, I am back into doing a bit more of my own.]

    Regards Andrew

    Filed under:
View as RSS news feed in XML

Copyright © 2007 David Harris / Peter Strömblad. All Rights Reserved. | Terms of Use | Privacy Statement
Questions/Problems with community.pmail.com? | Visit our Hoster: PraktIT | Pegasus Mail Home Page