[Esd-l] mangled mime type becomes text/plain (sanitizer 1.137)

[Morten Hemmingsson]

Having set sanitizer 1.137 up I got some problems with the mangled
mime type. When sending an .exe file, the filename and mime type gets
mangled differently using different clients, specifically for one
client I get Content-Type: text/plain instead of 
Content-Type: APPLICATION/DEFANGED.

In the example below I don't consider the file to be poisoned, I just
want the filename and mime type to get mangled, but even poisoned
files get mangled in this way.  

Browsing through the html-trap.procmail I only find  
Content-Type: TEXT/PLAIN whereas I get 
Content-Type: text/plain in the processed headers.
Where should I start looking?

/Morten

-- Original message --

--CXKrh5wV+/
Content-Type: text/plain; charset=us-ascii
Content-Description: message body text
Content-Transfer-Encoding: 7bit

fdgfdglkhfg

--CXKrh5wV+/
Content-Type: application/octet-stream
Content-Description: skoj
Content-Disposition: attachment;
        filename="funzip.exe"
Content-Transfer-Encoding: base64



-- Message after a pass through sanitizer --

X-Content-Security: [faraday] NOTIFY
X-Content-Security: [faraday] QUARANTINE
X-Content-Security: [faraday] REPORT: Trapped Windows executable attachment


--CXKrh5wV+/
Content-Type: text/plain; charset=us-ascii
Content-Description: message body text
Content-Transfer-Encoding: 7bit

fdgfdglkhfg

--CXKrh5wV+/
Content-Description: skoj
Content-Disposition: attachment; filename="funzip.9068DEFANGED-exe"
X-Content-Security: [faraday] original Content-Type was application/octet-stream
Content-Type: text/plain;
Content-Transfer-Encoding: base64