On 2014-04-03 23:14, James Knott wrote:
Carlos E. R. wrote:
Well, that is what you have to do to correct *your* apparmour installation. I don't know what all the above means, the "man" is close to unreadable, as typical (you noticed). According to the manual, the options are:
(A)llow, (D)eny, (N)ew, (G)lob last piece, (Q)uit
I let it run. After inherit, there were several allows. Still, after running it, it still won't work with enforce.
You have to restart dovecot, wait a bit, then check again with aa-logprof. It is often several iterations.
This is why I complain so much about the "improvements" that have been made that break so many things. This is complete incompetence, that would have got me fired had I done that at IBM, or elsewhere for that matter.
Calm down... the release notes said that we had to expect problems with apparmour. In case we found them, we had to report them. We did, they created an update or two, and now works now for many people, just not not for you... Wait. Run "rcrpmconfigcheck". Do you see any output related to apparmour or dovecot? If you do, that's your problem. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)