<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p><br>
</p>
<div class="moz-cite-prefix">On 25/01/2021 09:08, Rupert Gallagher
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:1SOZayQfgWE8AYnHJEPMsPlrxEKpg27CfdPMf_09TnuGK-Ti6cfL1DZl91gNKmAFI6TuRFfUvs1rRgJchXXzkigAPefkYrMIkHc4EGNJzWY=@protonmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
It would be useful to automatically de-HTML e-mails, but this is
not a task for dovecot. Even more useful would be to deprecate
HTML in e-mails.<br>
</blockquote>
<p>Why would it be useful to deprecate HTML in emails? Presumably
you're arguing for an alternative, more restricted markup language
such as Enriched Text[1], Markdown[2]? Mutt already supports
Enriched Text, but is probably the most popular MUA which does.
I'm not aware of an MUA that natively renders Markdown bodies -
most of the tutorials I see about that involve composing the
message in Markdown and then converting it to HTML for sending -
but to be honest, at this point the effort is a bit late.
Realistically, how are you going to render that Markdown text in a
Graphical MUA? Either you're going to write a custom control which
renders the markup as styled text (that is, converts **bold** to a
bold-face font etc) or you're just going to run the Markdown
through a Markdown->HTML converter and pass it to a Web Browser
component (both the converter and the renderer are "solved
problems" so guess which solution developers would choose), in
which case, what's the point of going "around the houses"?<br>
</p>
<p><br>
</p>
<p>[1] <a class="moz-txt-link-freetext" href="https://en.wikipedia.org/wiki/Enriched_text">https://en.wikipedia.org/wiki/Enriched_text</a></p>
<p>[2] <a class="moz-txt-link-freetext" href="https://en.wikipedia.org/wiki/Markdown">https://en.wikipedia.org/wiki/Markdown</a><br>
</p>
<p><br>
</p>
<blockquote type="cite"
cite="mid:1SOZayQfgWE8AYnHJEPMsPlrxEKpg27CfdPMf_09TnuGK-Ti6cfL1DZl91gNKmAFI6TuRFfUvs1rRgJchXXzkigAPefkYrMIkHc4EGNJzWY=@protonmail.com"><br>
<br>
<br>
-------- Original Message --------<br>
On Jan 20, 2021, 13:58, @lbutlr < <a class="moz-txt-link-abbreviated" href="mailto:kremels@kreme.com">kremels@kreme.com</a>> wrote:
<blockquote class="protonmail_quote"><br>
<p dir="ltr">On 20 Jan 2021, at 04:33, Piotr Auksztulewicz
<a class="moz-txt-link-rfc2396E" href="mailto:dcml@hasiok.net"><dcml@hasiok.net></a> wrote:<br>
> On Wed, Jan 20, 2021 at 04:27:11AM -0700, @lbutlr wrote:<br>
>> set imap_pass = "lasH-hds[er$asd" # Not a real
password<br>
><br>
> Use single quotes around the password. Double quotes make
$asd to be<br>
> interpreted as shell variable and replaced with (most
likely) empty<br>
> string, so you get a shortened passwort in effect.</p>
<p dir="ltr">This worked, thank you.</p>
<p dir="ltr">Also… grrrrr. Who though expansion inside a
password string was a clever idea and can I introduce them to
a clue bat? :p</p>
<p dir="ltr">> PS. Also a mutt lover :-)</p>
<p dir="ltr">With the amount of HTML mail out there I really
don't understand how people are able to use it anymore. Now,
if I could get a 'stip html down to plain text' side function
to work…<br>
</p>
<p dir="ltr">script execution error (#127): sh: line 3: fortune:
command not found</p>
</blockquote>
</blockquote>
</body>
</html>