From: "inwit" <inwit@sindominio.net>
To: "martin f krafft" <madduck@madduck.net>,
"David Bremner" <david@tethera.net>
Cc: notmuch@notmuchmail.org
Subject: Re: Forwarding inline html mails
Date: Tue, 07 Dec 2021 23:08:44 +0100 [thread overview]
Message-ID: <CG9EUQCL9DB5.1N7YL3GPMOKBZ@bisio> (raw)
In-Reply-To: <YavEDuK7b/V7jzFX@lotus.rw.madduck.net>
On Sat Dec 4, 2021 at 8:39 PM CET, martin f krafft wrote:
> I use
> [htmldump](https://git.madduck.net/etc/mutt.git/blob/HEAD:/.config/mutt/htmldump)
> to render HTML mail to markdown, and then mutt's new multipart/alternative
> handling and [this
> script](https://git.madduck.net/etc/mutt.git/blob/HEAD:/.config/mutt/markdown2html)
> to turn markdown back into HTML on sending, and this will also take care of
> forwarded emails to a suitable degree.
Thanks! However, if I understood it correctly, this means sending mail in html,
and I was hoping to forward them in plain text, by stripping html and leaving a
legible txt form (such as the one displayed in notmuch-show).
Regards,
>
> --
> @martinkrafft | https://matrix.to/#/#madduck:madduck.net
>
> "when a woman marries again it is because she detested her first
> husband.
> when a man marries again it is because he adored his first wife.
> women try their luck; men risk theirs."
> -- oscar wilde
>
> spamtraps: madduck.bogus@madduck.net
next prev parent reply other threads:[~2021-12-07 22:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-04 13:50 Forwarding inline html mails inwit
2021-12-04 15:42 ` David Bremner
2021-12-04 16:10 ` inwit
2021-12-04 19:05 ` David Bremner
2021-12-07 22:24 ` inwit
2021-12-08 0:30 ` David Bremner
2021-12-08 0:42 ` David Bremner
2021-12-04 19:39 ` martin f krafft
2021-12-07 22:08 ` inwit [this message]
2021-12-08 0:03 ` martin f krafft
2021-12-08 0:51 ` David Bremner
2021-12-08 17:03 ` inwit
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CG9EUQCL9DB5.1N7YL3GPMOKBZ@bisio \
--to=inwit@sindominio.net \
--cc=david@tethera.net \
--cc=madduck@madduck.net \
--cc=notmuch@notmuchmail.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).