From: Simon Josefsson <sj@extundo.com>
Cc: ding@gnus.org
Subject: Re: mail splitting and sieve
Date: 23 Dec 2000 16:00:02 +0100 [thread overview]
Message-ID: <ilug0jfrxn1.fsf@barbar.josefsson.org> (raw)
In-Reply-To: <87d7ej1elu.fsf@lovi.inf.elte.hu>
NAGY Andras <nagya@inf.elte.hu> writes:
> The nnimal.el todo list contains
>
> ;; o Sieve
Actually it has become a separate project, partially lost in a disk
crash a few weeks ago. However, it should include a nice font-lock
mode for editing sieve scripts together with functionality for
uploading sieve scripts to your server.
> Therefore it would be nice if Gnus could generate a Sieve script from
> an nnmail-split-fancy list and store it on the server. I plan to
> implement this, and wonder if anyone else has similar plans, either
> regarding this specific problem or Sieve support in general.
I'd like this. Though, Sieve is not a turing complete language. This
is by design, which IMHO is very unfortunate. Perhaps it's mostly a
theoretic problem, you can probably manage to convert most split rules
anyway.
prev parent reply other threads:[~2000-12-23 15:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-23 12:55 NAGY Andras
2000-12-23 15:00 ` Simon Josefsson [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=ilug0jfrxn1.fsf@barbar.josefsson.org \
--to=sj@extundo.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).