Yahoo! Mail Problems (and CRM Workflow) Worsen

Sometime over the past couple of years, I sought out Yahoo's customer service for premium mail users.  The problem at that time was an annoying false positive from the Norton AV scanner Yahoo was using.  It got me nowhere.  Because of that experience, I avoided contacting Yahoo service for ongoing problems with mail search.  But this week I decided I needed help, as I was unable to sort through the mail volume that had accumulated without using the search / filtering facility. 


This time, there seemed to be better, more courteous staffing in greater numbers.  As for effectiveness -- well, read on.


As the screenshot shows, the mail service would throw an error when asked to return more than headers for a sizeable search result (say, a few thousand emails). I'm now on the seventh contact with the Yahoo Mail help crew.  It seems that level 1 support has been given one tweak they are permitted to try before escalating.  For 2-3 of the calls, that's pretty much what was attempted, to no avail.  Once it was escalated to "Engineering," the problem seemed to get worse, not better.  After contacting Level 1 support again, as of this afternoon, I was told to try again in 24-48 hours (but only I had received a "We fixed it" message from Engineering). 


I'll be back on the chat line as suggested, but I thought I'd mention this error in case others have run into it.  There are some variations, but the symptom is either that the search fails, or that the result set will not fully load;  all the emails must be "retrieved" before one can, for example, move them to a folder. 


I'll update this post once it's resolved.


Error #5:
Method: SearchMessages
FAULT: SOAP-ENV:Server.MailboxOpenFailed.Busy
DESC: Error opening mailbox: mailbox busy
VER: 2.10.0 Build:374.4 04/28/2010 02:05 AM
HOST: cg1.c902.mail.ac4.yahoo.com
CBK: Converting circular structure to JSON
REQ: {

Update ~ noon eastern 30 May 2010:  Same CBK error, but now Error #20.  I.e., still not working. 


Update ~ 8 July 2010.  Still not working.  There have been more than 15 contacts with Customer Service and/or Engineering, including three purported Engineering escalations.