Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
Subject: ATRN, connection cacheing (was: ETRN too fast!)
From: Wietse Venema (wietseporcupine.org)
Date: Thu Sep 28 2000 - 09:17:02 CDT

Rask Ingemann Lambertsen:
> Should you still want to overburden Wietze with new things to add to
> Postfix, try ESMTP ATRN (RFC 2645), but IMHO, it fills a much needed gap.
> ETRN doesn't have the security problems of ATRN and is much simpler to
> implement in the server as well as in the client.

That RFC is easy to implement for a monolothic MTA.

It requires jumping a couple hoops with a Postfix/qmail architecture
that has separate agents for sending mail, for receiving mail, and
for running the queue, especially when sending agents are slaves
that get work pushed towards them, unable to take any initiative.

With a distributed MTA, one would maintain a pool of outbound
connections, and when sending mail, one would grab an available
connection rather than creating one, like Postfix currently does.

It adds a bit of complexity, but it could be useful to implement
connection cacheing in the best possible manner.