HOME
LOOKUP
REMOVE
SUPPORT
GRAPHS
REJECTIONS
STATUS
FAQ
TESTING
FEEDBACK
TYPES
LINKS
REGISTER
SUBSCRIPTION
MEMBERS
FIREWALL
|
pdl
orid
ahbl
wpbl
ucepn
spews
probes
spamsites
dsbl
sorbs
|
|
t1
|
rddn
ahrh
orrh
jwrh
|
rmst
ricn
rdts
|
osrs
omrs
osps
ohps
owps
owfs
|
|
ricn.dnsbl.net.au
dnsbl.net.au Incorrectly Configured Networks
Servers (/32) which are incorrectly configured (as detailed below), are listed here.
Networks (/24) containing 2 or more incorrectly configured servers (/32), are also listed here.
Current retesting cycle is taking :
hours
Typical reasons for entry here are:
server sending email is already listed on one or more DNSBL services
server sending email has no reverse DNS entry (aka PTR)
domain name of envelope sender has no MX records
MX record entries have incorrect or missing A records
message ID domain part does not match with envelope sender address
network sending email is not the same network that would receive replies
envelope sender address appearing from multiply incorrectly configured servers
All servers sending email into our network, with more that 2 errors, are
automatically listed onto the ricn.dnsbl.net.au list.
There are no current self removal methods, other than fixing the network
configuration of the server wanting to send legitimate email.
Steps you should take include:
consult with your local internet configuration professional.
ensure you get the server in question off all other dnsbl lists, first.
ensure all servers have correctly configured reverse DNS entries.
ensure domains which must receive email have correct MX records.
ensure each of those MX records, have correct A records also
configure your sending software to have the correct message ID format
ensure your outbound and inbound networks are one and the same
NOTE: Where more than one server is listed in any Class C block (aka /24) we
list the entire Class C (aka /24). Fix the security and configuration errors
on those individual servers (/32) and the Class C (/24) entries will auto remove
themselves.
Server tests are carried out upon initial email transaction, with retests carried
out each day.
