Yahoo Groups archive

Milter-greylist

Index last updated: 2026-04-28 23:32 UTC

Message

Re: [~Disarmed~] Re: [milter-greylist] Implement MySQL backend in Milter-greylist

2009-01-19 by Sven Holz

>
>
> I would prefer to have a "dummy greylist daemon" with something like  
> this http://www.ispras.ru/~knizhnik/fastdb/readme.htm as DB. All the  
> 20 greylists have this dummy greylist configured as peer (only 1)  
> and they send to this dummy peer all the transaccions. As the  
> transactions gets into the dummy, it's replyes to the other 19  
> clients.
>
>
>
>
> It will work as central node, behaving as a normal greylisting  
> daemon (so no need to alter p2p code to much) but acting as  
> redistribution daemon. I see as benefits, lightweight code, no need  
> to involve a huge db daemon, it can be reused all code of p2p trafic.


I think it´s a great idea to have master for the data.

And from my experience parsing a large file is much faster then  
parsing a large database but I´m not a db guru so don´t tak it as  
ultimate truth :-). So maybe you don´t even need any kind of db on the  
master.

And isn´t it possible with the actual software that you use one as  
master with a peering to all milter-greylist hosts and on a simple  
milter-greylist host just an entry to the master?
Hope you get what I mean.

I think you have to have all data in the memory on every host because  
it really would not perform well to generate a request for every  
single mail.
So wouldn´t it work right out of the box now?

Mit freundlichen Gruessen || with kind regards

            i.A. Sven Holz


WOBCOM GmbH
Sitz in Wolfsburg, Amtsgericht Braunschweig HRB 100052
Geschäftsführer: Prof. Dr. Markus Karp

-- 
Sven Holz - IP-Services - WOBCOM GmbH	Phone:	+49.5361.89.11.122
Hesslinger Str. 1-5, D-38440 Wolfsburg		Fax:		+49.5361.89.11.129
Email: sven.holz@... 				Mobile:	+49.151.544.491.22
Jabber: sholz@...

Attachments

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.