eM Client does not recognize it is default email app in windows 10

21

Yep, all red lights, so the car goes anyway, and SMASH.  My analogy still fits: the stoplight is NOT telling you when it is your turn or someone else’s.  The setting inside of em Client is not telling you it is the default e-mail client or that someone else is.  It is like a disconnected crosswalk button: push it as much as you want but it doesn’t effect a change.

As to opening a support ticket, why do you think users come here to post about problems?  Because they are using the free version of em Client which gets no support.  Dumping their users into these forums is the only way their free-version users get “support”.    

https://emclient.com/pro-vs-free?lang=en

For the free version, there’s a big red “X” denoting no [professional] support.  Forums is what free-version users get to use to request help.  When I click the About link at the top of this forum page, there are members listed who are devs, employees, and official reps.  They’re not participating here, so it’s just peer support here.

I’m not paying $50 to report a bug to them.  Of course, if you want to pay the $50 for a Pro license and register me for that product so I can get support, I’d have no qualms about that.

22

Maybe you just did not set all the defaults for the app in your Windows settings.

I did.

I am not seeing a problem here, besides your tenuous analogy. :wink:

23

One, yes, I did use Default Programs in Windows 10 to make sure eM Client was the default handler for e-mail.  That won’t affect how eM Client itself reports whether or not it is the default client.

Two, if eM Client cannot poll the OS to determine if it is the default e-mail client, the option within eM Client to make itself the default e-mail handler should be removed.  In fact, I’ve seen such programs where when you click on its option to make it the default that what it does instead is drop the user in the Default Programs wizard.

In your screenshot, you show that eM Client is showing “This application is the default mail handler”.  What others are noting is this discussion is that eM Client reports (emphasis added) “This application is not the default mail handler”.  Clicking the “Make default” button does not change that status.  Restarting eM Client does not change that status.  The user must go into Default Programs to make sure or set eM Client as the e-mail handler.

eM Client can be made the default e-mail handler.  That is not the issue.  That eM Client incorrectly states it is not the current e-mail handler when it is the default is the issue, and apparently an issue with eM Client only on Windows 10.  In prior versions of Windows, setting default handlers could be done by any program or process.  Since malware could do the same, Microsoft added protection to the default handlers, as already explained in my first and very lengthy reply.  eM Client knows the simple registry change to make itself the default handler in Windows prior to 10.  It does not know how to make itself the default under Windows 10.

In the screenshot you showed, under which version of Windows are you running em Client?  Not a problem before Windows 10.  A problem as of Windows 10.

24

If you have not selected all the defaults, then how can the application report something it is not? The problem lies with your Windows settings and not with eM Client.

This is on Windows 10 build 17134.829

Comments on this discussion are repetitive. This will be my final one.

25

“How can the application report something it is not?”

Because the APPLICATION has bug.  It has a bug.  That eM Client’s setting matches the currently defined registration of it assigned as the default e-mail program should work for you does not obviate that it is not working for others.  You didn’t start this discussion.  It is a defect experienced by others.

The reason that GeorgeC started this discussion is that eM Client is  not  reporting in its own settings that it is the default e-mail handler.  It is the default e-mail handler. 

For some users (apparently not for you):
eM Client is not detecting that it is the default e-mail handler in Windows 10.
What eM Client reports in its settings is WRONG  – for those experiencing the bug. I’ll ask again: Under which version of Windows are you running em Client?  The subject of this discussion states “Windows 10”.

eM Client’s settings say it is NOT the default e-mail program.  Yet Default Programs says it is, and double-clicking on a mailto: link proves eM Client is the default e-mail program.  The “Make default” button in eM Client is enabled which only happens if eM Client thinks it is NOT the default e-mail program. 

Stop trying to focus on whether eM Client is or is not the actual registered default e-mail client.  The bug is with eM Client claiming it isn’t.

  • eM Client  is  the default e-mail program.
  • eM Client  says it is not.
    You are not addressing the issue which is eM Client says it is not the default, not that it isn’t the default for usage.  I don’t think you can address this bug, because you cannot fix a bug in the code for eM Client.  And the devs don’t visit here to be made aware of the bug.  And I’m not paying $50 to tell them.
26

Please provide a screenshot (as below) showing that eM Client is set as default. If you have not selected the defaults, then please stop commenting on this thread.

27

Ah, so you are calling GeorgeC and myself to be liars.

eM Client settings:
https://imgur.com/a/ozJbwza

Click the “Make default” button.  eM Client does not change it settings and instead opens the Default Applications app.  It’s pretty obvious eM Client cannot change the defaults, so it pushes you off to the Windows 10 app.  eM Client does not know how to change the defaults under Window 10 which is why its settings do not match those defined in Windows 10.

Default Applications:
https://imgur.com/a/RsfEqLB

Exit the Default Apps app.  No change in eM Client: the button is still enabled (showing eM Client thinks it is not the default e-mail program) and still says “This application is not the default mail handler.”  Exit settings, exit eM Client, reload eM Client, go into settings, and still eM Client thinks it is NOT the default mail handler.

eM Client is *not* using its own settings dialog to change defaults in the OS.  It is pushing the user off to the Default Apps dialog.  No matter what you do in the Default Apps dialog (set eM Client to be the default mail handler or set to some other program), the settings in eM Client will not reflect the defaults registered in the OS. 

Instead of eM Client pretending to show the handler status, it should detect it is running under Windows 10 and: (1) Remove the “This application is [not] the default mail handler” (don’t even attempt to display the handler status); and, (2) Change the button’s title from  “Make default” to “Go to Default Apps”.

For a 2nd time, you refuse to divulge under which version of Windows you are running eM Client.  You aren’t running eM Client under Windows 10, and Windows 10 is where the misbehavior is getting reported.

What eM Client shows in its settings does not match the handler registration in Windows 10.  The user can hit the “Make default” until doomsday, but the “This application is not the default mail handler” status message will never change.

28

Please provide a screen shot showing eM Client’s defaults in Windows settings. If you don’t know how to do that, please ask.

29

I am using Windows 10 and made it default in Windows settings. Not the main one. You need to go to the bottom of that screen and choose set defaults by app. If you dont choose that one then EM is not completely set as the default.

Now it look fine.

Maybe the problem is that clicking the button in EM does not do anything but take you to the place to make the setting. It does not make the setting for you. You have to know something of Windows and how to make it the default.

30

Ah! Finally someone who knows how to configure Windows. Thanks Charlie. :wink:

That is what I did also. 

31

Only needed if you want eM Client to handle *filetype* associations besides the mailto *protocol*.  I use other tools to view .msg, .ics, .eml, and other e-mail filetypes.  eM Client doesn’t need to support those UNLESS you export your e-mails *out* of it AND you want eM Client to view those files.  I don’t need eM Client to support all the filetypes.  Supporting filetypes doesn’t make eM Client the mailto protocol handler.  Filetype associations are irrelevant of who is the mailto protocol handler.  You are conflating a viewer (by filetype association) with a protocol handler (mailto).

Plus, as Gary keeps ignoring, the problem was never with eM Client functioning as the default mail handler.  The problem remains that eM Client does not report itself as the default mail handler in its settings.  eM Client continues to report “This application is not the default mail handler” even after the user configures it in Default Apps to be the default mail handler.

I don’t see why it is so hard to recognize eM Client is not reporting the correct status of whatever is the default mail handler.  It’s right there to see.  You’ve been shown the screenshot.  Yet you continue to deny it.  Putting your hands over your eyes doesn’t change reality.

You can keep hitting the “Make default” button in eM Client’s settings forever.  You can use Default Apps to make eM Client the default mail handler.  In Default Apps, you can even configure eM Client to be the default *filetype* association.  None of that will alter that eM Client continues to report “This application is not the default mail handler.”

So, just how do YOU get eM Client (not Default Apps) on Windows 10 to report “This application is the default mail handler”, as per the opening post in this discussion?  The status reported in eM Client is wrong in Windows 10.  As such, and only under Windows 10, the easy fix is to simply remove eM Client’s status saying it is or is not the default mail handler. 

If Windows 10, don’t show bogus handler status; else, show handler status.  It has always been about the status reported in eM Client.  You folks keep confusing function with cosmetics.

32

I get EM to be default as I said. If you do it, it will show in EM. No problem. If you dont select it to be default for these things, how can it be default. The make default button only takes you to place to make default. You need to make settings yourself as I said. If you make it then it will be default. If you not make it it will not be default. What is problem?

33

So, just how do YOU get  eM Client  (not Default Apps)   on Windows 10 to report "This application is the default mail handler"

Charlie and I have described how to get eM Client to recognize it is the default. For that to happen, you actually need to make it the default otherwise it will not report that it is.

34

Charlie, you are right.  After changing EVERY listed e-mail filetype listed and the mailto protocol to be eM Client, now eM Client’s settings says it is the default mail handler.  That sucks.  How many users are going to go further than see eM Client is the default e-mail program to go look under “Set defaults by app”.

Alas, there are reasons why I still choose to use other tools to view EML, MSG, VCF, and other e-mail filetypes.  I’ll have to put up with eM Client thinking it is not the default mailto handler despite it is.  E-mail clients come an go.  I’m not loyal to any of them.  However, when I switch or during the transition, or on hosts with no local e-mail client, I still need to view those filetypes.  I never want to be dependent on a particular e-mail client to view those files.  eM Client does not require supporting those filetypes unless you export messages out of eM Client, but that assumes you want those filetypes associated to eM Client and not some other viewer.

Thanks to Charlie for reiterating pefunk’s advice on why eM Client  continues to think it is not the default mail handler unless eM Client is also associated to several e-mail filetypes.  GeorgeC (original poster) and other respondents replying after pefunk said the suggestion did not work for them, so I figured it wouldn’t work for me.  Maybe the others did not change ALL filetype associations (which are NOT protocols) to use eM Client.  Only then did eM Client report it was the default mail handler.  Looks like eM Client mixes “default mail filetypes handler” with “default mail protocol handler” together.  

eM Client functions without being the default filetypes handler which applies only if and after messages have been exported out of eM Client.  Odd that it mandates it must also be the filetypes handler to then report it is the mail handler.

Thank again, Charlie (and pefunk).

35

I really had this with Gary by email last year. He said this is the method to change in Windows settings. I just followed. Maybe for most people this is not a big thing.

36

Que diferença faz colocar o eM Client como padrão ou não?

37

Idacil Amarilho: Que diferença faz colocar o eM Client como padrão ou não?
Google Translate: What difference does it make to put eM Client as default or not?

I’m sure you have clicked on hyperlinks in web pages or in e-mails that are URIs for http:// and https://.  You click on those and the web browser opens to display the specified web page.  There are many URI schemes, like mailto:, ftp://, nntp:, and so on.  Someone that puts a mailto: URI in their e-mail or web page is giving you a link to load the default e-mail handler.  Most users don’t know about mailto: [hyper]links.  They just know they can click on a clickable object that opens the default e-mail program.

https://en.wikipedia.org/wiki/Mailto

mailto: with no arguments just opens your current or default e-mail client.  mailto:[email protected] is a link you click on to load your e-mail client to open its new-mail compose window with the From: header already prefilled with the e-mail address.  There are many arguments you can add to the mailto: URI to specify what other headers to pre-populate in the e-mail.

https://www.labnol.org/internet/email/learn-mailto-syntax/6748/
https://developer.yoast.com/guide-mailto-links/

You can specify no arguments, in which case the default e-mail client opens its new-mail compose window.  You can optionally specify one, or more recipients to put in the To: header, and the same for the CC: and BCC: headers, and can even prefill some text into the body of the message.

Because spaces are illegal in URIs (because parsing would become impossible) and some characters are reserved for parsing a URI (:, /, ?, &, etc), illegal and reserved characters must be represented using percent encoding: %xx, where xx = hexidecimal value for ASCII character.  For example, a space character is represented by %20.

https://developer.mozilla.org/en-US/docs/Glossary/percent-encoding

If you’ve ever done a search at Google or any online engine that tracks on which results you click, you’ll see the hyperlink has the form:

                path-arg delimiter \_\_\_\_     \_\_\_ \_\_\_arg delimiters

                                       |   |   |

https://<somethinggoogle>/<pathsorargs>?...&amp;...&amp;url=https%3A%2F%2F<somesite>%2F<somepath>/...</somepath></somesite></pathsorargs></somethinggoogle>

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_/&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_/

&nbsp;&nbsp;&nbsp;&nbsp; Google tracks the hyperlink&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; http://<somesite>/<somepath>/...</somepath></somesite>

Back to the mailto: URI, you can test this yourself.  Right-click on the desktop and select to create a new shortcut.  In the shortcut, define its command to “mailto:” (without the double-quotes).  Save the shortcut.  When you double-click on the shortcut, the default e-mail program should load and present its new-mail compose window.  I use that shortcut to quickly start writing a new e-mail without having to first load the e-mail program or redisplay its window and then click on “New Mail” (or make sure Mail is selected if the e-mail client just has “New”).

If you often send e-mails to the same person, use:
  mailto:[email protected]
as the shortcut’s command (or as a hyperlink in your web document or in an e-mail message).  To also prefill the Subject header, use:
  mailto:[email protected]?subject=Bug%20Report%3A%20eM%20Client
If you always prefix your message with some template text, use:
  mailto:[email protected]?subject=Bug%20Report%3A%20eM%20Client&body=Internal%20Distribution%20Only%21

You could forego using clickable mailto: links.  You copy the e-mail address in the mailto: link.  You open whatever e-mail client you want to use and start a new e-mail.  You click in the To: field and paste in the e-mail addresses (there could be more than one).  You fill in the Subject field, and start typing away your message.  Or, you click on the mailto: link and the new-mail compose window of the default e-mail client automatically opens with the To: field prefilled, and perhaps even the Subject field, too.  Using the mailto: link means you don’t misspell or truncate the e-mail address(es).  Clicking on mailto: links makes easier starting new e-mails, but you could do it all manually.

38

Ok, thanks. 

39

This forum took away the Edit link, so I couldn’t correct what this forum does to selected text using the

 tag.
40

Yes, the Edit option will be removed as soon as there is a comment, or a like, on your comment. You need to be quick Vanguard. :wink: