On Mon, Jul 27, 2009 at 11:59 PM, Mike
Cardwell<exim-users@???> wrote:
> Todd Lyons wrote:
>
>> This is an implementation of greylisting that uses memcached. Here
>> are what I perceive as advantages:
>>
>> 1. Uses distributed storage instead of local state files.
>> 2. Memcached is *FAST*.
>> 3. Only greylist if reverse IP does not exist for host that is connecting.
>> 4. Uses existing perl module.
>> 5. Two macros do everything.
>> 6. Uses config file to set memcache servers.
>
> Talking to memcached directly from Exim by using ${readsocket} is
> considerably more efficient than using Perl. Also, readsocket is
> compiled into Exim by default and is therefore available in all of the
> standard distributions of Exim.
>
> https://secure.grepular.com/blog/index.php/2009/05/13/accessing-memcached-from-exim/
>
We definitely need native memcached support compiled in exim. It would
be very useful to cache all kinds of lookup data (routing and user
information ...) as well. Currently exim looses all these information
as it is forking new processes for every mail processed.
Cache-invalidation might be a serious problem but there exist several
ways to solve it.
Talking to memcached via socket or perl are technically clever
approaches but i doubt if they are ready for production systems
(error-handling, round-robin, ...).
But who is going to implement it? :)
Chris
