Modifying Content-Type on inbound mail

[freeborn99]

I am trying to replicate an issue that we have on inbound mail that arrives with content-type us-ascii.  I want to replicate this problem so I have have created a filter that will be applied to emails arriving from a particular user and applies the following action

edit-header-text("Content-Type", "iso-8859-1", "us-ascii")

but it does not modify the Content-Type.

Any thoughts?

[Robert Sherwin]

I don't think that edit-header-text is what you want.  Can you provide a little more insight for the message headers and action you are trying to change/correct?

Checking the user guide:

The edit-header-text action allows you to rewrite specified header text using the regular expression substitution function. The filter matches the regular expression within the header and replaces it with a regular expression you specify.

For example, an email contains the following subject header:
Subject: SCAN Marketing Messages

The following filter removes the “SCAN” text, and leaves the text, “Marketing Messages”, in the header:

Remove_SCAN: if true
   {
edit-header-text (‘Subject’, ‘^SCAN\\s*’,’’);
}

After the filter processes the message, it returns the following header:
Subject: Marketing Messages

[freeborn99]

Actually I am trying to replicate an issue.  We have an external party that some meeting requests arrive the have a char-set of us-ascii and the message does not get recognized as a meeting.  (I beleive this is an issue in O365)

Anyways I was trying to replicate this issue.  What I did discover is my rule above does work....but strangley I can only modify Content-Type for emails.  It ignores the content type of a calendar event.