Milter-greylist

It never ceases to amaze me how easy things are to do in Linux. Your 
script is great and I will implement it.

I do have one question, I see that you don't restart the milter after 
changing the conf file. Does the milter dynamically read the conf file, 
or do we have to restart after each change?

Thanks
Brian.

manu@... wrote:

>Brian Snead <BSnead@...> wrote:
>
>  
>
>>Would you be willing to share the script. I agree that the mxsync should
>>not sync the conf file, but I think you can make a case for it treating
>>each mx servers' hardcoded addr records on startup?
>>    
>>
>
>Well, there is nothing exciting here:
> 
>On each MX, I have /etc/mail/greylist.conf.local that contains the peer
>statements
>
>The script that pushes the new configuration does that:
>
>MX="mx1.example.net mx2.example.net mx3.example.net"
>for m in $MX ; do 
>        scp greylist.conf $m:/etc/mail/
>        ssh $m cat /etc/mail/greylist.conf.local \
>                >> /etc/mail/greylist.conf
>done
>
>And everything is done with RSA keys so that it won't ask a password.
>You can do it with an unprivilegied account, it just needs to have a
>write right on /etc/mail/greylist.conf on each MX server.
>
>  
>