Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
Cc: ding@hpc.uh.edu
Subject: Re: Add hooks to Gnus on move/edit/delete?
Date: Sun, 29 Dec 2002 14:14:51 -0500	[thread overview]
Message-ID: <m3vg1cy6vo.fsf@heechee.beld.net> (raw)
In-Reply-To: <84fzsgk72x.fsf@lucy.cs.uni-dortmund.de> (kai.grossjohann@uni-duisburg.de's message of "Sun, 29 Dec 2002 19:34:14 +0100")

On Sun, 29 Dec 2002, kai.grossjohann@uni-duisburg.de wrote:
> First of all, ifile-gnus.el now uses a different mechanism for
> communicating with the backend, and the new mechanism works for more
> than one backend.

Is this released, and does it work with nnimap?  I haven't followed
ifile-gnus.el, unfortunately, due to lack of time.

> However, I think that integrating ifile into spam.el is not so good
> because ifile can also be used for general mail splitting.  It's
> really cool, actually.  Alas, I went back to nnimap so I'm having
> trouble using it.

Ah, so maybe it doesn't work with imap yet :)

Right now, all the other spam-split functions return spam-split-group
or nil (as a spam/non-spam convention), but IIRC ifile-spam-filter
could filter messages into regular groups as well.  The use of
spam-split-group is just a convention in spam.el.

The spam-check-ifile function is as follows right now:

;;; check the ifile backend; return nil if the mail was NOT classified as spam
(condition-case nil
    (progn
      (require 'ifile-gnus)
        ;;; 
      (defun spam-check-ifile ()
	(let ((ifile-primary-spam-group spam-split-group))
	  (ifile-spam-filter nil))))
  (file-error (setq spam-list-of-checks
		    (delete (assoc 'spam-use-ifile spam-list-of-checks)
			    spam-list-of-checks))))


So if ifile-spam-filter could and should be replaced with another
ifile-gnus.el function that returns regular group names, spam.el can
do all the ifile classification automatically if the user just sets
spam-use-ifile to t.

Does that sound reasonable?

Ted




  parent reply	other threads:[~2002-12-29 19:14 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-10 16:17 Kai Großjohann
2002-09-10 18:17 ` Jeremy H. Brown
2002-09-10 20:04   ` Kai Großjohann
2002-09-10 21:03     ` Jeremy H. Brown
2002-09-12 18:07       ` Clemens Fischer
2002-09-13  4:25         ` Jeremy H. Brown
2002-12-29 17:43 ` Lars Magne Ingebrigtsen
2002-12-29 18:34   ` Kai Großjohann
2002-12-29 18:44     ` Lars Magne Ingebrigtsen
2002-12-29 19:14     ` Ted Zlatanov [this message]
2002-12-29 22:06       ` Kai Großjohann
2002-12-29 22:53         ` Lars Magne Ingebrigtsen
2002-12-30  3:35           ` Ted Zlatanov
2002-12-30 18:49           ` Kai Großjohann
2002-12-30  3:33         ` Ted Zlatanov
2002-12-30 18:53           ` Kai Großjohann
2002-12-30 22:53             ` Ted Zlatanov
2002-12-31 12:08               ` Kai Großjohann
2002-12-31 14:32                 ` ifile-gnus: " Ted Zlatanov
2002-12-31 19:44                   ` Nathan J. Williams
2002-12-31 20:00                     ` Ted Zlatanov
2003-01-02 17:29         ` Simon Josefsson
2003-01-02 21:31           ` Kai Großjohann
2003-01-02 22:07             ` Simon Josefsson
2003-01-03 13:31               ` 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=m3vg1cy6vo.fsf@heechee.beld.net \
    --to=tzz@lifelogs.com \
    --cc=ding@hpc.uh.edu \
    /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).