Re: Sieve support?

[Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)]

Simon Josefsson <jas@extundo.com> writes:

>> Well, err, it would invoke stop only inside the if...
>
> Really?  I don't know Sieve, but the following seems to be the only
> explanation about "stop" in the RFC, and it looks like it quits the whole
> script.  I've never used "stop" though, so I may be misreading the RFC.

I meant: it only invokes `stop' if the condition matches.

>> Does that mean I get something like
>> 
>>     if foo {
>>         fileinto "bar";
>>         stop;
>>     }
>> 
>> when crossposting is off and
>> 
>>     if foo {
>>         fileinto "bar";
>>     }
>> 
>> when crossposting is on?  That's what I wanted to suggest, too.
>
> Right now you get
>
> if foo {
> 	fileinto "foo"
> }
> elsif bar {
> 	fileinto "bar
> }
>
> if `gnus-sieve-crosspost' is nil, and
>
> if foo {
> 	fileinto "foo";
> }
> if bar {
> 	fileinto "bar";
> }
>
> otherwise.

Ah, yes, I think I used to have your style, too.  But then somewhere
I read about problems with nesting depths.  So I converted your
if/elseif style into mine.

Hm.  But you're right -- in your case it would be possible to add
more action after the whole if/elseif/else statement.  Hm.

To learn more, I'd have to know more about how your idea constructs
the whole Sieve script -- where are the group specific rules inserted
and what happens when the user changes group rules and how is the
other part of the script preserved...

I can't test your sieve mechanism because I'm using an old Cyrus
version which uses an old sieve protocol.

Though of course I could test your rule-generating part.  Hm.  But
I've already got so many useful rules :-)

kai
-- 
Lisp is kinda like tpircstsoP