public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Helge Hafting <helgehaf@aitel.hist.no>
To: "Johnson, Richard" <rjohnson@analogic.com>
Cc: linux-kernel@vger.kernel.org
Subject: [OT] Re: Horiffic SPAM
Date: Thu, 25 Sep 2003 10:21:49 +0200	[thread overview]
Message-ID: <3F72A59D.4000407@aitel.hist.no> (raw)
In-Reply-To: Pine.LNX.4.53.0309241006500.30216@quark.analogic.com

Richard B. Johnson wrote:
> On Tue, 23 Sep 2003, Andrea Arcangeli wrote:
> 
> 
>>On Tue, Sep 23, 2003 at 02:11:59PM -0400, Richard B. Johnson wrote:
>>

> Well it seems that fire-walling the SPAM servers is *not* a good idea.
> They are persistant, gang up, and will not give up until they are
> able to deliver the mail! When I firewall them, my network traffic

According to standards they will give up after 5 days or so.

> ends up being continuous SYN floods as every spam-server in the
> country tries to connect. It doesn't do any good to set `ipchains` to
> REJECT instead of DENY. They just keep on banging on the door.
> 

Have you considered teergrubing them instead?  That ought to
fix the bandwith problem.  And it is not so fun for whoever has
the spam server either - either disrupting some spammers operation
or harassing some server admin into making his box un-abuseable.


Helge Hafting


  reply	other threads:[~2003-09-25  8:13 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-23 18:11 Horiffic SPAM Richard B. Johnson
2003-09-23 18:36 ` Andrea Arcangeli
2003-09-23 18:53   ` Matt Heler
2003-09-23 19:06     ` offtopic (Re: Horiffic SPAM) Andrea Arcangeli
2003-09-24  3:15       ` Sandy Harris
2003-09-24  6:28     ` Horiffic SPAM Paul Dickson
2003-09-24 14:18   ` Richard B. Johnson
2003-09-25  8:21     ` Helge Hafting [this message]
2003-09-25 12:30       ` [OT] " Richard B. Johnson
2003-09-25 14:59       ` Valdis.Kletnieks
2003-09-25 15:36         ` Toshiba Tecra S1 Battery Status Bernt Hansen
2003-09-23 18:43 ` [OT] Re: Horiffic SPAM Grant Miner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3F72A59D.4000407@aitel.hist.no \
    --to=helgehaf@aitel.hist.no \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rjohnson@analogic.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox