From: Ted Zlatanov <tzz@lifelogs.com>
Cc: ding@gnus.org
Subject: Re: widening in nnml split does not work
Date: Sat, 25 Jan 2003 11:18:33 -0500 [thread overview]
Message-ID: <m37kct2ofa.fsf@heechee.beld.net> (raw)
In-Reply-To: <iluu1fxz17f.fsf@latte.josefsson.org> (Simon Josefsson's message of "Sat, 25 Jan 2003 16:41:24 +0100")
On Sat, 25 Jan 2003, jas@extundo.com wrote:
> Yup. Hm. Would splitting code want the body deMIMEified?
>
> I guess some text analysis splitters would want to base64 decoding
> to happen of course. I wonder how much deMIMEification is wanted.
> Really, only the splitter functions can know this (some splitters
> might want raw MIME, some decoded base64 but not other
> MIME-decoding, some might want everything MIME related to be
> removed) so it should perform it itself, or Gnus should provide a
> framework for deciding what should be done for each splitter
> function. Anyway, until that happens, copying the raw body is
> probably mostly harmless.
Agreed, let's leave the raw body until someone requests more. I don't
believe in unnnecessary work on Saturday mornings :)
> I installed it.
How about the other backends? spam-split can only be invoked by
nnmail-split-fancy and nnimap-split-fancy; besides nnimap and nnmail,
are there any other backends I need to worry about to make spam-split
work universally?
Ted
next prev parent reply other threads:[~2003-01-25 16:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-25 6:41 Ted Zlatanov
2003-01-25 10:24 ` Kai Großjohann
2003-01-25 12:35 ` Ted Zlatanov
2003-01-25 13:14 ` Kai Großjohann
2003-01-25 14:48 ` Simon Josefsson
2003-01-25 15:14 ` Kai Großjohann
2003-01-25 15:29 ` Ted Zlatanov
2003-01-25 15:41 ` Simon Josefsson
2003-01-25 16:18 ` Ted Zlatanov [this message]
2003-01-25 21:37 ` Kai Großjohann
2003-01-26 0:46 ` Ted Zlatanov
2003-01-25 21:36 ` Kai Großjohann
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=m37kct2ofa.fsf@heechee.beld.net \
--to=tzz@lifelogs.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).