http://www.orbs.org/ says "Due to circumstances beyond our control,
the ORBS website is no longer available."
http://www.rfc-ignorant.org/ is an RBL-like blacklist of domains that
think RFC conformance is for wimps. Currently they list domains that
refuse mail from <> (null sender) and refuse mail to postmaster@.
rfc-ignorant.org uses a blacklist style similar to RBL. To check if
163.net doesn't support <> return paths:
alex@buick:~$ dnsip 163.net.dsn.rfc-ignorant.org
127.0.0.2
alex@buick:~$ dnstxt 163.net.dsn.rfc-ignorant.org
Not supporting null originator (DSN)
To check if 978.org doesn't support <> return paths:
alex@buick:~$ dnsip 978.org.dsn.rfc-ignorant.org
alex@buick:~$ dnstxt 978.org.dsn.rfc-ignorant.org
Zone transfers for dsn.rfc-ignorant.org was denied by ns1.megacity.org
but accepted by ns1.pyrotechnics.com. Zone transfers for
postmaster.rfc-ignorant.org were accepted by ns1.pyrotechnics.com.
With dnsip and some string manipulation against $SENDER it should be
trivial to implement a blacklist check in a dot-qmail file. I recommend
this, the choice to use any particular blacklist should be made by the
user, not the system administrator.
rblstmpd can't support this kind of blacklist because it doesn't
support a full SMTP transaction, and the blacklist operates on return
path addresses, not client IP addresses. It should be possible to
patch qmail-smtp to support this blacklist, let [EMAIL PROTECTED]
know if you have something working.
Spite listings have been a problem with other blacklists, no word yet
about spite listings on rfc-ignorant.org.
