“…another reboot of your computer after applying the interim fix. So first redo the SMTP workaround 1 interim fix again step by step, and at the end “reboot your computer”. Then try again to see if you can receive mail.”
OK… did this. It did not ask me for a password. Just asked me to allow EmClient to access Outlook. I clicked yes.
“…may now need to have a “generated app password” for your mailbox Outlook account login (to receive mail) as some other users found due to some possible eg: Microsoft online account changes.”
“…go into your Outlook account online and try generating an app password and then close and reopen eM Client and enter the generated app password.”
I can’t find where/how to generate an “app password”. I am ending up at the place that would allow me to change my outlook password.
I can’t find where/how to generate an “app password”. I am ending up at the place that would allow me to change my outlook password.
Go to your Microsoft Security page and click “Advanced Security Options” section. Then you normally need to turn on “Two Step Verification” which eM Client supports.
You should then see the App passwords (below that) section to create an app password. See example screenshot below from my Outlook live.com account.
Yes… that is what I thought… I was trying to avoid “Two Step Verification”… another phobia
I think I will go for “remove and re-add your Outlook account”. Will that allow me to avoid two step verification? Will I have to run the original fix again?
I think I will go for “remove and re-add your Outlook account”. Will that allow me to avoid two step verification? Will I have to run the original fix again?
Yes try just removing and re-adding your account.
You normally don’t need two step enabled to work in eM Client. It’s just an extra security option that then also allows you to then have an app password as well if you want which I use and as I said eM Client also does support 2FA with no issues. I’ve been using 2FA for years with both Microsoft and Google accounts in eM Client.
The only thing you can do then is alternatively setup your Microsoft account in eM Client as an Exchange account in the meantime or you can leave it that way permanently.
Some users including myself have done that and it works fine too. The only difference is that your email is delayed receiving from Microsoft for up to a minute but otherwise is the same.
Tried both (two-step and re-adding) solutions… neither ended well…
With two-step, I got the app password… but I never got to the point of being able to enter the app password. During the process Microsoft sent me a security code… but the code would not process… the dialog box just spun and spun…
So I turned off two-step and tried re-adding the account.
“The only thing you can do then is alternatively setup your Microsoft account in eM Client as an Exchange account in the meantime or you can leave it that way permanently.”
Is an Exchange account free? I don’t believe I have one…
Is an Exchange account free? I don’t believe I have one.
Yes the Exchange setup is free and is just merely a way to configure your exiting Personal or Business Outlook account in eM Client and you don’t pay for the configuration / setup in a mail client.
Seems to be working. Sending and receiving… but yes with some odd delay. The delay is no problem.
Great news the Exchange setup worked for you. It’s normal up to a minute delay with that setup, but I too can live with that. That’s just the way Exchange receiving works from the Microsoft end.
Note: With the Exchange setup you may see extra Microsoft Acct Calendar boxes checked in the eM Client Calendar view, so just uncheck what you don’t need or don’t use in there.
“Note: With the Exchange setup you may see extra Microsoft Acct Calendar boxes checked in the eM Client Calendar view, so just uncheck what you don’t need or don’t use in there.”
My issue is on W10 too not being able to send. I applied the registry fixes from Gary.
Worked for a few days and then started to get server errors again.
So thought MS had fixed the issue and ran the reverse Registry fix.
Now I can’t send again and all my replies are being dumped in the local folders outbox.
This is infuriating in the extreme.
So I am going to try and apply the reg fix again, but this is totally ridiculous having to go back and forwards like this and finding out emails have not been sent is the last straw.
Microsoft say email client providers have had enough time to implement appropriate secure measures when Basic Authentication is deprecated as detailed here:
So why is eMclient still not working properly?
So I’ve reapplied the registry ‘Fix’ again and deleted the Outlook accounts and now set them up as exchange accounts and so far my emails are now sending…
I eventually got my hotmail.com working by uninstalling EMC V9, and installing V8. I could then send and receive, and the tick box to ‘save sent mails etc’ magically reappeared, so I could get rid of having to delete duplicate sent emails - the down side being the nag screen from EMC trying to force me to update up to V9.
On my wife’s windows account on the same machine she uses EMC to outlook.com, and that needed some fiddling with, as it saw the data files had been used by the newer version. I got EMC sorted for her account but now she couldn’t send emails.
So I’ve spent ages going back and forth trying every combination of adding and deleting accounts, manual setups, versions, registry fixes, and settings till I’m blue in the face. If I get my EMC working, my wife’s won’t, and vice versa (we both have GMail accounts by the way, and they continue to work fine).
Meanwhile another email client on the machine works perfectly for both of us (thankfully IMAP means we don’t lose our folder structures), which leads me to the conclusion that EMC > Microsoft remains broken.
I really do like EMC, but this is so unnecessary, and I can’t carry on with it being in limbo when another client works fine.
I hear you and it is really frustrating. Since the end of January this battle with EMC & Outlook has been a struggle for sure. We all depend on our email these days and when it is lost the problems created are a setback for sure. I really love the EMC platform and for the most part the guys that monitor the forum (Gary, Cyberzork, Skybat,etc) do their very best to keep the user happy by offering suggestions and tips on how to fix the minor issues . This deal with MS is not a minor issue and I still beleive that it is an EMC problem. The fact that we the user are having to install registry fixes etc is not fair to the user. We are not IT personnel and when I read some of the details from users to create a fix I have no idea what the hell they are talking about. I am an 81 year old senior and I feel pretty good when I can turn the computer on and send an email to my family & friends. I however am not comfortable making changes to the registry or facilitating any of the suggestions offered by ther many users out there trying desparately to return their client back to health.
The fact that the Support Team at EMC sat back and did nothing but send out a registry fix was very disappointing and the fact that they left the fix up to the user was a major disappointment. Friends of mine use Thunderbird and Mozzilla sent out a patch that the users ran and the problem was fixed. This is what EMC should have done. Like I said I love the platform and it is a great email client however the Support Team at EMC is very lax and places way too much responsibility on the end user. When this problem hit there should have been a post from EMC explaining the situation and providing some detail as to what was being done in the background. Instead there were hundreds of posts in about 50 different locations in the forum asking for help. My email which was working fine on my Ipad was ringing constantly for three days with a lot of angry users or users that were computer savey offering suggestions for a temporary fix. This was totally unecessary and the lack of support from EMC has to accept the fact that they dropped the ball badly in this situation.
Like I said the guys I mentioned earlier do a wonderful job and everytime I asked for some assistance they were always there to help me through my problem. I cannot say enough about their contributions. However this is all about the developers and the main support team that dropped the ball here. There were a lot of very unhappy users and I am sure that they have now moved on to another client due to the manner in which this was handled. Hopefully a lesson was learned here.
Good luck with your new client choice and I understand your frustration!
This problem is with the Microsoft server. Your email provider broke their implementation of oAuth, so all applications using modern oAuth are affected by this, not just eM Client.
Your email provider needs to fix this. We would if we could, but there is nothing wrong with eM Client, so nothing to fix or patch, and we are not Microsoft and so don’t have access to their server to fix what they broke.
Best solution is to apply the workaround to your OS that we provided shortly after the issue with your email provider was discovered, so that you can send until your provider fixes their problem.
I believe what BobF, Ricky2 and many other EMC users are trying to say is that we understand that you stated this problem was caused by Microsoft many times in many discussions.
But, other email client apps realized that this problem affected many of their users and took the position to fix the problem on their end, even if they didn’t cause it, and make life easier for their users. So, other email client apps did correct the situation for their users by making ONE application patch that installed easily and resolved the problem for all their users. Instead of doing that, EMC is taking the position that EMC did not create the problem, so EMC is asking THOUSANDS of EMC users to fix the situation themselves with the help of an EMC registry workaround.
Customer service is the primary focus here. As a vendor, what can EMC do to help its customers so they can save time, money and energy? It seems like EMC is very frustrated by Microsoft and taking a defensive stand, and thus causing many EMC users to be very frustrated with EMC.
I believe EMC is a good email client app and it is apparent many EMC users feel the same way. However, as seen by so many topics and posts about this SMTP problem, many EMC users are screaming for better help and assistance from EMC. So, this has to be telling you something.
EMC is taking the position that EMC did not create the problem, so EMC is asking THOUSANDS of EMC users to fix the situation themselves with the help of an EMC registry workaround.
eM Client (did not) create this issue as @Gary advised This issue was caused by Microsoft and not eM Client. eM Client was using the new “Modern OAuth” with the automatic email IMAP wizard setup and (was working perfectly with the Microsoft servers for many months) where then all of a sudden something changed at the Microsoft end this year that caused this SMTP issue.
This same thing happened a few years ago as @Gary already advised with Microsoft and their OAuth changes which again at that time, eM Client had to do a temporary work around till Microsoft fixed their issue which took time.
At that time previously, @Gary provided users options to setup eM Client Manually which worked fine at that time (without an OAuth token) via the normal username and password and manually specifying the IMAP & SMTP mail servers.
However with the latest Microsoft Modern OAuth verification issue, (you cannot just connect via just a normal standard username and password anymore) like when this happened previously due to Microsoft changes in December 2022, and you have to now (in the interim) use the original / older OAuth token method till the new Microsoft Modern OAuth problem is fixed.
So the only way you are going to get this issue fixed for now to keep using eM Client like other users have had to do including myself is either one of the following options.
1). Do the eM Client official workaround which includes revoking permission for eM Client in your Microsoft account & the Registry modification etc. This then allows eM Client use the original older OAuth verification method. Recommend to reboot your computer after doing the modifications.
or
2). Alt configure your account as an Exchange account instead and setup 2 Step verification and generate an App password (within your Microsoft account) to then use in eM Client when setting up your Microsoft account via the “Add Mail / Other / Exchange” option. Most Microsoft accounts will work fine this way in eM Client.
Also as mentioned previously the difference with Microsoft accounts configured as exchange accounts have up to a min delay compared to IMAP accts which are pretty much realtime.
Note: You setup 2 Step verification and Generate the app password in your Microsoft Security / Advanced Security section of personal accts.
I completely agree @Laurel_Valley - until mid last year I owned an IT support company with 38 sites mainly in Europe plus UK, North Africa & Middle East.
For a period prior to my sale of the company we were evaluating eMC,I was very keen to adopt eMC, I am still and expect to be a very satisfied user, however, the head of IT plus the finance director
and the head HR & training were not totally convinced.
Just prior to Covid it we decided to run a 30 seat assessment whichis just less than 10% of the total seats. The trial did not go ahead primarily because of Covid, and now I simply do not know, I am no
longer involved on a daily basis as I only remain as a consultant for 5 years with no direct input in the day to day running of the company despite having a 12.5% holding. None of this is relevant except for the other reasons together with Covid, the prospect of moving a large number of users to a new system if a move was agreed, the cost involved, not so much capital but the ongoing training particularly until fully up and running.
There was also the issue of support over which the head of IT had, and I know still has reservations, a lot of this is as the result of what he monitors on this Forum that he believes is a good snapshot of how an organisation views and treats its clients, that the trial did not go ahead at the time and possibly never will - I simply do not know. He never loses the opportunity to remind me that we have never lost a client in over 20 years, he puts this down to customer service.
Although it is no longer my area of concern I agree with @Laurel_Valley it is an issue that needs to be considered and this is only emphasised with the recent debacle concerning the issue with Microsoft
If anyone is open to testing something, we have a version we just created that won’t use SMTP to send, but will use AirSync instead thus bypassing the issue altogether. You don’t need to change anything in eM Client except install this version, and you won’t need the registry workaround. You can remove that by using the removeoldoutlookcomflow.reg file on the Knowledgebase page or run the command for Mac users.
The above fix (version 9.2.1628) allowed me to send emails for my regular Outlook.com account.
If a user leaves everything at the default settings established by EMC, everything should work okay because IMAP, SMTP and AirSync are enabled on the General tab in the Account screen.
