![]() ![]() I’m not here to blame because I have not clue which is at fault, but I’m going to guess 225 million people using Yahoo every day from all sorts of clients are doing just fine. ![]() As others have mentioned, there are plenty of other email apps that connect to Yahoo fine while eM doesn’t. Yahoo can connect with the oauth stuff, or an app password, but it doesn’t seem likely it’s their server being out of date. It’s not likely Bob the IT guy forgot to run apt-upgrade. They have 225 million users sending/receiving 26 billion messages a day. They have a massive infrastructure like anybody else. For me personally, I don’t have those turned on, it’s just my user/pass is all.īefore eM makes the random claim Yahoo’s servers are bad/old/outdated as if they had like one server somewhere on GoDaddy they forgot to update. It also says if people have an account key or use two-step, this can be an issue and might be the cause for some people. Well, we do get “Authentication failed” messages, so again eM must be using outdated security protocols. This is because those email apps use outdated security protocols and we’ve disabled access to them by default now.” It says: “If you try to use Yahoo Mail in a third-party email client using less secure sign-in technology, you might get a “Server password has changed” or an “ Authentication failed” error message. End of stack trace from previous location -Īt .SynchronizeSubfoldersAsync(IFolderSynchronizer synchronizer, Folder folder, SynchronizationPriority priority, CancellationToken cancellationToken)Īt .SynchronizeIntAsync(Boolean forced)Īt .c_Displa圜lass6_0.d.MoveNext()Īt .EnqueueGetFolderList(Folder homeFolder, Action 1 completed) at .SynchronizeSubfolders(Folder folder, SynchronizationPriority priority, Action1 completed)Īt .c_Displa圜lass0_0.b_1()Īt .InnerInvoke()Īt .c.b_277_0(Object obj)Īt (Thread threadPoolThread, ExecutionContext executionContext, ContextCallback callback, Object state)Īt .ExecuteWithThreadLocal(Task& currentTaskSlot, Thread threadPoolThread)Īt .ExecuteEntryUnsafe(Thread threadPoolThread)Īt .ExecuteFromThreadPool(Thread threadPoolThread)Īt ()Īt System.Threading._ThreadPoolWaitCallback.PerformWaitCallback() Maybe the easy way it’s just not to display the errorġ7:34:31 IMAP Synchronisation de la liste des dossiersġ7:34:40 : Failed to LIST server folders ( LIST Invalid credentials)Īt .ListFoldersAsync(IListFoldersProgress progress, Folder homeFolder, CancellationToken cancellationToken)Īt .GetFolderList(IListFoldersProgress progress, Folder homeFolder, CancellationToken cancellationToken)Īt .c_Displa圜lass14_1.b_0(WorkerStatus status, CancellationToken cancellationToken)Īt .c_Displa圜lass13_0.b_0(WorkerStatus ws, CancellationToken ct)Īt .ExecuteInternalSync(WorkerStatus status)Īt .Execute(WorkerStatus status)Īt (WorkerStatus status) I mean, despite the error log everything works fine and when I click to ignore, next time this reappears again… it’s a never ending story ! Is it possible to simply not to display or hide the error ? An option somewhere in Em Client ?
0 Comments
Leave a Reply. |