From: Whyme Lyu <5longluna@gmail.com>
To: sup-devel <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] reading html mails
Date: Tue, 09 Jul 2013 02:42:34 +0800 [thread overview]
Message-ID: <1373307811-sup-1164@whymeDesk> (raw)
In-Reply-To: <1373019929-sup-8525@prxbdc.dyndns.org>
Excerpts from Ruthard Baudach's message of 2013-07-05 18:32:48 +0800:
> In the last years I'm receiving more and more emails containing only
> html-formatted text and no plain text.
I'm feeling the same pain here mainly due to unpolished in-house services
sending out html-only mails. More annoyingly, sup doesn't index these mails
since HTML is treated as attachments.
I've created an issue[1] on Github to talk about it further.
[1]: https://github.com/sup-heliotrope/sup/issues/101
--
-whyme http://randombu.gs/
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
next prev parent reply other threads:[~2013-07-08 19:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-05 10:32 Ruthard Baudach
2013-07-05 12:02 ` Vojtech Aschenbrenner
2013-07-05 13:15 ` Markus Klinik
2013-07-08 18:42 ` Whyme Lyu [this message]
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=1373307811-sup-1164@whymeDesk \
--to=5longluna@gmail.com \
--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