> -----Message d'origine----- > De : [Kreiz IT]Cédric GROSS [mailto:[email protected]] > > De : Mark Constable [mailto:[email protected]] > > > > On 04/09/14 19:26, [Kreiz IT]Cédric GROSS wrote: > > > No symlink. Permission wasn't change. > > > > > > Same config file. Upgrade process changed it but I put back my > > > previous config file. I checked diff between config files and it's > > > only comments differ. So should be ok. > > > > I can't really help other than to suggest moving your current pem > > files somewhere safe and create a set of self-signed certs and > confirm > > that they do work, or not. If they work as expected then it narrows > it > > down to your copied pem files (pull them into a editor and make sure > > there are no spaces or control chars). If there is still some errors > > with the self signed certs then it's something to do with courier or > > SSL/TLS libs. > > > > > > I will try that but it's really weird because, even if I get this error > message in syslog, TLS is working... > Cedric >
Just to let you know that problem came from obligation to specify a DH param file in configuration. So just generate a DH param file with command : #openssl dhparam 1024 > dh.pem And then configure TLS_DHPARAMS with the file generated. Restart courier-imapss / courier-pop3ds. Error message doesn't come anymore. Best regards. Cedric ------------------------------------------------------------------------------ Dive into the World of Parallel Programming. The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ courier-users mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
