This is the same bug as 590570, but this one has been around longer.
I think the real issue underlying this bug is in bug 525154 which
relates to a race condition while starting portmap which in turn starts
statd. This only seems to be an issue if you have /var as a separate
mount point where
Post 13 in bug 525154 above has solved the issue with statd, but now
autofs is failing to start. I tried to something similar with
/etc/init/autofs.conf but to no avail. Still no joy here.
k3nt-1 are you seeing the error messages in your /var/logs/boot.log file
that I posted above?
--
autofs
Public bug reported:
If dovecot -n is executed it will show the wrong settings. In other words it
seems to be ignoring what is in the /etc/dovecot/dovecot.conf
completely. For example I only have pop3s set in protocols but it is
permitting everything. Also the wrong certs are being used not
Yes the dovecot-postfix package is installed. I'm am using 10.04 Lucid.
I updated the file in /etc/dovecot/conf.d to what I want, now dovecot -n
gives me the right info, but I still get this:
$ openssl s_client -connect localhost:995
connect: Connection refused
connect:errno=111
This also
Yes port 110 only, but no matter what I do it will not listen to port
995.
--
dovecot reports Invalid configuration in /etc/dovecot/dovecot.conf in all cases
https://bugs.launchpad.net/bugs/623520
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Sorry for putting this directly into the post, but I was not on site
when I ran the command and it was a lot easier to just grab the screen
output an past it in.
These are the certs and keys on my box.
$ ll /etc/ssl/certs/ssl-mail.pem
lrwxrwxrwx 1 root root 36 2010-07-28 22:19
I know I'm not the only person getting this issue. It was said the issue
is that the /etc/aliases file needs to point to a valid user on the
system other that root. This I fix, but dovecot doesn't seem to listen
to this even after bouncing both postfix and dovecot.
The error below will show up in
OK, I waited a day to see how the changes I made to the /etc/aliases
file went and that seemed to solve the issue with dovecot trying to do
things in the /root/ dir.
There is still the issue where dovecot will NOT listen to port 995
either locally or externally.
$ openssl s_client -connect
$ ls -dl /etc/ssl/certs/ssl-cert-snakeoil.pem
-rw-r--r-- 1 root root 660 2010-01-27 22:39 /etc/ssl/certs/ssl-cert-snakeoil.pem
$ sudo ls -dl /etc/ssl/private/ssl-cert-snakeoil.key
-rw-r- 1 root ssl-cert 891 2010-01-27 22:39
/etc/ssl/private/ssl-cert-snakeoil.key
OK, it seems removing both
I suppose that
ssl_listen = *:995
would have worked.
So I have dovecot working now I cannot access postfix through smpts port
465. Almost the same problem I had with dovecot.
--
dovecot reports Invalid configuration in /etc/dovecot/dovecot.conf in all cases
I have finally physically got to where the machine is and rebooted it
after making the changes to /etc/pam.d/common-auth. This has solved the
issues I originally posted here. It has not solved the portmap issues I
mentioned above which indeed seems to be a completely separate issue.
Daniel thanks
11 matches
Mail list logo
