Mon, 06 Apr 2026 21:38:52 +0000 https://bugs.horde.org/ticket/8014 Script fault, when entering more than 4 email addresses in the filter blacklist When entering more then 4 email addresses (some includes wildcards, e.g. *@domain.xx) in the filter blacklist, I got an error from the script sieve.php: Fatal error: Call to undefined method Ingo_Script_sieve::addblock() in /var/www/webmail.domain.xx/html/horde/ingo/lib/Script/sieve.php on line 294 The script is not builded and the filtering against email addresses from the blacklist is not working. Thu, 19 Feb 2009 11:32:40 +0000 https://bugs.horde.org/ticket/8014#t52694 > When entering more then 4 email addresses (some includes wildcards, > e.g. *@domain.xx) in the filter blacklist, I got an error from the > script sieve.php: > Fatal error: Call to undefined method Ingo_Script_sieve::addblock() > in /var/www/webmail.domain.xx/html/horde/ingo/lib/Script/sieve.php on > line 294 > > The script is not builded and the filtering against email addresses > from the blacklist is not working. I found the following solution in the net: " In horde/ingo/lib/Script/sieve.php, I had to add (line 163): function addBlock($block) { $this->_blocks[] = $block; } I found this in older revisions and it fixed my error, but I received "There was an error activating the script. The driver said: Not currently in TRANSACTION state" The first time I tried to activate my sieve script. Logged out and tried it again with success. Is this code missing for a reason? Or is the addblock call left over from something?" The change of the code help to solve my problem. Thu, 19 Feb 2009 15:32:28 +0000 https://bugs.horde.org/ticket/8014#t52695 Filters are Ingo, not IMP. Which version are you using? Thu, 19 Feb 2009 16:46:44 +0000 https://bugs.horde.org/ticket/8014#t52696 > Filters are Ingo, not IMP. Which version are you using? Hello Jan, thanks for answering. Sorry, my fault to classify it as IMP bug and not as Ingo bug. The Version is: *Horde Groupware Webmail Edition* *1.1.5* => Ingo H3 1.2 As I wrote in comment #2 - adding this 4 rows of code solves my problem. Fri, 20 Feb 2009 07:03:34 +0000 https://bugs.horde.org/ticket/8014#t52710 Duplicate of bug #7077. Fri, 20 Feb 2009 10:23:14 +0000 https://bugs.horde.org/ticket/8014#t52714