OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
 
Re: best greylist method

From: Mike Horwath (drechsauiphouse.net)
Date: Tue Aug 01 2006 - 21:12:56 CDT


On Jul 30, 2006, at 6:04 PM, Baltasar Cevc wrote:
>> With multiple inbound systems, a database master is used, with
>> slave info of our virtual tables shared out to the inbound
>> servers. The greylisting database is *not* mirrored, and the
>> sqlgrey daemons connect to the master server on the greylisting
>> database for R/W access.
> Do you have any hints on what to mirror? Currently, I only use one
> MX, however we're planning a backup server.
> I noticed many spam senders will try to deliver mails to the host
> the A record points to if the MX produces a softfail; considering
> this I assume it would be ideal to share the whilelists but use
> separate greylisting records as spam would slip trough otherwise.
> Or can this be handled well enough by tuning the delay?

Well, that depends on what you are trying to accomplish.

Myself - my email system is set up so that it has 2 databases running
- one is mirrored to the slaves to lookup information.

The other is the sqlgrey database itself, which I don't mirror as I
want my frontend systems supporting greylisting to have matching data
at all times without the latency of mirroring. Sure. MySQL is
fast...but a hammering server will generate multiple 'writes' with
the same credentials - I don't need that.

make sense?

--
Mike Horwath drechsauiphouse.net
                          ipHouse - Welcome home!

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (Darwin)

iD8DBQFE0AouSlrD+aGww4ERArbPAJ99v4vu7QLxi0TZXzIa3VrUDK8lOACfdCtW
ga8aUhFg70FKqDzMQX4P9T0=
=x2Wv
-----END PGP SIGNATURE-----