Last modified: 2014-10-15 16:39:29 UTC
some text/plain parts are not displayed at all (but they do appear in other MUAs when bounced from OTRS) In this case it didn't really matter but I imagine it would sometimes cause confusion. test case: 2014062710022031 minimized test based on that ticket that should have the same issue: Content-Type: multipart/mixed; boundary="Boundary_(foo)" --Boundary_(foo) Content-type: text/plain; CHARSET=US-ASCII Content-transfer-encoding: 7BIT Most of the message... --Boundary_(foo) Content-type: image/png; name=image.png Content-transfer-encoding: base64 Content-disposition: inline; filename=image.png ... --Boundary_(foo) Content-type: text/plain; CHARSET=US-ASCII Content-transfer-encoding: 7BIT -- Robert. -- Robert Fulton --Boundary_(foo)--
Which MUA is this about? Can this be reproduced with other MUAs?
(In reply to Andre Klapper from comment #1) > Which MUA is this about? Can this be reproduced with other MUAs? The bug is in OTRS's rendering. (i.e. not in a message produced by OTRS, but by a message received by OTRS) The web interface has the wrong display for this ticket. (the last part is ignored) I guess this is similar to the bug where replies to some messages from OTRS don't show up in the web view. (it just shows the original instead of the new content) I thought we had a bug on that too...
