From: Simon Josefsson <jas@extundo.com>
Subject: Re: (: spam-split) doesn't work
Date: Fri, 28 Feb 2003 17:55:47 +0100 [thread overview]
Message-ID: <iluel5sbazw.fsf@latte.josefsson.org> (raw)
In-Reply-To: <4nznogicec.fsf@chubby.bwh.harvard.edu> (Ted Zlatanov's message of "Fri, 28 Feb 2003 11:43:39 -0500")
Ted Zlatanov <tzz@lifelogs.com> writes:
> On Fri, 28 Feb 2003, chris@splinter.inka.de wrote:
>> Ted Zlatanov <tzz@lifelogs.com> writes:
>>
>>> On Thu, 27 Feb 2003, chris@splinter.inka.de wrote:
>>>> As I had assumed, /tmp/bogofilter.input only contains the header,
>>>> whereas the message which is to be classified contains a
>>>> non-empty body.
>> [...]
>>>
>>> I see. Try setting nnimap-split-download-body to t. Does that fix
>>> it?
>>
>> As I don't use IMAP, there's no effect.
>
> I'm pretty sure Simon Josefsson did the necessary work to have the
> full message available in nnmail (nnml, specifically) splitting. See
> this message on the ding list and the surrounding discussion:
>
> <ilu7kct1e0d.fsf@latte.josefsson.org>
>
> Simon, am I supposed to do something special in spam-split to have the
> full message body available? I think (widen) wouldn't work, because
> it will remove all narrowing restrictions and I'll be looking at the
> full incoming mbox file, is that correct? I had assumed that your fix
> left the full message body in the buffer, but according to Chris'
> experience he's getting only the header.
>
> If it's not set up yet, it would be OK to have a variable analogous to
> nnimap-split-download-body to trigger that behavior optionally.
The behaviour enabled by n-s-d-b for nnmail should be the default. I
think Gnus copies the message around, so (widen) should work. Maybe
putting (progn (widen) (message (buffer-string))) in the split
function will tell for sure, I haven't used nnmail splitting recently.
next prev parent reply other threads:[~2003-02-28 16:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87vfzyjx2v.fsf@splinter.inka.de>
[not found] ` <4nisvxs1j6.fsf@lockgroove.bwh.harvard.edu>
[not found] ` <874r7g2f4w.fsf@splinter.inka.de>
[not found] ` <4nheb8qazq.fsf@lockgroove.bwh.harvard.edu>
[not found] ` <87vfznc21y.fsf@splinter.inka.de>
[not found] ` <4nk7g3gdbk.fsf@lockgroove.bwh.harvard.edu>
[not found] ` <87vfzm7p2f.fsf@splinter.inka.de>
[not found] ` <4nlm0iad77.fsf@lockgroove.bwh.harvard.edu>
[not found] ` <877kc26j07.fsf@splinter.inka.de>
[not found] ` <m3of5dc4tt.fsf@heechee.beld.net>
[not found] ` <87el5talpw.fsf@splinter.inka.de>
[not found] ` <4nfzq9k84r.fsf@chubby.bwh.harvard.edu>
[not found] ` <87wujl8tj8.fsf@splinter.inka.de>
2003-02-27 19:03 ` Ted Zlatanov
2003-02-27 20:06 ` Christopher Splinter
2003-02-27 20:56 ` Ted Zlatanov
2003-02-27 22:05 ` Christopher Splinter
2003-02-27 22:29 ` Ted Zlatanov
2003-02-27 23:45 ` Christopher Splinter
2003-02-28 16:43 ` Ted Zlatanov
2003-02-28 16:55 ` Simon Josefsson [this message]
2003-02-28 17:07 ` Ted Zlatanov
2003-02-28 17:34 ` Simon Josefsson
2003-02-28 21:22 ` Ted Zlatanov
2003-02-28 22:17 ` Christopher Splinter
2003-03-01 15:01 ` Ted Zlatanov
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=iluel5sbazw.fsf@latte.josefsson.org \
--to=jas@extundo.com \
/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).