Skip to content Skip to navigation

Reading Secure Email in Stanford Google Apps

The Stanford email service for some members of the Stanford community is provided through Google Apps.

Secure email messages will appear as encrypted attachments. The first time you receive a secure email, you will be required to register your email address with the Cisco Registered Envelope Service (CRES). For subsequent messages, you will need to enter your registered email address and your password.

To register your Stanford Google Email account :

  1. Go to
  2. Open a secure email message. It will have "Secure:" in the subject line and will have an attachment.
  3. Open the attachment.
  4. Expand the To: field and select Address not listed.

    expand To fileld and select Address not listed
  5. In the Your address field, enter your SUNet and then click Submit.

    enter destination address
  6. Click Register.

    start Cisco Registered Envelope Service registration process
  7. Fill out the registration form and then click Register.

    registration form
  8. When the New User Registration page is displayed, close your browser window.

    new user registration confirmation
  9. Check your email and open the message with the subject Please activate with CRES.
  10. On the Activation page, click the link titled Click here to activate this account.
    Note: This page contains your cancellation number if you want to close your CRES account.

    email with link to activate Cisco Registered Envelope Service account
  11. The Email Address Confirmed page is displayed when your account has been activated. Close your browser window.

    confirmation page saying that your account has been activated
  12. Return to your email Inbox. Open your secure message and then open the attachment.
  13. Enter your SUNet address and your email password. Then, click Open to read the message .
    Note: You will need to enter your address and password each time you want to open a secure email message.
    login dialog box to open a secure email message
Last modified October 24, 2016