From: Ted Zlatanov <tzz@lifelogs.com>
Subject: Re: splitting on body
Date: Fri, 22 Aug 2003 06:36:19 -0400 [thread overview]
Message-ID: <4n65kqj7x8.fsf@lockgroove.bwh.harvard.edu> (raw)
In-Reply-To: <egy8xmpa40.fsf@sefirot.ii.uib.no>
On 22 Aug 2003, ketil+@ii.uib.no wrote:
> Thomas Mittelstaedt <tmstaedt@t-mittelstaedt.de> writes:
>
>> "Ketil Malde" <ketil+@ii.uib.no> writes:
>
>>> I'm struggling to split messages based on body, using the example
>>> from the Info manual:
>
>>> (defun split-on-body ()
>>> (save-excursion
>>> (set-buffer " *nnmail incoming*")
>>> (goto-char (point-min))
>>> (when (re-search-forward "Some.*string" nil t)
>>> "string.group")))
>
>> Why don't you use procmail to do split-on-body stuff?
>
> Because I'm retrieving mail from an IMAP server? And of course,
> because I want to retain my belief that I'm using the most capable
> MUA known to mankind :-)
>
> I suppose I could replace the call to SET-BUFFER with something that
> first checks for the existence of the buffer? In what buffer can I
> find the current message when respooling?
I am pretty sure the current buffer contains the message while
splitting, you don't need to change buffers. Look at the spam-split
function in spam.el, it does body-based analysis for statistical spam
filters. Remember you have to set the nnimap-split-download-body
variable if you want to see the whole body with nnimap splitting.
Ted
prev parent reply other threads:[~2003-08-22 10:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <egada3qw1n.fsf@sefirot.ii.uib.no>
2003-08-21 21:53 ` Thomas Mittelstaedt
[not found] ` <egy8xmpa40.fsf@sefirot.ii.uib.no>
2003-08-22 10:36 ` Ted Zlatanov [this message]
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=4n65kqj7x8.fsf@lockgroove.bwh.harvard.edu \
--to=tzz@lifelogs.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).