<?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>Blacklist/Whitelist buttons in IMP 4.1.2</title> 
  <pubDate>Fri, 10 Apr 2026 07:03:45 +0000</pubDate> 
  <link>https://bugs.horde.org/ticket/4160</link> 
  <atom:link rel="self" type="application/rss+xml" title="Blacklist/Whitelist buttons in IMP 4.1.2" href="https://bugs.horde.org/ticket/4160/rss" /> 
  <description>Blacklist/Whitelist buttons in IMP 4.1.2</description> 
 
   
   
  <item> 
   <title>System: RHEL 4, Apache 2.0.52 w/PHP 4.3.9

Setup: Horde: 3.1</title> 
   <description>System: RHEL 4, Apache 2.0.52 w/PHP 4.3.9

Setup: Horde: 3.1.2, Imp: H3 (4.1.2), Ingo: H3 (1.1.1), SAM 0.1-cvs



I&#039;m setting up a completely new installation of IMP - what a seriously incredible update from 3.x.



Ingo is taking care of the Sieve filtering with Cyrus. SAM is taking care of all white/black lists with Amavisd-new and SpamAssassin. Pretty much everything is working better than ever before.



But I&#039;ve run into a little bug: With IMP 4.1.1, those white/black list buttons above an email worked just fine - automatically added the email address to the appropriate place and gave an additional link to manage the wblists.



As soon as I updated to 4.1.2, they stopped working - nothing is added to the wblists and there&#039;s no visible link or error message.



I went back to 4.1 - worked. Patched to 4.1.1 - worked. Patched to 4.1.2 - fails.

Installed 4.1.2 from virgin tarball - fails.

I tried it from the nightly snapshots - still fails.



Someone indicated on the IMP mailing list that it could be because of the patch to lib/IMP.php in the parseIndicesList function.



Thanks.</description> 
   <pubDate>Sat, 15 Jul 2006 15:05:28 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/4160#t22020</link> 
  </item> 
   
  <item> 
   <title>Fixed in HEAD and 4.1.3.</title> 
   <description>Fixed in HEAD and 4.1.3.</description> 
   <pubDate>Thu, 20 Jul 2006 04:13:06 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/4160#t22142</link> 
  </item> 
   
  <item> 
   <title>&gt; Fixed in HEAD and 4.1.3.



I tried to check out the IMP_4</title> 
   <description>&gt; Fixed in HEAD and 4.1.3.



I tried to check out the IMP_4_1_3 tag but that doesn&#039;t exist in order to get this fix so I can deploy my server.



Could you point me to the files I need to patch in order to get this fixed on my 4.1.2 installation? I&#039;ll make the patches on my own - just not entirely sure which files I need.



Thx.</description> 
   <pubDate>Wed, 02 Aug 2006 20:17:27 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/4160#t22575</link> 
  </item> 
   
  <item> 
   <title>&gt;&gt; Fixed in HEAD and 4.1.3.

&gt;

&gt; I tried to check out the I</title> 
   <description>&gt;&gt; Fixed in HEAD and 4.1.3.

&gt;

&gt; I tried to check out the IMP_4_1_3 tag but that doesn&#039;t exist in 

&gt; order to get this fix so I can deploy my server.

&gt;

&gt; Could you point me to the files I need to patch in order to get this 

&gt; fixed on my 4.1.2 installation? I&#039;ll make the patches on my own - 

&gt; just not entirely sure which files I need.



You either need to download a snapshot (http://snaps.horde.org/) or peruse the cvs mailing list to find the commit messages you need (see http://horde.org/mail/).</description> 
   <pubDate>Wed, 02 Aug 2006 20:52:29 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/4160#t22579</link> 
  </item> 
   
  <item> 
   <title>&gt; You either need to download a snapshot (http://snaps.horde</title> 
   <description>&gt; You either need to download a snapshot (http://snaps.horde.org/) or 

&gt; peruse the cvs mailing list to find the commit messages you need (see 

&gt; http://horde.org/mail/).



Perfect - forgot about the commit list - thanks again.</description> 
   <pubDate>Wed, 02 Aug 2006 21:16:36 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/4160#t22593</link> 
  </item> 
   
   
 
 </channel> 
</rss> 
