[Exim] relays.orbs.org deprecated

Top Page
Delete this message
Reply to this message
Author: Brian Candler
Date:  
To: exim-users
Subject: [Exim] relays.orbs.org deprecated
For those who haven't seen this, relays.orbs.org has been deprecated - see
announcement below.

So if you have uncommented the line

# rbl_domains = rbl.maps.vix.com:dul.maps.vix.com:relays.orbs.org

from Exim's configure.default will want to change 'relays.orbs.org' to
'inputs.orbs.org' (or remove it), and perhaps configure.default should be
updated in a future Exim release.

Right now, 'relays.orbs.org' has only a single NS record. This is the
reverse of the situation a few weeks ago, where 'inputs.orbs.org' had only a
single NS record (and that machine decided to stop responding, which in turn
turned our mailservers to treacle). It seems that if you use ORBS, you have
to keep on your toes :-(

Regards,

Brian.


>    [...]
>      relays.orbs.org is going away and will be deleted by 1 February
>    2001.

>
>      Manual entries and netblock entries have already been removed from
>    relays.orbs.org.

>
>      Use inputs.orbs.org for single stage relay filtering

>
>      Use outputs.orbs.org for immediate filtering of multihop relays.

>
>      Use delayed-outputs.orbs.org for multihop relay filtering using a
>    3-5 day grace period.

>
>    For testing, the IP address 127.0.0.2 is always in this database.

>
>    There are several other experimental DNS zones:

>
>      inputs.orbs.org - multistage inputs and direct open relays,
>    automated tester only, returns 127.0.0.2. Updated: 3-hourly

>
>      outputs.orbs.org - multistage and multipleIP outputs only, automated
>    tester only, returns 127.0.0.3 - This zone has no grace period for
>    open relay smarthosts. Updated: hourly

>
>      delayed-outputs.orbs.org - multistage and multipleIP outputs only,
>    automated tester only, returns 127.0.0.4 - This zone has a 4-5 day
>    grace period for open relay smarthosts. Updated: 3-hourly.

>
>      manual.orbs.org - open relays tested manually and believed to be
>    blocking the tester. Return code is 127.0.0.5. Updated: hourly

>
>      spamsources.orbs.org - direct spam sources. Returns 127.0.0.6.
>    Updated: hourly

>
>      untestable-netblocks.orbs.org - netblocks known to contain open
>    relays and which have been proven to be blocking the ORBS tester or
>    who have demanded that ORBS not test. Returns 127.0.0.7. Updated:
>    hourly

>
>      spamsource-netblocks.orbs.org - spam source and support netblocks. -
>    Returns 127.0.0.8. Updated: hourly

>
>      Spam source and haven netblocks get listed if our attention is
>    repeatedly drawn to them - the easiest way to do this is for those
>    netblocks to start filling ORBS spamtraps or for sustained complaints
>    to start surfacing in spam fighting forums.

>
>    These return codes will change eventually, as ORBS plans to return
>    greater detail about vulnerabilities any given host has via DNS
>    lookups. Because of this, they should be regarded as experimental

>
>      testing.orbs.org - hosts under test. Hosts believed to be currently
>    closed (this includes new checks) return 127.126.0.2. Hosts believed
>    open and being retested to see if they have been closed return
>    127.126.0.3. Updated: hourly

>
>      ok.orbs.org - This is not a whitelist and should not be treated as
>    one! - Hosts which the automated tester has been unable to relay
>    through. Hosts in this table may be secure, disabled, disconnected,
>    switched off, firewalled, not running a mail server or blocking the
>    automated tester. - 127.127.0.2. Updated: daily 

>
>      Any of these experimental zones may go away or have their parameters
>    altered without notice.
>    [spacer.gif]
>    Many packages already have hooks built in to check this sort of
>    database, since it works the same way as the MAPS RBL.