Re: [Sqlgrey-users] RELEASE: 1.5.7 (BUGFIXES)

[Lionel B. <lio...@bo...>]

Beast wrote:

> Lionel Bouton wrote:
>
>> Beast wrote:
>>
>>
>>> I have ver 1.5.5 installed, is it safe to just copy sqlgrey(.pl) to
>>> /usr/sbin ?
>>>
>>
>>
>> Yes, or better save your sqlgrey.conf file and "make install" from the
>> source directory (you'll have examples for the new parameters). If you
>
>
> What is the different between optinout and clients_*_whitelist?
>
>

## Whitelists

clients_*_whitelist goal is to allow known servers to bypass
greylisting. The distributed whitelists are used to:
- help performance for known MTA pools where each server can retry to
send the message,
- resolve cases where badly designed MTA don't retry a temporary failed
delivery.

You can add entries to clients_*_whitelist.local to:
- solve the same problems than above until I update the repository from
which SQLgrey users can fetch up-to-date whitelists,
- help performance on highly loaded sites by moving the full fqdns
(although using regexp or *.domain.nam is supported, it doesn't scale as
well) of your heavy senders : SQLgrey won't have to query the database.

## OPTIN/OUT

This is to control which users benefit from greylisting.
This can be used to:
- solve weird problems (like users willing to get spammed!),
- allow spamtraps to be spammed...,
- some admins might want postmaster, info, ... not being greylisted for
various reasons,
- make it a pay-per-user thingy on big systems where using greylisting
can mean serious money for the database system.

There's a README.OPTINOUT which details how to use it.

Lionel.