Re: No supported cipher suites have been found.

 can confirm that if you build I pem by "cat fullcert.cer key.car >
fullcert.pem" (where the origin files are generated by acme.sh or certbot),
the result will work for courier.
AFAIK in mine the pem is in this order: server,intermediate,key

On Sun, Dec 1, 2024 at 2:24 PM Sam Varshavchik <[email protected]>
wrote:

> Mike Wright writes:
>
> > On 12/1/24 12:56, Sam Varshavchik wrote:
> >> Mike Wright writes:
> >>
> >>> Changed permissions to -rwxr--r-- and got the same results.  Here is
> the
> >>> complete error message:
> >>>
> >>> Could not read certificate from dhparams.pem.
> >>> 4027B72ADD7F0000:error:1608010C:STORE
> >>>
> routines:ossl_store_handle_load_result:unsupported:../crypto/store/store_result.c:
>
> >>> 151:
> >>>
> >>> Unable to load certificate
> >>
> >> This is suggesting that it's trying to read a certificate, and not DH
> >> parameters.
> >>
> >> I presume that TLS_CERTFILE is not pointing to the dhparams file.
> >
> > esmtpd-ssl
> >
> > TLS_PRIVATE_KEYFILE=/etc/courier/my-privkey.pem
> > TLS_CERTFILE=/etc/courier/my-fullchain.pem
> > TLS_DHPARAMS=/etc/courier/dhparams.pem
> >
> > TLS_CERTFILE is the only certificate that openssl can read
>
> The private key file is not password protected, is it? There is no
> mechanism
> to provide a password to decrypt the private key file.
>
> Also, since there's a chain involved here, the intermediate cert and your
> signed cert must appear in the certificate file in a specific order, which
> I
> can't remember. Try reversing the order of your certificate and the
> intermediate cert, in the certificate file.
>
> _______________________________________________
> courier-users mailing list
> [email protected]
> Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
>

_______________________________________________
courier-users mailing list
[email protected]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users