Receiving EaSecure Messages

     

You do not have to do anything special to receive EaSecure messages. If you have an email address and someone sends you an EaSecure message, you will receive it in your Inbox. However, before you have opened any EaSecure message sent to your email address, your do not have a public key to encrypt the messages, and therefore each EaSecure message will be protected by a one-time password. The one-time password is sent to you in a separate email.

If there is no one to send you an EaSecure message, you can easily get a one-time-password protected EaSecure message by entering your email address below and click "Send Me an EaSecure Message." A "Welcome" EaSecure message will be sent to your email address. If you have never opened an EaSecure message sent to your email address before, the "Welcome" EaSecure message will be protected by a one-time password and the corresponding one-time password will also be sent to you in a separate email.

Enter your email address:

After receiving a one-time-password-protected EaSecure message, all you need to do is install the appropriate EaSecure plug-in or standalone client, open the one-time-password-protected EaSecure message, and create your own password. You public/private keys will be automatically established. Future EaSecure messages will be encrypted by your public key (no more one-time passwords). You will be able to open all past and future EaSecure messages using your own password, and you can send EaSecure messages to ANYONE who has an email address, even if the recipient is not yet an EaSecure user.

An EaSecure message always has an attachment file with an extension ".eas", which contains all encrypted contents, so please make sure your email server and email client do not block ".eas" attachments. The message will have the prefix "EAS:" on the subject line. An EaSecure message sent to yourself (sender = recipient) will have the prefix "EAC:" on the subject line. When you open an EaSecure message (open the ".eas" attachment), however, the decrypted message shown to you will not have such prefixes.