<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">I recommend reading the RFC: <a href="https://www.rfc-editor.org/rfc/rfc5228#section-2.10.2" class="">2.10.2</a> is where the Implicit Keep is described.<div class=""><br class=""></div><div class="">Basically, if you don’t take action on a message, there is an “implicit keep” that will save the mail in the default location. If an action *is* taken on a message (that results in it being saved somewhere; i.e., ‘fileinto’), then the implicit keep is removed (since you have explicitly said where to put it).</div><div class=""><br class=""></div><div class="">So there’s the “keep” keyword (see <a href="https://www.rfc-editor.org/rfc/rfc5228#section-4.3" class="">4.3</a>), to “do what you would do in the implicit keep” (more or less).</div><div class=""><br class=""></div><div class="">So:</div><div class=""><br class=""></div><div class="">fileinto :create “ac” -> puts the message into “ac” and removes “implicit keep”</div><div class="">keep -> puts implicit keep back (more or less)</div><div class=""><br class=""></div><div class="">fileinto :copy :create “ac” -> puts a *COPY* of the message into “ac”, and the original retains “implicit keep”.</div><div class=""><br class=""></div><div class="">They do the same thing, though I try and avoid unnecessary extensions when I can.</div><div class=""><br class=""></div><div class="">Sean<br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Aug 24, 2022, at 07:29, João Silva <<a href="mailto:joaopfmlist@lipc.fis.uc.pt" class="">joaopfmlist@lipc.fis.uc.pt</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class=""><br class="">On 23/08/2022 13:03, Rob Sterenborg (Lists) wrote:<br class=""><blockquote type="cite" class=""><br class="">On 23-08-2022 11:44, João Silva wrote:<br class=""><blockquote type="cite" class="">Hi<br class=""><br class="">If a sieve filter contains a rule<br class=""><br class="">if header :regex ["From"] ["@xxx.com","@yyy.pt"] {<br class=""> fileinto :create "ac";<br class="">}<br class=""><br class="">The mail should be copied to the folder ac and then proceed to other rules that a user might have or I understood the<br class=""><br class="">fileinto<br class=""><br class="">wrong?<br class=""><br class="">Using dovecot-pigeonhole-2.2.36-8.el7.x86_64<br class=""><br class=""></blockquote><br class="">I use it like this, and it works for me:<br class=""><br class="">if address :is "From" "sender@domain" {<br class=""> fileinto :create "some_mail_folder";<br class=""> stop;<br class="">}<br class=""><br class="">Almost 20 years ago, I figured out that I *need* the "stop;" line, but I don't remember why.<br class=""></blockquote><br class="">The stop; is needed to prevent further script actions on the email and that is a very curious thing that I dont know if falls in the "bug or feature" field.<br class=""><br class="">if I use<br class=""><br class="">if header :regex ["From"] ["@xxx.com","@yyy.pt"] {<br class=""> fileinto :create "ac";<br class=""><br class=""> keep;<br class=""><br class="">}<br class=""><br class="">It delivers the mail in my Inbox which was my intention in the first place.<br class=""><br class="">When I used the filter without the keep; and since I didn't had the stop; I was expecting further actions on that email that will lead to the email end up in the Inbox and that didn't happened.<br class=""><br class="">So it apears that the fileinto rule have a stop; into it without the stop being declared.<br class=""><br class="">In a complex mail management scenario that can cause problems. So my question is, "bug or feature"?<br class=""><br class=""><br class=""><br class=""><blockquote type="cite" class=""><br class=""><br class="">-- <br class="">Rob<br class=""></blockquote></div></div></blockquote></div><br class=""></div></body></html>