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...
Yahoo seems to be having some massive system issues the last 24 hours or so. DNS has been down, mail was down. I’m seeing reports things are coming back now, but there’s a lot of backed up mail traffic and the congestion may take a few hours to resolve. If you have the ability to do traffic shaping on the sending end, now would be a good time to be extra conservative in your sending...
There was confirmation this week that the increase in “user unknown” messages from Yahoo is actually Yahoo cleaning out abandoned accounts. At the same time a Yahoo is sending out notifications to folks to log into mail. The first thing every sender should do is remove all these Yahoo addresses from their lists. They’re done, kaput. Gone. There are some other things worth doing...
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. AOL migrated the last few users onto...
RSS - Posts