False 550 responses from Verizon

This week there was a reported uptick in user unknown responses for verizon email addresses. The specific response folks were seeing was:

554 delivery error: dd xx@verizon.net is no longer valid. [-20] -mta4047.aol.mail.bf1.yahoo.com

This appears to be a problem with their require-recipient-valid-since header checking. They are aware and are working on a fix.

What this means for senders is if you’re seeing Verizon addresses hard bounce, then you shouldn’t necessarily drop them from your list. They are likely still valid. You can continue to retry mail to those addresses. This does seem to have just affected the verizon.net addresses, not other addresses across the properties.

Related Posts

Yahoo and Verizon

Mickey at Spamtacular has information about Verizon’s email system that will have relevance for anyone working in delivery.

Read More

Email news today

Ironport have rolled out an update to their rule engine which has a bug causing mail problems. According to discussion on the mailop list, the new rule engine is folding the header with a line feed (LF) rather than a carriage return (CRLF). This is breaking things, including DKIM signatures. Ironport is aware of the issue. I expect an updated rollout shortly.

Read More

Changes coming to Verizon email

Last year Verizon bought AOL. As part of that merger some @verizon.net email is being migrated to the AOL backend. FAQs published by Verizon say this change is only affecting users in FL, TX and CA. Users will still have @verizon.net addresses but the backend and filtering will be managed by AOL.
This shouldn’t have a huge impact on commercial senders. However, one thing I did notice while reading through the FAQ is this:

Read More