[Mailman-Users] cleaning up config.pck

[Mike Cherry]

Mark,

Thanks the cron/checkdbs script had not been added to the crontab.  Running that script resulted in list1's config.pck shrinking to just 40K.

Cheers,
Mike



On Apr 21, 2010, at 10:52 AM, Mark Sapiro wrote:

> Mike Cherry wrote:
>> 
>> In looking at the dumpdb txt I see the issue is with the hold_and_cmd_autoresponses.  The size of the file does not correlate with the number of subscribers rather the amount of spam the list recieves.  
>> 
>> list 1; config.pck size 16M, 1.2M hold_and_cmd_autoresponses addresses, 113 subscribers
>> 
>> list 2; config.pck size 13M, 1.0M hold_and_cmd_autoresponses addresses, 584 subscribers
>> 
>> list 3; config.pck size 1.1M, 80K hold_and_cmd_autoresponses addresses, 62 subscribers
>> 
>> 
>> I'm assuming that 1.2 million addresses in hold_and_cmd_autoresponses might be keeping the file large?  I am assuming that my problem is with the size of the file as lists with smaller config.pck files release locks quicker and the web admin interface starts much much faster.
>> 
>> In Defaults.pk I have MAX_AUTORESPONSES_PER_DAY = 10.
> 
> 
> Your assumptions are more or less correct, but is cron/checkdbs
> running? It should be deleting all but the current day's
> hold_and_cmd_autoresponses entries from every config.pck every time it
> runs.
> 
> If you're getting spam to a list from a million addresses a day, you
> really do have a spam problem :(
> 
> So I'm guessing that cron/checkdbs is not running or something is going
> wrong with that process. See the FAQ at <http://wiki.list.org/x/H4Cj>
> which may be relevant.
> 
> -- 
> Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
> San Francisco Bay Area, California    better use your sense - B. Dylan