Topic
  • No replies
A Case
A Case
15 Posts

Pinned topic Native Email vs Containerized Email

‏2016-02-29T18:32:14Z | onprem saas

There is always a lot of discussion around putting corporate email inside the Native Email application (iOS, Samsung, etc) vs putting corporate email inside a containerized application (Secure Mail, Touchdown, etc). The table below outlines the differences in functionality between the two platforms.

 

 

Native

Container

Look & Feel (Email)

Data Storage

Cannot prevent where the data is stored - on the device

Data is stored in the secured container database

Data Wipe

Corporate data (email config) can be wiped via Selective Wipe

Copy & Paste

Impose screenshot/copy&paste restrictions to the entire device

Restrction of Screenshot (Android) within App, Restrict copy/paste outside of container

Certification Authentication

Support Certification authentications

Device Passcode

Device level passcode required to secure device from unauthorized users.

Possible to not require passcode at device level and only enforce passcode on container.

Secure Restrictions

  • Restrict which applications attachments are allowed to be opened in
  • Restrict which applications can open files in Native Email for distribution
  • Restrict Mail from moving to another mailbox
  • Prevent 3rd Party Apps from Sending Email
  • Other Apple MDM restrictions
  • Restrict Printing of Emails
  • Restrict Attachment Forwarding
  • Restrict Email to External Domains
  • Restrict Export of Contacts
  • Restrict Personal Contacts in Secure Mail

Mail Notifications

Email can be configured to:

  • Push Notifications (As Mail Comes in)
  • Or Manual Sync Intervals

iOS: Email will not sync in background, app must be opened for sync to occur. However, configuring the Cloud Extender Module for Push Notifications does provide some notification functionality.

Android: The app will sync email in the background

 

Updated on 2016-02-29T18:32:32Z at 2016-02-29T18:32:32Z by A Case