public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Ian Lance Taylor <ian@airs.com>
To: pfeifer@dbai.tuwien.ac.at
Cc: cgf@cygnus.com, overseers@sourceware.cygnus.com
Subject: Re: [kshiring@nc.rr.com: [postmaster@sourceware] Fwd: failure notice]
Date: Mon, 26 Jun 2000 22:52:00 -0000	[thread overview]
Message-ID: <20000627055237.11951.qmail@daffy.airs.com> (raw)
Message-ID: <20000626225200.bP5ost6XHy7uwMHRtRtJ1qcHdrdQy_twrqYwyOZo3z8@z> (raw)
In-Reply-To: <Pine.GSO.4.21.0006270732280.5623-100000@nunki.dbai.tuwien.ac.at>

   Date: Tue, 27 Jun 2000 07:36:03 +0200 (MET DST)
   From: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>

   That mail server is an open relay but apparently the provider (rr.com
   has a somewhat bad reputation) blocks the regular relay tests performed
   by ORBS.

   These kind of static ORBS listing usually shows that a provider is a
   die-hard spammer haven or just does not care about the problem at all.

The result of the ORBS tests on many correctly configured systems is
to send mail to the postmaster (I personally get a bunch of ORBS mail
every couple of months).  Many people block the ORBS relay tests
because they don't care to get unsolicited ORBS mail dumped in their
mailbox.  Blocking the ORBS tests does not imply that a site is a
spammer haven or that they don't care about the problem.

ORBS blocks sites which blocks the ORBS tests, which I don't think is
particularly friendly.  However, fortunately, it blocks them with a
different mechanism.  See
    http://www.orbs.org/usingindex.html
You can look at the result of the DNS lookup to see which table the
ORBS entry is in.  You may also be able to look at a subdomain of
orbs.org--I'm not quite sure what the subdomains mean.  This can be
used to permit mail from ORBS administratively blocked site.

Ian

  parent reply	other threads:[~2000-06-26 22:52 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-30  6:08 Chris Faylor
2000-06-26 17:58 ` Chris Faylor
2000-12-30  6:08 ` Gerald Pfeifer
2000-06-26 22:36   ` Gerald Pfeifer
2000-12-30  6:08   ` Ian Lance Taylor [this message]
2000-06-26 22:52     ` Ian Lance Taylor
2000-12-30  6:08 ` Ulrich Drepper
2000-06-26 18:07   ` Ulrich Drepper
2000-12-30  6:08   ` Chris Faylor
2000-06-26 18:42     ` Chris Faylor
2000-12-30  6:08 ` Jim Kingdon
2000-06-26 21:49   ` Jim Kingdon

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=20000627055237.11951.qmail@daffy.airs.com \
    --to=ian@airs.com \
    --cc=cgf@cygnus.com \
    --cc=overseers@sourceware.cygnus.com \
    --cc=pfeifer@dbai.tuwien.ac.at \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).