CRES FAQ: Why Company Logo is not Displayed in the Encrypted Envelope via CRES?

Available Languages

Download Options

  • PDF     (4.9 KB)
    View with Adobe Reader on a variety of devices
  • ePub     (85.1 KB)
    View in various apps on iPhone, iPad, Android, Sony Reader, or Windows Phone
  • Mobi (Kindle)     (71.2 KB)
    View on Kindle device or Kindle app on multiple devices
Updated:May 6, 2021
Document ID:118805

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

    Introduction

    This document provides information for why a company logo might not be displayed in the encrypted envelope via Cisco Registered Envelope Service (CRES).

    Why Company Logo is not Displayed in the Encrypted Envelope via CRES?

    From an active CRES account, verify these items:

    • The Envelope Profile on the CRES account and the Email Encryption Profile Name on the Email Security Appliance (ESA) must match.

    • The Envelope Profile on the CRES account has a 32 character limit. If you enter in additional characters and try to Add Image, you see a blank white screen, and the image is not uploaded. 

    • The logo should be at most 60x160 pixels and less than 100 KB.

    • This applies to .GIF and .JPG files only.

    • Since the CRES servers sync based on periodic schedules, there are times where the logo might take up to 24 hours in order to propagate. Most of the time this should occur within one hour.

    Related Information

    TAC Authored

    Contributed by Cisco Engineers

    • Scott Vu
      Cisco TAC Engineer
    • Enrico Werner
      Cisco TAC Engineer
    • Dennis McCabe Jr
      Cisco TAC Engineer

    Was this Document Helpful?

    FeedbackFeedback

    Contact Cisco