On Wed, Aug 05, 2009 at 04:28:22PM -0500, Noel Jones wrote:
> Jay G. Scott wrote:
>> Greetings,
>>
>
> Instructions to test SASL:
> http://www.postfix.org/SASL_README.html#server_test
[snip]
Sigh. Truly, I am a noob.
I spent all morning getting the sasl2-sample-[server|client] to
finally give me a successful test. (From the Hildebrandt and
Koetter book)
sasl2-sample-server -p 888
sasl2-sample-client -p 888 smail
sasl2-sample-client -m PLAIN -p 888 smail
also works.
The daemon started thusly:
/usr/sbin/saslauthd -m /var/run/saslauthd -a pam
So that means saslauthd is working, right?
However, this does not work:
[r...@smail ~]# telnet smail 25
Trying 10.3.16.25...
Connected to smail.arlut.utexas.edu (10.3.16.25).
Escape character is '^]'.
220 smail.arlut.utexas.edu ESMTP Postfix
EHLO arlut.utexas.edu
250-smail.arlut.utexas.edu
250-PIPELINING
250-SIZE 10240000
250-VRFY
250-ETRN
250-STARTTLS
250-AUTH LOGIN PLAIN
250-AUTH=LOGIN PLAIN
250-ENHANCEDSTATUSCODES
250-8BITMIME
250 DSN
AUTH PLAIN XDB0ZXN0XDB0ZXN0cGFzcw==
535 5.7.0 Error: authentication failed: bad protocol / cancel
quit
221 2.0.0 Bye
Connection closed by foreign host.
I used saslpasswd2 to set up the user, I reset the unix password
to match it. I used this to generate the AUTH PLAIN string:
perl -MMIME::Base64 -e 'print encode_base64("\\0test\\0testpass");'
I assume I haven't told you enough, so my first question is
what do you need to know?
How can the protocol be bad? I explicitly asked for PLAIN
on sasl2-sample-client and it worked.
j.
>
> Mutt info:
> http://mutt.kublai.com/
>
> -- Noel Jones
>
[snip]
--
Jay Scott 512-835-3553 g...@arlut.utexas.edu
Head of Sun Support, Sr. Operating Systems Specialist
Applied Research Labs, Computer Science Div. S224
University of Texas at Austin
