On 2011-07-26 17:40, Claudio Prono wrote:
Il 26/07/2011 17.37, Jerry ha scritto:
On Tue, 26 Jul 2011 17:22:19 +0200
Claudio Prono articulated:
Il 26/07/2011 17.13, Wietse Venema ha scritto:
Claudio Prono:
Hello all,
This problem is made me mad all today, with no solution...
Turn off chroot. This is a magical cure for many mysteries.
http://www.postfix.org/DEBUG_README.html#no_chroot
If that solves the problem, complain to your distributor. They
should not turn on chroot and make life difficult for newbies.
Tnx for the reply, but my chroot is already disabled, as you can see:
#
==========================================================================
# service type private unpriv chroot wakeup maxproc command +
args # (yes) (yes) (yes) (never) (100) #
==========================================================================
smtp inet n - n - - smtpd
As per the<http://www.postfix.com/DEBUG_README.html> page:
Reporting problems to postfix-users@postfix.org
If the problem is SASL related, consider including the output from the
saslfinger tool. This can be found at
http://postfix.state-of-mind.de/patrick.koetter/saslfinger/.
Ok, now works. Is strange but if i set the permissions of the folder
/var/run/authdaemon.courier-imap to 777, it doesn't work, and the error
is the last i have posted.
If i set the permissions correctly, like this:
drwxrwx--- 2 root postfix 4096 Jul 26 17:35
authdaemon.courier-imap
It works...
Maybe a permission check from postfix of "too many permissions" on the
dir/socket?
That would be my supposition, yes.
Connecting to something as security-sensitive as an auth provider should
not happen over a wide-open socket.
--
J.
