Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
Cc: ding@gnus.org
Subject: Re: planned spam.el features
Date: Fri, 24 Jan 2003 15:25:18 -0500	[thread overview]
Message-ID: <4nadhq9txt.fsf@lockgroove.bwh.harvard.edu> (raw)
In-Reply-To: <84vg0ee2qn.fsf@lucy.is.informatik.uni-duisburg.de> (kai.grossjohann@uni-duisburg.de's message of "Fri, 24 Jan 2003 21:01:36 +0100")

On Fri, 24 Jan 2003, kai.grossjohann@uni-duisburg.de wrote:
> Ted Zlatanov <tzz@lifelogs.com> writes:
> 
>> - capturing messages when they are accepted, moved, or replaced.
>>   This is what I saw in the ifile-gnus.el code - is it sufficient
>>   to trap those three article events to track an article as it
>>   moves around?  What functions should I advise?  Examples would be
>>   greatly appreciated; the ifile-gnus.el example is only applicable
>>   to nnml unfortunately.
> 
> I think a more recent version of ifile-gnus supports more backends.
> But I haven't looked at the code.

Latest (0.3.5) ifile-gnus.el release notes say: "currently works with
most (all?) of the nnmail backends.  It does not currently work with
nnimap."

> Maybe it would be a good idea to put some hooks into Gnus.

Yes!

Ted



  reply	other threads:[~2003-01-24 20:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-24 19:22 Ted Zlatanov
2003-01-24 20:01 ` Kai Großjohann
2003-01-24 20:25   ` Ted Zlatanov [this message]
2003-01-25 20:54 ` Stephen Zander
2003-01-27 18:20   ` Ted Zlatanov
2003-02-22  7:00     ` Stephen Zander
2003-02-24 15:42       ` 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=4nadhq9txt.fsf@lockgroove.bwh.harvard.edu \
    --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).