|
From: Lionel B. <lio...@bo...> - 2016-06-27 13:41:30
|
Hi, Le 27/06/2016 02:07, Jonathan Nichols a écrit : > Just a couple of questions that I didn’t see covered in the archives… > > I see that there’s a list of pre-whitelisted servers. is this ever updated by the maintainers at any time? Rarely. These pre-configured whitelists are under my direct control (the script updating them fetch files on a web server that I maintain) and my filter to allow new entries in is : - they must be cases that auto-whitelisting doesn't handle efficiently, - they must affect several users. If this doesn't pass the first test this defeats the greylisting process (greylisting is not whitelisting...). If this doesn't pass the second test this might be a fluke or a temporary situation. > Is this something that we can should just do manually? You can maintain whitelists yourself by creating files with ".local" appended to the original name. These files are under your direct control and won't ever be overwritten by SQLgrey. > > if t’s recommended to just deal with it manually, what web interface is recommended these days? > > my setup is pretty straight forward, but there are a couple of different domains. manually adjusting the sql tables would be kind of a pain. You should not have to adjust anything unless your users report delayed emails from specific domains for an extended period (several days). If there is a problem on some origin domains you can inspect the logs to find our what is going on with these domains and if they don't behave well enough for SQLgrey to auto-whitelist them add entries to /etc/sqlgrey/clients_fqdn_whitelist.local or /etc/sqlgrey/clients_ip_whitelist.local (see the original files for the format used). You are then encouraged to report them here so that I can keep track of domains which need whitelisting to perform well. Best regards, Lionel |