<?xml version="1.0" encoding="UTF-8"?> 
<?xml-stylesheet href="https://dev.horde.org/themes/horde//default/feed-rss.xsl" type="text/xsl"?> 
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"> 
 <channel> 
  <title>IMAP stop-script rules halt all processing, not just processing of the matched message</title> 
  <pubDate>Fri, 10 Apr 2026 17:20:04 +0000</pubDate> 
  <link>https://bugs.horde.org/ticket/5539</link> 
  <atom:link rel="self" type="application/rss+xml" title="IMAP stop-script rules halt all processing, not just processing of the matched message" href="https://bugs.horde.org/ticket/5539/rss" /> 
  <description>IMAP stop-script rules halt all processing, not just processing of the matched message</description> 
 
   
   
  <item> 
   <title>

I have rules A, B, and C.

I have unseen messages #1 throu</title> 
   <description>

I have rules A, B, and C.

I have unseen messages #1 through #9.



#1 - Matches rule A.

#2 - A

#3 - A

#4 - B

#5 - A

#6 - B

#7 - C

#8 - C

#9 - B



My options are set up to only filter unseen messages and to apply the filter rules whenever the Inbox is displayed.



Upon first login, messages matching filter rule A (#1, #2, #3, #5) will get filtered. No other messages get filtered.



Refreshing the Inbox immediately results in messages matching filter rule B (#4, #6, and #9) being filtered.



Refreshing the Inbox again results in the remaining messages getting filtered by rule C.



All rules have the &quot;Stop checking if this rule applies&quot; checkbox marked, but that should not prevent the other rules from running in the same session. Expected behavior should be that messages #1 through #9 get filtered by the 3 different rules.



Just an assumption that maybe a &quot;stop checking other rules&quot; flag is being set on larger variable scope instead of just the current message being filtered?</description> 
   <pubDate>Mon, 09 Jul 2007 16:56:40 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/5539#t35033</link> 
  </item> 
   
  <item> 
   <title>Which script backend are you using?</title> 
   <description>Which script backend are you using?</description> 
   <pubDate>Tue, 31 Jul 2007 20:44:17 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/5539#t35598</link> 
  </item> 
   
  <item> 
   <title>&gt; Which script backend are you using?



I&#039;m not entirely su</title> 
   <description>&gt; Which script backend are you using?



I&#039;m not entirely sure what you mean. Like what version of PHP? Should be PHP 5.2.3</description> 
   <pubDate>Tue, 31 Jul 2007 20:52:53 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/5539#t35602</link> 
  </item> 
   
  <item> 
   <title>No. Sieve? IMAP filters? Procmail? Maildrop?</title> 
   <description>No. Sieve? IMAP filters? Procmail? Maildrop?</description> 
   <pubDate>Tue, 31 Jul 2007 21:00:47 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/5539#t35608</link> 
  </item> 
   
  <item> 
   <title>If the filters are executed on login and refresh, he has to </title> 
   <description>If the filters are executed on login and refresh, he has to be using imap.</description> 
   <pubDate>Tue, 31 Jul 2007 21:25:18 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/5539#t35614</link> 
  </item> 
   
  <item> 
   <title>It looks to me like we simply do a break, aborting all furth</title> 
   <description>It looks to me like we simply do a break, aborting all further rules, if a stop-script rule matches in the imap driver. Since we&#039;re processing multiple messages at once, this makes no sense.



I think what we should do instead is store a cache of the imap uids that have matched stop rules, and exclude them from all future rules. Does that make sense?</description> 
   <pubDate>Wed, 01 Aug 2007 04:28:22 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/5539#t35632</link> 
  </item> 
   
  <item> 
   <title>&gt; I think what we should do instead is store a cache of the </title> 
   <description>&gt; I think what we should do instead is store a cache of the imap uids 

&gt; that have matched stop rules, and exclude them from all future rules. 

&gt; Does that make sense?



Yes, it does.</description> 
   <pubDate>Wed, 15 Aug 2007 05:42:37 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/5539#t35985</link> 
  </item> 
   
  <item> 
   <title>Implemented for Ingo 1.2.</title> 
   <description>Implemented for Ingo 1.2.</description> 
   <pubDate>Tue, 28 Aug 2007 04:30:31 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/5539#t36421</link> 
  </item> 
   
   
 
 </channel> 
</rss> 
