Freron MailMate

Comments and changes to this ticket

• 

  benny February 27th, 2015 @ 04:43 PM

  • State changed from “new” to “accepted”

  Ideally, this is how MailMate is supposed to work:

  • If a plain text body part exists in the email (it should) then that is used for forwarding/replying.
  • If no plain text body part exists then the HTML body part is converted to plain text (Markdown).

  In practice, it doesn't always work since some HTML messages are hard to convert and, especially for forwarding, MailMate some times gives up. I'm pretty sure there are also some bugs lurking, but I'm postponing looking into it until I can, hopefully soon, switch to this strategy:

  • Prefer plain text when possible.
  • When HTML is needed or the user explicitly requests HTML then the received HTML is inserted into the reply/forwarded message similar to how MailMate handles HTML signatures. The HTML is also converted to plain text for the plain text body part. The end result is essentially the same as seen with email clients with HTML editors except that I don't allow editing the forwarded/replied HTML.

  It is, of course, not as simple as that, but it's a relatively high priority to allow the user to handle HTML in a way that the correspondent does not notice that MailMate is mainly a plain text email client.

  There are various tickets touching various aspects of this issue, but I'll keep this one open as well until a solution exists :-)

  (I didn't know w3m.)

• You flagged this item as spam.
  

  Roy Crowder February 27th, 2015 @ 05:32 PM

  w3m and links are pretty common and is generally what mutt and alpine use to handle HTML. It generally works pretty well.

• 

  benny September 16th, 2016 @ 06:11 PM

  • State changed from “accepted” to “fixreleased”

  A solution very similar to what I describe above has now been implemented (and released).