On Friday 23 April 2004 08:24, Polarcom Webmaster wrote: > I receive this error when trying to send message to some.domain.com > I have a generated key in .../share/esmtpd.pem > So what's the problem?
How did you generate the key? Courier requires the private key (unencrypted) and the public cert to be in the .pem file. So it needs to look something like: -----BEGIN RSA PRIVATE KEY----- <snip> -----END RSA PRIVATE KEY----- -----BEGIN CERTIFICATE----- <snip> -----END CERTIFICATE----- You can use the scripts mkesmtpdcert, mkpop3dcert, and mkimapdcert in the /usr/lib/courier/share directory to create certs. Also, courier's start-up scripts usually read esmtpd.cnf pop3d.cnf, and imapd.cnf from courier's 'etc' directory and generate the proper certs if they don't exist. So you should be able to just delete whatever you made and courier will generate a new self-signed cert at start-up If you create your own certs then make sure the private key is not encrypted and include it in the same pem file as the cert itself. If you want to create your own self-signed certs using openssl you need to do something along the lines of: openssl req -x509 -newkey rsa:1024 -nodes -keyout key.pem -out key.pem Then fill in the information correctly for your setup as it asks you and you'll have a cert that courier can use. I made my own and them symlinked the three .pem files in the share directory to it so that all three services use the same cert. Jeff Jansen ------------------------------------------------------- This SF.net email is sponsored by: The Robotic Monkeys at ThinkGeek For a limited time only, get FREE Ground shipping on all orders of $35 or more. Hurry up and shop folks, this offer expires April 30th! http://www.thinkgeek.com/freeshipping/?cpg=12297 _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
