Yahoo breaks IMAP (was: Error Synchronizing Mail: Network Error)

[JHW]

It appears the difference between what you did and I what I did was that I reinstalled my old K-Mail email program...  I am not familiar with "web mail" but I suggest installing K9-Mail to download all your emails... and try then try Aquamail again. 

As I recall, I had Aquamail active while I was downloading from K9-Mail....  I am not a software geek, but K9-Mail may have supplied the missing but required "deficiency" in Aquamail.

JWegge

[JHW]

And as an addendum.... I my email account is imap...  JWegge

[mikeone]

And as an addendum.... I my email account is imap...  JWegge

Thanks.

Just a note:
You have the opportunity to modify  your posts by using the small button "Modify" in the header (upper right corner) of your own posts.
> see screenshot

[Kostya Vasilyev]

Yes, it's on Yahoo's side, and it needs to be fixed there.

It's so nice of Yahoo to not provide any support, only a "community forum where you questions will be answered by other users like you" (maybe I should stop support too... oh wait, I guess only multibillion corporations with celebrity CEOs can do that...?)

Please see below:

http://www.aqua-mail.com/?p=1981

Apple Mail is also affected, looks like same issue (look at the number of posts and their times / dates):

https://answers.yahoo.com/question/index?qid=20150114021156AA4PjIX

There is no "deficiency" here -- the IMAP command used in Aqua is perfectly valid, has worked with Yahoo from 2010 (!!!) until now, and continues to work with all other IMAP mail services known to man or woman.

I have not had a single report of this issue until yesterday when I got 4 or 5 messages, and about a dozen today. Yahoo must be doing a "staged" (gradual) update.

As for K9 -- IMAP is a rich protocol, and has many command and many ways to use them.

If it so happens that K9 doesn't use the command that Yahoo broke -- well, good for them -- but there is no guarantee that Yahoo (or some other mail service) won't break something used by K9, Kaiten, Boxer, or any other mail app, mobile or desktop. And then the tables will turn.

And to reiterate -- Apple Mail is also affected, apparently they are using same IMAP command to ask the server for the list of unread messages in a folder.

---

Now that being said, I made this test build where I replaced one perfectly valid IMAP command with another perfectly valid IMAP command. Maybe Yahoo's server will be able to process that other one?

http://www.aqua-mail.com/download/AquaMail-market-1.5.1.12.10.apk

You can update in-place without a full reinstall.

Update: does not help, details below, two messages down.

Another update (January 15): looks like Yahoo has recognized the issue and started to implement a fix. Fingers crossed

[pects99]

Tried the new apk download above. Didnt work. Said Invalid server response. Can i uninstall that apk i just downlowded?

[ABOSWORTH]

I kind of figured it was a yahoo thing since it just randomly stopped working and my other two accounts (work and gmail) are still working perfectly. I too have tried deleting and re-adding the account and even tried uninstalling and installing aquamail again. I tried the apk download and that didn't work for me either. I appreciate you spending time on this when it is clearly a yahoo problem and not a problem with the app. Support for this app is amazing. I'm sure yahoo will get this sorted eventually.

So you think it's fine to leave the apk that I downloaded from above? I'm not sure how I'd go about uninstalling it anyway. I've deleted it from the downloads folder. 

[Yaateeh]

Thank you for the support. I just tried the new apk file. Still getting an error message but now it is an invalid server response error message

[Kostya Vasilyev]

Yes, I changed the wording in the error message on my side.

Other than that, it must mean that the issue is not in Yahoo's IMAP command parser (where it would be particular about the syntax) but rather is in the message store back-end (which has to come up with the requested data).

Oh well, I tried.

For those wishing to go back to "official" Google Play version (although it should not be necessary), here it is:

http://www.aqua-mail.com/download/AquaMail-market-1.5.1.12.apk

A temporary workaround is to use POP3, for this you'll need to add the same account into Aqua again, choosing Manual setup (after entering email / password) and changing IMAP to POP3 near the top of the next screen.

[ABOSWORTH]

My yahoo account has started working again. Note that I'm using the apk that Kostya posted a few posts ago, not the play store version. I'm guessing it doesn't make a difference at this point so I'll stick with this one. Thanks a lot, for the support, Kostya.

[Kostya Vasilyev]

Yep, there is no difference with this issue as far as my code goes (Play version vs. attempted fix), although there are a few accumulated bug fixes / changes since the release.

As far as Yahoo goes, I'm starting to see reports of "started working" on the Apple Mail thread in Yahoo Communities.

So they (Yahoo) must have noticed and started to implement a fix.

[ABOSWORTH]

Well, now it's back down again. Lol. Yahoo is all messed up right now.

[pects99]

On my end everything works now.  Thanks for the quick replies. Ill never leave Aquamail. Keep up the good work.

[Kostya Vasilyev]

I'm getting mixed reports today.

A few users reported that it's working again, and a few emails from others about how it's broken.

Maybe Yahoo needs to do something on a case by case basis to fix the affected accounts -- while the staged deployment that produces the bug continues to roll forward. That would be the worst, hope it's not like that.

For anyone still seeing this, I encourage to "register" your issue on this Apple Mail thread, which has a Yahoo employee or two there.

https://answers.yahoo.com/question/index?qid=20150114021156AA4PjIX

[npaillat]

It's back to normal since this am. Don't know what happened, but I'm glad it's working.

Nicolas

[godd]

Yahoo came back to business this morning but as of 4.30 PM EST it stopped working again with the same error