sqlgrey-users

[Sqlgrey-users] RELEASE: 1.5.7 (BUGFIXES)

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

1.5.7 is on sourceforge.

- The memory leak should be fixed.
- Migrating from earlier version will not lose first_seen values.
- The config directory can be changed if needed.


There's a preliminary log parser, it doesn't do anything exciting and
wasn't meant to be released in this shape but there were urgent bugfixes
to release. Anyway you can check it out.

Lionel.

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

[Beast <be...@i6...>]

Lionel Bouton wrote:
> 1.5.7 is on sourceforge.
> 
> - The memory leak should be fixed.
> - Migrating from earlier version will not lose first_seen values.
> - The config directory can be changed if needed.
> 
> 
I have ver 1.5.5 installed, is it safe to just copy sqlgrey(.pl) to 
/usr/sbin ?


-- 

--beast

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

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

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
need an init-script you can use "make rh-install" instead, it installs a
SysV init script, "make gentoo-install" installs a Gentoo init script.

That said, if you can, it's even safer to use the packaging system of
your distribution (easy uninstall, dependency resolution, ...).

On RPM-based distros, you can make an rpm by running "rpmbuild --ta
sqlgrey-1.5.7.tar.bz2", on Gentoo you can fetch an ebuild from sqlgrey's
sourceforge page (http://sqlgrey.sf.net/).

I'll start to provide rpms on sourceforge again shortly.

Lionel.

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

[Beast <be...@i6...>]

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?


-- 

--beast

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.