From: Jan Tatarik <jan.tatarik@gmail.com>
To: ding@gnus.org
Subject: Re: Scoring on basee64 encoded message body
Date: Wed, 11 Apr 2012 21:34:48 +0200 [thread overview]
Message-ID: <5n5x2rehrudpuv.fsf@nb-jtatarik2.xing.hh> (raw)
In-Reply-To: <m3iph7z8lj.fsf@stories.gnus.org> (Lars Magne Ingebrigtsen's message of "Tue, 10 Apr 2012 21:32:08 +0200")
On Tue, Apr 10 2012, Lars Magne Ingebrigtsen Lars Magne Ingebrigtsen wrote:
> Yes. And I almost applied it, but then I remembered that this
> wouldn't, in general, really give us what we wanted, anyway. :-/
> That is, a lot of messages are MIME multipart messages. If we start
> decoding, we really should decode all the parts, and score on the
> decoded text of them all, I think.
All text/* parts, I assume?
I had a quick look at mm handling in gnus. My idea would be to
- run mm-dissect-buffer on the message body (any idea which args would
be appropriate?)
- for multipart messages, pick the handles with text/* type, run them
through their respective mm-inline-* function as defined in
mm-inline-media-tests
- score on all the decoded text parts
Is this the way to go?
next prev parent reply other threads:[~2012-04-11 19:34 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-13 10:39 Jan Tatarik
2012-03-14 14:38 ` Lars Magne Ingebrigtsen
2012-03-14 20:21 ` Reiner Steib
2012-03-15 1:29 ` Lars Magne Ingebrigtsen
2012-03-15 21:05 ` Jan Tatarik
2012-03-22 20:38 ` Lars Magne Ingebrigtsen
2012-03-23 12:11 ` Jan Tatarik
2012-04-10 19:32 ` Lars Magne Ingebrigtsen
2012-04-11 7:30 ` Jan Tatarik
2012-04-11 19:34 ` Jan Tatarik [this message]
2012-04-12 18:45 ` Lars Magne Ingebrigtsen
2012-04-12 22:58 ` Jan Tatarik
2012-06-10 21:08 ` Lars Magne Ingebrigtsen
2012-06-28 9:45 ` Jan Tatarik
2012-09-05 13:40 ` Lars Ingebrigtsen
2012-09-05 14:39 ` Jan Tatarik
2012-09-05 14:43 ` Lars Ingebrigtsen
2012-09-05 15:07 ` Jan Tatarik
2012-09-05 15:35 ` Lars Ingebrigtsen
2012-09-05 15:42 ` Andreas Schwab
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=5n5x2rehrudpuv.fsf@nb-jtatarik2.xing.hh \
--to=jan.tatarik@gmail.com \
--cc=ding@gnus.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;
as well as URLs for NNTP newsgroup(s).