Re: e-mail encoding/formatting (was Re: Split-screen mode in mutt?)
On Friday, September 22, 2006 at 12:30:08 +0900, Henry Nelson wrote:
> In .muttrc I have "auto_view text/html [...] and in .mailcap I have
> "text/html; lynx -dump %s; copiousoutput; nametemplate=%s.html".
Works very well here: The pager shows the HTML rendered as text,
after an /attachment/ colored line:
| [-- Autoview using lynx -dump '/tmp/mutt.html' --]
> other forms of the .mailcap entry which don't have "nametemplate".
I believe Lynx needs either *.html filename, or -force_html.
> After pressing 'v', the first mail has an index:
>| I 1 <no description> [text/html, 7bit, euc-jp, 2.8K]
Looks good. Even if 7bit and euc-jp may seem contradictory: How is
the body really encoded? Is there a Content-Transfer-Encoding header?
Hum... Please gzip the whole mail and send it to me attached.
> The second mail has an index in the attachment menu like:
>| I 1 <no description> [multipa/alternativ, 7bit, 2.6K]
>| I 2 |-><no description> [text/plain, 7bit, us-ascii, 1.0K]
>| I 3 `-><no description> [text/plain, 7bit, us-ascii, 1.4K]
> Both 1 and 3 show up as raw HTML.
FUBAR. You can always workaround the mess by selecting (3) and
<edit-type>ing it to text/html. But better investigate what damaged the
mail like this: The sender's mailer, or some evil procmail rule?
Bye! Alain.
--
A "Reply-To:" header field pointing to the same email address
as the "From:" is uselessly redundant: A loss of space.