public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Nick LeRoy <nleroy@cs.wisc.edu>
Cc: "Nicholas Knight" <nknight@pocketinet.com>,
	"Gérard Roudier" <groudier@free.fr>,
	Linux <linux-kernel@vger.kernel.org>
Subject: Re: Bounce from andre@linuxdiskcert.org
Date: Tue, 08 Jan 2002 18:35:00 +0000	[thread overview]
Message-ID: <31539.1010514900@redhat.com> (raw)
In-Reply-To: <200201081738.g08Hcw125981@schroeder.cs.wisc.edu>
In-Reply-To: <200201081738.g08Hcw125981@schroeder.cs.wisc.edu>  <20011230122500.E859-100000@gerard> <WHITEvJ1xKjtgZe0J64000008b1@white.pocketinet.com> <20020108181224.M5235@khan.acc.umu.se>


nleroy@cs.wisc.edu said:
>  It sure would be nice if they'd send you an email informing you that
> your  site has an open relay, and if it's not corrected within, say, 1
> week, you'll  be put on the black list.  These sites also obviously
> have tests for checking  for open relays, also.  The administrator of
> said site should be allowed  access to these same tests to aid in
> diagnosing and solving the problem.

I don't understand your complaint - is there any particular stupidity you
think your own mail server might be guilty of, for which you are not capable
testing for yourself _before_ you get blacklisted? Or indeed for which any
responsible admin wouldn't test automatically as part of the process of
commissioning a new system?

Some blacklists do have a policy of warning the owners of offending sites
before actually adding the site to the list, and postponing the addition for
as long as the admin says that they're working on fixing the brokenness.
This gets abused.

The list of offences for which you'll get blacklisted isn't very large. If
you can't manage to set up a well-behaved system without external
assistance, you shouldn't be running it in the first place.

--
dwmw2



  parent reply	other threads:[~2002-01-08 18:35 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3C2BE2010004B5F3@mail.libertysurf.net>
2001-12-30 11:33 ` Bounce from andre@linuxdiskcert.org Gérard Roudier
2001-12-30 14:26   ` Lionel Bouton
2001-12-30 14:59   ` Nicholas Knight
2001-12-30 17:05     ` Gérard Roudier
2001-12-30 19:11     ` Stephan von Krawczynski
2001-12-31  9:38       ` brian
2001-12-31 15:38         ` Stephan von Krawczynski
2001-12-31 16:00           ` Rik van Riel
2002-01-01  1:58           ` brian
2002-01-01 16:47             ` Stephan von Krawczynski
2002-01-04  0:52           ` Petro
2002-01-08 17:12     ` David Weinehall
2002-01-08 17:36       ` Nick LeRoy
2002-01-08 18:35       ` David Woodhouse [this message]
2002-01-08 18:51         ` Richard B. Johnson

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=31539.1010514900@redhat.com \
    --to=dwmw2@infradead.org \
    --cc=groudier@free.fr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nknight@pocketinet.com \
    --cc=nleroy@cs.wisc.edu \
    /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