×

Switch Account

Help, not blacklisted, but email traffic not reaching relay.verizon.net

Help, not blacklisted, but email traffic not reaching relay.verizon.net

Reply
Highlighted
Contributor FloridaHardware
Contributor
Posts: 1
Registered: ‎06-07-2017
Message 1 of 2
(682 Views)

I’m reaching out to you as we are a bit of a loss on whom to reach or how to resolve the issue we are having sending email to @verizon.net. I hope you can help or provide advice on how to reach the correct resources within Verizon.

 

I am the administrator for the email domain that is having the following problem.

The issue is email sent to verizon.net accounts times out.

 

[admin@mx ~]# host -t MX verizon.net
verizon.net mail is handled by 0 relay.verizon.net.

 

[admin@mx ~]# host -t A relay.verizon.net
relay.verizon.net has address 206.46.232.11

 

[admin@mx ~]# /opt/trend/imss/postfix/usr/sbin/postqueue -p
-Queue ID- --Size-- ----Arrival Time---- -Sender/Recipient-------
64E2094060 79090 Tue Jun 6 10:32:42 ffffff.lllllll@floridahardware.com
(connect to relay.verizon.net[206.46.232.11]:25: Connection timed out)
nnnnnnnn@verizon.net

 

626CA9405C 2787 Tue Jun 6 08:32:42 ffffff.lllllll@floridahardware.com
(connect to relay.verizon.net[206.46.232.11]:25: Connection timed out)
nnnnnnnn@verizon.net

2049094062 8799 Tue Jun 6 12:08:13 ffffff.lllllll@floridahardware.com
(connect to relay.verizon.net[206.46.232.11]:25: Connection timed out)
nnnnnnnn@verizon.net

-- 1652 Kbytes in 4 Requests.

We checked all of our public IP address with http://my.verizon.com/micro/whitelist/RequestForm.aspx?id=isp and found that none of them are blocked.

Verizon return emails messages with subject line as follows for all the IP/addresses
RE: Whitelist Request for IP Address 4.7.33.222 (NOT BLOCKED)

What we did find was a Verizon router dropping the traffic to relay.verizon.net. We can reach xe-0-0-0-0.DFW03-CORE-RTR2.verizon-gni.net (100.41.0.3) , but not the next hop.

Failing traceroute from mx.floridahardware.com to relay.verizon.net

The following is the bad traceroute from our mail gateway servers, . ...
Note: server is NAT’s 10.1.62.25 is NAT’d to 4.7.33.222 on a Cisco ASA5520 with is address 10.1.62.1
[root@mx ~]# traceroute -T -p 25 relay.verizon.net
traceroute to relay.verizon.net (206.46.232.11), 30 hops max, 60 byte packets
1 10.1.62.1 (10.1.62.1) 0.590 ms * *
2 4.7.33.209 (4.7.33.209) 3.358 ms 3.389 ms 3.409 ms
3 ae3-328.bar1.Orlando1.Level3.net (4.7.33.81) 12.493 ms 12.498 ms 12.482 ms
4 * * *
5 Verizon-level3-10G.Miami2.Level3.net (4.68.71.170) 17.707 ms 17.708 ms 30.305 ms
6 xe-0-0-0-0.DFW03-CORE-RTR2.verizon-gni.net (100.41.0.3) 47.590 ms 46.554 ms 44.963 ms
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *

For a comparison I did a traceroute from a Rackspace Cloud server we have at the Rackspace DFW facility to relay.verzon.net. This traffic is routed through the same Verizon core router.

The following is a known good working traceroute from one of our rackspace servers. ...
root@fork:~# traceroute -T -p 25 relay.verizon.net
traceroute to relay.verizon.net (206.46.232.11), 30 hops max, 60 byte packets
1 166.78.53.2 (166.78.53.2) 18.709 ms 18.645 ms 18.684 ms
2 aggr170a-9-core10.dfw3.rackspace.net (67.192.88.220) 0.956 ms 1.312 ms 1.335 ms
3 core10-coreb.coreb.dfw3.rackspace.net (74.205.108.50) 2.809 ms 2.449 ms core10-corea.corea.dfw3.rackspace.net (74.205.108.48) 3.767 ms
4 be32.dcpe2.dfw1.rackspace.net (74.205.108.124) 2.898 ms be31.dcpe2.dfw1.rackspace.net (74.205.108.120) 3.096 ms be31.dcpe1.dfw1.rackspace.net (74.205.108.112) 4.005 ms
5 be2-mspe2.dfw31.rackspace.net (10.25.1.135) 4.651 ms be2-mspe4.dfw30.rackspace.net (10.25.1.119) 4.622 ms be2-mspe1.dfw1.rackspace.net (10.25.1.113) 3.824 ms
6 ae-22.a01.dllstx04.us.bb.gin.ntt.net (129.250.207.117) 6.166 ms dls-bb1-link.telia.net (62.115.33.77) 3.497 ms ae2.er1.dfw2.us.zip.zayo.com (128.177.70.85) 2.431 ms
7 xe-10-1-0.cr4-dal3.ip4.gtt.net (89.149.130.170) 4.331 ms ae-9.r10.dllstx09.us.bb.gin.ntt.net (129.250.4.177) 3.808 ms xe-8-3-2.cr4-dal3.ip4.gtt.net (89.149.132.14) 4.951 ms
8 xe-0-0-0-0.DFW03-CORE-RTR2.verizon-gni.net (100.41.0.3) 6.249 ms ae27.cs1.dfw2.us.eth.zayo.com (64.125.30.180) 34.399 ms ae-0.a01.dllstx09.us.bb.gin.ntt.net (129.250.3.244) 4.726 ms
9 0.ae12.BR2.DFW13.ALTER.NET (204.255.168.157) 12.833 ms xe-0-0-0-0.DFW03-CORE-RTR2.verizon-gni.net (100.41.0.3) 5.711 ms ae5.cs1.iah1.us.eth.zayo.com (64.125.28.98) 32.761 ms
10 * * *
11 * * *
12 * * ae6.er1.iad10.us.zip.zayo.com (64.125.20.118) 32.590 ms
13 relay.verizon.net (206.46.232.11) 6.292 ms 5.511 ms 6.323 ms

Both traceroutes share "xe-0-0-0-0.DFW03-CORE-RTR2.verizon-gni.net (100.41.0.3)" in common.

Lastly I wanted to you to know that we are a new customer to these Level3 IP/address. The IP/address 4.7.33.222 and its subnet was assigned to us on March 24th 2017 and we move onto them on May 22nd 2017. If the issue that Verizon has had with these IP/address predates our assignment, please know we make every effort to be good netizens and have previously used IP/addresses Windstream IP/address for 10+ years without issue. If the issues have occurred since those dates, please help us understand the issue and how to rectify the issue and be in good standing with Verizon.

Warm Regards,
{edited for privacy}

1 REPLY 1
Moderator Moderator
Moderator
Posts: 9,048
Registered: ‎03-18-2013

Hi FloridaHardware,

Your issue has been escalated to a Verizon agent. Before the agent can begin assisting you, they will need to collect further information from you. Please go to your profile page for the forum and scroll down the page to an area titled "My Support Cases". You can reach your profile page by clicking on your name located above your post, or at the top right of this page.

Under "My Support Cases" you will find a link to the private board where you and the agent may exchange information. The title of your post is the link. This should be checked on a frequent basis, as the agent may be waiting for information from you before they can proceed with any actions. To ensure you know when they have responded to you, you may subscribe to the case. At the top right of your support case there is a gear icon which provides a drop down menu with support case options. Click that and choose "subscribe". Please keep all correspondence regarding your issue in the private support portal.

How-To Videos
 
The following videos were produced by users like you!
   
Videos are subject to the Verizon Fios Community Terms of Service and User Guidelines and contains content that is not created by Verizon.


Browse Categories
Categories:
Posts

Verizon Troubleshooters
Unable to find your answer here? Try searching Verizon Troubleshooters for more options.