security_tokens exhausted userprefs database

It seems that SM 1.4.20 puts a rather large security_token prefkey in 
the userprefs database (we use the mysql backend). Because of the large 
number of entries (45K users0, I have exhausted all the space in the 
database which causes SM to fail. Here is the check table output:

Table     Op     Msg_type     Msg_text
squirrelmail.olduserprefs     check     warning     Datafile is almost 
full, 4294967288 of 4294967294 ...
squirrelmail.olduserprefs     check     error     got error: 127 when 
reading datafile at record: 40...
squirrelmail.olduserprefs     check     error     Corrupt

The mysql server is 4.1.22. I copied the table and the copy ended up 
being 200MB smaller so my 45,000 users can use SM for now. This only 
buys me a little time though to address the problem better. I have 
noticed that SM never seems to delete any entries from the userprefs db 
backend. If you edit an entry it just seems to create a new entry with a 
bigger id number and somehow (haven't looked into yet) just seems to 
know to use the highest numbered entry. This has created an ever 
expanding userprefs db over the years. I've always meant to ask about 
that but never did. Now with these huge security_token prefvals in the 
userprefs db it's become a crisis. What can be done?

thanks,
David

-- 
David Severance
Central Computing Services
Office of Information Technology
(949) 824-7552
[email protected]


------------------------------------------------------------------------------

-----
squirrelmail-devel mailing list
Posting guidelines: http://squirrelmail.org/postingguidelines
List address: [email protected]
List archives: http://news.gmane.org/gmane.mail.squirrelmail.devel
List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-devel