Are there Sieve policy limits? (ubergeek interest only)

elvey · 25 Apr 2003, 05:17 AM

What are FastMail/Cyrus' Sieve action policy limits?
How does it notify users of an error?

[SIEVE] is frustratingly confusing me.

I had incorrectly thought that [SIEVE] forbade multiple fileinto and redirect commands.
[SIEVE] says

"Implementations SHOULD prohibit reject when used with other actions."
and

"Site policy MAY limit numbers of actions taken and MAY impose
restrictions on which actions can be used together. In the event
that a script hits a policy limit on the number of actions taken for
a particular message, an error occurs."

and

that "reject + fileinto" is an invalid set of actions

and

" When an error happens, implementations MUST notify the user that an
error occurred, which actions (if any) were taken, and do an implicit keep"

By [SIEVE] , I mean
the official SIEVE RFC

robmueller · 25 Apr 2003, 05:17 PM

Bletch. We don't impose any site specific restrictions or limits.

I'm really not sure what sieve does if you try doing a reject then fileinto sorry, I guess just need to try it.

Rob

DrStrabismus · 25 Apr 2003, 08:13 PM

I think the reason why fileinto+reject is a SHOULD rather than MUST is that an implementation might perform the actions before the script completes.

The Cyrus implementation queues actions until the script is finished, and only processes the queue if there are no errors. Fileinto+reject is treated as an error. AFAIK the number of actions is limited only by available dynamic memory.

The error message in the source code are

"Reject can not be used with any other action";
"Fileinto can not be used with Reject";
"Redirect can not be used with Reject";
"Keep can not be used with Reject";
"Vacation can not be used with Reject or Vacation";
"Setflag can not be used with Reject";
"Addflag can not be used with Reject";
"Removeflag can not be used with Reject";
"Mark can not be used with Reject";
"Unmark can not be used with Reject";

elvey · 27 Apr 2003, 01:09 AM

Thanks for the great replies!

I get what you're saying, doc.

Tried the follwing as the first lines in my script:
if header :contains "subject" ["TwoRuleTest"] {
reject "TwoRuleTest";
fileinto "INBOX.afoldername";
keep;
And sent a test message
Results: The email ended up in my Inbox.
No error emails I can see, no bounce/reject or email in afoldername, either.

I conclude that when there's an error, Cyrus just leaves the mail in the Inbox, as is doesn't process the queue(good), and there's no direct user indication that there's been an error. (not so good).

Bletch indeed. Still waiting for a Sieve GUI editor, unfortunately.

25 Apr 2003, 05:17 AM	#1
elvey The "e" in e-mail Join Date: Jan 2002 Location: San Francisco Posts: 2,458	Are there Sieve policy limits? (ubergeek interest only) What are FastMail/Cyrus' Sieve action policy limits? How does it notify users of an error? [SIEVE] is frustratingly confusing me. I had incorrectly thought that [SIEVE] forbade multiple fileinto and redirect commands. [SIEVE] says "Implementations SHOULD prohibit reject when used with other actions." and "Site policy MAY limit numbers of actions taken and MAY impose restrictions on which actions can be used together. In the event that a script hits a policy limit on the number of actions taken for a particular message, an error occurs." and that "reject + fileinto" is an invalid set of actions and " When an error happens, implementations MUST notify the user that an error occurred, which actions (if any) were taken, and do an implicit keep" By [SIEVE] , I mean the official SIEVE RFC

25 Apr 2003, 08:13 PM	#3
DrStrabismus The "e" in e-mail Join Date: May 2002 Posts: 2,804	I think the reason why fileinto+reject is a SHOULD rather than MUST is that an implementation might perform the actions before the script completes. The Cyrus implementation queues actions until the script is finished, and only processes the queue if there are no errors. Fileinto+reject is treated as an error. AFAIK the number of actions is limited only by available dynamic memory. The error message in the source code are "Reject can not be used with any other action"; "Fileinto can not be used with Reject"; "Redirect can not be used with Reject"; "Keep can not be used with Reject"; "Vacation can not be used with Reject or Vacation"; "Setflag can not be used with Reject"; "Addflag can not be used with Reject"; "Removeflag can not be used with Reject"; "Mark can not be used with Reject"; "Unmark can not be used with Reject"; Last edited by DrStrabismus : 25 Apr 2003 at 08:16 PM.

25 Apr 2003, 05:17 PM	#2
robmueller Intergalactic Postmaster Join Date: Oct 2001 Location: Melbourne, Australia Posts: 6,102 Representative of: Fastmail.FM	Bletch. We don't impose any site specific restrictions or limits. I'm really not sure what sieve does if you try doing a reject then fileinto sorry, I guess just need to try it. Rob

27 Apr 2003, 01:09 AM	#4
elvey The "e" in e-mail Join Date: Jan 2002 Location: San Francisco Posts: 2,458	Thanks for the great replies! I get what you're saying, doc. Tried the follwing as the first lines in my script: if header :contains "subject" ["TwoRuleTest"] { reject "TwoRuleTest"; fileinto "INBOX.afoldername"; keep; And sent a test message Results: The email ended up in my Inbox. No error emails I can see, no bounce/reject or email in afoldername, either. I conclude that when there's an error, Cyrus just leaves the mail in the Inbox, as is doesn't process the queue(good), and there's no direct user indication that there's been an error. (not so good). Bletch indeed. Still waiting for a Sieve GUI editor, unfortunately.