I know people have reported this, but I have tried the various suggestions, including the registry tweak and disabling Airsync, and I still get the red triangle.
This started exactly on Friday the 4th of October, and since then I have not been able to do proper email check on my Outlook. I have even deleted account and reloaded the whole account a few times as well downgrading to the latest version of 9 series.
The big problem, at least for me, is that this is my main account with a 200,000 emails and a database size of ~33Gb. Reloading this whole account takes forever (one to two days), and right after that, the red triangle shows up. It’s driving me crazy.
The issue does not seem to be Airsync-related, as it is still happening to me after disabling Airsync.
I don’t know what else to do. Has anyone had any luck with this situation?
Thanks for any suggestion!
(This happened to me only one time before, a few years ago, at which point I immediately reported it through the VIP support (this was before lifetime VIP support was canceled.) At that time, all I had to do was to downgrade to the previous working version, and wait for a newer version.)
Yesterday I thought of one more way to see if I can get a workaround for this issue. I made a new account with another alias of the same outlook account. This strategy also failed. That is one more day without proper email checking and hours wasted searching on the best emclient alternative.
I even gave another shot to my mailbird licence after a decade, but found out that it is no longer valid for their newest version and they charge annual fee for future updates, so that was another disappointment.
I turn off all my rules and enable forwarding in Outlook so all my emails go to my Yahoo address. Then after some time, EmClient starts working, and I reverse the changes, and for a while, EmClient works fine with Outlook. But then it stops again. I’m sick off constantly changing rules and turning forwarding on/off.
It is definitely an EmClient issue, not a Microsoft issue, as I have been testing mailbird, thunderbird, postbox, and of course Outlook New and Outlook Classic over the last few weeks, and none of them have any issues with outlook syncing.
But none of these five clients are a match for EmClient; they all lack a few features that makes them unusable for me. I was not able to find any other worthy client to test.
I’m so frustrated, and the AirSync registry trick is not working either. It’s not an Airsync vs. SMTP issue. It’s some other bug, and I wonder why it is so difficult to find it and fix it, given that none of these other clients have such a bug.
I moved over from Postbox. Thought this would be a seamless transition but I have spent the last 24 hours trying to get Outlook to work in eM Client without success. It makes the app experience pretty underwhelming bordering on unusable. I never had any issues in Postbox with Outlook syncing. I am surprised that at this price point such a basic functionality is not working. I probably should have checked around before buying a licence and lifetime upgrades because at the moment this app is about as useful to me as a chocolate teapot.
Postbox is as close a match as it can get to EmClient. The reason I didn’t switch to Postbox is that it doesn’t seem to have a working “folder” column. It has “account” and “location” columns, and even though “location” is intended to show the folder, it just shows the account name.
I’ve been using EmClient since 2013, and in 2014, I paid and upgraded, and up until this month, it was working really well (other than that same syncing issue that I explained in the first post, which was solved pretty quickly back then). So I really hope they can fix this quickly again. Perhaps they need to look at their builds at around that time when I told them about the syncing issue; perhaps it’s the same bug from that time that has reemerged.
It’s been a few hours, on two computers, and I haven’t seen the red triangle and any freezes so far. I hope it stays like this when I wake up tomorrow morning, knock on wood.
Assuming it holds up, tomorrow I’m gonna revert to my usual rules and turn off forwarding in Outlook and see how it goes for the rest of the day.
It seems that the email sync is now working; both of my computers were on overnight, and I don’t see any email syncing issues in the log and the red triangle doesn’t show up next to the account name.
However, calendar sync is still faulty, and I notice that Outlook events appear and disappear as EmClient keeps trying to sync the events. The red triangle indeed shows up at the top left of EmClient.
I believe they decoupled these two (email and calendar syncing) processes, that I think has been the original cause of the recent email sync failure, in 10.1.4411 so that now the calendar sync bug doesn’t affect the email sync. This also shows that the bug which seems to be related to calendar syncing has not yet been completely fixed; but I can live with that as long as my email syncing works well.
I just turned off forwarding at my outlook.com and turned on my regular rules in EmClient, and so far emails are syning and being routed to the right folders with no glitch. I’ll see how it continues throughout the day.
JK; after a couple of hours, EmClient 10.1.4411 stopped syncing Outlook emails on the computer where I enabled rules on. The other computer is still syncing. So back to rules off and forwarding Outlook to Yahoo.
But I also just noticed that there is a 10.1.4417 update posted, so now I’m gonna try that. Will update later.
Update 10.1.4417 failed upon initializing, with the red triangle appearing immediately right next to outlook account name, so the issue is definitely not fixed yet.
The other computer with rules disabled and running on 10.1.4411 is still syncing.
I made another observation; It seems that as long as my rules are disabled and forwarding is turned on in my Outlook.com email, EmClient starts syncing emails; and as soon as I turn on rules and turn off forwarding, it freezes on Outlook email sync.
Now both my computers are syncing emails fine and one is on 10.1.4417 and the other on 10.1.4411. Calendar, though, is broken on both, regardless of the status of rules and forwarding.