At 2:43 PM +0100 12/9/08, Andre Heine wrote:
Hello all,
supports qpopper the "Auth Plain" command with
PAM together?
We have a special program, which needs the command...
In the documentation I found that only RFC 1939 and 2449
is supported.
The AUTH command is described in RFC 1734 as "optional"...
We use PAM, that's works fine. But in that case "AUTH"
returns the following message:
----- snip ----
a...@se6:~/src> telnet post 110
Trying XXX.XXX.XXX.XXX...
Connected to post.
Escape character is '^]'.
+OK ready <16263.1228829...@post>
AUTH
+OK Supported SASL mechanisms:
X-NONE-SO-USE-APOP-OR-STLS.
Did you compile Qpopper with a SASL library, such as the one from
Cyrus? E.g., use "--with-cyrus-sasl" with ./configure.
"Plain" is not in the list and the switch "-p2" don't take any effect;()
No SASL mechanisms were in the list, which is what happens when you
compile without a SASL library.
The idea of SASL is that the library implements specific
authentication mechanisms, so the individual servers (such as
Qpopper) only need to call the general library functions. This
allows new mechanisms to be invented and supported in one place (the
SASL library).
--
Randall Gellens
Opinions are personal; facts are suspect; I speak for myself only
-------------- Randomly-selected tag: ---------------
It is only the superficial qualities that last. Man's deeper
nature is soon found out. --Oscar Wilde
