Upgrade to 2.3.1 has failed

Phil Turmel
2018-12-16T12:41:22Z

Andy,

This is just rude.  You have been told multiple times that the less-than
symbol is required to read the certificate from the file.  Otherwise,
the filename is parsed as if it is the certificate itself.  Which yields
garbage.

If dovecot can't read that file, it is *not* dovecot's fault.  You are
simply not going to succeed until *you* figure out what security
differences you have in your new installation.  So dovecot can read the
files.  Every single attempt to connect via openssh depends on dovecot
reading your certificate and key files.  They are pointless exercises
until dovecot actually loads your files.  Focus on the real problem if
you wish to fix your service.

On 12/15/18 5:12 PM, C. Andrews Lavarre wrote:
> Alexander, Thanks, as described before, if I include the "<"
then
> Dovecot fails to start at all.
>
> Thank you again for your time. I have forwarded my latest to Aki to the
> group.


Regards,

Phil