From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: Add hooks to Gnus on move/edit/delete?
Date: Sun, 29 Dec 2002 18:43:56 +0100 [thread overview]
Message-ID: <m3smwgzpnn.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <vafelc1g6p6.fsf@lucy.cs.uni-dortmund.de>
Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:
> But of course it doesn't make much sense to advise the nnml
> functions, instead we would like to provide hooks that can be called
> when articles are moved.
Yup. But doesn't it make even more sense to not hook into the mail
backend functions at all, and use spam.el instead? It seems cleaner
to implement this from the Gnus side instead of using the backend.
However, that might not be the best solution of you're using ifile as
the MTA...
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~2002-12-29 17:43 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 [this message]
2002-12-29 18:34 ` Kai Großjohann
2002-12-29 18:44 ` Lars Magne Ingebrigtsen
2002-12-29 19:14 ` Ted Zlatanov
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=m3smwgzpnn.fsf@quimbies.gnus.org \
--to=larsi@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).