SiegeX-
I am finally getting around to setting up SMTP AUTH on my work server. I need to set up Server-side SMTP AUTH for mobile use (e.g. from cell phones and laptops).
In reading through the set up for cyrus-sasl, I came across a few questions. They are related to the fact that cyrus-sasl is now included in the /n series in Slackware -current. From the changelog:
Quote:
|
n/cyrus-sasl-2.1.20-i486-1.tgz: Added Cyrus SASL library (for Kmail).
|
So I am wondering if instead of compiling cyrus-sasl following your guide I would be able to simply use the newly added official Slackware package.
Some thoughts I had. The SlackBuild script for cyrus-sasl and your config options differ.
First, the SlackBuild creates an i486 build and your guide creates an !386 build. I don't think that is an issue. Either way will work on an i686, I figure.
Next is the config options. We have :
SlackBuild
Code:
./configure \
--prefix=/usr \
--sysconfdir=/etc \
--localstatedir=/var \
--disable-static \
--enable-login \
--disable-anon \
--without-ldap \
--with-saslauthd \
--with-gdbm \
--with-dblib=gdbm
SiegeX
Code:
./configure \
--prefix=/usr \
--enable-anon \
--enable-plain \
--enable-login \
--disable-krb4 \
--with-mysql \
--with-saslauthd=/var/state/saslauthd \
--with-openssl \
--with-plugindir=/usr/lib/sasl2 \
--enable-cram \
--enable-digest \
--enable-otp
I hope this isn't as messy an expalination as I think it's going to be, but...
From the Slackware config.
--prefix=/usr \
Same for both. Doesn't matter.
--sysconfdir=/etc \
--localstatedir=/var \
Slackware standards. Don't think these matter.
--disable-static \
Don't think this really matters. "./configure --help" says that the default is "--enable-static=no" which means that this is really not required, as this gives the same results as the SiegeX build.
--enable-login \
Same for both. Doesn't matter.
--disable-anon \
I think this might be an issue. This is the exact opposite of the guide. Is the "--enable-anon" switch required for Sendmail to function properly with Server-side SMTP-AUTH?
--without-ldap \
Don't think this really matters. "./configure --help" says that the default is "--with-ldap=no" which means that this is really not required, as this gives the same results as the SiegeX build.
--with-saslauthd \
Not sure this really matters. "./configure --help" says:
Code:
--with-saslauthd=DIR enable use of the saslauth daemon using state dir DIR
I think that is the equivalent of
Code:
--with-saslauthd=/var
Whereas the SiegeX switch is:
Code:
--with-saslauthd=/var/state/saslauthd
Am I wrong about the default? Does it matter?
--with-gdbm \
--with-dblib=gdbm
Don't know if these matter at all.
Now, onto what we don't see in the SlackBuild config:
--enable-plain \
This seems to be enabled by default anyway, so I don't think it matters.
--disable-krb4 \
This seems to be disabled by default anyway, so I don't think it matters.
--with-mysql \
Since no PATH is specified, isn't this the same as no switch?
Is mysql even used for SMTP AUTH? If so, does mysql need to be running for SMTP AUTH to function properly?
--with-openssl \
Since no PATH is specified, isn't this the same as no switch?
--with-plugindir=/usr/lib/sasl2 \
This seems to be the default path, so I don't think it matters.
--enable-cram \
This seems to be enabled by default anyway, so I don't think it matters.
--enable-digest \
This seems to be enabled by default anyway, so I don't think it matters.
--enable-otp \
This seems to be enabled by default anyway, so I don't think it matters.
So, what do you think? The anon switch seems like the only possible real issue. Any thoughts?
If the new Slackware package won't work for Server-side SMTP AUTH, I will probably use the SlackBuild as a base and change the switches. What are the best choices?
Thanks in advance,
, I'm learning fast that short-cuts are not the way toward progress. SiegeX, thank you for making this easy and teaching me additional tips.
