[Expired for dovecot (Ubuntu) because there has been no activity for 60
days.]
** Changed in: dovecot (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dovecot in ubuntu.
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
On 25.08.2010 18:03, Carl Nobile wrote:
/etc/ssl/certs/ssl-cert-snakeoil.pem
/etc/ssl/private/ssl-cert-snakeoil.key
Give me output of 'ls -dl' for these files.
ssl_listen: 995
^^ remove this
verbose_ssl: yes
^^ and this
--
dovecot reports Invalid configuration in
$ 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
On 26.08.2010 17:33, Carl Nobile wrote:
So is this a bug in covecot or a bug in the tutorials I have been
reading?
# IP or host address where to listen in for SSL connections. Defaults
# to above if not specified.
#ssl_listen =
It's an IP, not a port. Or IP:port.
--
dovecot reports Invalid
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
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
On 25.08.2010 18:03, Carl Nobile wrote:
I also cannot get dovecot to stop looking in the /root dir, so my log is
full of error messages about permissions being denied.
Can you paste those errors?
--
dovecot reports Invalid configuration in /etc/dovecot/dovecot.conf in all cases
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
On 25.08.2010 18:34, Carl Nobile wrote:
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
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
Is the dovecot process listening on any port?
** Changed in: dovecot (Ubuntu)
Importance: Undecided = Low
** Changed in: dovecot (Ubuntu)
Status: New = Incomplete
--
dovecot reports Invalid configuration in /etc/dovecot/dovecot.conf in all cases
https://bugs.launchpad.net/bugs/623520
13 matches
Mail list logo
