Home/ Questions/Q 228801
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-11T19:42:46+00:00

Good morning, I’ve successfully created a little app that registers itself under a custom

  • 0

Good morning,

I’ve successfully created a little app that registers itself under a custom uri protocol (‘irma:’) following the msdn entry at http://msdn.microsoft.com/en-us/library/aa767914(VS.85).aspx

This works perfectly fine when opening such a link manually via the shell/cmd etc, but when sending out links like that, outlook does not recognize those ‘automatically’ on the clients that registry key is set. Do I have to do something extra to let outlook handle such custom uri’s or is it possible at all?

Cheers and thanks,
-j

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    [OK, I’ll post this as a new answer to keep this one clean without deleting all of the previously posted content.]

    I have just repeated the research mentioned in my other answer and it seems that things have greatly improved in the last three years. Both Outlook 2003 (SP3) and Outlook 2007 (SP2) now automatically recognize all of the protocols listed in the MS product support mail quoted in the NG thread linked from my older answer, including the url:-protocol!

    The latter means that you can now write something like:

    url:irma:whatever

    and have it properly linkified and handled. Outlook will however display a security confirmation dialog before executing the protocol handler.

    Update: Note that in Outlook 2003 SP3 the new protocols (e.g. url:, mms://, etc.) are only auto-linkified in HTML-mails. The plain-text inspector behaves as described in my other answer. It does work with plain-text mails in Outlook 2007 SP2, however.

    I have still found no hints at the ability to simply register custom protocols within Outlook that would work without the url:-prefix, however.

    • 0