Metting request + disclaimer

[mewi]

Hello,

When we send meeting requests to another organization the requests are not arriving at the recipient.

Just an empty email with 2 attachments.

When I remove the ESA-disclaimer, it´s working.

I tried to change these settings:

---------------------------------------------------------------------------------------------------------------

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

Behavior when decoding errors found: Disclaimer is displayed as inline content

and the message body is added as an attachment.

---------------------------------------------------------------------------------------------------------------

But without success,

Any idea?

Meinrad

[Libin Varghese]

You can try using command “localeconfig” as explained in the below article to see if the issue is corrected.

https://www.cisco.com/c/en/us/support/docs/security/email-security-appliance/118501-qa-esa-00.html

This is also listed under under the below defects with a few other workarounds:

https://bst.cloudapps.cisco.com/bugsearch/bug/CSCul48268/?reffering_site=dumpcr

https://bst.cloudapps.cisco.com/bugsearch/bug/CSCva96465/?reffering_site=dumpcr

The issue is known to be with email clients such as Windows based Microsoft Outlook based on how they interpret a certain type of MIME encoding.

When the ESA can't directly insert the stamping, it will fall back to creating a separate MIME part that Outlook has chosen not to support. The separate MIME part that the ESA inserts is an RFC 2183 Content-Disposition: inline MIME part, which signals the intended presentation method of combining the disclaimer with the original message. Some email clients, such as Thunderbird and even Outlook for Mac, respect this header directive, but unfortunately there’s a design decision in Outlook for Windows which ignores this header.

Regards,

Libin Varghese

[mewi]

Hi,

I tired to user localconfig, but had no success.

My solution is to put the disclaimer away from ESA.

Now the Disclaimer ist attached by Exchange2016 and I have no problems.

Thank you and Best Regards