http://bugzilla.opensuse.org/show_bug.cgi?id=1099764 http://bugzilla.opensuse.org/show_bug.cgi?id=1099764#c2 David Chewning changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(chevy.stroker@yah | |oo.com) | --- Comment #2 from David Chewning --- I ran across this after seeing two people with issues i the opensuse forms with denied file permissions after running the script. My apologies if I am incorrect. Please give me a few hours to see if I can reproduce the dovecot error and report back. I only know I did not receive their errors when I placed my certs inside of /etc/dovecot. I am learning Apparmor and may have jumped the gun on my conclusion. I will provide you a test case where it breaks or report back if I cannot produce the case. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1099764 http://bugzilla.opensuse.org/show_bug.cgi?id=1099764#c4 Christian Boltz changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |INVALID --- Comment #4 from Christian Boltz --- (In reply to David Chewning from comment #3)

Here is where things break and /usr/share/doc/packages/dovecot/README.SUSE seems to be incorrect. 1. Instructed to edit /usr/share/doc/packages/dovecot/dovecot-openssl.cnf - Completed.

Having to edit a file in /usr/ doesn't sound like the best idea ;-) When you report the other issues for README.SUSE, you should probably also add a note about this detail.

[...] The individuals complaining about a permission error seemed to be running up against an Apparrmor issue since they were placing their cert/key in /etc/postfix.

Right, that obviously isn't allowed in the dovecot profiles.

On looking at Apparmor I did not find the reference to /etc/ss/private (my grep -R must have failed me).

See my previous comment - the rule says /etc/ssl/**, so you won't find "private" in it.

Apologies for reporting the wrong issue, but there does appear to be a documented steps issue in /usr/share/doc/packages/dovecot/README.SUSE which maybe easier to fix.

No worries - I prefer a superfluous bugreport over having something unnoticed. And, as a side effect, you probably learned something ;-) I'll close this bugreport - in theory, you could move it to the dovecot maintainer to get README.SUSE fixed, but opening a new bugreport (you can even do some copy&paste) makes things less confusing ;-) -- You are receiving this mail because: You are on the CC list for the bug.