- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
E-mail test referred to in above post: finally arrived at 11:10 AM EST. That's 32 minutes - not good!
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
As we continue to chase down the root cause for the complaints of latency with our email experience, we need the following info:
1. When was/is it occurring?
2. Was this inbound or outbound email?
3. What mail store is customer on?
4. Using Netmail or POP3
5. Are specific domains appear to be affected?
To troubleshoot outbound latency, we need the headers from the delayed message
The headers from the received message that was delayed
We need data from the sender’s mail system like …
o How many attempts did they make before the message was delivered?
o On those previous attempts, what was the response from the MTA or was it just unreachable?
o A telnet test to relay.verizon.net with the exact output
o A ping and a traceroute to relay.verizon.net
o IP ranges that they use so we can make sure they’re not RBL’d
I would like to have the following info PM'd to me so I can get this resolved
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Huh?
@bbranco wrote:
Google re-writes the outbound email address as your address, so you can't use myname@domain.com as the outbound address.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Google changes the from address to your Google email account...
If you have your email address as brian@abccompany.com when you send email out, it will show up as coming from brian1234@google.com - where brian1234 is my google email address.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
As we continue to chase down the root cause for the complaints of latency with our email experience, we need the following info:
1. When was/is it occurring?
2. Was this inbound or outbound email?
3. What mail store is customer on?
4. Using Netmail or POP3
5. Are specific domains appear to be affected?
To troubleshoot outbound latency, we need the headers from the delayed message
The headers from the received message that was delayed
We need data from the sender’s mail system like …
o How many attempts did they make before the message was delivered?
o On those previous attempts, what was the response from the MTA or was it just unreachable?
o A telnet test to relay.verizon.net with the exact output
o A ping and a traceroute to relay.verizon.net
o IP ranges that they use so we can make sure they’re not RBL’d
I would like to have the following info PM'd to me so I can get this resolved
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I posted two days ago about having to wait 22 minutes for my email to be delivered by Verizon, and included the mail headers showing that Verizon received the email as soon as I sent it, but did not deliver it until 22 minutes later.
Today, however, I cannot provide mail headers because the mail message has not yet arrived, after 12 hours.
I'm simply using outgoing.verizon.net as the SMTP server with my mail client. Since it works sometimes, I know the port settings and password are correct. There is no problem with TRACERT to outgoing.verizon.net, but the TRACERT to vms173005pub.verizon.net (the server that delivered my mail two days ago) times out.
Tracing route to vms173005pub.verizon.net [206.46.173.5]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 11 ms 7 ms 10 ms L100.PHLAPA-VFTTP-71.verizon-gni.net [96.227.51.1]
3 10 ms 10 ms 9 ms G12-1-671.PHLAPA-LCR-06.verizon-gni.net [130.81.104.166]
4 10 ms 9 ms 10 ms so-5-2-0-0.PHIL-BB-RTR2.verizon-gni.net [130.81.28.156]
5 10 ms 9 ms 10 ms so-7-0-0-0.PHIL-BB-RTR1.verizon-gni.net [130.81.19.62]
6 15 ms 14 ms 17 ms so-8-0-0-0.LCC1-RES-BB-RTR1-RE1.verizon-gni.net[130.81.17.3]
7 54 ms 54 ms 54 ms so-4-0-0-0.DFW01-BB-RTR1.verizon-gni.net [130.81.17.41]
8 54 ms 54 ms 54 ms so-1-0-0-0.DFW03-CORE-RTR1.verizon-gni.net [130.81.20.157]
9 54 ms 54 ms 54 ms po1.ctn-border1.vzlink.com [206.46.225.85]
10 53 ms 54 ms 55 ms po121.ctn-core1.vzlink.com [206.46.225.18]
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Tracing route to outgoing.verizon.net [206.46.232.12]
1 <1 ms <1 ms <1 ms 192.168.1.1
2 7 ms 7 ms 6 ms L100.PHLAPA-VFTTP-71.verizon-gni.net [96.227.51.1]
3 6 ms 7 ms 6 ms G12-1-571.PHLAPA-LCR-05.verizon-gni.net [130.81.97.88]
4 9 ms 9 ms 10 ms so-5-2-0-0.PHIL-BB-RTR1.verizon-gni.net [130.81.28.158]
5 14 ms 15 ms 14 ms so-8-0-0-0.LCC1-RES-BB-RTR1-RE1.verizon-gni.net[130.81.17.3]
6 56 ms 52 ms 54 ms so-4-0-0-0.DFW01-BB-RTR1.verizon-gni.net [130.81.17.41]
7 55 ms 55 ms 54 ms so-1-0-0-0.DFW03-CORE-RTR1.verizon-gni.net [130.81.20.157]
8 54 ms 55 ms 54 ms po1.ctn-border1.vzlink.com [206.46.225.85]
9 56 ms 54 ms 54 ms po121.ctn-core1.vzlink.com [206.46.225.18]
10 55 ms 55 ms 54 ms 206.46.228.66
11 57 ms 53 ms 55 ms outgoing.verizon.net [206.46.232.12]
PING
Reply from 206.46.232.12: bytes=32 time=55ms TTL=243
Reply from 206.46.232.12: bytes=32 time=54ms TTL=243
Reply from 206.46.232.12: bytes=32 time=53ms TTL=243
Reply from 206.46.232.12: bytes=32 time=55ms TTL=243
Ping statistics for 206.46.232.12:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 53ms, Maximum = 55ms, Average = 54ms
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The problem has been happening since last Friday to all domains I have been trying to send to.
This message came in at 6:58 am and was sent through Verizon's web site (per the request of the tech on the phone).
Return-Path: <{edited for privacy}>
Delivered-To: {edited for privacy}
Received: (qmail 18088 invoked from network); 18 Jun 2009 06:57:50 -0400
Received: from mfrt1.wave2wave.com (209.178xxx.xx)
by proartechorale.org with SMTP; 18 Jun 2009 06:57:50 -0400
Received: from mx01.wave2wave.com ([209.178.xxx.xx])
by mfrt1.wave2wave.com (IceWarp 9.4.3 (2009-05-14)) with ESMTP id ZQX76549
for <{edited for privacy}>; Thu, 18 Jun 2009 06:57:49 -0400
X-ASG-Debug-ID: 1245322647-62a701190000-BurF63
X-Barracuda-URL: http://209.178.200.37:8000/cgi-bin/mark.cgi
Received: from vms173017pub.verizon.net (localhost [127.0.0.1])
by mx01.wave2wave.com (Spam & Virus Firewall) with ESMTP id 7A6E0C6EB57
for <{edited for privacy}>; Thu, 18 Jun 2009 06:57:27 -0400 (EDT)
Received: from vms173017pub.verizon.net (vms173017pub.verizon.net [206.46.xxx.xx]) by mx01.wave2wave.com with ESMTP id L54ngmkSf3P0r3JU for <{edited for privacy}>; Thu, 18 Jun 2009 06:57:27 -0400 (EDT)
X-Barracuda-Envelope-From: {edited for privacy}
Received: from vms125.mailsrvcs.net ([192.168.1.2]) by vms173017.mailsrvcs.net
(Sun Java(tm) System Messaging Server 6.3-7.04 (built Sep 26 2008; 32bit))
with ESMTPA id <0KLE00JYJ74D7VJ0@vms173017.mailsrvcs.net> for
{edited for privacy}; Wed, 17 Jun 2009 11:57:49 -0500 (CDT)
Received: from 96.242.xx.xxx ([96.242.xx.xxx])
by vms125.mailsrvcs.net (Verizon Webmail) with HTTP; Wed,
17 Jun 2009 11:57:49 -0500 (CDT)
Date: Wed, 17 Jun 2009 11:57:49 -0500 (CDT)
From:{edited for privacy}
To: {edited for privacy}
Message-id: <1294757992.79292.1245257869158.JavaMail.root@vms125.mailsrvcs.net>
X-ASG-Orig-Subj: Test from Verizon Web
Subject: Test from Verizon Web
MIME-version: 1.0
Content-type: text/html; charset=UTF-8
Content-transfer-encoding: 7bit
X-Originating-IP: [96.242.xx.xxx]
X-Barracuda-Connect: vms173017pub.verizon.net[206.46.xxx,xx]
X-Barracuda-Start-Time: 1245322669
X-Barracuda-Bayes: INNOCENT GLOBAL 0.4014 1.0000 0.0000
X-Barracuda-Virus-Scanned: by Barracuda Spam & Virus Firewall at wave2wave.com
X-Barracuda-Spam-Score: 1.05
X-Barracuda-Spam-Status: No, SCORE=1.05 using per-user scores of TAG_LEVEL=3.9 QUARANTINE_LEVEL=4.0 KILL_LEVEL=1000.0 tests=HTML_MESSAGE, HTML_MIME_NO_HTML_TAG, MIME_HTML_ONLY, NO_REAL_NAME
X-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.2.1135
Rule breakdown below
pts rule name description
---- ---------------------- --------------------------------------------------
0.00 NO_REAL_NAME From: does not include a real name
0.00 HTML_MESSAGE BODY: HTML included in message
0.00 MIME_HTML_ONLY BODY: Message only has text/html MIME parts
1.05 HTML_MIME_NO_HTML_TAG HTML-only message, but there is no HTML tag
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Bbranco,
send this to me in a PM as it contains private info 😉