Matus UHLAR - fantomas:
> >> >A. Schulze:
> >> >> I like to ask about a documented limitation
> >> >> (http://www.postfix.org/CONNECTION_CACHE_README.html#limitations)
> >> >>
> >> >> "For this reason, the Postfix smtp(8) client always closes the
> >> >> connection after completing an attempt to deliver mail over TLS."
> >>
> >> On 07.03.18 09:07, Wietse Venema wrote:
> >> >Indeed. Postfix can migrate the TCP connection from one process to
> >> >another, but the TLS library does not support migration of live TLS
> >> >state. It supports reuse on new connections only.
> >> >
> >> >Possible solutions would be:
>
> >Matus UHLAR - fantomas:
> >> a smtp client that able to process multiple mails in a single run is not
> >> planned, correct?
>
> On 15.03.18 09:22, Wietse Venema wrote:
> >Wasn't a dedicated per-destination delivery agent one of the possible
> >solutions?
>
> if you mean this one:
>
> > - For each destination, use dedicated SMTP clients that handle all
> > TLS sessions with that destination (no inter-process migration),
> > and cache TCP+TLS state in those processes. Unfortunately, that
> > does not scale to thousands of destinations.
>
> ... which does not scale, I was under impression that it requires site
> configuration, or keeping multiple clients alive.
Indeed.
> what I meant, is that if SMTP client connecting to destination couldn't
> try to deliver multiple (all) mail directed to the destination and then
> quit, the only difference would be it could deliver more than just one mail.
Indeed. And there is no scalable approach for doing that.
Wietse
