Hello everyone,
our rt3 installation (3.0.11-5, debian) does not assign the correct
content-type to messages, which are non-multipart html.
Example (as being produced from web.de’s web frontend):
[…]
MIME-Version: 1.0
Content-Type: text/html; charset=“iso-8859-1”
Organization: http://freemail.web.de/
rt does convert the html-file into an attachment, but doesn’t transfer
the content-type corrently.
Inside rt, the file is only avaiable as “text/plain”, while it should
keep “text/html”, which causes the browser not to parse the markup.
Is this a known issue or a local configuration problem?
Maybe, it is possible to convert html messages to plain text via lyns
or perl (html2text)?
Thanks,
Franz Georg Köhler
No replys on this?
Is this behaviour reproducible with the vanilla rt or is it debian
related?
Franz Georg Köhler wrote:
Hello everyone,
our rt3 installation (3.0.11-5, debian) does not assign the correct
content-type to messages, which are non-multipart html.
Example (as being produced from web.de’s web frontend):
[…]
MIME-Version: 1.0
Content-Type: text/html; charset=“iso-8859-1”
Organization: http://freemail.web.de/
rt does convert the html-file into an attachment, but doesn’t transfer
the content-type corrently.
Inside rt, the file is only avaiable as “text/plain”, while it should
keep “text/html”, which causes the browser not to parse the markup.
Is this a known issue or a local configuration problem?
It’s not an issue, it’s right behaviour. Protection from cross site
scripting. Check RT Config.pm file there is special option that enable
text/html content type.
Maybe, it is possible to convert html messages to plain text via lyns
or perl (html2text)?
In 3.0.x you can use html2text outside of RT in your mail delivery
chain. RT-3.2.x and higher show stripped HTML parts in line so you may
want to upgrade.