Encryption Management Server PDF Email Protection attachments contain no text
Article ID: 172018
Updated On:
Products
Issue/Introduction
Encryption Management Server PDF Email Protection users receive PGPMessage.pdf attachments that contain no text.
Environment
Encryption Management Server 3.3 and above using PDF Email Protection.
Cause
The PDF Email Protection PGPMessage.pdf attachments can only include plain text in the body of the file although the PGPMessage.pdf file can also include embedded files.
When an internal user sends an HTML format message to a PDF Email Protection external user, the email client will generally generate a multipart/alternative MIME format message that contains a text/plain section. For example:
Content-Type: multipart/alternative; boundary="=-iJmEQTvJkO3vXRsVYqye"
Mime-Version: 1.0
--=-iJmEQTvJkO3vXRsVYqye
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
This is an html message.
--=-iJmEQTvJkO3vXRsVYqye
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: 7bit
<html><head></head><body><div>This is an html message.</div></body></html>
--=-iJmEQTvJkO3vXRsVYqye--
Encryption Management Server does the following:
- Converts the contents of the text/plain section to the file
PGPMessage.pdf. - Converts the contents of the text/html section to the file
body.htmland embeds it inPGPMessage.pdf.
Resolution
All email clients will include a text/plain section when constructing a multipart/alternative MIME message.
However, some applications may not adhere to this standard. Note that some anti-spam products contain rules that will flag such messages as spam.
Unless the MIME message contains a text/plain section, neither Encryption Management Server PDF Email Protection or Web Email Protection will be able to process the message correctly.
Please ensure that any application sending to PDF Email Protection users or Web Email Protection users contains a plain text version of the message content within the message.
Feedback
