$$SSL Configuration$$

||include||style.htm||
||include||body.htm||

$$Current certificate$$ ||ifdef||cert_untrusted|| ($$UNTRUSTED$$) ||endif|| ||ifdef||ssl_per_domain|| $$for domain$$: | ||else|| $$for server$$ ||ssl_host|| ||endif||

    	$$Domain (Common Name)$$		: ||cert_domain||

    	$$Issued by$$			: ||cert_issuer||
    	$$Valid until$$			: ||cert_valid||
    	$$Organization Name$$ 		: ||cert_organisation||
    	$$Organizational Unit Name$$ 	: ||cert_unit||
    	$$Locality Name$$ 			: ||cert_city||
    	$$State or Province Name$$  	: ||cert_state||
    	$$Country Code$$ 			: ||cert_country||
    	Extra info			: ||cert_info||

Note: If the private key already existed this is ok, you can proceed, unless you wish to change the bits in your private key!

$$Certificate Signing Request (CSR)$$ | $$SSL certificate(s)$$
||do_show_sslcsr|| | ||do_show_sslcert||

$$Surgemail automatically generates a private key and untrusted certificate when required. To get a trusted certificate you need to generate new a CSR to send to your signing authority.$$

$$Once you have your trusted certificate paste it in the above SSL certificate form replacing the untrusted certificate. The certificate is automatically loaded without restarting surgemail$$.

If you are given intermediate certificates place them under your certificate in the window, leave a blank line between each certificate. Or you can if necessary copy/paste the files directly into the surge_cert.pem file and then restart surgemail.

### Warning:

If your certificate doesn't match the current private key, or is miss formatted etc, then you may loose connection to this page when you press 'save changes', instead use the non ssl admin port: http://your.server:7026, examine mail.err for the cause, remove ssl/surge_cert.pem and restart surgemail to recreate a working unsigned certificate!

### Manual Installation of Certificates - And debugging bad certificates....

You can install your certificate manually by replacing the file ssl/surge_cert.pem with your certificate followed by intermediate certificates, then restart surgemail.
If your certificate was created from a different private key then also replace ssl/surge_priv.pem. If your certificate is faulty in any way ssl will not work, in that case examine mail.err to find the cause, and remove surge_cert.pem and restart surgemail to recreate an unsigned but working certificate.