From: Jason Molenda <jason-swarelist@molenda.com>
To: Chris Faylor <cgf@cygnus.com>
Cc: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>,
overseers@sourceware.cygnus.com
Subject: Re: Visited http://www.orbs.org/ recently?
Date: Mon, 17 Jul 2000 17:52:00 -0000 [thread overview]
Message-ID: <20000717175225.A19278@shell17.ba.best.com> (raw)
Message-ID: <20000717175200.nqw75NI07hwJeZKoW-zi-h5pHtazK1x1KXB0vn1LRy4@z> (raw)
In-Reply-To: <20000717204250.A29996@cygnus.com>
On Mon, Jul 17, 2000 at 08:42:50PM -0400, Chris Faylor wrote:
> We've been getting a flurry of complaints from people who insist that
> there is no reason for them to be blocked. When you check the IP
> address they are not blocked and subsequent email from them is
> delivered just fine.
>
> I wonder if this is somehow a symptom of ORBS problems with MAPS.
Maybe it is. As far as I know, that _shouldn't_ happen. For
instance, when another RBL we were using went off the air (IMRSS?
I forget what it was called), there was no affect on the lookup
script. /usr/local/bin/rblcheckup would try to look the addr up
in the IMRSS DNS domain, time out after 30-60 seconds, and move on
to the next RBL.
Similarly, if ORBS wasn't reachable, rblcheck _should_ just waste
half a minute or so waiting for a response. In fact, you can tell
when this kind of thing is happening if you look at the rbl log on
sourceware - there is an initial "Checking this IP#" log message,
and then when rblcheck has checked all the RBLs, there is a "This
IP is OK" message. There are timestamps on both.
I could be mistaken - I'm only talking about how it is supposed to
work. I have trouble imaging a scenario where non-response from
the RBL could be interpreted as a match, though.
(On the other hand, it may be that ORBS' database is buggy or
something. I'd be pretty willing to believe something like that
was happening.)
J
next prev parent reply other threads:[~2000-07-17 17:52 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-30 6:08 Chris Faylor
2000-07-17 15:51 ` Chris Faylor
2000-12-30 6:08 ` Jason Molenda
2000-07-17 16:14 ` Jason Molenda
2000-12-30 6:08 ` Tom Tromey
2000-07-17 16:26 ` Tom Tromey
2000-12-30 6:08 ` Jason Molenda
2000-07-17 16:47 ` Jason Molenda
2000-12-30 6:08 ` Jim Kingdon
2000-07-17 18:55 ` Jim Kingdon
2000-12-30 6:08 ` Gerald Pfeifer
2000-07-17 17:27 ` Gerald Pfeifer
2000-12-30 6:08 ` Chris Faylor
2000-07-17 17:29 ` Chris Faylor
2000-12-30 6:08 ` Jason Molenda
2000-07-17 17:38 ` Jason Molenda
2000-12-30 6:08 ` Jason Molenda
2000-07-17 17:40 ` Jason Molenda
2000-12-30 6:08 ` Chris Faylor
2000-07-17 17:43 ` Chris Faylor
2000-12-30 6:08 ` Jason Molenda [this message]
2000-07-17 17:52 ` Jason Molenda
2000-12-30 6:08 ` Chris Faylor
2000-07-17 17:54 ` Chris Faylor
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=20000717175225.A19278@shell17.ba.best.com \
--to=jason-swarelist@molenda.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).