Hello,
I’m looking for a Yahoo email administrator who could contact me offlist.
I have a customer with a clean record that is getting thsi error:
Error: "421 4.7.1 [TS03] All messages from x.x.x.x permanently deferred" when sending email to Yahoo
The customer is a local non-profit and sends a very limited amount of emails to members, suppliers and other contacts. Mailing-lists are only used to contact members of the NPO.
I checked the recommendation listed at
https://help.yahoo.com/kb/postmaster/SLN3436.html
and checked his IP address on several “multi-rbl” lookup sites. All looks clean.
So I need more input to understand what we need to correct.
Thank you very much in advance.
Best regards,
Marc
http://postmaster.yahoo.com, click on "Contact Us" at the top since your question isn't one of the giant ones in the middle of the page.
Elizabeth Zwicky
Elizabeth Zwicky via NANOG <nanog@nanog.org> writes:
"permanently deferred"
Does not compute 
Bjørn
If you find one, tell them to go look up the difference between 4xx and 5xx
return codes. 
Yes this one intrigued me as well, especially as one of the suggestions provided:
https://help.yahoo.com/kb/postmaster/review-practices-senders-sln3435.html
Which states:
If your messages are being blocked, look closely at any SMTP error codes our mail servers are returning and make sure you're addressing the problem:
[…]
Retry 4xx messages - This is a temporary error. (sic)
[…]
Regards,
Marc
Today the situation cleared on it’s own as it appears. (at least I haven’t been notified of any human action)
Thanks to all those replying on and off list.
Regards,
Marc
Ancient wire-line telephone and telegraph (aka "data" in the latter days) technology, trouble ticket code "CCWT" ("Came Clear While Testing").
Wait I thought that was NTF, (No Trouble Found), as it magically cleared
up. Amazing what was/is done to avoid reporting issues/problems to the PUC
or the like.
Wait I thought that was NTF, (No Trouble Found), as it magically cleared
up. Amazing what was/is done to avoid reporting issues/problems to the
PUC or the like.
"NTF" is valid only if the reported condition was not observed by the reporter at all. "CCWT" means the reporter observed the reported condition that disappeared while inserting or removing test cords, thumping on the bay iron, or correcting an unrelated adjustment.
Couple of short war stories--we had a scandal and investigation of the proportion of tickets that were closed "NTF".
Turns out that the night equipment man, as a matter of habit, every night when he arrived for work, retrieved a piece of 2 X 4 he had hidden, and whacked the end of every lineup on his way in.
In a different office, but the same kind of problem, one day the tool crib clerk stopped me and asked about a stack of tickets in an "analysis" project she had been assigned.
All of the tickets in the stack were mine, and they all referred to equipment that day-shift patched-out and wrote up that night-shift cleared as NTF or CCWT. I had gotten tired of writing up the sad and detailed story every day and had started reporing them as "AFU"-- she wanted to know what "AFU" meant.
I told her it meant "All Fouled Up", where upon she picked up another stack, also mine, marked "NFG".
I told her those were the same at the AFU ones.
That is a really muddy statement--should have said:
"NTF" is valid only if the reported condition was not observed by the
tester at all. "CCWT" means the tester observed the reported
condition, but disappeared while inserting or removing test cords,
thumping on the bay iron, or correcting an unrelated adjustment and not as a result of a palliative action.
On 1/12/16, 7:04 PM, "NANOG on behalf of Larry Sheldon"
I told her it meant "All Fouled Up", where upon she picked up another
stack, also mine, marked "NFG".
At $DAYJOB we often ship audio/video equipment via air counter to counter
for same-day delivery.
On Southwest those deliveries are coded "Next Flight Guaranteed" and
stickered NFG.
Occasionally a client will see a highly expensive piece of gear arrive
with an NFG sticker on the case and come unglued asking why he paid tens
of thousands of dollars if we're sending him gear that is "No F*ing Good."
Hilarity ensues....
Yahoo is again "permanently" deferring mails with a persistent transient (sic) failure codes.
I followed all the instructions provided online, on and off-list.
Not sure what they expect operators to do in that case...
Regards, Marc
Yahoo and Hotmail have always caused us problems with list delivery. The issue comes and goes and nothing seems to fix it. I've _assumed_ that subscribers mark list traffic as spam instead of unsubscribing and some sort of score increases, shunting us, and then the score tapers off and delivery resumes.
In the meantime, Mailman unsubs piles of *@yahoo accounts.
Yay,
Ryan
I've seen this often on the feedback loop i get from aol,
namely their users similarly mark stuff as spam they meant to delete.
the best is when they mark the monthly mailman item as spam.
i've taken the approach of removing and blocking the user if I can
ID them, but mostly just ignoring the spam report.
much easier that way. you can't fix the users
sadly, they arrived in a broken state.
- jared