Re: Etch sasl weirdness [solved]
Roberto C. Sánchez wrote: On Sat, Jun 09, 2007 at 08:22:40PM +0100, Hans du Plooy wrote: What I did notice is that /etc/defaults/saslauthd mentions /etc/saslauthd.conf, but there is no such file. I also don't see a client config file. # ldap -- use LDAP (configuration is in /etc/saslauthd.conf) So, unless you are having your saslauthd get its authentication information from an LDAP store, then you don't need the file. Thanks Roberto. The /etc/default/saslauthd doesn't actually say that /etc/saslauthd.conf is *only* for LDAP, but the manpage does: FILES /var/run/saslauthd/mux The default communications socket. /etc/saslauthd.conf The default configuration file for ldap support. Cheers Hans -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Etch sasl weirdness
Sorry for the delay in replying.
On Thu, Jun 07, 2007 at 12:31:17PM +0100, Hans du Plooy wrote:
Hi guys,
I'm setting up an Etch server for postfix with smtp auth. I changed
/etc/default/saslauthd so that the mux file gets made under
/var/spool/postfix/var/run/saslauthd. I restarted saslauthd, and
checked that it's working right. It is making the file in the right
place, and ps shows me that it is reading the right settings:
Personally, I think that running Postfix in a chroot is more trouble
than it's worth.
But I'm getting this:
# testsaslauthd -u user -p password
connect() : No such file or directory
and when strace it, I see:
connect(3, {sa_family=AF_FILE, path=/var/run/saslauthd/mux}, 110) = -1
ENOENT (No such file or directory)
Did you try passing the -f switch to testsaslauthd to tell it where the
socket is located? The /etc/defaults/saslauthd file is actually read by
the Debian-provided init script in the sasl2-bin package. The upstream
programs know nothing of that file. Specifically, the testsaslauthd
program, which is a SASL client, won't know where the socket is if you
have moved it.
So saslauthd so sasl seems to be ignoring the -m stuff. If I make a
symling /var/run/saslauthd pointing to
/var/spool/postfix/var/run/saslauthd it works fine.
Is this a bug or am I missing something I should have done?
That is one way to deal with the postfix in a chroot issue and not break
other applications. Other options include taking postfix out of its
chroot or using a local TCP connection.
Regards,
-Roberto
--
Roberto C. Sánchez
http://people.connexer.com/~roberto
http://www.connexer.com
signature.asc
Description: Digital signature
Re: Etch sasl weirdness
Roberto C. Sánchez wrote:
Sorry for the delay in replying.
On Thu, Jun 07, 2007 at 12:31:17PM +0100, Hans du Plooy wrote:
Hi guys,
I'm setting up an Etch server for postfix with smtp auth. I changed
/etc/default/saslauthd so that the mux file gets made under
/var/spool/postfix/var/run/saslauthd. I restarted saslauthd, and
checked that it's working right. It is making the file in the right
place, and ps shows me that it is reading the right settings:
Personally, I think that running Postfix in a chroot is more trouble
than it's worth.
So do I. In fact, that turned out to be the root of my problem. The
howto I was reading assumed that postfix is running in chroot (as it is
by default on Debian), but it wasn't. I remember now when I setup the
box initially - about three years ago - I disabled it for some reason,
can't even remember what.
connect(3, {sa_family=AF_FILE, path=/var/run/saslauthd/mux}, 110) = -1
ENOENT (No such file or directory)
Did you try passing the -f switch to testsaslauthd to tell it where the
socket is located?
I didn't. Just tried it and that solved it. Also tried all of the
above on a fresh Etch install, and the postfix auth works (because it is
chrooted).
What I did notice is that /etc/defaults/saslauthd mentions
/etc/saslauthd.conf, but there is no such file. I also don't see a
client config file.
Thanks Roberto - you pointed me in the right direction.
Hans
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Etch sasl weirdness
On Sat, Jun 09, 2007 at 08:22:40PM +0100, Hans du Plooy wrote: What I did notice is that /etc/defaults/saslauthd mentions /etc/saslauthd.conf, but there is no such file. I also don't see a client config file. # ldap -- use LDAP (configuration is in /etc/saslauthd.conf) So, unless you are having your saslauthd get its authentication information from an LDAP store, then you don't need the file. Thanks Roberto - you pointed me in the right direction. Regards, -Roberto -- Roberto C. Sánchez http://people.connexer.com/~roberto http://www.connexer.com signature.asc Description: Digital signature
