When rolling out ChromeMailer to the people on the wild internets, some reported problems with missing mailto: handlers in registry. If ChromeMailer redirected you here, please see the steps below to repair your mailto handlers.

 NOTE: YOU ARE RESPONSIBLE FOR THE CHANGES YOU MAKE IN YOUR REGISTRY!

There’s two ways to fix the issue:

 1) Download fix_mailto.reg , (right click -> save as…) then double click it to install. It will recreate all required nodes.

2) Manually. Open Regedit (Start / Run… or in Vista type Regedit into search)

click on HKEY_CLASSES_ROOT. right click on it, New > key, rename it to “mailto”, then select mailto, New > key, create “shell”, in shell, create “open”, in open create “command”, in command: New > string value .it will create a key named (Default), double click on the (Default), and enter the following:

a) on Vista: C:\Program Files\Windows Mail\WinMail.exe /mailurl:%1

b) on XP: C:\Program Files\Outlook Express\msimn.exe /mailurl:%1

This will reset the mailto: protocol handler to Windows default settings. If you now want to use ChromeMailer, simply run it, press ‘Install as Default Mailer’ and it will work as expected.

Update:

Installing Chromemailer does NOT mean you’ve set it up! Please go to Start menu -> Programs -> ChromeMailer and run ChromeMailer.exe!

You can always find the executable under (your install drive, usually C:) \Program Files\Skaelede Online\ChromeMailer\ChromeMailer.exe

People keep asking me, why do they need to use ChromeMailer, how it differs from the good old registry hacks?

Here’s the technical information: ChromeMailer modifies the default mailto: handler in the registry (HKEY_CLASSES_ROOT || HKEY_CURRENT_USER \mailto\shell\open\command), as the good old registry hacks do.

If a computer is a stand-alone one, it will use the HKEY_CLASSES_ROOT,if it’s in a domain it will use HKEY_CURRENT_USER. (others’ settings will not be affected - only if the user is logged in as a Domain Administrator.)

The true difference between the other registry-hacks and ChromeMailer is, that it sets the handler to itself, and rewrites the mailto: parameters.

A valid mailto: is like:

mailto:balint@skaelede.hu?subject=Hello&body=Message&cc=info@skaelede.hu&bcc=hidden@skaelede.hu

If you pass Gmail URL + mailto: params directly to Chrome (or any other browser) in the registry, with %1 parameter, it will truncate some parts of it, because 2 question marks will be in the URL, and it’s not permitted without UrlEncode: so anything after the second will miss.

For example: https://mail.google.com/mail/?extsrc=mailto&url=mailto:balint@skaelede.hu?subject=Hello would show up a window with the to address filled, but subject missing.

Parameter rewrite is the reason for UAC error on Vista, i don’t have $399 to to buy code authentication for my *free* app.
So for a user request, in version 0.2 I added the possibility to use this “truncated” mode, so it will not show up any messages, and will work in 80%…

Google Chrome is the world’s most advanced browser, with many new technical features. We found one missing: we can’t send emails through Google Mail by clicking on mailto: links. All clicks will open up Windows’ default mail client. So we created an application that does the above: it’s called ChromeMailer.