On Mon, 29 Mar 2010 20:32:45 +0200, Patrick Wallura
<patrick.wall...@medictronic.de> articulated:
> I don't see any ssl-cert-file parameter in your config.
I finally figured out what the problem was. It was a misconfiguration
of the MUA.
In any case, I do have the files listed in my dovecot.conf:
ssl_cert_file = /etc/ssl/certs/dovecot.pem
ssl_key_file = /etc/ssl/private/dovecot.pem
I am not sure why "dovecot -n" does not show them. I also noticed
another error. At the end of the output of "dovecot -n" is this
notation:
client:
path: /var/run/dovecot/auth-client
mode: 438
master:
path: /var/run/dovecot/auth-master
mode: 438
However, in my conf file, it is listed like this:(snippet)
master {
path = /var/run/dovecot/auth-master
mode = 0666
}
client {
path = /var/run/dovecot/auth-client
mode = 0666
From the "/var/run/dovecot" directory:
drwxr-xr-x 3 root wheel 512B Mar 26 05:33 ./
drwxr-xr-x 16 root wheel 1.0K Mar 29 05:32 ../
srw-rw-rw- 1 root wheel 0B Mar 26 05:33 auth-client=
srw-rw-rw- 1 root wheel 0B Mar 26 05:33 auth-master=
srw------- 1 root wheel 0B Mar 26 05:33 auth-worker.1250=
srwxrwxrwx 1 root wheel 0B Mar 26 05:33 dict-server=
lrwx------ 1 root wheel 27B Mar 26 05:33 dovecot.conf@ ->
/usr/local/etc/dovecot.conf
drwxr-x--- 2 root dovecot 512B Mar 26 05:33 login/
-rw------- 1 root wheel 5B Mar 26 05:33 master.pid
I am not sure if something is wrong or not. In any case, everything is
working correctly again.
--
Jerry
dovecot.u...@seibercom.net
Disclaimer: off-list followups get on-list replies or get ignored.
Please do not ignore the Reply-To header.
__________________________________________________________________
FORTUNE PROVIDES QUESTIONS FOR THE GREAT ANSWERS: #15
A: The Royal Canadian Mounted Police.
Q: What was the greatest achievement in taxidermy?
