#4 More control over different blocking methods

Next_Release
closed-fixed
None
7
2003-09-04
2003-07-26
No

It would be handy to have the ability to block or tag
with Junkmail at a finer level.

For example, spam-traps and header wildcard matching
seem to be 100% effective, so I would be happy to
block mail with these checks. DNSBL checks are less
reliable and I would therefore like to tag positives so the
user still gets the email.

At the moment, I have to run everything as tagged with
Junkmail as even 1 falsely rejected message - we get
get 1 or 2 wrongly tagged messages a day out of 800+
which I think is brilliant - throws my users into panic.

Neil

Discussion

  • Stephen Smith

    Stephen Smith - 2003-07-28

    Logged In: YES
    user_id=783750

    Hi Neil,
    It seems to me you don't have to use DNSBL checks at all if
    you don't want to, although these stop over 50% of our junk
    even before the header/match is applied.
    I would agree that it would be cool to be able to say a
    site/match should selectively be dumped or tagged - because
    one could then experiment with doubtful sites which one can't
    be sure about but don't yet want to scrub!

     
  • Neil Burnett

    Neil Burnett - 2003-07-28

    Logged In: YES
    user_id=431787

    Steve - I agree with you on all points. However, DNSBL
    checks seem to be the only place at the moment where mail
    gets wrongly - in my users' opinions - tagged as Junkmail.
    Thus I would like to let DNSBL rejects through, but block
    spamtrapped mail. Its not a big deal though:-)

     
  • Wayne McDougall

    Wayne McDougall - 2003-08-02
    • milestone: --> Next_Release
    • priority: 5 --> 7
    • assigned_to: nobody --> waynemcdougall
     
  • Wayne McDougall

    Wayne McDougall - 2003-08-02

    Logged In: YES
    user_id=660239

    Yup. This is a good idea that I've been mulling over. Mostly
    it's figuring out how the UI would work, and how to store the
    configuration files.

    And yes you will be able to tag individually by DNSBL so some
    you trust will always block, and others you're trying out you
    can have marked as JunkMail?

    And things iwll be better when the long-promsied pass-
    through address is available. Definitely soon - the
    infrastructure is almost all in place.

    I also plan to allow the fine tuning based on domains and also
    username within a domain.

    So you can have global settings, and then alter those by
    domain, and then alter those by user.

    That's a couple of release away. In the meantime, I'll see if I
    cna quickly hack together an option to junk mail tag only the
    dnsbl blocks. That shouldn't be hard, even if it is crude - but
    effective.

    So keep coming up with the ideas and suggestions.

     
  • Wayne McDougall

    Wayne McDougall - 2003-08-02

    Fluffy release 1.1.32

     
  • Wayne McDougall

    Wayne McDougall - 2003-08-02

    Logged In: YES
    user_id=660239

    Ok, in the attached version 1.1.32 you can specify for each
    DNSBL whether or not that a match on that DNSBL will
    generate a warning, rather than a rejection.

    The server generating the warning is listed in the message
    headers as per other warnings.

    DNSBLs that generate rejections are checked first.

    So if you have Block incoming Junk mail turned on, you can
    still generate warnings for individual DNSBls - useful if a
    DNSBL is a bit unreliable (but you want to use it to warn) or if
    you want to trial a DNSBL.

     
  • Wayne McDougall

    Wayne McDougall - 2003-09-04
    • status: open --> closed-fixed
     
  • Wayne McDougall

    Wayne McDougall - 2003-09-04

    Logged In: YES
    user_id=660239

    Added to 1.1 Release

     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.





No, thanks