| Summary: | HTML-only email rendered as plain text | ||
|---|---|---|---|
| Product: | [Applications] trojita | Reporter: | Luke-Jr <luke-jr+kdebugs> |
| Component: | Desktop GUI | Assignee: | Trojita default assignee <trojita-bugs> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | major | Keywords: | triaged |
| Priority: | NOR | ||
| Version First Reported In: | git | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: | Raw email | ||
Created attachment 96517 [details]
Raw email
Please attach the data that your IMAP server returns in the BODYSTRUCTURE for this message. Here's how to do it: 1) Activate logging into an on-disk file (IMAP -> Debugging -> Log into ...). 2) Create a new mailbox just for this new e-mail. 3) Copy this message into that mailbox. 4) Open that mailbox. 5) Attach the log. I don't really want to mess with my folders or mailbox... Isn't there some cleaner way to run the command? No. You can try to grep the relevant data from the full log, but you won't like doing that. What's the problem about adding a subdir, copy the mail there, open the dir, dump the log and then removing the dir again? That's not nearly as troublesome. I assume Jan requires it to figure whether trojita messes network replies or the server returns the html part as text/plain. I'd expect the latter and the question is then whether trojita would better post-inspect the content-type field to "fix" that - however, there's no point in doing that if there's actually a bug in reply handling, so please provide the log data. In order to know whether the bug is in Trojita or somewhere else, we need the raw BODYSTRUCTURE response from your IMAP server. The steps above are an example on how to get one (and as Thomas suggested, it's trivial to remove that extra folder afterwards). Please reopen this bug when you've attached the requested log. Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |
Message has the header Content-Type: text/html; charset="iso-8859-1" But the HTML is displayed as plain text, not rendered as HTML. Reproducible: Always