Menu
▾
▴
Re: [Sqlgrey-users] Re: Is clients_fqdn_whitelist.local still being used?
|
From: Lionel B. <lio...@bo...> - 2005-03-14 21:47:18
|
Lionel Bouton wrote the following on 11.03.2005 14:23 : > Klaus Alexander Seistrup wrote the following on 11.03.2005 14:06 : > >> I wrote: >> >> >> >>> # GMX >>> /^(mail|mx0|pop|imap)\.gmx\.(de|net|co\.uk)$/ >>> >> >> >> Gmail's outgoing servers: >> >> # Gmail >> /^[mrw]proxy\.gmail\.com$/ >> >> are being ignored, too... >> >> >> > I'll look into it this evening or this week-end. > Just tested with 1.5.3. WORKSFORME(tm). When SQLgrey detects a change in the local file it logs a reload like this (even with 'quiet'): Mar 14 22:33:38 ns sqlgrey: reloading /etc/sqlgrey/clients_fqdn_whitelist.local just add a blank line somewhere and wait for an SMTP connexion... If it doesn't log a line like this, here's what could have happened: The code works by checking the mtime of the *.local files (if the file doesn't exists it is considered having a 0 mtime). I chose this method and not a content check because the check is done on *each* request to SQLgrey. A stat call is much much faster than a file open and read... The only reason why the reloading wouldn't work is if these *.local files traveled into the past. Either because at one time they were in the future or the last update put them in the past... Probable solution: restart SQLgrey and don't handle these files on systems in the future, past or an alternate dimension. Cheers, Lionel. |
