Willie Gillespie wrote:

Does your configuration file have those "<" characters in it? If so, try getting rid of those.

It was pointed out to me that v2 does show "<" characters in the docs, which I guess is a change since v1.

http://wiki2.dovecot.org/SSL/DovecotConfiguration

So, I'm not really sure why it wouldn't be reading your ssl_cert line.

On 15.12.2010, at 21.57, Noel Butler wrote:

...

Willie Gillespie wrote:

...

Does your configuration file have those "<" characters in it? If so, try getting rid of those.

It was pointed out to me that v2 does show "<" characters in the docs, which I guess is a change since v1.

http://wiki2.dovecot.org/SSL/DovecotConfiguration

WTF? What was the rationale behind that I wonder.

It's now possible to put the SSL certs into the config file directly rather than require it to be in a separate file. This made it possible and easy to implement per-IP certificates. Well, now that I think about it, I guess it would have been possible to keep the original ssl_cert_file setting and just mark it as a "this is a filename, read it into memory" setting. That wouldn't have allowed in-config certs though. Also this "<" mechanism works for all settings, and might be useful in some places (such as ssl_key_password = </etc/dovecot/ssl-key-pass).

Yes I know but it does not work !

On 12/15/2010 06:33 PM, Odhiambo Washington wrote:

You can change the "ssl = yes" to "ssl = no" and try again or specify the correct paths to your SSL certs. That is what it is telling you.

On Wed, Dec 15, 2010 at 3:36 PM, Frank Bonnet<f.bonnet@esiee.fr> wrote:

...

hello

trying to install dovecot 2 on a fresh installed machine I get this error message :

doveconf -n> dovecot-new.conf doveconf: Error: ssl enabled, but ssl_cert not set

doveconf: Fatal: Error in configuration file /usr/local/etc/dovecot/dovecot.conf: ssl enabled, but ssl_cert not set the ssl config file look like the following : Thanks for any info.

SSL settings

SSL/TLS support: yes, no, required.<doc/wiki/SSL.txt>

ssl = yes

PEM encoded X.509 SSL/TLS certificate and private key. They're opened

before

dropping root privileges, so keep the key file unreadable by anyone but

root. Included doc/mkcert.sh can be used to easily generate self-signed

certificate, just make sure to update the domains in dovecot-openssl.cnf

ssl_cert =</etc/ssl/certs/dovecot.pem ssl_key =</etc/ssl/private/dovecot.pem

If key file is password protected, give the password here. Alternatively

give it when starting dovecot with -p parameter. Since this file is often

world-readable, you may want to place this setting instead to a different

root owned 0600 file by using ssl_key_password =<path.

#ssl_key_password =

PEM encoded trusted certificate authority. Set this only if you intend to

use

ssl_verify_client_cert=yes. The file should contain the CA certificate(s)

followed by the matching CRL(s). (e.g. ssl_ca =</etc/ssl/certs/ca.pem)

#ssl_ca =

Request client to send a certificate. If you also want to require it, set

auth_ssl_require_client_cert=yes in auth section.

#ssl_verify_client_cert = no

Which field from certificate to use for username. commonName and

x500UniqueIdentifier are the usual choices. You'll also need to set

auth_ssl_username_from_cert=yes.

#ssl_cert_username_field = commonName

How often to regenerate the SSL parameters file. Generation is quite CPU

intensive operation. The value is in hours, 0 disables regeneration

entirely.

#ssl_parameters_regenerate = 168

SSL ciphers to use

#ssl_cipher_list = ALL:!LOW:!SSLv2:!EXP:!aNULL

--

Frank BONNET

01.45.92.66.17

Service des Moyens Informatique Generaux

ESIEE PARIS Cité Descartes / BP 99 93162 NOISY-LE-GRAND Cedex http://www.esiee.fr<http://www.esiee.fr/>

--

Frank BONNET

01.45.92.66.17

Service des Moyens Informatique Generaux

ESIEE PARIS Cité Descartes / BP 99 93162 NOISY-LE-GRAND Cedex http://www.esiee.fr <http://www.esiee.fr/>