http://bugzilla.suse.com/show_bug.cgi?id=1117844 http://bugzilla.suse.com/show_bug.cgi?id=1117844#c1 Tristan Miller changed: What |Removed |Added ---------------------------------------------------------------------------- Component|AppArmor |Other Assignee|suse-beta@cboltz.de |bnc-team-screening@forge.pr | |ovo.novell.com --- Comment #1 from Tristan Miller --- On further testing, this appears to be the same issue described for Debian at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903161. That is, Dovecot has made a change that no longer allows doveadm to be run by regular users; they must be in the dovecot group. I can confirm that adding myself to the dovecot group fixes the issue. So this isn't an issue with AppArmor. It might help to document the new permission requirement (for example, in a dedicated README file), as proposed in the Debian bug. I'll leave this bug report open in case anyone wants to implement that solution; if not, then this can be closed as RESOLVED/INVALID. -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1117844 https://bugzilla.suse.com/show_bug.cgi?id=1117844#c4 Christian Boltz changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED |--- --- Comment #4 from Christian Boltz --- (In reply to Peter Varkoly from comment #3)

Was fixed in the version 2.13.3 of apparmor-profiles

Peter, I'm sorry to disappoint you, but - as mentioned in the previous comments, this bug is unrelated to AppArmor. Therefore I'm reopening it. Instead, it's about the socket permissions (as in "chmod"), see comment 1 and comment 2 for the details. Marcus, what's the status of the upstream issue? -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1117844 https://bugzilla.suse.com/show_bug.cgi?id=1117844#c6 --- Comment #6 from Tristan Miller --- (In reply to Marcus R�ckert from comment #5)

a better fix than adding the user to the dovecot group:

``` service stats { unix_listener stats-writer { mode = 0666 } } ```

Could you please be more specific? If this line is supposed to go in some configuration file, what is the name of the file and where should this text be inserted? -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1117844 https://bugzilla.suse.com/show_bug.cgi?id=1117844#c8 --- Comment #8 from Tristan Miller --- (In reply to Marcus R�ckert from comment #7)

you have a service stats block already.

Where? You still haven't indicated what file you are talking about. No file in /etc/dovecot or its subfolders contains the string "stats" on my system. -- You are receiving this mail because: You are on the CC list for the bug.