Black/whitelists via SQL lookup

Ken Anderson (Pacific Internet) ka at PACIFIC.NET
Tue Mar 23 18:07:58 GMT 2004


ISP List wrote:

> At 09:16 AM 3/17/2004 -0800, Ken Anderson (Pacific Internet) wrote:
>
>> Hi,
>>
>> We process about 600k msgs across 2 machines, and use per user rules in
>> CustomConfig.pm. We store the per user rules in mySQL, but push them out
>> via a perl script to mailscanner rules directories that MailScanner
>> reads when it starts up.
>>
>> MailScanner loads and stores them all in memory and this increases the
>> startup time as it reads the rules, and the RAM requirements of each
>> MailScanner child process, but once they are in memory, it doesn't
>> matter where they came from (sql or flat file).
>
>
> Did you find that reading them from the SQL database on startup was too
> slow?  I'm just curious on the extra step to have it pushed out to a
> flat file.

No, we didn't even try reading directly from sql db. Our db server and
user interfaces are on a machine on a separate network from the mail
gateways, and we wanted no possible downtime for the MailScanner
processes or broken rules. Reading everything from the db, checking it,
and then writing out flat files into the rules directory is more
reliable than depending on the sql server to be available every time MS
reloads rules.

Ken A
Pacific.Net


> Also, any idea if modifications will be necessary for Oliver's CustomConfig
> code to work in the new "special CustomConfig directory" stuff that Julian
> implemented in 4.29.5?
>
>
> ---------------------------------------
> Mike Bacher / mike at sparklogic.com
> SparkLogic Development / ISP Consulting
> Use OptiGold ISP? Check out OptiSkin!
> http://www.sparklogic.com/optiskin/
> ---------------------------------------
>
>



More information about the MailScanner mailing list