Problem Sending eMail through Outlook - all messages delayed in Verizon POP-3 Account!

[#1]

So here is my question – why hasn’t there been a greater outcry?

Forgive my ignorance of the technology, but how does this all work?

Everyone who is using Outlook puts their POP-3 settings into the application. For the outgoing server, we all point to “outgoing.verizon.net.”

I am assuming that this is not one super-gigantic e-mail server that handles all of the e-mails sent out from the entire Verizon community, correct? If it were, there would be a story on CNBC and FBN about how Verizon customers were all flooding in to complain about their e-mails being delayed.

So I assume that Verizon owns multiple servers and the one that I (and others who posted on this thread) am assigned to has some sort of problem that is causing the e-mails to be delayed. Is that a safe assumption?

So, if this is the case, then isn’t it a matter of moving/assigning the existing users to a more problem-free server, and then bringing down the problem server and troubleshooting it?

Or am I oversimplifying the problem?

Here’s my status: I switched over to Verizon from Comcast on Monday. Thank God I left my Comcast account active because I have sent about 60-70 e-mails from my new Verizon account, and about 5 of them actually arrived at their destination immediately. All of the others were delayed anywhere from 5 minutes to 15 hours (I kid you not). So, the blazing fast FiOS connection – for e-mail … not so much.

If this is not resolved soon, I’ll have no other recourse than to switch back to Comcast.

Will setting up a Gmail account solve this problem?

[#2]

This email delivery delay is insane! I just spoke with customer support, the rep said they've identified the problem and that it's been an issue for a couple weeks now, but they have no idea when it will be fixed. I pay an arm and a leg for FIOS as it is, that kind of response is unacceptable. I can't believe I'm saying this, but I am returning to Com{please keep your posts courteous}. As much as I hate them, email delay was NEVER an issue and they are cheaper. 

As a contractor, I depend on email reliability. This has cost me BIG TIME in terms of my clients this week. But I'm sure as a corporate giant, Verizon couldn't care less.

Message Edited by KaLin on 06-18-2009 03:49 PM

[#3]

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

[#4]

Timo888,

Keeping everything in one thread will help me help you faster post in your first thread

[#5]

In response to:

"I am assuming that this is not one super-gigantic e-mail server that handles all of the e-mails sent out from the entire Verizon community, correct? If it were, there would be a story on CNBC and FBN about how Verizon customers were all flooding in to complain about their e-mails being delayed."

Actually, it is a pretty significant problem. The reason why it hasn't gotten attention is because customers are slowly finding out the hard way. It looks to me like Verizon bit off more than it could chew in bandwidth due to their aggressive marketing of FIOS. The delays are random. If it was a situation of a plain old outage, everyone would be talking.

In this case it's a matter of the press needing to be notified- which is what I do for a living. Of course, I'll have to actually call Telephony, Telecommunications Magazine, America's Network, The Wall Street Journal, etc. because who knows if the reporters would actually get my emails...!

Comcast's PR department is going to have a field day with this, considering they were getting clobbered by Verizon in terms of publicity for the last year.

[#6]

Sounds like the right approach to me...

I had a tech call me on Tuesday at 12:30 pm - told him the problems said give it a day and would call me back on Wedneday around the same time - guess what?  No call from them...

[#7]

---

@BostonDelayed wrote:

In response to:

"I am assuming that this is not one super-gigantic e-mail server that handles all of the e-mails sent out from the entire Verizon community, correct? If it were, there would be a story on CNBC and FBN about how Verizon customers were all flooding in to complain about their e-mails being delayed."

Actually, it is a pretty significant problem. The reason why it hasn't gotten attention is because customers are slowly finding out the hard way. It looks to me like Verizon bit off more than it could chew in bandwidth due to their aggressive marketing of FIOS. The delays are random. If it was a situation of a plain old outage, everyone would be talking.

In this case it's a matter of the press needing to be notified- which is what I do for a living. Of course, I'll have to actually call Telephony, Telecommunications Magazine, America's Network, The Wall Street Journal, etc. because who knows if the reporters would actually get my emails...!

Comcast's PR department is going to have a field day with this, considering they were getting clobbered by Verizon in terms of publicity for the last year.

---

Perhaps it's a denial of service attack from comcast to Verizon's mail servers. Just kidding. I am sure that it is being fixed but I agree it should not take this long. There have been a few people that have provided the information requested, I myself as one. My email has been 99.9% reliable for the last six plus years with Verizon. Yesterday I started having the same issue and sent information in a private Email showing a 10 hour delay and the route the mail took. So it should be fixed soon, if not already.

[#8]

When I first saw this forum thread, I had hoped that since this had been going on a while, it'd be fixed quickly. But today's calls with tech support sent that confidence down the drain. And I quote, "Apparently this has been going on for a couple of weeks and they figured out the problem. But right now they have no idea when it will be fixed. I really can't give you an estimate, except that they are working on it."

I nearly dropped the phone. I'm a consultant who's emails go through Verizon. I had no clue anything was wrong until I was informed on Wednesday that I missed a Monday deadline. Turned out my email I sent at 12:20 p.m. this past Monday arrived about 11:30 a.m. WEDNESDAY!

Then I had a call yesterday where my client said, "Please send me an email with the follow-up items after our call." I did.

FOUR HOURS LATER I get an email, "We're waiting on you, please send the list ASAP..."

I had to create a Gmail account to send everything, which made me look unprofessional.

I've been a FIOS subscriber for several years. All of my services are under Verizon. I'm really disgusted that they weren't proactive in notifying us of a very serious problem that's been going on for two weeks. Instead, they just figured if they ignored it, maybe it wouldn't turn into an issue.

[#9]

I signed up for this service... it seems to be working fine - but now I am sending a copy of every email to me so I can make sure it goes out and comes in.

http://www.authsmtp.com/?gclid=CKHkiKyNlZsCFeFM5QodXEZupg

[#10]

Thank you for sharing that! It looks like the bandaid we all need for now.

I think Verizon should provide this to all of the affected customers. It would be cheaper than the financial losses that will result in all of us switching to Comcast.