Convert HTML Question

Greg Rowe greg at
Thu Feb 16 15:19:37 GMT 2006

Hi Aaron,
 Does this rule differ than having a rule in the MailScanner.conf that looks
like this:

Convert HTML To Text = %rules-dir%/strip.html.rules

And the contents of "strip.html.rules":

To:  *  yes
FromOrTo:  default   no


The above rule is working and the message is being delivered properly, but
still contains the following in the message body after the HTML is stripped:

 > This is a multi-part message in MIME format.
 > ------_=_NextPart_001_01C63248.6B567FBD
 > Content-Type: text/plain;
 >   charset="US-ASCII"
 > Content-Transfer-Encoding: quoted-printable
 > This is a test page
 > ------_=_NextPart_001_01C63248.6B567FBD
 > Content-type: text/plain; charset="US-ASCII"
 > Content-Transfer-Encoding: quoted-printable
 > This is a test page
 > ------_=_NextPart_001_01C63248.6B567FBD--

The Paging service, right or wrong, is doing some check to determine if the
message contains HTML or MIME and is rejecting the message based on still
finding these MIME statements. If the Paging service returned some
informative message to the user that pointed them towards the HTML problem,
I wouldn't be as concerned. Unfortunately, all it returns is a Remote
protocol Error. Since I'm already using MailScanner to remove the HTML, I
was wondering if I could also remove the MIME and Content lines too ?


On 2/16/06 9:16 AM, "Aaron K. Moore" <amoore at> wrote:

> Greg,
> You need to set Non Spam Actions in your MailScanner.conf to be a rule
> set with rules like the following.
> To: pager at striphtml deliver
> FromOrTo: default deliver
> Check the documentation for more information on using rule sets.
> Greg Rowe wrote:
>> Greetings,
>>  I have an existing MailScanner installation running as a gateway for
>> multiple domains into backend mail servers. Current version is
>> 4.45.4, but planning to upgrade to 4.50.15 this weekend. One new
>> domain that the MailScanner systems accepts mail for gets relayed to
>> a vendor paging service after processing. The paging service can only
>> accept pure text messages and rejects any message containing MIME or
>> HTML. Unfortunately a large number of the people sending to this
>> domain are on OutLook and use HTML by default. The paging service
>> also returns a meaningless error message to the sender if it
>> encounters HTML or MIME tags.
>>  Using the Convert HTML To Text rule in MailScanner works great for
>> messages destined to that domain to strip the HTML, but the MIME tags
>> are still contained in the message, and message body text is repeated:
>> Any ideas as far as a best solution to stripping out all the MIME and
>> HTML and being left with just the message body text ?
>> Thanks,
>> Greg

More information about the MailScanner mailing list