From: Simon Josefsson <jas@extundo.com>
Cc: ding@gnus.org
Subject: Re: Sieve support?
Date: Thu, 01 Nov 2001 17:50:47 +0100 [thread overview]
Message-ID: <ilu4roesae0.fsf@dhcp128.extundo.com> (raw)
In-Reply-To: <vafhese4gom.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de> (Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "Thu, 01 Nov 2001 17:08:41 +0100")
Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:
> Simon Josefsson <jas@extundo.com> writes:
>
>> if address \"sender\" \"sieve-admin@extundo.com\" {
>> fileinto \"INBOX.list.sieve\";
>> }
>
> My hand-crafted script looks similar, but adds "stop" after
> "fileinto". Thoughts?
I don't think the automatically generated code should ever invoke
"stop", since you may want to put Sieve code after the Gnus generated
code block. Do you agree?
If you're thinking about crossposting, there is `gnus-sieve-crosspost'.
next prev parent reply other threads:[~2001-11-01 16:50 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-21 13:01 Simon Josefsson
2001-10-21 14:02 ` Kai Großjohann
2001-10-22 1:21 ` Daniel Pittman
2001-11-01 0:53 ` Simon Josefsson
2001-11-01 16:08 ` Kai Großjohann
2001-11-01 16:50 ` Simon Josefsson [this message]
2001-11-02 8:25 ` Kai Großjohann
2001-11-02 8:50 ` Simon Josefsson
2001-11-02 9:14 ` Kai Großjohann
2001-11-02 12:39 ` Simon Josefsson
2001-11-02 16:24 ` Kai Großjohann
2001-11-02 17:52 ` Amos Gouaux
2001-11-02 22:29 ` Kai Großjohann
2001-11-04 14:49 ` Steinar Bang
2001-11-04 17:35 ` Amos Gouaux
2001-11-04 18:06 ` Simon Josefsson
2001-11-04 18:44 ` Amos Gouaux
2001-11-02 17:48 ` Amos Gouaux
2001-11-02 19:59 ` Simon Josefsson
2001-11-03 0:35 ` NAGY Andras
2001-11-03 18:58 ` possible gnus-sieve bug NAGY Andras
2001-11-03 19:06 ` Simon Josefsson
2001-11-04 13:17 ` NAGY Andras
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=ilu4roesae0.fsf@dhcp128.extundo.com \
--to=jas@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).