Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 25 Jan 2007 08:28:50 -0300
From:      JoaoBR <joao@matik.com.br>
To:        freebsd-stable@freebsd.org
Cc:        "Peter N. M. Hansteen" <peter@bsdly.net>
Subject:   Re: Loosing spam fight
Message-ID:  <200701250828.50540.joao@matik.com.br>
In-Reply-To: <87ps93poqg.fsf@thingy.datadok.no>
References:  <8a20e5000701240903q35b89e14k1ab977df62411784@mail.gmail.com> <87ps93poqg.fsf@thingy.datadok.no>

next in thread | previous in thread | raw e-mail | index | archive | help
On Thursday 25 January 2007 04:08, Peter N. M. Hansteen wrote:
> For purposes of making the subject less true, setting up greylisting
> with an optional tarpit for known baddies can be very effective.  See
> Dan Langille's recent Onlamp article[1] or for that matter my tutorial[2]
> for how this is done using PF and spamd - this way it doesn't matter much
> which MTA(s) you use.
>
> [1] http://www.onlamp.com/pub/a/bsd/2007/01/18/greylisting-with-pf.html
> [2] http://home.nuug.no/~peter/pf/en/, with the specifics of spamd and
>     greylisting starting at http://home.nuug.no/~peter/pf/en/spamd.html


all this methods are certainly useless, stay calm ok

the only way to block spam really is blocking any incoming tcp:25 ...

any firewall based method you may use do block innocents as well, ike some =
do=20
they block entire IP ranges from countries because most spam comes from the=
m,=20
that is stupid, more brainless since the spam mostly is not generated by an=
y=20
of this servers, it only goes through it, this method might cause *you* not=
=20
getting this spam but does not stop spam at all ...

probably better, if you like firewall blocks, cutting the complete US IP=20
address space from sending to any tcp:25 to stop spam definitly, because I=
=20
never heard of chinese or african viagra hahahaha

spam block list abviously are very usefull so long as they are maintained

IMO a good way and probably the best way is to do some inicial checks like=
=20
connection rate and limit them, then a spam checker like spamassassin for=20
regex and header checks

still you get SPAM and you never can block spam 100%, spammers change serve=
rs,=20
IPs, patterns faster then we can react, but we all know this right?=20

and even then if you get it all into your box you still get spam by whom se=
nds=20
it out without caring of identity or hiding it, a correct email msg but spam

where spam needs to be catched is at the origin, ISPs should take care of t=
his=20
problem by not permitting access to outside servers but only passing throug=
h=20
their smtp gateways, an outgoing spam check is what needs to be done but =20
here nobody cares ...

=2D-=20

Jo=E3o







A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura.
Service fornecido pelo Datacenter Matik  https://datacenter.matik.com.br



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200701250828.50540.joao>