On Tue, Jan 26, 2010 at 04:45:25PM -0600, adrian ilarion ciobanu wrote:
> > Instead of using a DOMAIN_PORT kludge which requires "reserving"
> > a TCP port or UNIX-domain pathname per customer, it would make
> > sense to use the existing Postfix connection caching mechanism.
> >
> > The idea is to push an open socket into the scache daemon (with a
> > suitable time to live) under the name of the customer's domain.
> > Then, the Postfix SMTP client would automatically find that open
> > socket and start talking SMTP over it.
>
>
> So I would push the socket to scache after I'm done setting it up
> from SMTPD (auth, policy checks) and forget about it. If it times
> out before local smtp will start deliver then the client is welcome to
> reconnect.
> This will happen if it has to happen in SMTPD or in SCACHE the same way.
> In fact it's a descriptor passing tweaked for smtp deliveries. Nice! :)
Yes, but in this case, because the client is authenticated, and requesting
a service that it is willing to wait for with typical SMTP command timeouts,
the scache lifetime of the cache entry needs to be (significantly) higher.
I would suggest ~300s. There may need to be some minor scache code tweaks
to support a new class of longer-lived cache slots.
--
Viktor.
P.S. Morgan Stanley is looking for a New York City based, Senior Unix
system/email administrator to help architect and sustain our perimeter
email environment. If you are interested, please drop me a note.
