Recieving signed and/or encrypted emails and attachments with NotifySync - Powered by Kayako SupportSuite Helpdesk Software

09 Sep 2010

Support Center » Knowledgebase » NotifySync Device Client » Recieving signed and/or encrypted emails and attachments with NotifySync

	Recieving signed and/or encrypted emails and attachments with NotifySync

Article

NotifySync Device Client:

Signed and Encrypted Email in NotifySync

Signed and/or encrypted email messages can be sent to NotifySync using S/MIME or PGP standards. These results of sending these messages to NotifySync will vary based upon the mail server which processes the incoming messages as well as how the message was signed and/or encrypted. The table below displays the results of the tests using various ActiveSync servers.

Terminology

S/MIME and PGP allows you to sign and/or encrypt an email in three different ways: Body Only, Body and Attachments Separately, and Message as a Whole. 'Body Only' means that only the body of the message will be signed/encrypted; any attachments will be left alone. 'Body and Attachments Separately' means that the body of the message will be signed/encrypted and any attachments will be signed/encrypted individually. 'Message as a Whole' means that both the body and any attachments will be signed/encrypted as one entity.

Testing Criteria (PGP)

The following tests were done using PGP with the same set of data. The email sent to NotifySync contained a body and several plaintext (.txt) or image (.png) attachments. The only difference in each test was how the message was signed and/or encrypted. It should be noted that signing/encrypting the message and attachments may result in the attachment filename and extension being changed and/or new attachments being added to the message (for example, the signature of the message is sometimes added to the message as an attachment).

NotifySync PGP Results

Test	Exchange 2003	Exchange 2007	Zimbra 5.0.11	Kerio 6.7.0
Signed - Body Only	Downloaded and opened.	Downloaded and opened.	Came down without attachment. No attachments in web client either.	Downloaded and opened.
Signed - Each Attachment Separately	Downloaded and opened.	Downloaded and opened.	Came down without attachment. Only the signature attachment was available in webclient.	Downloaded and opened.
Signed - Message as a Whole	Could only save attachment. It said there was no app to open with.	Came down without attachment. Verified attachment was present in OWA.	Came down without attachment. Only the signature attachment was available in webclient.	Downloaded and opened.
Encrypted - Body Only	Downloaded and opened.	Downloaded and opened.	Came down without attachment. No attachments in webclient either.	Downloaded and opened.
Encrypted - Each Attachment Separately	Was able to download, but changed filename to .txt.pgp	Was able to download, but changed filename to .txt.pgp	Was able to download, but changed filename to .txt.pgp	Was able to download, but changed filename to .txt.pgp
Encrypted - Message as a Whole	Was able to download attachment, but the content-type was application/octet-stream instead of text/plain and filename was changed.	Was able to download attachment, but the content-type was application/octet-stream instead of text/plain and filename was changed.	Was able to download attachment, but the content-type was application/octet-stream instead of text/plain and filename was changed.	Was able to download attachment, but the content-type was application/octet-stream instead of text/plain and filename was changed.
Signed and Encrypted - Body Only	Downloaded and opened.	Downloaded and opened.	Came down without attachment. No attachments in webclient either.	Downloaded and opened.
Signed and Encrypted - Each Attachment Separately	Was able to download, but changed filename to .txt.pgp	Was able to download, but changed filename to .txt.pgp	Was able to download, but changed filename to .txt.pgp	Was able to download, but changed filename to .txt.pgp
Signed and Encrypted - Message as a Whole	Was able to download attachment, but the content-type was application/octet-stream instead of text/plain and filename was changed.	Was able to download attachment, but the content-type was application/octet-stream instead of text/plain and filename was changed.	Was able to download attachment, but the content-type was application/octet-stream instead of text/plain and filename was changed.	Was able to download attachment, but the content-type was application/octet-stream instead of text/plain and filename was changed.