[Tickets #2165] NEW: corrupt data in blacklist deletes all messages

bugs@bugs.horde.org bugs at bugs.horde.org
Tue Jun 21 12:12:50 PDT 2005


DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/?id=2165
-----------------------------------------------------------------------
 Ticket             | 2165
 Created By         | robin.west at dal.ca
 Summary            | corrupt data in blacklist deletes all messages
 Queue              | Ingo
 Version            | 1.0.1
 State              | Unconfirmed
 Priority           | 3. High
 Type               | Bug
 Owners             | 
-----------------------------------------------------------------------


robin.west at dal.ca (2005-06-21 12:12) wrote:

Hi there - not sure if this belongs in the IMP queue or the Ingo queue as
I'm not sure where the source of the problem is. 

We recently upgraded to IMP 4.0.3 / Ingo 1.0.1. We have 47 users (out of
17,000+) whose blacklist has an invisible "empty" string in it. This empty
string matches any message and has the rather catastrophic effect of
deleting everything in the user's inbox. 

Most of the 47 cases appear to be the result of bad filter settings in our
previous installation (IMP 3.2.3), which was converted using the script
provided in ingo/scripts/convert_imp_filters.php. However - at least a few
of the 47 were definitely created AFTER the upgrade, meaning that users are
somehow generating this empty string in their blacklist.

The "empty" string I am referring to looks like this in the serialized data
in our horde_prefs table (the 2nd line with index i:0):

  a:2:{s:1:"a";a:26:
   {i:0;s:0:"";
    i:1;s:14:"j21n at chello.nl";
    i:2;s:15:"k1thy at chello.nl";
    i:3;s:27:"creditcardservices at cibc.com";
   etc...

I am so far unable to reproduce the problem, except by editing the data via
sql. I have not yet determined how the empty string is getting into their
blacklist, but I thought I should open a ticket here to find out anyone else
has experienced the problem.

We are using:
Horde 3.0.4, IMP H3 4.0.3 (final), Ingo H3 1.0.1, Turba H3 2.0.2
Cyrus IMAP4 v2.1.12
Postgres 7.3.6-RH
PHP 4.3.2








More information about the bugs mailing list