Re: [Exim] Planning for Exim 4 - Revised Document

Top Page
Delete this message
Reply to this message
Author: Yann Golanski
Date:  
To: Philip Hazel
CC: exim-users
Subject: Re: [Exim] Planning for Exim 4 - Revised Document
On Tue, Jan 16, 2001 at 10:55:57AM +0000, Philip Hazel wrote:
> ftp://ftp.csx.cam.ac.uk/pub/software/email/exim/Exim4Plan.html
>
> New and changed text is indicated by a green font, so you should be able
> to find it easily.


Here are some comments on it all... There aren't many and I think this
is good plan and should be carried out. Want a hand with anything?

* Configuration perl script.
Is it really needed? Wouldn't it help people to re-write their
configuration so that they *know* what changed and how it changed?

* Routers.
Agree with most of what is said about complexity there. I like the way
this is going, but there maybe a benefit to have sub-section in the
router. Just formating, so it will look like:

a_router_example:
condition: ...
condition: ...
do: ...
do: no_more

* Message arrival rate checking
Since I proposed this in the first place... At E^2, thats already what
we are doing. Since we are load balanced and have multiple servers in
each spool, the problems of flood is very limitted. However, this may
well provide a problem on smaller deployment.

Ceratinly not reject messages -- that's bad (tm). But freeze them should
be fine.

Compile time or configure option?

* Configuration file
I don't see the use of that for configuration files. However, some
filter files *may* benefit from this feature -- for example, Nigel's
ILOVEYOU scanner.

Keep the backslash, it's a `standard way' of doing stuff with Unix.

-- 
Dr Yann Golanski                                      Senior Developer
         Please use PGP: http://www.kierun.org/pgp/key-planet