From: Ted Zlatanov <tzz@lifelogs.com>
To: Daniel Pittman <daniel@rimspace.net>
Cc: <ding@gnus.org>
Subject: Re: gnus-sieve: make it easier to customize.
Date: Mon, 14 Dec 2009 09:43:44 -0600 [thread overview]
Message-ID: <87skbdtvbj.fsf@lifelogs.com> (raw)
In-Reply-To: <87pr6j2mu1.fsf@rimspace.net> (Daniel Pittman's message of "Sun, 13 Dec 2009 21:24:38 +1100")
On Sun, 13 Dec 2009 21:24:38 +1100 Daniel Pittman <daniel@rimspace.net> wrote:
DP> Ted Zlatanov <tzz@lifelogs.com> writes:
>> I've been curious about Sieve but there's no info on using it with Gnus.
DP> The Gnus manual, and the Gnus-Sieve manual, both in info format, don't do it
DP> for you? In fairness, I guess, they are "technical reference" guides to the
DP> integration features, not anything user-focused about the Sieve language
DP> itself.
Sorry, I meant to say there's no user-focused info on using it with Gnus
as you said. I was not thinking when I wrote that.
The information in both manuals is for those who already have Sieve set
up. It's especially important to explain how Sieve works and how it's
different from client-side Gnus splitting, so maybe that requires a
separate section?
My eventual goal is to store the Gnus registry in a distributed way
(probably via imap-hash.el) and generate Sieve scripts from it to split
by sender, subject, or references. I don't know if that's the right
approach but it seems most useful.
DP> The short version is, though, that you edit group properties to add a "sieve"
DP> property resembling the expression to file messages into that group:
DP> INBOX/personal =>
DP> ((sieve address ["to" "cc"] "daniel@rimspace.net"))
Thanks for explaining. I saw the example in the "Sieve Commands" node
too.
The Gnus Sieve section points to a broken link
(http://www.gnu.org/software/emacs/manual/html_node/sieve/index.html#Top).
I think that's because the Emacs Sieve mode has its own manual.
http://www.emacswiki.org/emacs/SieveMode also has some good links.
>> Do we have ManageSieve support in Gnus, and if not, can it be added?
DP> Mostly outside it, but the facilities are there. Read the Sieve manual
DP> shipped with Emacs for details. :)
Yeah, that seems sufficient. It seems like there are only a few Sieve
Gnus users, though. I wonder if it's worth supporting ManageSieve
explicitly in Gnus. Maybe it's better to concentrate on generating the
rules on the server side from distributed rules, like the Gnus registry
I mentioned.
Ted
prev parent reply other threads:[~2009-12-14 15:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-03 13:35 Daniel Pittman
2009-12-03 18:04 ` Ted Zlatanov
2009-12-04 1:46 ` Daniel Pittman
2009-12-07 15:56 ` Ted Zlatanov
2009-12-13 10:24 ` Daniel Pittman
2009-12-14 15:43 ` Ted Zlatanov [this message]
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=87skbdtvbj.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=daniel@rimspace.net \
--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).