------- You are receiving this mail because: -------
You are on the CC list for the bug.

http://bugs.exim.org/show_bug.cgi?id=838

Nigel Metheringham <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Target Milestone|Exim 4.72                   |Exim 4.73

Phil Pennock <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         AssignedTo|[email protected]              |[email protected]




--- Comment #5 from Phil Pennock <[email protected]>  2010-06-06 04:16:54 ---
In summary, the proposal is to replace the configuration language with Perl in
a future version of Exim.

There's certainly something to the idea of a full scripting language driving an
MTA.  I suggest that the best way to tackle this is to do what Philip Hazel did
when he had some ideas for MTA design with Smail -- he wrote Exim, based on
Smail.

There's certainly a potential to fold that back in.  The new code could become
Exim 5 or 6, if you don't want to keep your own name.  With a JIT you could
probably get back to the speed of Exim as it is now and even improve things. 
Languages such as Lua are designed to be embedded, while Python and Perl 6 both
have active projects on making the languages very fast.  But this is a highly
ambitious major project outside the scope or manpower of the current Exim
maintenance crew.

I'm going to close this as WONTFIX as it's more honest than just leaving it in
the queue.  However, there is an upcoming meeting of Exim developers later this
month; see Nigel's mail to exim-dev, entitled "Meet Up - Taking Exim Forward". 
Perhaps someone else will argue that I'm wrong and open the bug back up.  Or
you could attend?


-- 
Configure bugmail: http://bugs.exim.org/userprefs.cgi?tab=email

-- 
## List details at http://lists.exim.org/mailman/listinfo/exim-dev Exim details 
at http://www.exim.org/ ##

Reply via email to