Tickets :: Comment on [#5746] patch to resolve sieve forward/keep ambiguity

* Your Email Address
* Spam protection	Enter the letters below: . . __ . .. .\ / \ // `\| \|\|\ \| >< \/ \__.\|__\|\| \\|/ \
Comment	> The attached patch fixes a problem in the keep behavior for the > Forward script by > > creating two Sieve rules to handle 'redirect' and 'keep' as separate actions. > > > > Currently using Forward with Keep looks like this: > > # Forwards > > if true { > > redirect "username@server"; > > keep; > > } > > > > and without Keep: > > # Forwards > > if true { > > redirect "username@server"; > > } > > > > The behavior of the first script is to redirect mail as expected and > then immediately > > drop a copy into the Inbox followed by parsing of any additional filters. > > > > The second script will redirect the mail and then continue to parse > via additional rules > > until a stop is encountered. Mail is not delivered into the Inbox at > the end of the > > script. > > > > The reason why mail does not go to the inbox during a Forward request > is that the > > redirect action disables the implicit keep within Sieve. > > > > The keep action declares an _explicit_ keep action which is the same > as declaring: > > fileinto "Inbox". > > > > This patch results one of the following: > > > > Without Keep: > > > > # Forwards > > if true { > > redirect "username@server"; > > stop; > > } > > > > With Keep: > > > > # Forwards > > if true { > > redirect "username@server"; > > } > > > > ... any other rules that exist with the last rule being ... > > > > # Forward Keep Action > > if true { > > keep; > > stop; > > } > > > > A user can still move the position of the Forwards script within Ingo. > > The Forward Keep Action script is always placed at the end. This > script replicated the > > implicit keep function. > > > > - Tobias Drewry
Attachment
Watch this ticket

Saved Queries