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

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

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 ot

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 t

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. > Mu

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 f

Re: Creating HTML emails with mutt

Sorry, I'm coming into this late. Early on, Kevin McCarthy said: Native support for multipart/alternative composition isn't in my todo list. Too bad -- that would be conceptually clean, to generate multipart/alternative as part of composition. Mutt runs an external text editor to compose p

Re: Creating HTML emails with mutt

> […] 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

Re: Creating HTML emails with mutt

Regarding the following, written by "martin f krafft" on 2019-11-02 at 23:40 Uhr +1300: How does this message fare? I’ve hacked up my script so that it actually keeps the ‘>’ even in the HTML, but uses CSS to hide it. Yeah, so I am not convinced at all, because all the html2text converters w

Re: Creating HTML emails with mutt

Regarding the following, written by "Martin Trautmann" on 2019-11-02 at 10:22 Uhr +0100: However, the usage of blockquote within HTML is something where there is not necessarily a proper way of handling this - Thunderbird does not do it properly, as you see above. How does handle html itself n

Re: Creating HTML emails with mutt

On 19-11-01 11:37, martin f krafft wrote: > Regarding the following, written by “Stefan Hagen” on 2019-11-01 at > 08:53 Uhr +0100: > > While I was able to just write an email and send it, it is now a > process of carefully “coding” an email, previewing, correcting, > previewing, sendin

Re: Creating HTML emails with mutt

On 2019-11-01, Stefan Hagen wrote: > >> . > > This is interesting - I'm trying this... > > I'm using this MIMEBellish script to transform plaintext mail to > multipart mail with HTML for a few years and it works quite well: > http:/

Re: Creating HTML emails with mutt

Regarding the following, written by "Stefan Hagen" on 2019-11-01 at 08:53 Uhr +0100: While I was able to just write an email and send it, it is now a process of carefully "coding" an email, previewing, correcting, previewing, sending... There's a lot of good things to be said about carefully

Re: Creating HTML emails with mutt

Regarding the following, written by "Kevin J. McCarthy" on 2019-11-01 at 14:45 Uhr +0800: I've merged the branch into master. For those who want to give it a try, please see the documentation under "MIME Multipart/Alternative"

Re: Creating HTML emails with mutt

Kevin J. McCarthy wrote: On Tue, Oct 29, 2019 at 06:28:34PM +0800, Kevin J. McCarthy wrote: I'll be working on this in the 'kevin/multipart-alternative' branch, but just fyi that I force-push to my development branches, and they are usually "work in progress". I've merged the branch into mast

Re: Creating HTML emails with mutt

On Tue, Oct 29, 2019 at 06:28:34PM +0800, Kevin J. McCarthy wrote: I'll be working on this in the 'kevin/multipart-alternative' branch, but just fyi that I force-push to my development branches, and they are usually "work in progress". I've merged the branch into master. For those who want to

Re: Creating HTML emails with mutt

On Thu, Oct 31, 2019 at 10:20:21AM +, John Long wrote: > On Wed, 30 Oct 2019 15:49:05 -0500 > Derek Martin wrote: > > > On Wed, Oct 30, 2019 at 11:31:21AM +, John Long wrote: > > > That doesn't really help. From my point the issue is not only what I > > > have to configure or what can be

Re: Creating HTML emails with mutt

On Thu, Oct 31, 2019 at 11:43:07AM +, John Long wrote: > On Thu, 31 Oct 2019 23:47:38 +1300 > martin f krafft wrote: > > > Regarding the following, written by "John Long" on 2019-10-31 at > > 10:30 Uhr +: > > >1. Commonly done != standard. There are standards for things like > > >MIME, PO

Re: Creating HTML emails with mutt

On Thu 31 Oct 2019 09:24, martin f krafft put forth the proposition: > Regarding the following, written by "Dave Woodfall" on 2019-10-30 at 11:25 > Uhr +: > > When messages turn up with no plain text part to them at all, or one > > that's completely useless, it's wrong. > > I'd guess we all a

Re: Creating HTML emails with mutt

I'm uninterested about this thread now. -- 存在于未知的空间

Re: Creating HTML emails with mutt

On Thu, 31 Oct 2019 23:47:38 +1300 martin f krafft wrote: > Regarding the following, written by "John Long" on 2019-10-31 at > 10:30 Uhr +: > >1. Commonly done != standard. There are standards for things like > >MIME, POP3, IMAP etc. I'm not aware of ANSI, ISO, IETF standards > >that say that

Re: Creating HTML emails with mutt

On Thu, 31 Oct 2019 23:49:37 +1300 martin f krafft wrote: > Regarding the following, written by "John Long" on 2019-10-31 at > 10:17 Uhr +: > >> The approach Kevin proposed is completely HTML-agnostic and leaves > >> it up to the user to provide an external tool that provides the > >> HTML. M

Re: Creating HTML emails with mutt

Regarding the following, written by "John Long" on 2019-10-31 at 10:17 Uhr +: The approach Kevin proposed is completely HTML-agnostic and leaves it up to the user to provide an external tool that provides the HTML. Mutt then just does the required MIME-handling, which is clearly within the

Re: Creating HTML emails with mutt

Regarding the following, written by "John Long" on 2019-10-31 at 10:30 Uhr +: 1. Commonly done != standard. There are standards for things like MIME, POP3, IMAP etc. I'm not aware of ANSI, ISO, IETF standards that say that HTML email is a thing. Quoting the HTML RFC from 1995: "The Hypert

Re: Creating HTML emails with mutt

On Wed, 30 Oct 2019 16:29:31 -0500 Derek Martin wrote: > On Wed, Oct 30, 2019 at 11:29:31AM +, John Long wrote: > > > I don’t think this is about right and wrong, and not only because > > > there is no objectivity. multipart/alternative is an accepted > > > standard, and so is HTML. You might

Re: Creating HTML emails with mutt

On Wed, 30 Oct 2019 15:49:05 -0500 Derek Martin wrote: > On Wed, Oct 30, 2019 at 11:31:21AM +, John Long wrote: > > That doesn't really help. From my point the issue is not only what I > > have to configure or what can be configured, but also how much code > > is behind doing that. Less code

Re: Creating HTML emails with mutt

On Thu, 31 Oct 2019 09:29:23 +1300 martin f krafft wrote: > Regarding the following, written by “John Long” on 2019-10-30 at > 11:31 Uhr +: > > > > From my point the issue is not only what I have to configure or > > what can be configured, but also how much code is behind doing > > that. Les

Re: Creating HTML emails with mutt

On Wed, Oct 30, 2019 at 11:29:31AM +, John Long wrote: > > I don’t think this is about right and wrong, and not only because > > there is no objectivity. multipart/alternative is an accepted > > standard, and so is HTML. You might not like how things have > > developed, and neither do I, but th

Re: Creating HTML emails with mutt

On Wed, Oct 30, 2019 at 11:31:21AM +, John Long wrote: > That doesn't really help. From my point the issue is not only what I > have to configure or what can be configured, but also how much code is > behind doing that. Less code is easier to manage than more code. I > can't see the benefit of

Re: Creating HTML emails with mutt

On Tue, Oct 29, 2019 at 07:04:48PM +, John Long wrote: > > so you cater to people who have no idea, and cannot be bothered. > > Which is probably 99.9% of everybody in corp. offices worldwide. > > Don't get me wrong, I'm not advocating for HTML support in mutt. HTML > has absolutely no place

Re: Creating HTML emails with mutt

Regarding the following, written by “John Long” on 2019-10-30 at 11:31 Uhr +: From my point the issue is not only what I have to configure or what can be configured, but also how much code is behind doing that. Less code is easier to manage than more code. I can’t see the benefit of junking

Re: Creating HTML emails with mutt

Regarding the following, written by “Mark H. Wood” on 2019-10-30 at 08:22 Uhr -0400: Even Outlook seems incapable of badly damaging blocks of text, indented blocks of text, emphasis, underscore/italics, or lists. I think this is the perfect reason why mutt needs to learn creating multipart/alte

Re: Creating HTML emails with mutt

Regarding the following, written by “Dave Woodfall” on 2019-10-30 at 11:25 Uhr +: When messages turn up with no plain text part to them at all, or one that’s completely useless, it’s wrong. I’d guess we all agree on that point. We’re currently discussing the creation of multipart/alternativ

Re: Creating HTML emails with mutt

On 2019-10-30, Derek Martin wrote: > On Tue, Oct 29, 2019 at 10:31:19PM -, Grant Edwards wrote: >> On 2019-10-29, martin f krafft wrote: >> That's true (as I understood the problem, anyway). Fortunately, I >> never needed to send a signed message with an attachment (or just a >> signed messa

Re: Creating HTML emails with mutt

On Tue, Oct 29, 2019 at 10:31:19PM -, Grant Edwards wrote: > On 2019-10-29, martin f krafft wrote: > That's true (as I understood the problem, anyway). Fortunately, I > never needed to send a signed message with an attachment (or just a > signed message, AFAIR). Nobody I know would have the

Re: Creating HTML emails with mutt

On Mon, Oct 28, 2019 at 11:11:31PM +0100, Matthias Apitz wrote: > El día lunes, octubre 28, 2019 a las 04:50:40p. m. -0500, Derek Martin > escribió: > > > > FWIW, I (as a mutt user for 15++ years) do not need this. Thanks > > > > Perhaps not, but the fact that it keeps coming up here is pretty c

Re: Creating HTML emails with mutt

On 2019-10-30, Sean Greenslade wrote: > Of course there's massive selection bias in this list. No question > about that. I just wanted to point out that there definitely are > some younger Mutters out there. Though I tend to fall more on the > grumpy about HTML mails side of this argument, so may

Re: Creating HTML emails with mutt

On Wed, 30 Oct 2019 07:53:30 -0700 Sean Greenslade wrote: > Of course there's massive selection bias in this list. No question > about that. I just wanted to point out that there definitely are some > younger Mutters out there. Though I tend to fall more on the grumpy > about HTML mails side of t

Re: Creating HTML emails with mutt

On October 30, 2019 7:41:34 AM PDT, Patrick Shanahan wrote: >* Sean Greenslade [10-30-19 10:37]: >> On October 30, 2019 5:29:01 AM PDT, Patrick Shanahan > wrote: >> >* Mark H. Wood [10-30-19 08:26]: >> >> On Wed, Oct 30, 2019 at 11:37:43PM +1300, martin f krafft wrote: >> >> >I'd love to see

Re: Creating HTML emails with mutt

* Patrick Shanahan [10-30-19 10:42]: > * Sean Greenslade [10-30-19 10:37]: > > On October 30, 2019 5:29:01 AM PDT, Patrick Shanahan > > wrote: > > >* Mark H. Wood [10-30-19 08:26]: > > >> On Wed, Oct 30, 2019 at 11:37:43PM +1300, martin f krafft wrote: > > >> >I'd love to see some statisti

Re: Creating HTML emails with mutt

* Sean Greenslade [10-30-19 10:37]: > On October 30, 2019 5:29:01 AM PDT, Patrick Shanahan > wrote: > >* Mark H. Wood [10-30-19 08:26]: > >> On Wed, Oct 30, 2019 at 11:37:43PM +1300, martin f krafft wrote: > >> >I'd love to see some statistics about the age of mutt users. > >> > >> 62 > >

Re: Creating HTML emails with mutt

On October 30, 2019 5:29:01 AM PDT, Patrick Shanahan wrote: >* Mark H. Wood [10-30-19 08:26]: >> On Wed, Oct 30, 2019 at 11:37:43PM +1300, martin f krafft wrote: >> >I'd love to see some statistics about the age of mutt users. >> >> 62 > >78 Not sure if these are guesses at the average or r

Re: Creating HTML emails with mutt

* Mark H. Wood [10-30-19 08:26]: > On Wed, Oct 30, 2019 at 11:37:43PM +1300, martin f krafft wrote: > >I'd love to see some statistics about the age of mutt users. > > 62 78 -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.orgopenSUSE Co

Re: Creating HTML emails with mutt

On Wed, Oct 30, 2019 at 11:37:43PM +1300, martin f krafft wrote: >I'd love to see some statistics about the age of mutt users. 62 -- Mark H. Wood Lead Technology Analyst University Library Indiana University - Purdue University Indianapolis 755 W. Michigan Street Indianapolis, IN 46202 317-

Re: Creating HTML emails with mutt

On Wed, Oct 30, 2019 at 12:57:59PM +1300, martin f krafft wrote: >Regarding the following, written by "Martin Trautmann" on 2019-10-30 at >00:14 Uhr +0100: > > That's such a strange thing. > [...] > since they never learned, how proper threading and quoting could > have

Re: Creating HTML emails with mutt

On Wed, 30 Oct 2019 23:37:43 +1300 martin f krafft wrote: > Regarding the following, written by “Nuno Silva” on 2019-10-30 at > 09:21 Uhr +: > > > > There are users who don’t need text/html. It’s okay to want some > > way to use HTML for e-mail in mutt, but I’d say it’s not okay to > > say e

Re: Creating HTML emails with mutt

On Wed 30 Oct 2019 23:53, martin f krafft put forth the proposition: > Regarding the following, written by "Dave Woodfall" on 2019-10-30 at 10:05 > Uhr +: > > I don't think embracing wrong email practices is the way forward. > > I don't think this is about right and wrong, and not only becaus

Re: Creating HTML emails with mutt

On Wed, 30 Oct 2019 23:53:40 +1300 martin f krafft wrote: > Regarding the following, written by “Dave Woodfall” on 2019-10-30 at > 10:05 Uhr +: > > > > I don’t think embracing wrong email practices is the way forward. > > I don’t think this is about right and wrong, and not only because > t

Re: Creating HTML emails with mutt

Regarding the following, written by “Dave Woodfall” on 2019-10-30 at 10:05 Uhr +: I don’t think embracing wrong email practices is the way forward. I don’t think this is about right and wrong, and not only because there is no objectivity. multipart/alternative is an accepted standard, and s

Re: Creating HTML emails with mutt

Regarding the following, written by “Nuno Silva” on 2019-10-30 at 09:21 Uhr +: There are users who don’t need text/html. It’s okay to want some way to use HTML for e-mail in mutt, but I’d say it’s not okay to say everybody needs it. I’d love to see some statistics about the age of mutt user

Re: Creating HTML emails with mutt

On Wed 30 Oct 2019 12:57, martin f krafft put forth the proposition: > Regarding the following, written by "Martin Trautmann" on 2019-10-30 at 00:14 > Uhr +0100: > > That's such a strange thing. > > […] > > since they never learned, how proper threading and quoting could have > > worked? > > 78 c

Re: Creating HTML emails with mutt

On 2019-10-29, martin f krafft wrote: [...] > Society has moved on, and we all risk sounding like grumpy old folks > reminiscing at the times when everyone knew what netiquette was if we > don't embrace the progress that's been happening around us. And > text/html is part of that progress, whether

Re: Creating HTML emails with mutt

* Grant Edwards [10-29-19 18:27]: > On 2019-10-29, Patrick Shanahan wrote: > > * Grant Edwards [10-29-19 13:10]: > > > >> Muttdown (a "sendmail" filter) which creates mutlipart alternative > >> html/text messages is the only reason I've been able to continue to > >> use mutt for the past 5-6 yea

Re: Creating HTML emails with mutt

Regarding the following, written by “Martin Trautmann” on 2019-10-30 at 00:14 Uhr +0100: That’s such a strange thing. […] since they never learned, how proper threading and quoting could have worked? 78 characters wide text/plain is just not the lowest common denominator anymore. I am not going

Re: Creating HTML emails with mutt

On 19-10-29 18:09, Grant Edwards wrote: > Muttdown (a "sendmail" filter) which creates mutlipart alternative > html/text messages is the only reason I've been able to continue to > use mutt for the past 5-6 years. About 90% of the people to whom I > send email can't deal with plaintext only. The

Re: Creating HTML emails with mutt

On 2019-10-29, martin f krafft wrote: > [/home/grante/bin/unmime.py: html rendered using w3m] > Regarding the following, written by “Grant Edwards” on 2019-10-29 at 17:09 Uhr > -: > > Muttdown (a “sendmail” filter) which creates mutlipart alternative html/ > text messages is the only r

Re: Creating HTML emails with mutt

On 2019-10-29, (Nuno Silva) wrote: > On 2019-10-29, John Long wrote: > >> On Tue, 29 Oct 2019 14:50:05 -0400 >> Patrick Shanahan wrote: >> >>> * Grant Edwards [10-29-19 13:10]: > [...] >>> > Muttdown (a "sendmail" filter) which creates mutlipart alternative >>> > html/text messages is the only

Re: Creating HTML emails with mutt

On 2019-10-29, Patrick Shanahan wrote: > * Grant Edwards [10-29-19 13:10]: > >> Muttdown (a "sendmail" filter) which creates mutlipart alternative >> html/text messages is the only reason I've been able to continue to >> use mutt for the past 5-6 years. About 90% of the people to whom I >> send

Re: Creating HTML emails with mutt

Regarding the following, written by “Grant Edwards” on 2019-10-29 at 17:09 Uhr -: Muttdown (a “sendmail” filter) which creates mutlipart alternative html/text messages is the only reason I’ve been able to continue to use mutt for the past 5-6 years. Muttdown suffers from the same problems r

Re: Creating HTML emails with mutt

On 2019-10-29, John Long wrote: > On Tue, 29 Oct 2019 14:50:05 -0400 > Patrick Shanahan wrote: > >> * Grant Edwards [10-29-19 13:10]: [...] >> > Muttdown (a "sendmail" filter) which creates mutlipart alternative >> > html/text messages is the only reason I've been able to continue to >> > use mu

Re: Creating HTML emails with mutt

On Tue, 29 Oct 2019 14:50:05 -0400 Patrick Shanahan wrote: > * Grant Edwards [10-29-19 13:10]: > > On 2019-10-28, Matthias Apitz wrote: > > > El día lunes, octubre 28, 2019 a las 04:50:40p. m. -0500, Derek > > > Martin escribió: > > >> > FWIW, I (as a mutt user for 15++ years) do not need th

Re: Creating HTML emails with mutt

* Grant Edwards [10-29-19 13:10]: > On 2019-10-28, Matthias Apitz wrote: > > El día lunes, octubre 28, 2019 a las 04:50:40p. m. -0500, Derek Martin > > escribió: > > > >> > FWIW, I (as a mutt user for 15++ years) do not need this. Thanks > >> > >> Perhaps not, but the fact that it keeps coming

Re: Creating HTML emails with mutt

On 2019-10-28, Matthias Apitz wrote: > El día lunes, octubre 28, 2019 a las 04:50:40p. m. -0500, Derek Martin > escribió: > >> > FWIW, I (as a mutt user for 15++ years) do not need this. Thanks >> >> Perhaps not, but the fact that it keeps coming up here is pretty clear >> indication that it's a

Re: Creating HTML emails with mutt

On Tue, Oct 29, 2019 at 10:15:22PM +1300, martin f krafft wrote: Regarding the following, written by "Kevin J. McCarthy" on 2019-10-29 at 12:58 Uhr +0800: instead of the script returning content of a specific type, and thus always with the same content type (unless the filter script is interac

Re: Creating HTML emails with mutt

Regarding the following, written by “Kevin J. McCarthy” on 2019-10-29 at 12:58 Uhr +0800: The part creation (and removal) will be in Mutt’s pipeline, and so will follow normal processing that Mutt does. That include encoding, delimiters, charset conversion, etc. So I would like the script to sim

Re: Creating HTML emails with mutt

On Tue, Oct 29, 2019 at 12:41:44PM +1300, martin f krafft wrote: Script output would be the content-type, a blank line, then the generated content. This makes me itch, but I cannot really devise a better approach. I want to say that the script needs to return the complete MIME part, including

Re: Creating HTML emails with mutt

Matthias Apitz writes: > So, run mutt in an unicode-rxvt terminal. It presents URLs underlined > and click-able. I do so and sometimes I do hate it: you click into your Definitely not by default. I'm using rxvt-unicode, and I've tried the "matcher" and "selection" extensions but neither one worked

Re: Creating HTML emails with mutt

El día lunes, octubre 28, 2019 a las 06:33:19p. m. -0400, José María Mateos escribió: > On Mon, Oct 28, 2019 at 11:11:31PM +0100, Matthias Apitz wrote: > >Well, do you speak for you or for a 'lot of people'? Who they are? > >I speak only for my own interests (as I said: I do not need this). > >

Re: Creating HTML emails with mutt

El día martes, octubre 29, 2019 a las 11:19:43a. m. +1300, martin f krafft escribió: > Regarding the following, written by "Matthias Apitz" on 2019-10-28 at 23:11 > Uhr +0100: > >Well, do you speak for you or for a 'lot of people'? Who they are? > >I speak only for my own interests (as I said:

Re: Creating HTML emails with mutt

> 2. The ability to natively display a subset of HTML (the same subset) >with the ability to trigger links to open in a browser (or perhaps >execute an arbitrary configured command). Modern terminal windows >can handle all of the formatting required to do just this much... elinks -dum

Re: Creating HTML emails with mutt

Hi Kevin, Thanks for sharing your thoughts and plans on this. This all reads really well, and I think it would go most of the way towards the ideal solution. I have a couple of points/questions about some of the things you propose: If there were an error sending, the alternative would be s

Re: Creating HTML emails with mutt

On Mon, Oct 28, 2019 at 10:40:16PM +, Chris Green wrote: Isn't that handled by your terminal program? Mine certainly allows one to right click on any URL to open it. Not if the URL spans several lines. I think it's a common issue across several terminal programs and last time I read about

Re: Creating HTML emails with mutt

On Mon, Oct 28, 2019 at 06:33:19PM -0400, José María Mateos wrote: > On Mon, Oct 28, 2019 at 11:11:31PM +0100, Matthias Apitz wrote: > > Well, do you speak for you or for a 'lot of people'? Who they are? > > I speak only for my own interests (as I said: I do not need this). > > Talking for myself,

Re: Creating HTML emails with mutt

On Mon, Oct 28, 2019 at 11:11:31PM +0100, Matthias Apitz wrote: Well, do you speak for you or for a 'lot of people'? Who they are? I speak only for my own interests (as I said: I do not need this). Talking for myself, I really don't need point 1 (composing of HTML messages), but number 2, open

Re: Creating HTML emails with mutt

Regarding the following, written by "Matthias Apitz" on 2019-10-28 at 23:11 Uhr +0100: Well, do you speak for you or for a 'lot of people'? Who they are? I speak only for my own interests (as I said: I do not need this). Matthias, any such feature would of course be optional, and probably def

Re: Creating HTML emails with mutt

El día lunes, octubre 28, 2019 a las 04:50:40p. m. -0500, Derek Martin escribió: > > FWIW, I (as a mutt user for 15++ years) do not need this. Thanks > > Perhaps not, but the fact that it keeps coming up here is pretty clear > indication that it's a feature that would be useful to a lot of > peop

Re: Creating HTML emails with mutt

On Mon, Oct 28, 2019 at 10:06:18PM +0100, Matthias Apitz wrote: > El día lunes, octubre 28, 2019 a las 03:59:01p. m. -0500, Derek Martin > escribió: > > > FWIW, my two biggest wishlist items for Mutt are: > > > > 1. the ability to create and send at least simple HTML messages, with > >or wit

Re: Creating HTML emails with mutt

El día lunes, octubre 28, 2019 a las 03:59:01p. m. -0500, Derek Martin escribió: > FWIW, my two biggest wishlist items for Mutt are: > > 1. the ability to create and send at least simple HTML messages, with >or without multipart alternatives, specifically for basic text >formatting (bold,

Re: Creating HTML emails with mutt

On Sun, Oct 27, 2019 at 10:02:38AM +0800, Kevin J. McCarthy wrote: > On Sat, Oct 26, 2019 at 11:16:25AM +1300, martin f krafft wrote: > Native support for multipart/alternative composition isn't in my todo list. > However, I do have a plan to allow external filter generation of the > alternative.

Re: Creating HTML emails with mutt

On Sat, Oct 26, 2019 at 11:16:25AM +1300, martin f krafft wrote: I need to start sending out `text/html` alternative parts to my messages with mutt. Hi martin, Native support for multipart/alternative composition isn't in my todo list. However, I do have a plan to allow external filter gener

Re: Creating HTML emails with mutt

Regarding the following, written by “Amit Ramon” on 2019-10-26 at 09:03 Uhr +0300: A few years back I developed a simple filter that does, more or less, what you’re looking for. […] https://github.com/amitramon/plainMail2HTML Thanks for the pointer. If messages aren’t PGP/MIME-signed, then both

Re: Creating HTML emails with mutt

martin f krafft [2019-10-26 11:16 +1300]: Folks, I need to start sending out text/html alternative parts to my messages with mutt. However, this is a rabbit hole, so if you’re afraid of those, stop reading now. My requirements are, in decreasing order of priority: 1. Compatible with all Gmai

Re: Creating HTML emails with mutt

Regarding the following, written by “José María Mateos” on 2019-10-25 at 18:32 Uhr -0400: If you want to accomplish this, wouldn’t it be enough not to wrap the text? That way the client/screen will do its own wrapping, no need to go the HTML way. That would indeed take care of the extraneous li

Re: Creating HTML emails with mutt

On Sat, 26 Oct 2019 11:16:25 +1300 martin f krafft wrote: > In any case, given how email has changed in the last 20 years, and how > text/plain messages are causing display issues across different device types > (e.g. they are not “responsive”) If you want to accomplish this, wouldn't it be eno