|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
Re: (solved) SASL problem (cannot connect to saslauthd server: no such file or directory)
From: Patrick Ben Koetter (p
state-of-mind.de)
Date: Wed Aug 24 2005 - 18:51:47 CDT
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
* Alaor B. de Carvalho Neto <alaorfdc.br>:
> >>>I've a smtpd.conf in /usr/lib/sasl2 that contains:
> >>>
> >>>pwcheck_method: saslauthd
> >>>mech_list: PLAIN LOGIN CRAM-MD5 DIGEST-MD5
make mech_list this:
mech_list: PLAIN LOGIN
saslauthd can only handle plaintext-mechanisms and authentication will fail if
a client chooses to use CRAM-MD5 or DIGEST-MD5, which they always do if they
are able to, because they are more secure.
> >>>My main.cf only have the lines to activate the sasl auth, the
> >>>broken sasl for old clients and add to permit sasl authenticated to
> >>>relay.
> >>>
> >>>My postfix ins't running chrooted.
> >>>
> >>>Where I can start?
> >>
> >>/etc/rc.d/init.d/saslauthd start
> >>
> >saslauthd already is started, but I've started it with: saslauthd -a
> >shadow
> >I already have given read previleges do shadow (I know that this ins't
> >secure).
Take it away. saslauthd runs as root. It has every privilege a process can
have.
> I created one symbolic link from /var/state/saslauthd to
> /var/run/saslauthd and now it works, but don't identify... ={ I think
> that I have other problem to solve =P~
saslauthd -m /var/state/saslauthd -a shadow
prick
--
The Book of Postfix
<http://www.postfix-book.com>
saslfinger (debugging SMTP AUTH):
<http://postfix.state-of-mind.de/patrick.koetter/saslfinger/>
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]