Date: Sun, 10 Nov 2002 10:22:57 -0600 From: "Jack L. Stone" <jackstone@sage-one.net> To: budsz <budsz@kumprang.or.id>, FreeBSD-Questions <freebsd-questions@FreeBSD.ORG> Subject: Re: How to stop SPAMMER??! Message-ID: <3.0.5.32.20021110102257.00ec9908@mail.sage-one.net> In-Reply-To: <20021110154757.GB50058@kumprang.or.id> References: <3.0.5.32.20021110083235.00ec9908@mail.sage-one.net> <3.0.5.32.20021109211740.011f73b8@mail.sage-one.net> <20021110030443.1b0577ad.gs@vacfu.org> <5.1.0.14.2.20021109150436.069a4d50@us-webmasters.com> <5.1.0.14.2.20021109150436.069a4d50@us-webmasters.com> <3.0.5.32.20021110083235.00ec9908@mail.sage-one.net>
next in thread | previous in thread | raw e-mail | index | archive | help
At 10:47 PM 11.10.2002 +0700, budsz wrote:
>On Sun, Nov 10, 2002 at 08:32:35AM -0600, Jack L. Stone wrote:
>>Sorry again.... only one sip of coffee yet. The ${oif} and ${fwcmd} are
>>both my own defined variables at the beginning of my FW script. Just
>>replace these variable commands with your own script setup cmds. I thought
>>you were already running a script.....
>
>How about if we use like spamassassin program it's will terminate this
problem?
>
>--
>budsz
>
You are only referring to a fix for emails. My FW rule stops the intruder
from using any other services as well... like using up bandwidth though the
web server, etc... DoS....
Of course, if the intruder is persistant enough, he(she) may switch IPs,
even entire IP network to get around the block. But, you just need to keep
some monitors going on all of the key logs to watch for this intrusion and
modify the block to include more IPs.... the block can be modified more
times than he(she) can change IPs eventually.....
Best regards,
Jack L. Stone,
Administrator
SageOne Net
http://www.sage-one.net
jackstone@sage-one.net
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3.0.5.32.20021110102257.00ec9908>