Emails Received but won't Send

@Ricky2

do I have to reverse the registry fix first before running the update?

Yes you should in my view reverse the registry workaround and reboot your computer before running the new update or you could have problems.

@bigbird

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

If you initially did the registry workaround, “I would recommend to undo that” or the updated eM Client using ActiveSync may not send.

Now if you already have reversed the registry workaround and rebooted your computer / laptop and still not sending, then “move or drag those items stuck in the outbox” to your drafts folder. Then close eM Client and reopen the program and try re-sending those draft emails.

I’m the creator of this topic. All is working well now, so I decided not to load the latest update until I can be sure that the ‘no send’ problem is dead and buried.

Just as well I waited, since we’re now told that the registry workaround must be undone before installing the update!

What is the process for undoing it, please? In simple terms that a novice can understand.

It is not necessary to undo the registry fix, but if you want to you will find instructions in the same Knowledgebase page.

I never applied the registry workaround. My desktop now updated to V9.2.1735 still won’t send MS Outlook mail. My laptop after applying the fix (AriSync) worked fine with V9.2.1628. However EMC sent an update to my laptop which I installed (V9.2.1735) which caused my laptop to stop sending MS Outlook mail despite having previously worked in V9.2.1628.

Can you send instructions to revert to V9.2.1628 on both my laptop and desktop without losing configuration, contacts and content (Archive Folders,etc)?

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

If that still fails go to Menu > Operations > Log tab. Look for an SMTP error, it will explain more.

@Gary

It is not necessary to undo the registry fix, but if you want to you will find instructions in the same Knowledgebase page.

The problem in my view with not doing the registry workaround reversal is that eg: when Microsoft do eventually fix the Modern OAuth login method and eM Client then in a later update maybe reverts back to normal SMTP protocol which uses the previous newer Microsoft Modern OAuth method, eM Client then won’t send as your registry is still set to the older OAuth method due to the reg work around.

So yes it maybe not necessary currently “if eM Client sticks with ActiveSync protocol for sending” permanently instead of SMTP protocol for Microsoft accounts, but will be a problem in my view if eM Client changes back in the future.

Or is eM Client going to permanently now stick with ActiveSync protocol for sending with Microsoft accounts.

Many thanks, Gary.

I’ve carried out the update without reversing the registry workaround and a test email sent without problem.

I understand cyberzork’s advice about reversing the workaround and will do this if the need arises with any change to the system by Microsoft in the future.

Thanks much for your help. The router reboot solved the sending problem with the new V9.2.1735.

Hi Gary, I spoke too soon. The test email from my MS acct. to my gmail acct. showed up in the “Local Folder Outbox” instead of my “Outlook Outbox”. I had rebooted my router and disabled my anti-virus and anti-ransomware. I am enclosing a link to the redacted copy of the Operations Log File. I don’t see any entry for an SMTP error.
Link to redacted Operations Log File