<?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>Sieve script fileinto clause should have &quot;INBOX.folder&quot;, not only &quot;folder&quot;</title> 
  <pubDate>Fri, 10 Apr 2026 13:16:43 +0000</pubDate> 
  <link>https://bugs.horde.org/ticket/6736</link> 
  <atom:link rel="self" type="application/rss+xml" title="Sieve script fileinto clause should have &quot;INBOX.folder&quot;, not only &quot;folder&quot;" href="https://bugs.horde.org/ticket/6736/rss" /> 
  <description>Sieve script fileinto clause should have &quot;INBOX.folder&quot;, not only &quot;folder&quot;</description> 
 
   
   
  <item> 
   <title>Sieve script fileinto clause should have &quot;INBOX.folder&quot;, not</title> 
   <description>Sieve script fileinto clause should have &quot;INBOX.folder&quot;, not only &quot;folder&quot;. If there is a line in a sieve script such as &#039;fileinto &quot;junk4&quot;;&#039;, the script tries to insert the mail into a folder &quot;junk4&quot; in the global namespace, not in &quot;user.$userid.junk4&quot;. The line should be &#039;fileinto &quot;INBOX.junk4&quot;;&#039;.</description> 
   <pubDate>Wed, 21 May 2008 12:02:50 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/6736#t45436</link> 
  </item> 
   
  <item> 
   <title>If it is enough to disallow spam folders outside one&#039;s INBOX</title> 
   <description>If it is enough to disallow spam folders outside one&#039;s INBOX, then this patch might suffice...

</description> 
   <pubDate>Wed, 21 May 2008 12:23:30 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/6736#t45437</link> 
  </item> 
   
  <item> 
   <title>And where are you getting the folder name? If you&#039;re using I</title> 
   <description>And where are you getting the folder name? If you&#039;re using IMP to get the folder list I believe INBOX. should be included automatically.</description> 
   <pubDate>Thu, 22 May 2008 16:40:08 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/6736#t45468</link> 
  </item> 
   
  <item> 
   <title>The patch was inappropriate for a general-purpose sieve gene</title> 
   <description>The patch was inappropriate for a general-purpose sieve generation app. Folder paths should never be hardcoded.</description> 
   <pubDate>Thu, 22 May 2008 16:41:05 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/6736#t45470</link> 
  </item> 
   
  <item> 
   <title>&gt; And where are you getting the folder name? If you&#039;re using</title> 
   <description>&gt; And where are you getting the folder name? If you&#039;re using IMP to get 

&gt; the folder list I believe INBOX. should be included automatically.



I used IMP&#039;s Options -&gt; Server and Folder Information -&gt; Spam folder drop-down menu. And I also used INGO&#039;s Spam Filter -&gt; Folder to receive spam menu. Both resulted in a sieve script without any prefix. I was also able to create new spam folders with both (with some trouble, see ticket #6640 - IMP spam_folder appears to override INGO spam[&#039;folder&#039;] upon login) - and the resulting script had no prefix in the folder name.</description> 
   <pubDate>Fri, 23 May 2008 06:32:37 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/6736#t45482</link> 
  </item> 
   
  <item> 
   <title>See bug 6527 - how are both of these possible open bugs at t</title> 
   <description>See bug 6527 - how are both of these possible open bugs at the same time?</description> 
   <pubDate>Fri, 23 May 2008 19:11:28 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/6736#t45494</link> 
  </item> 
   
  <item> 
   <title>This was apparently a failure in our configuration (default </title> 
   <description>This was apparently a failure in our configuration (default value for IMP spam_folder), not a bug. My apologies for the confusion.

</description> 
   <pubDate>Wed, 28 May 2008 13:20:07 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/6736#t45647</link> 
  </item> 
   
   
 
 </channel> 
</rss> 
