We all know that email is insecure…..
But how do you offer some limited protection for plain text email content?
The answer is to encode it as base64 and set the content disposition as inline. This will tell the email client that the section that is inline is plain text encoded to base64….and magically the conversion is done.
What does this mean??? It means that content cannot be easily scraped or siphoned off….that’s all….
Example:
Content-Disposition: inline
Content-Transfer-Encoding: base64
Content-Type: text/plain; charset=”UTF8″
MIME-Version: 1.0
Date: Tue, 12 Sep 2006 18:34:42 UT
To: jmoore@johnmo.com
From: alert@johnmo.com
Subject: Sales AlertCgpUaGUgZm9sbG93aW5nIHJlY2VudCBwcm9wZXJ0eSBsaXN0aW5ncyBtYXRjaGVk
bCBFc3RhdGUgQWxlcnQgc2VhcmNoIGNyaXRlcmlhLgoKCgoNLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tCgo
T2ZmZXJzIG92ZXIgJDYyNS….The plain text section has been base64 encoded for a little privacy….
ClarionX is a proud contributor to DevDawn.com.
