Re: Creating HTML emails with mutt
Regarding the following, written by "Kurt Hackenberg" on 2019-11-03 at 00:11 Uhr -0400: Mutt runs an external text editor to compose plain text; it could do the same for this -- run some external composition program that would return both HTML and plain text. There is nothing stopping you from setting `$editor` to a HTML editor, and defining `$content_type` to be `text/html`, and then using Kevin's `multipart/alternative` functionality to generate a `text/plain` part. The only issue with this approach would be that you'd now have the `text/plain` part after the `text/html`, which means that dumb clients such as Gmail and Outlook and Thunderbird too would actually prefer the plain-text message over the HTML one. Getting mutt to sort those into order might get really messy though, and while I think it it wouldn't be too hard to ensure that `text/html` always comes after `text/plain`, anything beyond that would require a new command, but `alternative_order` is already taken for something else, and cannot be reused, I don't think. -- @martinkrafft | https://riot.im/app/#/room/#madduck:madduck.net "no work of art ever puts forward views. views belong to people who are not artists." -- oscar wilde spamtraps: madduck.bo...@madduck.net digital_signature_gpg.asc Description: Digital GPG signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)
Re: Creating HTML emails with mutt
On Sat, Nov 02, 2019 at 12:31:29PM -0400, Patrice Levesque wrote: > > > […] virtually all of the people who use mutt either as their only > > email client or along with others, chose mutt because of its > > simplicity. > > People who want a simple text mail client will use Alpine or similar. > Mutt's possibly the most “complicated” text MUA. > > I don't use mutt because of its “simplicity”, I use it because of its > power and flexibility. Yes. There is simple and then there is simple. I choose Mutt because I can adjust it to be simple in the ways I want it to be simple, and sophisticated in the ways I want it to be sophisticated. That exacts a cost in configuration complexity which I'm quite willing to pay. I like that Mutt presents emails simply. It ignores all the fancy to-the-pixel formatting, pointless images, distracting backgrounds, and flashing multicolored nonsense. I find that reading mail with Mutt is more restful than with other MUAs. Occasionally I do encounter a message whose text/plain part says only "you must enable HTML mail to read this message." I interpret this as "you do not need or want to read this message," and I happily hit "d" and move on. I like that Mutt can be configured to handle signing and encryption well using the tools that I use for these operations in other contexts. I like that Mutt gives me ready access to the structure of MIME messages. I like that Mutt understands me when I add an attachment, and sets the Content-Type correctly instead of just blowing it off as application/octet-stream. I like that Mutt just asks me what I want to do with this funky attachment, instead of trusting it and performing it without my leave. I like that Mutt makes me stop and think about following that URL. I like that Mutt lets me choose my editor and just accepts what I have composed with it. For some messages I really need EMACS. I like that Mutt treats me as someone who takes the trouble to understand the medium, and facilitates my use of that knowledge. Most of that was not simple to achieve but, having achieved it, Mutt makes sending and reading email *my way* simple for me, and that is the simplicity which I value most highly in a MUA. What it boils down to is that Mutt is a tool rather than an appliance, and I prefer tools. An appliance does the work for me, the same way it does it for everyone else; a tool enhances my ability to do the work using my skills and expressing my intent. -- Mark H. Wood Lead Technology Analyst University Library Indiana University - Purdue University Indianapolis 755 W. Michigan Street Indianapolis, IN 46202 317-274-0749 www.ulib.iupui.edu signature.asc Description: PGP signature
Re: Creating HTML emails with mutt
* Mark H. Wood [11-03-19 07:58]: > On Sat, Nov 02, 2019 at 12:31:29PM -0400, Patrice Levesque wrote: > > > > > […] virtually all of the people who use mutt either as their only > > > email client or along with others, chose mutt because of its > > > simplicity. > > > > People who want a simple text mail client will use Alpine or similar. > > Mutt's possibly the most “complicated” text MUA. > > > > I don't use mutt because of its “simplicity”, I use it because of its > > power and flexibility. > > Yes. There is simple and then there is simple. I choose Mutt because > I can adjust it to be simple in the ways I want it to be simple, and > sophisticated in the ways I want it to be sophisticated. That exacts > a cost in configuration complexity which I'm quite willing to pay. [...] > What it boils down to is that Mutt is a tool rather than an appliance, > and I prefer tools. An appliance does the work for me, the same way > it does it for everyone else; a tool enhances my ability to do the work > using my skills and expressing my intent. thankyou. you have expressed most elegantly my feelings and adjustments to utilize mutt to read and send email over the last +20 years and I hope another 20 or so. and we are neighbors and I used to photograph for IUPUI men's soccer. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.orgopenSUSE Community Memberfacebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode
Re: Creating HTML emails with mutt
On Sun, Nov 03, 2019 at 07:56:34AM -0500, Mark H. Wood wrote: I like that Mutt presents emails simply. It ignores all the fancy to-the-pixel formatting, pointless images, distracting backgrounds, and flashing multicolored nonsense. I find that reading mail with Mutt is more restful than with other MUAs. Occasionally I do encounter a message whose text/plain part says only "you must enable HTML mail to read this message." I interpret this as "you do not need or want to read this message," and I happily hit "d" and move on. My bank still sends me this in the text/plain part of the message every month: Your %%MONTH%% %%ACCOUNTTYPE%% %%STATEMENTRECEIPT%% is ready But yes, I've also learned to ignore it. Also, I also want to thank you for writing this down. All the reasons why I use mutt boil down to essentially this. Cheers, -- José María (Chema) Mateos || https://rinzewind.org/
Re: Creating HTML emails with mutt
Derek Martin wrote: > TBH most of the time, if I really need to see what's in an HTML mail, > I just bounce it to gmail. But sometimes that doesn't work either due > to DNS-based spam prevention. Forwarding the email as an attachment rather than bouncing it should solve that. cheers, raf
Re: Creating HTML emails with mutt
* raf [11-03-19 18:23]: > Derek Martin wrote: > > > TBH most of the time, if I really need to see what's in an HTML mail, > > I just bounce it to gmail. But sometimes that doesn't work either due > > to DNS-based spam prevention. > > Forwarding the email as an attachment rather than bouncing it should solve > that. If I wish to view an html email that w3m fails to render satisfactory, I copy the html portion to a particular location with a key combo/mutt-macro and open it with firefox or waterfox or seamonkey or ... I do not post html, even from gmail. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.orgopenSUSE Community Memberfacebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode
