On Fri, Dec 27, 2024 at 23:41:39 -0500, hobie of RMN wrote:
For 20 years I've enjoyed Mutt as my primary mail reader. I used its 'bounce' feature to deal with HTML mails, sending them to a webmail
program on a different server. But now the jellyfish anti-spam daemon
won't allow me to do that; it rejects my bounced emails because "From:"
and "(envelope-from)" are not the same.
What's the best way to handle this?
It depends on what you want to do. For me, there are two different
modes of dealing with HTML email in mutt.
The first mode is allowing mutt to run a text web browser to render
the HTML into readable text. It's been a while since I configured
this, but I believe it's these three lines in my .muttrc which do it:
alternative_order text/plain text/html
unauto_view *
auto_view = text/html
If a message is sent in mixed mode (text/plain AND text/html parts),
then mutt shows the text/plain part. (Note: this may or may not be
a faithful rendering of the HTML part. It's whatever the sender put
in that part, and it may be missing some information.)
If a message is sent with ONLY a text/html part, then mutt chooses
a text web browser to render it. I recommend installing "links"
because it does a better job than "lynx". If links is not present
but lynx is, lynx will be used, which is... marginally acceptable.
The second mode that I use is to copy the HTML part to a file, and
then scp it to my local machine, and then load it in a web browser.
While reading the message, press 'v' to view the parts in a tree
layout. Use the arrows to select the text/html part, then press 's'
to save it to a file. You'll be prompted for a filename; I use the
same filename every time (foo.html) just to make the procedure easy.
Once foo.html is saved on the mutt host, scp it to your local host.
If your local and remote hosts are the same machine, then you can
skip this step. Of course, you can use rsync, sftp, or whatever.
Once foo.html is copied to the local host, go to your web browser
(Firefox or Chromium or whatever), press Ctrl-t to open a new tab,
and select file:///home/yourname/foo.html in the URL bar. If you
use the same filename every time, then this will be in your history
already (after the first time), which greatly reduces the amount of
typing needed in this step. Hit Enter, and voila. Now you're
reading the text/html part the way the sender intended, including
loading all of the tracking images that tell them you've opened the
email.
Now, this is just my personal workflow, and you may come up with
different ways to deal with it. Just find whatever works best for
you.
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)