<?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>Update filters when folders are moved</title> 
  <pubDate>Thu, 09 Apr 2026 14:30:28 +0000</pubDate> 
  <link>https://bugs.horde.org/ticket/12946</link> 
  <atom:link rel="self" type="application/rss+xml" title="Update filters when folders are moved" href="https://bugs.horde.org/ticket/12946/rss" /> 
  <description>Update filters when folders are moved</description> 
 
   
   
  <item> 
   <title>#1 Create filter and choose to place emails in a folder. Cre</title> 
   <description>#1 Create filter and choose to place emails in a folder. Create the folder on the fly.
# 2 Go to mail view and re-arrange folders by placing the newly created one inside INBOX
# 3 Go back to filters and edit the filter which was created at step #1

The rule has lost track of the folder and is asking the user to pick a folder to store the messages which meet the criteria.

I&#039;m not sure how IMP could keep track of folders, but could be nice to have, just like on desktop clients.</description> 
   <pubDate>Thu, 30 Jan 2014 18:57:22 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/12946#t82197</link> 
  </item> 
   
  <item> 
   <title>Ingo (the filter frontend) doesn&#039;t have much to do with IMP,</title> 
   <description>Ingo (the filter frontend) doesn&#039;t have much to do with IMP, e.g. there is no way to notify Ingo if a folder name in IMP has changed. More important though, the folders can be renamed outside of IMP too, which would go  completely unseen by Ingo.</description> 
   <pubDate>Fri, 31 Jan 2014 10:58:11 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/12946#t82210</link> 
  </item> 
   
  <item> 
   <title>&gt; Ingo (the filter frontend) doesn&#039;t have much to do with IM</title> 
   <description>&gt; Ingo (the filter frontend) doesn&#039;t have much to do with IMP, e.g. 
&gt; there is no way to notify Ingo if a folder name in IMP has changed. 
&gt; More important though, the folders can be renamed outside of IMP too, 
&gt; which would go  completely unseen by Ingo.
OK.
I was wondering if folders could be tracked internally using some sort of IMAP folder ID which never changes despite the name change, but since you know tons more than I do regarding IMAP, I trust you when you say it&#039;s not feasible :)
</description> 
   <pubDate>Fri, 31 Jan 2014 11:12:20 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/12946#t82214</link> 
  </item> 
   
  <item> 
   <title>&gt;&gt; Ingo (the filter frontend) doesn&#039;t have much to do with I</title> 
   <description>&gt;&gt; Ingo (the filter frontend) doesn&#039;t have much to do with IMP, e.g.
&gt;&gt; there is no way to notify Ingo if a folder name in IMP has changed.
&gt;&gt; More important though, the folders can be renamed outside of IMP too,
&gt;&gt; which would go  completely unseen by Ingo.

Jan is (mostly) correct ... we absolutely can&#039;t rely on Ingo having any knowledge of the current state of the mailboxes on the server, since there are a multitude of ways to change the mailboxes outside of IMP.

That being said... it should be possible to *notify* the user in the following situation:

1) A mailbox is altered in IMP
2) That mailbox is a member of one or more rules in the current filtering backend.

In this case, there is nothing wrong with reminding the user to update their filters, as long as nothing is changed automatically.  Even better would be to link to an Ingo page that filters rules by a mailbox name, so you can instantly see which rules are connected to an individual mailbox.

Reopening ticket for these two features.

&gt; I was wondering if folders could be tracked internally using some 
&gt; sort of IMAP folder ID which never changes despite the name change, 
&gt; but since you know tons more than I do regarding IMAP, I trust you 
&gt; when you say it&#039;s not feasible :)

No.  There is no IMAP equivalent to mailbox names as there is to CONDSTORE/QRESYNC IMAP extensions (i.e. mod sequence values for messages).</description> 
   <pubDate>Tue, 11 Feb 2014 08:06:43 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/12946#t82314</link> 
  </item> 
   
  <item> 
   <title>&gt; Even better would be to link to an Ingo page that filters </title> 
   <description>&gt; Even better would be to link to an Ingo page that filters rules by a 
&gt; mailbox name, so you can instantly see which rules are connected to 
&gt; an individual mailbox.

This part has been added in Ingo.</description> 
   <pubDate>Fri, 14 Feb 2014 03:42:50 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/12946#t82374</link> 
  </item> 
   
  <item> 
   <title>&gt; In this case, there is nothing wrong with reminding the us</title> 
   <description>&gt; In this case, there is nothing wrong with reminding the user to 
&gt; update their filters, as long as nothing is changed automatically.  
&gt; Even better would be to link to an Ingo page that filters rules by a 
&gt; mailbox name, so you can instantly see which rules are connected to 
&gt; an individual mailbox.
Should Ingo quickly scan the rules at login time and notify the user then? I don&#039;t know by how much it would slow down the login process.

I like the page where we can see the connections and it would be great if broken rules could be highlighted.

</description> 
   <pubDate>Fri, 14 Feb 2014 10:48:14 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/12946#t82376</link> 
  </item> 
   
  <item> 
   <title>&gt; Should Ingo quickly scan the rules at login time and notif</title> 
   <description>&gt; Should Ingo quickly scan the rules at login time and notify the user 
&gt; then? I don&#039;t know by how much it would slow down the login process.

For a variety of reasons, no.</description> 
   <pubDate>Fri, 14 Feb 2014 19:48:27 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/12946#t82379</link> 
  </item> 
   
   
 
 </channel> 
</rss> 
