Hello, I recently upgraded to courier-0.40.1 from 0.38.x. My setup consists of four virtual domains each with respective IP addresses. Each domain has SMTP (for external mail delivery), SMTPs (for secure authenticated relay), POP3s, and IMAPs. For the latter three services (SMTPs, POP3s, IMAPs) I have been heavily relying upon the somewhat undocumented feature of the *.pem.<ip_address> for IP-address specific SSL certificates.
However in the latest version, the esmtpd.pem.<ip_address> feature seems to be broken or missing. So in the interim I have created a esmtpd.pem file, but this does not give the desired effect since the CN name of this certificate will not match the domain name of the IP-address to which the user connects. In fact it appears that when you configure Courier for SMTP over SSL, the SMTP server will not start up unless an esmtpd.pem file exists. Further, in my previous installation of 0.38.x, I found that when I used the esmtpd.pem.<ip_address> feature, Courier would only advertise the STARTTLS feature over port 25 connections if the "esmtpd.pem" file existed. In other words, a zero-size esmtpd.pem file would allow for advertising the STARTTLS authentication method, and correctly deliver the IP-address specific certificate to the connection. This feature removed the need for people to use port 465 for secure authenticated relay. Am I doing something wrong or has a feature of courier been wiped away? __________________ Thanks in advance, Suresh ------------------------------------------------------- This sf.net email is sponsored by: To learn the basics of securing your web site with SSL, click here to get a FREE TRIAL of a Thawte Server Certificate: http://www.gothawte.com/rd524.html _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
