Comment 11 for bug 1594202

Thanks for the feedback, and you likely meant bug 1373070 - the other one is about your apport not being able to report.

I have created a new KVM installed dovecot via mail-stack-delivery as I usually did and started to similarize our configurations.

I found that you had no mail-stack so I had to remove some configs I had - in others you had customized your system

I needed to drop:
/etc/dovecot/conf.d/20-lmtp.conf
/etc/dovecot/conf.d/20-pop3.conf
/etc/dovecot/conf.d/auth-ldap.conf.ext
/etc/dovecot/dovecot-ldap.conf.ext

And I adapted the following which differed
Diff:
dovecot/conf.d/10-ssl.conf
  adapted, enable ssl as required (except using self signed cert in my case)
dovecot/conf.d/20-imap.conf
  adapted (max connections)
dovecot/conf.d/10-mail.conf
  adapted, moving inbox to /var/mail
dovecot/conf.d/10-auth.conf
  adapted, disable plaintext auth

Finally I needed to add one that you had but I didn't:
./dovecot/dovecot-db.conf.ext
  This was only delivered in /usr/share in precise, and dropped since then - taking yours for now anyway despite I think Berkley DB support isn't existing atm.

Checking server and apparmor status with that after a full reboot:
No apparmor Denies.

I tested it a bit by conencting for imap, pop3 and smptp (postfix in that latter case) - but no matter what I didn't get any apparmor issues.

Here a log of what I see - all as it should be: http://paste.ubuntu.com/22147539/

I'd be interested in:
a) if you have a different report on "sudo apparmor_status"
b) if the messages you see are aligned to any activity like "receiving a mail"

All others were the same by md5sum.