On Tue, Apr 01, 2014 at 06:24:52PM +0200, Andrea wrote:
> > No, it is a Cyrus SASL configuration problem, Postfix is just the messenger
> > between Cyrus SASL and the SMTP client.
> >
> > Perhaps testsaslauthd is not the right tool to test with, because
> > you're trying to use rimap, auxprop, ... which are not directly
> > implemented by saslauthd. In fact it is not clear why you need
> > saslauthd at all if you're using rimap, but I must admit to an
> > incomplete familiarity with this part of Cyrus SASL, I would
> > move this question to a Cyrus SASL list if there is one.
>
> Well, I'm newbie for sure about this, I was trying to use saslauthd
> because of some how-to I found on web.
One question we have not discussed is file permissions and chroot.
To use saslauthd, the Postfix smtpd(8) server must be able to access
the saslauthd socket. You probably performed your tests as root,
but smtpd(8) will connect to SASL while running as the $mail_owner
(typically "postfix") user. Furthermore, if you configure Postfix
in master to run smtpd(8) chrooted, the saslauthd socket may be
outside the chroot jail.
You need to make sure that the saslauthd socket is accessible inside
chroot if applicable, and the "postfix" user (or primary group of the
"postfix" user) can access the saslauthd "mux" socket.
Perhaps someone else on the list can provide some additional guidance
on how to properly configure the socket permissions. You need to
look at you master.cf file and determine whether smtpd(8) is chrooted
or not (yes unless chroot column is "n").
--
Viktor.
