parsing/reading /etc/MailScanner/conf.d/README

[Julian Field]

On 03/12/2009 10:09, Götz Reinicke - IT-Koordinator wrote:
> Julian Field schrieb:
>    
>>
>> On 03/12/2009 08:11, Götz Reinicke - IT-Koordinator wrote:
>>      
>>> Hi,
>>>
>>> I noticed, that I do have the /etc/MailScanner/conf.d/README File and
>>> Mailscanner tries to pare or read it ...
>>>
>>>        
>> MailScanner processes all files in conf.d by mistake. That's why I
>> carefully added comment characters at the start of each line in the
>> README file, specifically so that it wouldn't cause any harm.
>>      
>
> Thats what I thought :-), but wouldn't it be "better" to parse only e.g.
> ".conf" Files?
>    
No, I wanted to parse them regardless of what you felt like naming them.
> You say "by mistake" - are there any parsing-changes in the next MS?
>    
Sorry, I meant "by design" and not "by mistake" ! :(
Typing too fast too early in the morning...
> E.g. sometimes I do have a working config for a system and if I change
> multiple parameters for testing, I just copy the working config to an
> other name (.conf.working), so I can switch back very fast to the
> working config...
>    
cd /etc/MailScanner
cp -r conf.d conf.d.working
should do the job nicely for you.
> Cheers,
>
> 	Götz
>
>
>    

Jules

-- 
Julian Field MEng CITP CEng
www.MailScanner.info
Buy the MailScanner book at www.MailScanner.info/store

Need help customising MailScanner?
Contact me!
Need help fixing or optimising your systems?
Contact me!
Need help getting you started solving new requirements from your boss?
Contact me!

PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654
Follow me at twitter.com/JulesFM and twitter.com/MailScanner


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