安全 : Cisco IronPort Email 安全设备

在页脚的免责声明为什么显示作为附件?

2016 年 10 月 27 日 - 机器翻译
其他版本: PDFpdf | 英语 (2015 年 8 月 22 日) | 反馈

简介

本文在思科电子邮件安全工具(ESA)描述如何做对配置的变动,当打算包括作为一处理的电子邮件的页脚时的免责声明显示作为对电子邮件的一个附件。

贡献用凯文Luu和罗伯特Sherwin, Cisco TAC工程师。

在页脚的免责声明为什么显示作为附件?

一般,当有消息主题和页脚之间的一编码不匹配作为附件显示的页脚发生。AsyncOS尝试编码在编码的全部消息和消息主题一样,以便页脚在正文将包括(线型)和不会包括作为一个分开的附件。然而,如果页脚不可能与正文一起,从ESA CLI您能使用localeconfig命令配置AsyncOS尝试促进或者转换,匹配页脚的编码的正文,以便页脚在消息的正文可以包括。

myesa.local> localeconfig
Behavior when modifying headers: Use encoding of message body
Behavior for untagged non-ASCII headers: Impose encoding of message body
Behavior for mismatched footer or heading encoding: Only try encoding from message body

Choose the operation you want to perform:
- SETUP - Configure multi-lingual settings.
[]> setup

If a header is modified, encode the new header in the same encoding as the message
body? (Some MUAs incorrectly handle headers encoded in a different encoding than the
body. However, encoding a modified header in the same encoding as the message body
may cause certain characters in the modified header to be lost.) [Y]>

If a non-ASCII header is not properly tagged with a character set and is being used
or modified, impose the encoding of the body on the header during processing and
final representation of the message? (Many MUAs create non-RFC-compliant headers
that are then handled in an undefined way. Some MUAs handle headers encoded in
character sets that differ from that of the main body in an incorrect way. Imposing
the encoding of the body on the header may encode the header more precisely. This
will be used to interpret the content of headers for processing, it will not modify
or rewrite the header unless that is done explicitly as part of
the processing.) [Y]>

Disclaimers (as either footers or headings) are added in-line with the message body
whenever possible. However, if the disclaimer is encoded differently than the message
body, and if imposing a single encoding will cause loss of characters, it will be
added as an attachment. The system will always try to use the message body's encoding
for the disclaimer. If that fails, the system can try to edit the message body to use
an encoding that is compatible with the message body as well as the disclaimer. Should
the system try to re-encode the message body in such a case? [N]> y

返回到主CLI提示符和对配置的进行更改。 您应该然后看到从localeconfig列出的以下设置:

Behavior when modifying headers: Use encoding of message body
Behavior for untagged non-ASCII headers: Impose encoding of message body
Behavior for mismatched footer or heading encoding: Try both body and footer or
heading encodings

相关信息



Document ID: 118501