FYI, this topic was discussed on this listserv in mid-October (http://mailman.nanog.org/pipermail/nanog/2014-October/070532.html) and mailops (archives restricted to listserv members) in mid-November. In the NANOG thread reference was made that Verizon was filtering out the 107/8 network.
Frank -----Original Message----- From: NANOG [mailto:[email protected]] On Behalf Of Chris Adams Sent: Friday, January 16, 2015 4:03 PM To: [email protected] Subject: Re: Verizon.net email admin? Once upon a time, Pete Carah <[email protected]> said: > On 01/16/2015 04:00 PM, Chris Adams wrote: > > Anybody Verizon.net mail admins around? > > > > I have a downstream customer on a newly-deployed IP allocation that > > can't get to pop.verizon.net (connections just time out). > I can't either ping or telnet to that either but can connect with > s_client. I'm *on* verizon (fios)... Yeah, apparently they only allow SSL-wrapped connections on 993 and 465, block ping/traceroute, etc. (makes it hard to debug). However, I believe the customer when they say the computer is configured correctly, because it is a notebook and works on another network (both at our downstream, in a different IP block, and a fast-food place with free wifi). > Maybe they only allow secure, at least from some locations. > (Just for reference, I'm seeing pop.verizon.net at a 206.46.x.x address, > no v6.) Me too (didn't think if they might have different IPs in different locations). I see pop.verizon.net is 206.46.232.132. > (not saying that they don't filter, but there are no 107 prefixes in the > current cymru fullbogon4 list fetched about 5 minutes ago.) I don't know; that's just a guess on my part that it may be the problem (seems to fit). -- Chris Adams <[email protected]>
