Comments on: Verizon 450 Requested mail action not taken-Try later

By: Web Spinners, LLC

Web Spinners, LLC — Sat, 12 May 2007 01:56:30 +0000

See my earlier post above about the delay. If your response to their checkback test of the email address takes longer than 15 seconds Verizon will deny your email. Too many filters will do this. It is good advice to bypass their IP range from filters and greylisting to ensure you respond “that is a valid email address…go ahead” to which they will just drop connection and accept your email then.
-Mike

By: Bob

Bob — Thu, 08 Mar 2007 16:05:21 +0000

According to McAfee:

……..
When sending email to Verizon.net addresses they attempt to validate that the Sender E-mail Address (Mail From:) is a valid mailbox before accepting the e-mail. Due to several factors the Verizon.net SMTP servers have been placed in the Reputation Database so the connections are denied. When the connection is denied the Verizon server then denies the incoming connection with SMTP Error 450 Try Again Later.
……..

Their solution is to add the addresses for the server block that performs the sender checks to the permitted sender list. They say:

……..
In order to resolve this issue you will also need to ensure that your McAfee Appliance is not blocking connections from 206.46.252.137 – 206.46.252.164. These IP addresses are used solely for the above explained process and deliver no email.
……..

I have done this and connections from those servers are now no longer being rejected and mail is being delivered to verizon.net recipients.

You watch now as they decide to change the addresses on all those servers…

By: Bob

Bob — Thu, 08 Mar 2007 15:08:21 +0000

Smith College has recently been experiencing the same issue with non delivery to verizon.net

Trying to get a meaningful dialog going with Verizon was an exercise in futility. All the support centers I spoke to ended with something along the lines of ‘We cannot help with that issue and we do not have the contact information you require.’

Prompted by Geekzero’s post I checked our McAfee appliance logs more thoroughly and found the following:

… Event=’Reputation Service triggered’, status=’Connection closed’, source=sv3pub.verizon.net(206.46.252.139) …

The appliance uses the Postini IP reputation service to block known spammer sources.

Now I have to figure a way of trusting Verizons servers enough to allow them to authenticate senders without opening the flood gates to all their spam.

I so want to just block all verizon traffic…

By: GeekZero

GeekZero — Mon, 05 Mar 2007 23:25:54 +0000

Yep that worked – I removed uceprotect from my RBL list and now Verizon mail delivers. But to work around their spam solution, I have to expose myself to more spammers.

By: GeekZero

GeekZero — Mon, 05 Mar 2007 23:15:07 +0000

Here’s an interesting kettle o’ fish. Based on the discussion here I tweaked my DNS servers and added some more SPF records, but Verizon was still cranky. Then I checked my SMTP logs, and found that the server they’re using to check whether they are receiving spam, it itself listed as a spam source! Therefore my server rejects their test (since they are blacklisted as a spammer) and they in turn fail and refuse to take my legitimate mail. Here’s the message in my log:

Sorry 206.46.252.164 is Level 1 listed at UCEPROTECT-NETWORK. See http://www.uceprotect.net/rblcheck.php?ipr=206.46.252.164

Looking there, it appears the /24 block is blacklisted due to spamtraps catching them.

So they won’t allow my legitimate mail through because they are spammers. Yikes.

I’m going to try removing uceprotect from my list of sources to check for spam and see if it goes through.

By: Kelly

Kelly — Tue, 28 Nov 2006 19:24:46 +0000

Thanks Web Spinners. I have Merak it this fixed my problem

By: Marc R

Marc R — Tue, 26 Sep 2006 16:44:02 +0000

In the case of my client it took 50 seconds to respond when I telnetted to their Domino server. I then found they had 10 blacklists defined. I took them down to 4 blacklists and there is only a 15 second delay now. They are now able to send to Verizon.

By: Tom F

Tom F — Fri, 01 Sep 2006 14:57:02 +0000

Hi all, I use Merak Mail and had this same issue. I found that my smtp delay was at 10, and was still too long for Verizon. I dropped down to 3 and that seems to help. I also bypassed verizon.net in the ‘Deny SMTP VRFY’ bypass file. Now I see what looks like greylisting errors, instead of the endless 450 errors. And the mail eventually looks like it goes. Hope it helps you.

By: Matt S.

Matt S. — Wed, 19 Jul 2006 05:57:59 +0000

Followup: I added an SPF record to my zone file and Verizon is still rejecting my mail. Hmm.

By: Matt S.

Matt S. — Wed, 28 Jun 2006 00:00:16 +0000

THANK YOU for taking the time to post –OP and all you other folks too. I feel like I have a fighting chance at getting mail from my server through to Verizon now.