Content-types added to the SAS Registry in SAS 9 have caused email
attachments to be sent in EBCDIC and not transcoded to ASCII.  These
email attachments are not readable.

For example, if an email was generated in SAS 9 with an extension of
RTF, the content-type needs to be text/plain, an extension of PDF
needs to be application/pdf and extension csv needs to be content-type
text/plain or text/csv to be legible.  If it was not created in SAS
and has embedded images, it will need a content-type of
application/msword.  The extension needs to match what the document is
regardless of the content-type.

SAS will look at the content-type first and use it if there is one
coded.  If there is no content-type coded and there is an extension,
we will look up that extension in the SAS Registry and use the
content-type for that extension.  Currently the content-types are not
always correct for MVS in the SAS Registry.  If there is no
content-type or extension specified in the email, we will always
default to text/plain.  If no extension and a incorrect content-type is
specified, the client side may not know how to display it properly and
will ask for an application to display it in.

Microsoft Outlook does not look at the content-type to determine how to
render the attachment.  Instead it looks at the extension.

Operating System and Release Information