Tried disabling apparmor still a no go.

> Date: Mon, 27 Jul 2015 22:23:42 -0400
> From: tmore...@ajmconsulting.ca
> To: dovecot@dovecot.org
> Subject: Re: \ help, permissions issues‏
> 
> Try turning off Apparmor.  When I did the same OpenSuSE upgrade, 
> Apparmor messed up my dovecot installation with similar errors.  I 
> disabled Apparmor and the permissions issues disappeared.  BTW, I gave 
> up trying to re-configure Apparmor and have left it disabled with no 
> issues.
> 
> On 27/07/2015 9:32 PM, josh schooler wrote:
> > both of my other servers its owned by exim, the permissions in the other 
> > two servers are 644, and dovecot starts just fine on those, I don't know 
> > what happened I updated my server from opensuse 12.1 to 13.2 and now 
> > dovecot is refusing to start.> From: alvin...@mail.linux-consulting.com> 
> > Subject: Re: help, permissions issues> To: dovecot@dovecot.org> Date: Mon, 
> > 27 Jul 2015 14:47:14 -0700> CC: alvin...@mail.linux-consulting.com> > > hi> 
> > > > Hey everyone I've tried changing the permissions with the file it is 
> > telling me is giving me the issue, restarted exim and the computer, but 
> > still can't get dovecot to start.> > > > 2.2.13> > > dovecot -F> > 
> > doveconf: Fatal: Error in configuration file 
> > /etc/dovecot/conf.d/10-ssl.conf line 14: ssl_cert: Can't open file 
> > /etc/exim/openssl/exim.crt: Permission denied> > wag ...> > chown root.root 
> > /etc/exim/openssl> chmod 750 /etc/exim/openssl> > chown root.root 
> > /etc/exim/openssl/exim.*> chmod 400 /etc/exim/openssl/exim.*> > OpenSSL 
> > certs should always be read only by root> > you might want to check the 
> > docs regarding uid/gid running dovecot > and uid/gid of dovenull> and 
> > permissions for the dovecot dir tree /etc/dovecot*> > wag ... i think it 
> > should not be owned by exim> > ...> > > ssl_cert = 
> > </etc/exim/openssl/exim.crt> > ssl_key = </etc/exim/openssl/exim.key> > 
> > pixie dust> alvin> - http://NetworkNightmare.net/OpenSSL> - 
> > http://DDos-Mitigator.net                                    
                                          

Reply via email to