From: Andreas Winkelmann (mlawinkelmann.de)
Date: Sun May 27 2007 - 01:10:04 CDT

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On Sunday 27 May 2007 04:39, Mark Edwards wrote:

> Updating from postfix 2.3.3 to postfix 2.3.8 on Ubuntu (that's the
> Edgy to Feisty update) I suddenly started getting warnings in the logs:
>
> May 25 15:37:41 mini postfix/smtpd[4735]: looking for plugins in '/
> usr/lib/sasl2', failed to open directory, error: No such file or
> directory
>
> Its clear that this is because certain processes are chrooted and
> the /var/spool/postfix directory doesn't contain any link to /usr/lib/
> sasl2. If I remove the chroots from master.cf the problem goes away,
> however I don't particularly like that solution. If I `ln -s /usr/
> lib/sasl2 /var/spool/postfix/usr/lib/` I get an error about too many
> levels of symbolic links.
>
> Is this a mis-configuration on the part of Ubuntu/Debian? Should /
> usr/lib/sasl2 be included in /var/spool/postfix?
>
> Moreover, why these errors all of a sudden? Nothing changed in my
> configuration except updating to postfix 2.3.8. Did 2.3.8 decide to
> start warning about something that was there all along.

/usr/lib/sasl2/ contains the Plugins lib*.so and in the case of non-Debian
Postfix Editions the Configuration File smtpd.conf. Everything in it is read
and loaded into Memory before Postfix enters the chroot Jail. There is no
need to link or copy this Directory to the chroot Jail.

It looks like Debian has changed something in their Postfix Packages once
more. Best to ask on a Debian-List or fill in a Bug-Report.

> FWIW, I use Dovecot sasl authentication, so I don't think this is a
> serious issue for me (right?), I just want to get rid of these warnings.

--
        Andreas

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]