From: "Ted Zlatanov" <tzz@lifelogs.com>
Cc: ding@gnus.org
Subject: Re: Spam splitting and multiple nnimap methods
Date: 20 May 2004 14:49:47 -0400 [thread overview]
Message-ID: <4nlljn0w8k.fsf@lifelogs.com> (raw)
In-Reply-To: <u8yfn5r6y.fsf@icts-tech.com> (Yair Friedman's message of "Thu, 20 May 2004 12:27:33 +0200")
On Thu, 20 May 2004, yairfr@icts-tech.com wrote:
> Please, generic cross-server splitting method is *very* useful even
> when not filtering spam.
>
> Having quota on IMAP servers where you want most important email to
> stay and less important directly split to nnmail groups is one
> example.
OK. Is there a hook I can use for right after all the mail splitting
has been done? I plan to spool all the external-destination mail
in a "gnusexternalqueue" group and then move it out, and that group
name will be customizable. I can't think of a cleaner approach that
wouldn't require too many hours of work :)
Ted
next prev parent reply other threads:[~2004-05-20 18:49 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-17 21:50 Timothy Brown
2004-05-18 9:53 ` Jonas Steverud
2004-05-18 12:53 ` Timothy Brown
2004-05-18 13:50 ` Jonas Steverud
2004-05-18 14:02 ` IMAP Splitting with multiple mailboxes (was Re: Spam splitting and multiple nnimap methods) Timothy Brown
2004-05-18 14:13 ` IMAP Splitting with multiple mailboxes Kai Grossjohann
2004-05-18 14:15 ` Timothy Brown
2004-05-18 15:53 ` Kai Grossjohann
2004-05-18 15:58 ` Timothy Brown
2004-05-18 16:14 ` Kai Grossjohann
2004-05-18 14:13 ` Spam splitting and multiple nnimap methods Jonas Steverud
2004-05-18 19:11 ` Ted Zlatanov
2004-05-18 22:19 ` Timothy Brown
2004-05-19 11:36 ` Jonas Steverud
2004-05-19 14:50 ` Ted Zlatanov
2004-05-19 14:48 ` Ted Zlatanov
2004-05-20 10:27 ` Yair Friedman
2004-05-20 18:49 ` Ted Zlatanov [this message]
2004-05-22 23:45 ` Lars Magne Ingebrigtsen
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=4nlljn0w8k.fsf@lifelogs.com \
--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).