Bug#398224: This is a design flaw

[Andreas Metzler]

On 2006-11-12 Julien Danjou <acid at debian.org> wrote:
> clone 321025 -1
> reassign -1 exim4-config
> severity -1 important
> retitle -1 "Please include greylistd ACL configuration files"
> thanks

> On Sun, Oct 29, 2006 at 01:46:26PM +0000, Stephen Gran wrote:
[...]
>> The simplest solution is to just store the acl files as
>> /etc/greylistd/exim-{rcpt,data}-acl and ask the exim4 maintainers to put
>> an 
>> .include_if_exists /etc/greylistd/exim-$acl-acl

>> at the right moment in the default acl.  Then you can manage your own
>> file as you like, and not break unrelated software.

>> I have pinged Zugschlus on IRC about this, but not heard back yet.

> I'm planning to upload a new version of greylistd based on this.
> I'd like to do it with synchronisation with the exim4 maintainers, so
> I'm cloning and assigning this bug to them in order to track this down.

> Please keep me in touch as soon as you're ok to this change.

> The files would be 
> /etc/greylistd/exim-rcpt-acl
> /etc/greylistd/exim-data-acl

> and should be included from:
> /etc/exim4/conf.d/acl/30_exim4-config_check_rcpt
> /etc/exim4/conf.d/acl/40_exim4-config_check_data

I have a couple of questions about this:

How are you going to handle the "greylistd is removed but not purged
case"?

Where exactly would you want the references to be added?

There is also the issue of adding two stat() calls for every forked
daemon.
cu andreas
-- 
The 'Galactic Cleaning' policy undertaken by Emperor Zhark is a personal
vision of the emperor's, and its inclusion in this work does not constitute
tacit approval by the author or the publisher for any such projects,
howsoever undertaken.                                (c) Jasper Ffforde