One of the
major positives of Open Source to me is that we can share knowledge
and improvements across projects.
I came here to make Postfix users/developers aware of this situation.
That mission has been accomplished. Do with the information what you
want.
I'll be available off list if
n only tell you that I,
as one admin, would absolutely take the extra load to get proper
shutdown behavior.
If I need a mailer on my PDP/11 I'll be sure to consider postfix
for it's stingy use of resources. Does it compile on Unix version
6? :)
--
Leo Bicknell - bickn...@ufp.org
PGP keys at http://www.ufp.org/~bicknell/
shutdown.
And while I support fixing the TLS librarys, the OpenSSL link to
do that is above. Until those libraries are improved, applications
that use them just have to deal with the mess they have made.
--
Leo Bicknell - bickn...@ufp.org
PGP keys at http://www.ufp.org/~bicknell/
roper shutdown sequence provides
quick confirmation that all was well -- where as intentional
incomplete sequences provide an provide an endless stream of dead
ends to chase down while hunting for legitimate problems.
I've made the community aware of my findings. I cannot force the
Postfix com
t point.
And that means _both_ sides must properly perform the termination.
Perhaps Postfix does not support returning to clear text from a STARTTLS
session and doing futher protocol operations. I have not looked. But if it
does, I believe the proper shutdown behavior is a MUST.
--
Leo Bicknell - bickn...@ufp.org
PGP keys at http://www.ufp.org/~bicknell/
see significant unclean shutdowns from
other mailers. Currernly I am seeing about 44% clean shutdowns, and
66% unclean shutdowns from remote Internet mailers. That's why I'm on
a quest here to see if I can get all mailers to handle all of the cases
correctly, and make the Internet a better
