|Main Archive Page > Month Archives > postfix-users archives|
On Thu, Jun 17, 2010 at 10:00 AM, Andrew G. Grant
> Unfortunately, looking at another server OS doesn't help me to find the
> answer to this question. But thank you for the suggestion.
I know, but it would simplify your life.
> I am still trying to find out how Apple OS X Server 10.6.3
> (Darwin Kernel Version 10.3.0), running Postfix 2.5.5, Amavisd,
> ClamAV, SpamAssassin, Dovecot, and Squirrel Mail can have
> SASL access Open Directory's LDAP when Postfix isn't compiled
> on my system to use LDAP library types?
Postfix doesn't do SASL on its own, it depends on Dovecot or Cyrus,
just read here:
> This all revolves around finding a way to use:
> reject_sender_login_mismatch on smtpd_sender_restrictions
> without having to keep a separate smtpd_sender_login_maps
> hash file updated.
If you want to be able to use postfix with ldap tables, you *must*
have the ldap support, off course, postfix support "plug-ins"
architecture, so, it is likely that you just need to add the ldap
part. As for Mac: I don't know exactly how to do it, but in the worst
of the cases, it would involved recompiling postfix (or, maybe,
compile the plug-in). I don't know how to do it, because I use
Debian, and I just had to install the package: postfix-ldap, and
everything was just fine after that.
> Currently, I believe SASL is using Open Directory to reference
> User Name and Password information for SASL to work, as I haven't
> duplicated this information anywhere.
> Since my Postfix is not compiled to use LDAP, how is SASL accessing
> Open Directory information?
By default this uses cyrus sasl, so, you should check for it on your system.
> If SASL can access Open Directory, why can't Postfix access Open Directory
> to lookup smtpd_sender_login_maps?
I hope this helps,