From: jhbrown@ai.mit.edu (Jeremy H. Brown)
Cc: ding@gnus.org
Subject: Re: spam.el experiences
Date: 22 Nov 2002 12:55:32 -0500 [thread overview]
Message-ID: <uv6vg2ppjzf.fsf@tenebrae.ai.mit.edu> (raw)
In-Reply-To: <4nptszx77g.fsf@brainy.bwh.harvard.edu>
Ted Zlatanov <tzz@lifelogs.com> writes:
> Not currently. gnus-ifile.el only supports nnml newsgroups from what
> I understand, so processing on summary exit with it in spam.el (which
> is backend-independent) would not work well.
ifile-gnus.el has supported all of the nnmail backends for awhile, but
I haven't gotten to nnimap yet.
> The gnus-ifile.el maintainer told me the next release would be
> backend-independent. I don't know when that will be.
I don't either. Probably not until January at the earliest.
Jeremy
next prev parent reply other threads:[~2002-11-22 17:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-16 14:54 Andreas Fuchs
2002-11-19 9:09 ` Patch for ifile spam splitting in spam.el (was: Re: spam.el experiences) Andreas Fuchs
2002-11-21 15:37 ` Patch for ifile spam splitting in spam.el Ted Zlatanov
2002-11-21 15:39 ` spam.el experiences Ted Zlatanov
2002-11-22 17:55 ` Jeremy H. Brown [this message]
2002-11-22 18:09 ` 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=uv6vg2ppjzf.fsf@tenebrae.ai.mit.edu \
--to=jhbrown@ai.mit.edu \
--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).