We've got customers trying to receive email from people using Verizon for
Internet acess, and we are rejecting that mail because
out013pub.verizon.net [206.46.170.44] is on the MAPS RSS list. Can't pull
up the MAPS RSS website at the moment to check why. Anyone know contact
info for Verizon for this kind of issue?
Thanks.
Josh
maps RSS is open relays.
try the abuse.net relay tester on the BL'd IP and see what it turns up,
http://www.abuse.net/relay.html
richard
Looks like that IP is on quite a few lists actually...
http://rbls.org/?q=206.46.170.44
Must be a very abused Verizon mail server, possibly one of many...
Vinny Abello
Network Engineer
Server Management
vinny@tellurian.com
(973)300-9211 x 125
(973)940-6125 (Direct)
PGP Key Fingerprint: 3BC5 9A48 FC78 03D3 82E0 E935 5325 FBCB 0100 977A
Tellurian Networks - The Ultimate Internet Connection
http://www.tellurian.com (888)TELLURIAN
There are 10 kinds of people in the world. Those who understand binary and those that don't.
ah. then they will find it "challenging" to get off of anybody's open relay
list.
richard
(just fixed one of those types of open relay at a customer's site)
MAPS RSS is a list of open relays, no? It's a pretty good guess that the
above mentioned server is therefore an open relay...and it's a correct one
in this case.
http://www.njabl.org/cgi-bin/lookup.cgi?query=206.46.170.44
http://openrbl.org/ip/206/46/170/44.htm
If you're going to use a dnsbl, anybody's dnsbl, figure out how to
whitelist first (or real soon after), because this sort of thing will
happen from time to time.
jlewis@lewis.org wrote:
If you're going to use a dnsbl, anybody's dnsbl, figure out how to
whitelist first (or real soon after), because this sort of thing will
happen from time to time.
Or learn how to tell people that spam is evil and under no circumstances
will you accept spam from a system that sends it out in mass volume. If an
AS became insecure and could start allowing anyone to setup new netbock
advertisements from it, you would filter out the AS. If it was small, you
might hardcode in the valid netblocks, but when it's a large AS, you tend
just to shut it all down. Such is the way with smtp.
This server is an open relay. It's been on RSS since Sept. It's also on
njabl.org, and their web site is responding more quickly.
Verizon has been contacted many times about this and either doesn't care or
just doesn't know how to fix it. In fact, the MAPS page has a specific
message that they must be contacted by a Verizon rep to have it removed.
It will relay for anyone who gives a @verizon.net return address.