Hello,
I have opensuse 13.1 and package Dovecot 2.1.17, whole system updated. I use file passwd authentication, here is content my vpasswd file (only for test):
Trying ::1...
Connected to localhost.
Escape character is '^]'.
+OK Dovecot ready.
user user1@example.org
+OK
pass password
-ERR Authentication failed.
In mail log this error:
dovecot: auth: Error: passwd-file /etc/dovecot/vpasswd: open(/etc/dovecot/vpasswd) failed: Permission denied (euid=482(dovecot) egid=479(dovecot) UNIX perms appear ok (ACL/MAC wrong?), dir owned by 0:0 mode=0755)
dovecot: auth: passwd-file(user1@example.org,::1,<l0Hz89L2JwAAAAAAAAAAAAAAAAAAAAAB>): no passwd file: /etc/dovecot/vpasswd
Rights is OK. When I compile a install Dovecot 2.1.17 from source (http://www.dovecot.org/releases/2.1/dovecot-2.1.17.tar.gz) no problem,
file passwd authentication running correct. Problem is IMHO in opensuse package Dovecot 2.1.17 for opensuse 13.1.
On 2014-04-14 16:56, georgeyz wrote:
>
> robin_listas;2636929 Wrote:
>>
>> Apparmour running?
> No, computer is only normal desktop. And moreover, Dovecot compiled from
> sources running corrected!
Well, a default openSUSE 13.1 desktop installation gets apparmour
installed. It came with bugs in the dovecot profiles, so you should
expect problems. Most of them were corrected with updates, so you should
make sure you applied all the official updates (yast online update).
All that is on the release notes. More or less
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
Oh no, on my PC runing my compiled Dovecot, this is OK. Now I install package Dovecot from opensuse and error occurred again! Apparmor disabled and inactive.
I apologize for the confusion…
On 2014-04-15 10:16, georgeyz wrote:
>
> georgeyz;2637037 Wrote:
>> Huh, Apparmor was disabled, but active! My error, sorry. Package
>> Dovecot is OK.
>
> Oh no, on my PC runing my compiled Dovecot, this is OK. Now I install
> package Dovecot from opensuse and error occurred again! Apparmor
> disabled and inactive.
> I apologize for the confusion…
I would recommend to keep apparmour active if your machine serves
dovecot to any other machine.
You can correct AA profiles by running “aa-logprof” now and then.
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)