Question 1

What is the difference between PGP/MIME and PGP/INLINE?

Accepted Answer

PGP/INLINE puts the armored ciphertext directly into the email body. PGP/MIME wraps it in a multipart MIME structure with proper headers (Content-Type: multipart/encrypted; protocol="application/pgp-encrypted"). PGP/MIME is the modern standard.

Question 2

Will my email client read the output?

Accepted Answer

Any RFC 2015–compliant client will. Thunderbird, Apple Mail, ProtonMail, K-9 Mail, and similar all handle PGP/MIME natively. Webmail clients without PGP support will show the MIME structure as raw text.

Question 3

Can I sign and encrypt at the same time?

Accepted Answer

Yes — sign the body first, then encrypt the signed result. The MIME wrapper indicates both operations were performed. Most email clients show a single combined "signed and encrypted" indicator.

Question 4

Why is PGP/MIME multi-part?

Accepted Answer

To preserve clean separation between the encrypted/signed payload and the protocol indicator part. MIME tools that do not understand PGP can still parse the envelope.

Question 5

Does this tool send email?

Accepted Answer

No — it only formats and parses MIME content. Use any email client (or paste into Gmail compose) to actually send.