Email to Verizon.net customers delayed

[TiggerTina]

We own a mail service for several hundred clients and for the past 2 weeks have seen emails to verizon.net customers sporadically fail with the following message:  601 Attempted to send the message to the following ip's: 206.46.232.11

Our mail server attempts to send at regular intervals for up to 24 hours and eventually it will go, but I can see many verizon.net intended emails pile up in our queue for a time, and then it will be fine again for a few hours.

Has there been a recent issue with the verizon.net server?  It is causing delays to verizon.net email customers.

It has only just started occurring over the past 2 weeks.  Our server has proper RDNS and DNS records and is not blacklisted.

Any insight would be appreciated so we can convey to our clients as well as Verizon customers as to what is causing this delay.

Thanks

{edited for privacy}

[mmeisler]

I am a Verizon customer who has been complaining about this for almost 2 weeks!  Verizon denies there is any problem and tells me there server is fine and everyone else's servers are delaying things!  I get emails anywhere from a few minutes to a few days after they are sent.  Can't say that there aren't some that I haven't received because, well, don't know.  I even received a Verizon corporate e-mail that took 9 minutes. Verizon's rep said that doesn't prove anything because e-mails from other senders are also delayed.  I didn't even know how to respond to that.  Wish I had more information but I am glad someone else is noticing the problem now.

[osd]

Yes. I can see email from outside is getting delayed for hours sometimes, and I don't know how much is getting lost or returned. Today is the first day I noticed this, though I could go back and check raw source to estimate actual delays.

Trying email from MIT and from Outlook directly to verizon.net accounts and they are not getting received by the Verizon customers (verizon.net).

[YankeeDoodle1]

I also have experienced delays for the past couple of weeks.  Some emails come in timely but the problem appears to have gotten worse.  Can be anywhere from 1 hour delay to 12 hour delay.  Involves many different senders.  Should be a way to review the email path to see where the hold up is.

[mmeisler]

I guess if nothing else, the fact that other people are claiming to have the same problem might get Verizon's attention to acknowledge this. Even emails that are coming from Verizon corporate (e.g. ads) are being delayed!

[TiggerTina]

Yesterday just sent an email from my work to my Verizon account and it was delayed by 1 hour.  The next message I sent I actually got an NDR saying the account was temporarily disabled - YET - I was logged into the webmail and sent an email out!

Later in the night I was unable to log into my webmail on Verizon as it told me my username did not exist.  Went through the whole recovery for UserID and it told me exactly what my UserID was that says does not exist.  An hour later I was able to log in again.

CRAZY stuff here!

As we speak, I just sent another email from my work to my personal and going on 15 mins and I have not received it in my Verizon box.  

Mail server queue reports this:

601 Attempted to send the message to the following ip's: 206.46.232.11

What is going on!!

[TiggerTina]

Maybe this will help - got a new message as my email sits in queue trying to send to my Verizon.net account:

450 4.3.0 Spam filter message initialization failure [slot 1 name 1]

I have not seen that one before!

[FWEhr]

Having very similar problems for at least last 2 months, and wish that Verizon would step up and (1) acknowledge it and (2) work to troubleshoot & fix.

For a while we thought it was just one sender, but not so. Using Thunderbird as client. Most recent download of messages about 0900 EST today 2Dec14. Previous download around 1630 1Dec14. Sigh, Verizon's website deleted most of my post. Screenshot of Thunderbird inbox, gold starred messages are New. Multiple delayed messages, pointing finger at Verizon rather than any one server.

Headers from one of these messages:

From - Tue Dec 02 08:44:58 2014
X-Account-Key: account2
X-UIDL: 25621-1264173357
X-Mozilla-Status: 0000
X-Mozilla-Status2: 00000000
X-Mozilla-Keys: $label3                                                                         
Return-path:
 <bounce-224254_HTML-632608994-4293017-1314031-136@bounce.e.wgbh.org>
Received: from mta.e.wgbh.org ([68.232.206.201]) by vms172051.mailsrvcs.net
 (Oracle Communications Messaging Server 7.0.5.34.0 64bit (built Oct 14 2014))
 with ESMTP id <0NFX004Z1UR3JTK0@vms172051.mailsrvcs.net> for
 rap.tors@verizon.net; Mon, 01 Dec 2014 22:50:03 -0600 (CST)
Received: by mta.e.wgbh.org id hfl2eu163hsg for <rap.tors@verizon.net>; Mon,
 1 Dec 2014 06:21:54 -0600
 (envelope-from <bounce-224254_HTML-632608994-4293017-1314031-136@bounce.e.wgbh.org>)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; s=200608; d=e.wgbh.org;
 h=From:To:Subject:Date:List-Unsubscribe:MIME-Version:Reply-To:Message-ID:Content-Type;
 i=info@e.wgbh.org; bh=fsKLcDWYCcaeSk65gHm7Bt75QLE=;
 b=P3pE69hKI3uiqCt+hgE9wANbvX97VWww1MddDSEosYjx16ToL+LD9BbZ9mVYzfoDqVQ6o9qjGvbh
   4zYvnv3tuBykioOWR0NOvl0HC51kIPjIt0ITEtuHhnDCe44IIZHc+VYN/PSpsfvKEVBEQ7FxwYqA
   3menZgtC9KcXL6gkIwg=
Date: Mon, 01 Dec 2014 06:21:53 -0600
From: "WGBH" <info@e.wgbh.org>
Subject: Tomorrow Is #GivingTuesday
X-Originating-IP: [68.232.206.201]
To: {edited for privacy}
Reply-to: "WGBH"
 <reply-fe9510727c67047c72-224254_HTML-632608994-1314031-136@e.wgbh.org>
Message-id: <0b34b4b8-7955-4c7f-a30e-2f4f03a241a6@xtnvmta1201.xt.local>
MIME-version: 1.0
Content-type: multipart/alternative;
 boundary="Boundary_(ID_Xp9+c2Jw/0C/RPbJMwsIGw)"
X-CMAE-Score: 0
X-CMAE-Analysis: v=2.1 cv=XoZN4uB4 c=1 sm=1 tr=0 b=1
    a=pCuGTe9LiHLaBZG+AjPkvg==:117 a=pCuGTe9LiHLaBZG+AjPkvg==:17    a=iX_q9hrvAAAA:8
 a=oR5dmqMzAAAA:8 a=-9mUelKeXuEA:10 a=A92cGCtB03wA:10    a=r77TgQKjGQsHNAKrUKIA:9
 a=9iDbn-4jx3cA:10 a=cKsnjEOsciEA:10    a=gZbpxnkM3yUA:10 a=o1OHuDzbAAAA:8
 a=0rCVaXwTAAAA:8    a=OFsTZ617XCmX352dNZQA:9 a=gEmjcRPp8LnY5E6_:21
 a=ikIB_WheD6GqgpRl:21    a=CjuIK1q_8ugA:10 a=bGZOQ3IfqlAA:10 a=baurAh5I0lsA:10
 a=BbFPUVBDDWAA:10    a=Ay_1P_Xr-EEA:10 a=GAn-aSadAAAA:8 a=SSmOFEACAAAA:8
    a=unaPqI2LCttBOhjee68A:9 a=69lzMqBAfJK2apu6:21 a=WT2pjjSPw7p8AjCC:21
    a=vbotpX_3p6LZUENe:21 a=_W_S_7VecoQA:10 a=_MMahgqCxqMA:10 a=p403mkujtbAA:10
x-job: 1314031_4293017
List-Unsubscribe:
 <mailto:leave-fcb81672716601791a4c342838-fe201273776204757c1d74-fe9510727c67047c72-fea215737460047e74-ff65157373@leave.s4.exacttarget.com>
Original-recipient: rfc822;{edited for privacy}
X-Antispam: clean, score=1
X-Antivirus: avast! (VPS 141202-0, 12/02/2014), Inbound message
X-Antivirus-Status: Clean

This is a multi-part message in MIME format.

--Boundary_(ID_Xp9+c2Jw/0C/RPbJMwsIGw)
Content-type: text/plain; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT

[TiggerTina]

This was not received until 9:52AM in my Verizon webmail!!

Here is the header for the email I sent at 8:56am from my work to my Verizon.net account and was received at Dec 2 09:52 AM  in my Verizon inbox in webmail:

Return-path: <XXX.com>

Received: from mail.270net.com ([216.127.146.226]) by vms172085.mailsrvcs.net

 (Oracle Communications Messaging Server 7.0.5.34.0 64bit (built Oct 14 2014))

 with ESMTP id <0NFY003H2MN53O00@vms172085.mailsrvcs.net> for

 XXXX@verizon.net; Tue, 02 Dec 2014 08:52:38 -0600 (CST)

Received: from DC-HQ.270net.local

 ({edited for privacy})

 by mail.270net.com with SMTP; Tue, 2 Dec 2014 08:56:36 -0500

Received: from DC-HQ.270net.local ([fe80::c108:c74a:38d0:89b8])

 by DC-HQ.270net.local ([fe80::c108:c74a:38d0:89b8%10]) with mapi; Tue,

 2 Dec 2014 08:56:04 -0500

Date: Tue, 02 Dec 2014 08:56:03 -0500

From: TinaXXX <XXX.com>

Subject: testing Incoming Verizon

X-Originating-IP: {edited for privacy}

To: "XXX@verizon.net" <XXX@verizon.net>

Message-id: <F1926AFCDE1E0840A67D92838835595074E8C0EF5E@DC-HQ.270net.local>

MIME-version: 1.0

Content-type: multipart/alternative;

 boundary="Boundary_(ID_grlnZBewsRMgxhlyBRGXTQ)"

Content-language: en-US

Accept-Language: en-US

Thread-topic: testing Incoming Verizon

Thread-index: AdAON7Xt6XQjAYYIRUy89kefGXYJsQ==

acceptlanguage: en-US

X-CMAE-Score: 0

X-CMAE-Analysis: v=2.1 cv=UtfU7F0E c=1 sm=1 tr=0      a=+lkUUNZnMbWSlrX+JrROXA==:117

 a=+lkUUNZnMbWSlrX+JrROXA==:17        a=xqWC_Br6kY4A:10 a=iwq3sYZAAAAA:8

 a=oR5dmqMzAAAA:8 a=tS228Fp5AAAA:8           a=-9mUelKeXuEA:10 a=A92cGCtB03wA:10

 a=JFBUtCveDJy_5HfuRgUA:9          a=CjuIK1q_8ugA:10 a=zJr0y-yyQYEA:10 a=Ru4uOsth9cEA:10

 a=5_sWFbAxKMcA:10         a=eo_cv28HwyYA:10 a=Ka3ohaIofhwA:10 a=y3GBW9SuemYA:10

 a=hUg8QywxBK4A:10         a=yMhMjlubAAAA:8 a=SSmOFEACAAAA:8 a=rr1us6ov17SjhSd0aqIA:9

            a=g4WzspQrzpw1ENRa:21 a=gKO2Hq4RSVkA:10 a=UiCQ7L4-1S4A:10 a=hTZeC7Yk6K0A:10

            a=frz4AuCg-hUA:10 a=h_njdGdCWi8A:10

X-MS-Has-Attach:

X-MS-TNEF-Correlator:

X-Declude-Sender: XXX@270net.com {edited for privacy}

X-Declude-Spoolname: 1544364539467.eml

X-Declude-RefID:

X-Declude-Note: Scanned by Declude 4.12.05 

X-Declude-Scan: Outgoing Score [0] at 08:56:38 on 02 Dec 2014

X-Declude-Tests: Whitelisted

X-Country-Chain:

X-Declude-Code: 0

X-HELO: DC-HQ.270net.local

X-Identity: {edited for privacy} |  | verizon.net

Original-recipient: rfc822;XXX1@verizon.net

This was not received until 9:52AM in my Verizon webmail!!

[mmeisler]

On the phone with Verizon right now.  They insist it is not there problem.  They claim "email is not instant".  Not sure where to go with this now.