FW: Stop Using relays.osirusoft.com *NOW*!

[Matt]

> I personally recommend _not_ using DNS-based blockers, rather focusing on
the
> content, as most DNS-based blockers are of the
guilty-until-proven-innocent /

I disagree.  We have a client that sends out legitiment opt in email.
Talking to her they have to word everything carefully so it gets through and
if it does get falsely tagged most users won't look through there junk mail
folder to find the error anyway.  So content filtering can be slipped by and
it can tag legitiment email as well.  Here is what we currently are trying.

*(Block These, sender gets a link in bounce message as to why)
relays.orbd.org (if its an open smtp relay why let it through)
proxies.relays.monkeys.com (open socks proxies are worse yet)
opm.blitzed.org (more open socks proxies)
(**Got it in the shorts here)
dialups.relays.osiruSoft.com (if its a dial-up they can use there ISP's smtp
server)
sbl.spamhaus.org (this one is iffy, but they only seem to block the worst of
the worst, anyone got opinions on it?  Looking through logs it looks to be
pretty conservative.  Perhaps should move it to tag again.)

*(Tag headers here on more agressive ones)
bl.spamcop.net (occasionally falses but quite effective)
(**Yep, gone)
relays.osiruSoft.com (occasionally falses but quite effective again)

I think its just a matter of taking the middle ground or whatever suits you.
SPAM is way out of hand.  I really wish Outlook Express allowed you to
filter based on header content.  Then we would just tag the headers with a
score and give the end users complete control.  If I modify the Subject I
get tons of complaints.  Perhaps adding a tag to the end of the body would
work.

Matt


> <rant>
>
> I personally recommend _not_ using DNS-based blockers, rather focusing on
the
> content, as most DNS-based blockers are of the
guilty-until-proven-innocent /
> shoot-first-ask-questions-later variety which cause untold damage to
innocent
> businesses and people.
>
> </rant>