If you are using postfix then you can run sqlgrey in
"learn" mode for a couple of weeks to pre-prime the tables.
That worked very well here and resulted in very little user
impact when we actually made it active.
Ken
On Fri, May 23, 2008 at 02:29:32PM +0200, Lionel Bouton wrote:
> Yann Cezard wrote the following on 23.05.2008 14:06 :
> > Hi,
> >
> > I was wondering if there was any tool to migrate postgrey BDB data
> > to an SQLGrey database ?
> >
>
> SQLgrey was initially a fork of postgrey, but there's nearly no original
> code left. The greylisting process uses it's own algorithm and data
> formats so migrating postgrey data might not be straightforward.
>
> > I can still try to code one myself, but I don't want to loose time
> > if someone already does.
> >
>
> I'll simply switch from postgrey to SQLgrey without migrating data. I
> recently installed SQLgrey for a customer : the auto-whitelists where
> ~50% effective in 3 hours and ~80% in 24 hours, with a limit reached at
> around 85-90%. So if you time it right, installing the greylisting
> during low-usage periods, nobody even notices the change. This is even
> more true since the mail reliability went down the sink thanks to
> aggressive webmail services dropping mails instead of bouncing them
> (*cough* hotmail *cough*): people slowly get used to low-quality service
> and often assume there's a problem at one of the two end of the pipe and
> work around it without bothering admins :-/.
>
> For the case above, the only end-user reaction was : "What did you do?
> Most of us didn't receive any SPAM since yesterday!".
>
> Lionel
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Sqlgrey-users mailing list
> Sql...@li...
> https://lists.sourceforge.net/lists/listinfo/sqlgrey-users
>
|
