Blacklist removal guide
How to remove your IP from ORVEDB
ORVEDB is an old open-relay list from ANTISPAM-UFRJ. Here is what a listing means, and why fixing your server is the whole job.
What it is
The list, in plain terms.
ORVEDB — the Realtime Open-Relays Verifying Engine Database List — is one of three DNS blocklists run by ANTISPAM-UFRJ, the anti-spam project of the Signal Processing Laboratory at the Federal University of Rio de Janeiro (UFRJ) in Brazil. It is published as the DNS zone orvedb.aupads.org and lists the IP addresses of mail servers confirmed to be open relays.
A listing here is not an accusation of spamming. As the operator puts it, an open relay is usually run accidentally, through the inexperience of its administrator. The list is built and maintained entirely by an automated engine called ORVE, which tests a host, and adds it only if the host actually relays a test message back intact.
ORVEDB is a legacy list. Its own pages date to the early 2000s and reference services such as MAPS RBL and ORBS that have long since closed. Few mainstream receivers still consult it, so an ORVEDB listing on its own rarely causes widespread bouncing — but some blacklist checkers still query the zone, and the underlying problem it flags, a genuinely open relay, is worth fixing regardless.
Why you get listed
What a listing on ORVEDB means.
How to get removed
Delisting, in order.
Removal is free. Fix the cause first — a listing you clear without a fix comes straight back.
- 1 Confirm the listing. Look your IP up with the ANTISPAM-UFRJ lookup tool at aupads.org/cgi-bin/ordb-lookup. A query on the zone returns 127.0.0.3 when the IP is listed. There is no cost and no account.
- 2 Close the open relay. This is the real work and everything else depends on it. Reconfigure your MTA to require authentication for outbound mail and to reject relaying for hosts outside your own networks. Removal is impossible while the server still relays, because ORVE simply re-lists it.
- 3 Let ORVE re-test, or request a re-test. ORVEDB has no manual delist form. The engine re-tests each listed host every 90 days, or sooner if the administrator requests it via ANTISPAM-UFRJ. The re-test is a battery of 20 relay attempts.
- 4 Refuse all 20 relay tests. Only a host that refuses every one of the 20 relay tests is removed immediately. If any single test still looks suspicious, ORVE waits a further 90 days before removing you. So make sure the relay is fully and correctly closed before the re-test runs.
- 5 Do not firewall ORVE. Blocking the ORVE tester at your firewall does not clear the listing. If ORVE cannot connect at all, it keeps trying for two years before treating the host as non-existent and removing it. Let the test through against a properly closed relay instead.
The official route
Straight to the source.
Removal happens on ORVEDB's own tool — never through a paid service.
ORVEDB removal tool ↗Return codes
How long it takes
Removal is automatic, not instant. A listed host is re-tested every 90 days or on administrator request. Refuse all 20 relay tests and removal happens immediately after that re-test; if any test still shows suspicion, ORVE waits another 90 days. A host that blocks the tester entirely is only removed after two years of failed connection attempts.
Common questions
About ORVEDB, specifically.
Related
The bounce behind the listing.
Do not fix it blind.
See every list you are on and every authentication problem behind the listing in one 40-second check — then let monitoring tell you the day a listing comes back.