How do Cerbot files map to Dovecot?

[me at tdiehl.org]

On Thu, 12 Nov 2020, Raymond Herrera wrote:

> I am postponing the Apache plugin issue (CentOS is not Certbot friendly) and

For the record, certbot works just fine on CentOS. It just requires that you
understand how things work. :-)

The plugin which you seek is called python2-certbot-apache.noarch. You can 
see all of the available plugins on CentOS 7 by running the following:
yum list \*certbot\*

In addition there are MANY other packages available for generating LE certs.
Most are not included in CentOS or EPEL. Some are easier to configure some not
so much. It really depends on your requirements and skill level.

> requesting a standalone, generic certificate. After the command "1: Spin up a 
> temporary webserver" I have the following 2 files in the folder 
> /etc/letsencrypt:
>
> -rw-r--r-- 1 root root  924 Nov 12 11:14 csr/0000_csr-certbot.pem
> -rw------- 1 root root 1708 Nov 12 11:14 keys/0000_key-certbot.pem
>
> The "key" is probably a direct replacement for the file in the distribution. 
> What about the "csr" file? It seems to be a request, not the certificate 
> itself.

You have something mis-configured or something is running on port 80 when Certbot
is trying to install a tmp web server on port 80. What is mis-configured or what
is running on port 80, I cannot tell with the information you have provided. I
can tell you I have been running Certbot for the last 3 or 4 years without
issue on various CentOS systems I maintain.

In addition, I suspect this whole thread is off topic for the Dovecot list.

If you want further help, I suggest asking on the CentOS list.

Regards,

-- 
Tom			me at tdiehl.org