Emails Received but won't Send

@Gary The new updated Interim Release as per your info & link above now sends fine :slightly_smiling_face:

What has made EM decide NOT to wait for Microsoft to provide a “fix” when it’s "their "problem and not EM? Perhaps the developers have come to the conclusion MS will not provide a solution to this issue which seems to only plague EM?

martes 28 febrero 2023 :: 0731hrs (UTC +0100)

Good question - AirSync was used years ago


skybat

¥Saludos desde Valencia la soleada en España!

[email protected]

Hablo español, luego portugués e inglés, con conocimiento de varios otros idiomas.

No, this issue affects all email applications using modern oAuth for SMTP. As I have said many times, the issue is that Microsoft broke their oAuth implementation for SMTP. We decided to use AirSync instead to send messages, thus bypassing the server issue completely as it doesn’t appear your email provider is going to fix their server any time soon.

1 Like

Thanks Gary - emails now sending!

Thanks Gary. This special version works for me. Emails are now sending.

Much appreciated.

Hi Gary,

couldn’t resist your offer, and have installed this new version to try it out.

Setting up for myself, EMC saw my other email client and offered to import it all. I thought “why not?”, and it worked perfectly (yes, even Hotmail!)

Setting up for my wife, I used the automatic setup for her outlook.com, but it failed. I removed it and started again, but set it up to outlook365.com, and that was successful.

Pity it took so long for this to be made available, but we are both up and running again with me using airsync, and both of us on EMC. I’ll see how it goes.

Thanks!

Finally a fix from eM Client. The new version is working well
so far.

Having clicked Gary’s link and installed the fix, i.e. version 9.2.1628 (a307a94), and checked that airsync is now active, imap and smtp greyed out, and “send immediately” is ticked, there is no change - outgoing mail still fails
although no error messages are now triggered (have checked they are ticked for airsync logging). I note that others are finding the fix works for them, but no luck with mine. I had not previously used the registry workaround, so there would be no residual issues from that; nor made any changes to my MS-outlook.com account settings. All was working fine prior to the Microsoft oauth change. I can of course use MS-outlook.com online or desktop with no issues - but I have all my vast local work files from many years on eMclient, and in any event no wish to change. It’s frustrating though, would be grateful for any suggestions.

@RBCS

Having clicked Gary’s link and installed the fix, i.e. version 9.2.1628 (a307a94), and checked that airsync is now active, imap and smtp greyed out, and “send immediately” is ticked, there is no change - outgoing mail still fails

Make sure you reverse the registry workaround and recommend to reboot after doing that.

As a test, can you completely disable any anti-virus, firewall, proxy or VPN, then try again. Sometimes even restarting your router may resolve this.

Thanks Gary - I disabled firewall etc. (Norton, also checked W.Defender was off) as suggested; still receiving fine but nothing sending. (Reference cyberzork’s response, thanks for that but I had not implemented the registry workaround so nothing to roll back; I did restart pc after installing the latest fix version of eMclient). I can only think that maybe there is an Account setting on my Microsoft outlook.com (hotmail) account that needs changing maybe, or carried-forward setting(s) in eMclient I’ve overlooked? Meantime thanks for the advice thus far


It could be incorrect settings.

The SMTP tab should look like this:

image

Hello. I have the same issue. I receive emails but cant send, and the emails received have blocked images. Happens every time I awake the computer after suspension. If I restart the computer, its all good. But my issue affects gmail server settings. If I go through the web, all ok, but after suspension, dont work through em client.

P.S. I discovered that the bug happened after changing the system font via “winaero tweaker”. I changed back and the issue doesnt occur anymore!

Now using those settings Gary; Host and port were correct, Security was on the legacy setting but now changed to force usage of SSL/TLS; saved settings and closed/reopened eMclient just in case that helped. Unfortunately, still not sending.

jueves 09 marzo 2023 :: 1825hrs (UTC +0100)

Nothing to do with the eMC issue.
We had a client who messed around with Winaero changing from Segoe UI system
font that caused a lot of problems.
The only font that we managed to change to for him that did not cause issues was
Webleysleek UI Semibold

ÂĄBuena suerte!

skybat

¥Saludos desde Valencia la soleada en España!

[email protected]

Hablo español, luego portugués e inglés, con conocimiento de varios otros idiomas.

O problema estĂĄ resolvido. Obrigado!
Cumprimentos desde Portugal!
Abraço forte.

Update - I removed my account then reinstated it. That (following the earlier fix using latest eMclient update) seems to have worked. Thank you Gary et al for help.

Gary,

Since I did the registry fix EMC has been working just fine. I keep getting the update notice for “1628” but I was wondering do I have to reverse the registry fix first before running the update? With everything working I am concerned that I will end up back at ground zero?
Thanks in advance!

Hi Gary

Before leaving for a 3 month vacation my Windows 10 desktop running eMclient had the MS problem of not being able to send mail. I took my Windows 10 laptop with me on vacation and initially had the same MS problem. While away I saw the eMclient workaround to use AirSync. I downloaded V9.2.168 and set up AirSync for EMC on my laptop and all worked well.

Upon returning home my desktop still had the same MS issue sending mail. I Upgraded to the current V9.2.1735 and configured the account to use AirSync exactly as my laptop. The MS sending issue remained. The other day EMC pushed an update to V9.2.1735 to my laptop and the same MS inability to send messages returned.

It seems like the work around only works in V9.2.1628 but I’m unable to revert to that version. Please send information on how I can revert to V9.2.162 on both computers without losing my contacts and groups.