From: Ruthard Baudach <ruthard.baudach@web.de>
To: Sup developer discussion <sup-devel@rubyforge.org>
Subject: [sup-devel] reading html mails
Date: Fri, 05 Jul 2013 12:32:48 +0200 [thread overview]
Message-ID: <1373019929-sup-8525@prxbdc.dyndns.org> (raw)
In the last years I'm receiving more and more emails containing only
html-formatted text and no plain text.
sup displays these emails as empty mails with an html attachment.
It would be great if sup was able to distinguish between actual html
attachments and such deficient mails, and would extract and display
the text part of these mails.
I'm not able to hack this myself at the moment, but perhaps someone
picks up the idea?
It's written a lot of times, but let me repeat it:
Good that sup is alive again!
Greetings to all
Ruthard
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
next reply other threads:[~2013-07-05 11:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-05 10:32 Ruthard Baudach [this message]
2013-07-05 12:02 ` Vojtech Aschenbrenner
2013-07-05 13:15 ` Markus Klinik
2013-07-08 18:42 ` Whyme Lyu
2013-07-09 12:13 ` Ruthard Baudach
2013-07-09 21:02 ` Mark Alexander
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1373019929-sup-8525@prxbdc.dyndns.org \
--to=ruthard.baudach@web.de \
--cc=sup-devel@rubyforge.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox