\ help, permissions =

[josh schooler]

Alright I've finally gotten passed the permission issues, apparmor was the issue, I guess I wasn't fully killing the stupid thing, but now I'm having another issue trying to start dovecot

writing the configuration failed:
Could not enable dovecot. Dovecot.service dovecot IMAP server
Loaded: loaded (lib/systemd/system/dovecot.service; enabled)
Activate: inactive (dead) since Wed 2015-07-28- 09:45:16 PDT: 39min ago
Main PID 570 (code=exited status=0/SUCCESS)

July 29 9:45:15 hosting dovecot[611]: master: dovecot v2.2.12 starting up for pop3 (core dumps disabled)
July 29 10:22:33 hosting systemd[1] [/lib/systemd/system/dovecot.service:6] executable path is not absolute, ignoring kill ‘cat /car/run/dovecot/Master.pid’


> On Jul 28, 2015, at 2:28 PM, alvin <alvin.sm at Mail.Linux-Consulting.com> wrote:
> 
> 
> hi josh
> 
>> 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.
> 
> i also do periodic rolling updates from suse-11.x to 12.x to 13.x 
> on the same server and now just run suse-factory and need to
> tweek some apps/settings
> 
> in your case, i'd also check suse iptables rules and also maybe
> it's an issue with /etc/init.d vs systemctl 
> 
> systemctl enable dovecot && systemctl restart dovecot
> 
> ---> what is the output of systemctl status doveoct
> 
> pixie dust
> alvin
> - http://IPtables-BlackList.net
> 
>>> 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.