This would have been the first post, except Philip stole that with his Exim
Course spam :-).
Perhaps it is time to kick this list to life now?
To begin with: What characterizes Exim? Chapter 1 and 3 of the Exim
specification describe the basic assumptions and ideas behind Exim, but I
think what matters most to mail admins is the configuration file. Exim is
easy to configure and can do almost anything you can think of.
By now there are many improvement ideas listed on
http://www.exim.org/eximwiki/Exim5. In fact, I think that if all or most of
them were to be implemented (in particular the idea of building the
configuration around Lua or similar), we would hardly recognize Exim anymore,
I think. (This is just an observation of a somewhat philosophical nature. I
certainly don't think nostalgia should limit development.)
How do we start? By making a copy of the current Exim 4 code and start
wielding the sledgehammer, or by starting with an empty plot of land and
picking reusable bricks from the old code? I suppose the latter.
About the configuration language: It would be nice if Nigel would expand on
his idea. Exactly how would the scripting language fit in? What about
performance? Lua claims to be as fast as can be, but isn't it true that
something allround can never be faster and smaller than something
specialized?
--
Magnus Holmgren holmgren@???
(No Cc of list mail needed, thanks)
"Exim is better at being younger, whereas sendmail is better for
Scrabble (50 point bonus for clearing your rack)" -- Dave Evans
