You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Feature request: right now the email in letsencrypt command line is hardcoded in this format postmaster@$domain. This is a good solution right now.
My sugestion is to get email address from ISPConfig client table, if provided.
Also, I don't know if we have to use same domain of the certificate and email address. So, maybe you could get the email address in this order:
from client.email table;
if missing, from cli.ini;
and finally fallback to hostmaster@$domain.
I think hostmaster is better than postmaster, which refers to mail servers admins (even if most of time they are the same guy).
The text was updated successfully, but these errors were encountered:
WKnak
changed the title
Use client email address by default to issue certificates
Use email address field from client table by default to issue certificates
Dec 8, 2015
or add a new emal address on SSL page under Letsencrypt section & ispconfig db.
so if there are a problem with ssl can send directly to hosting, nor to client
ISPConfig 3.1 will coming soon.
Obviously, this version supports Let's Encrypt, so I will help to develop as priority for this stable release.
My development time on repo will be disrupted, but it remains open to collaboration and patch submitted.
Feature request: right now the email in
letsencrypt
command line is hardcoded in this formatpostmaster@$domain
. This is a good solution right now.My sugestion is to get email address from ISPConfig
client
table, if provided.Also, I don't know if we have to use same domain of the certificate and email address. So, maybe you could get the email address in this order:
client.email
table;cli.ini
;hostmaster@$domain
.I think
hostmaster
is better thanpostmaster
, which refers to mail servers admins (even if most of time they are the same guy).The text was updated successfully, but these errors were encountered: