MailScanner.conf and MailScanner.conf.local

[Rick Cooper]

 > -----Original Message-----
 > From: mailscanner-bounces at lists.mailscanner.info 
 > [mailto:mailscanner-bounces at lists.mailscanner.info] On 
 > Behalf Of Scott Silva
 > Sent: Thursday, July 12, 2007 7:02 AM
 > To: mailscanner at lists.mailscanner.info
 > Subject: Re: MailScanner.conf and MailScanner.conf.local
 > 
 > Julian Field spake the following on 7/11/2007 1:03 PM:
 > > 
 > > 
 > > Nigel Kendrick wrote:
 > >> Julian et al.
 > > 
 > >> It occurs to me that over my not-very-massive pile of 4 
 > mail servers, many
 > >> of the settings are common to the lot and if I tweak a 
 > 'generic' setting on
 > >> one I generally tweak it on all of them. To this end, is 
 > it possible (or
 > >> would it be possible) to have the site-specific settings 
 > in one config file
 > >> and generic ones in another (MailScanner.conf.local and 
 > MailScanner.conf?)
 > >> so I could arrange for a replication script to keep the 
 > generics in sync? 
 > > 
 > > I guess an "include" command could be possible. It would ruin the 
 > > upgrade_MailScanner_conf though which would be a great shame.
 > >> Following on from that, is there (or could there) be a 
 > mechanism to remotely
 > >> restart MailScanner - say, for example, by MailScanner 
 > noticing the creation
 > >> of /etc/MailScanner/restart.flg that could be put in 
 > place during a sync
 > >> operation as mentioned above?
 > > 
 > > Things like rsync allow a command to be executed upon 
 > completion of the 
 > > sync process.
 > > 
 > > Jules
 > > 
 > Or you could run mon or monit or something like that, and 
 > tell it to restart
 > MailScanner if the conf file changes.
 > -- 
 > 

Something I had asked before would be Behavior similar to exim where it
notices when an external file changes and reloads any data it uses rather
than using the cached information. If I change something in a lookup file
(in exim) I don't have to worry about restarting the daemon. So with MS if I
change something in a rule file it would be nice not to have to restart MS
to gain access to the changed information. Before it processes a rulefile
check to see if it has changed and reload if it has. Same with the config
file, check ever XYZ min and reload if the file has changed. I would think
some kind of crc or simple stat would work. Of course that might be
difficult with the internal structure of MS I have never really looked at
the flow that closely

Rick


--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.