Topic · Transport Security
S/MIME
Secure Multipurpose Internet Mail Extensions supports certificate-based signing and encryption of MIME messages.
How it works
Participants use public-key certificates to sign and encrypt email content.
What can go wrong
Certificate distribution and endpoint trust can limit deployment. Expired or mismatched certificates can cause validation failures.
What to check or do
Manage certificates and keys carefully and verify signed identities. Test verification and decryption across the intended clients.
How to investigate S/MIME
- Signal to investigate
- A signed S/MIME email displays a certificate warning at one recipient but not another.
- Evidence to collect
- Inspect the signer certificate chain, email-address identity, revocation and trust stores on affected clients.
- Common wrong conclusion
- Encryption and signing are separate S/MIME operations and solve different problems.
How to interpret the evidence
S/MIME uses X.509 certificates to sign or encrypt MIME contents. Recipient key discovery and certificate lifecycle can create interoperability challenges.
What to change and how to verify it
Issue and renew trusted identity certificates, document client support and test both signing validation and encrypted reply workflows.
Put this into practice
Run a focused check, then explore protection if your domain needs it.