From: Ted Zlatanov <tzz@lifelogs.com>
Subject: Re: spam.el and IMAP
Date: Thu, 23 Oct 2003 18:00:11 -0400 [thread overview]
Message-ID: <4nu15zlims.fsf@lockgroove.bwh.harvard.edu> (raw)
In-Reply-To: <v91xt3kan7.fsf@marauder.physik.uni-ulm.de>
On Thu, 23 Oct 2003, 4.uce.03.r.s@nurfuerspam.de wrote:
> BTW, is there a simple way to tell `spam.el' to put ham articles
> from "Spam/spamblock" to both, "bayes/ham" _and_ "INBOX"?
> I.e. probably first copy the article to the first group and then
> move it to the second.
I see no reason why we can't handle multiple groups for
{spam,ham}-process-destination. I added the necessary code but it's
untested - please try it out and let me know how it works.
We used to use gnus-summary-move-article, now it's
gnus-summary-copy-article followed by gnus-summary-delete-article.
I assume an error in copy-article will abort the delete as well.
My topic and group parameters are very weird right now (see my
earlier post about auto-expire) and I was not able to test the
multiple groups code with group/topic parameters.
Ted
next prev parent reply other threads:[~2003-10-23 22:00 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-22 20:58 Gnus and Outlook and spam? Kai Grossjohann
2003-10-23 0:55 ` Jody Klymak
2003-10-23 16:06 ` Ted Zlatanov
2003-10-23 16:22 ` Jake Colman
2003-10-23 17:38 ` Ted Zlatanov
2003-10-23 17:42 ` Jake Colman
2003-10-23 19:29 ` Ted Zlatanov
2003-10-24 13:35 ` Jake Colman
2003-10-27 20:59 ` Ted Zlatanov
2003-10-28 15:25 ` Jake Colman
2003-10-28 15:57 ` Ted Zlatanov
2003-10-23 22:31 ` Danny Siu
2003-10-23 19:38 ` spam.el and IMAP (was: Gnus and Outlook and spam?) Reiner Steib
2003-10-23 22:00 ` Ted Zlatanov [this message]
2003-10-24 12:53 ` spam.el and IMAP Reiner Steib
2003-10-24 13:55 ` Adrian Lanz
2003-10-26 12:41 ` Adrian Lanz
2003-10-27 7:30 ` Adrian Lanz
2003-10-27 23:34 ` Ted Zlatanov
2003-10-27 8:23 ` Adrian Lanz
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=4nu15zlims.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).