S/MIME Implementation Guide

We've been working on this S/MIME implementation guide for some time so it's great to finally blog post it!

S/MIME provides open, interoperable protocols that allow compliant software to exchange messages that are protected with digital signatures and encryption. S/MIME requires that each sender and recipient have an X.509-format digital certificate, so public-key infrastructure (PKI) design and deployment is a major part of S/MIME deployment. This paper describes the S/MIME protocol, explains your options for obtaining, installing, and using certificates; describes different methods of certificate storage and their attributes; and describes how you can use S/MIME to protect messages sent from, and received by, Windows Mobile devices. The information and instructions in this paper are applicable to Windows Mobile 5.0 and Windows Mobile 6 devices and to users whose mailboxes are hosted on Exchange Server 2003 and Exchange Server 2007.


Windows Mobile SMIME implementation guide-final-1101.pdf

Comments (4)
  1. This document is a great help. I’m using Windows Mobile 6 on an AT&T 8525 (aka HTC Hermes). HTC just released the Windows Mobile 6 upgrade and I am very pleased.

    I have one nagging problem. I have imported my certificate and I can send and receive encrypted email but I am unable to send plain text signed messages or signed encrypted messages. I get the all too familiar error "The message cannot be signed because the certificate for sending signed email is not on the device or accesible via smart card."

    How can this be the case if I can send and receive encrypted messages?

  2. One step better than get-command MAPI Messaging Benchmark Being Retired Outlook Anywhere changes in Exchange

  3. 黎波 says:


  4. 黎波 says:

    S/MIME 提供了开放、可互操作的协议,它允许软件之间交换经过数字签名和加密保护的消息。

Comments are closed.

Skip to main content