[imp] Blacklist problem

[Cedric Tardif]

Hi,

I think 600 is to high to.

The problem is now that this value is bugged since you lost information when the max value is reached.

A better way to do it will be to have a error message to the use to tell him that he have reached the maximum number of filter he can have on is blacklist.

I will try to find more about that.

Thank for your reply.

Regards
Cedric


At 14:12 10/12/02, you wrote:
>On Tue, 10 Dec 2002, Cedric Tardif wrote:
>
>> Hi all,
>> 
>> CVS 5 day old horde/imp
>> 
>> I have a user that when he reached 600 blacklisted address.
>> 
>> Now if he add a 601 filter the filter setting is reseted and he only have 1 filter il the blacklist.
>> 
>> It is possible to limit the number of filter a user can create and why the present maximum is 600 ?
>
>I posted the same problem a week or two ago with Horde-2.1/IMP-3.1.  
>Assuming this is the same problem I ran into, the problem is you're
>overflowing the storage capability of horde_prefs.pref_value which is 
>defined as type text.  On my installation, I've done nothing about this 
>yet, as I'm not sure I want users to define so many blacklisted addresses.  
>IMO, imp isn't the best place to do this.  The horde/imp code really ought 
>to be modified to know (it'd probably all have to be configured) the 
>storage limits of the db backend and not overflow them.
>
>----------------------------------------------------------------------
> Jon Lewis *jlewis@lewis.org*|  I route
> System Administrator        |  therefore you are
> Atlantic Net                |  
>_________ http://www.lewis.org/~jlewis/pgp for PGP public key_________