On Mon, 23 Dec 2002, Giuliano Gavazzi wrote:
> I have finished implementing virtual domains on my server with envelope
> and headers rewriting (for pine), but I think pine does not
> authenticate. I use smtp-server=127.0.0.1/novalidate-cert/user=$username
> in pine.conf.
>
> I have an antispam rule that forbids senders in the local (virtual or
> not) domains unless they come from an authenticated connection (I do not
> even trust 127.0.0.1). When I use pine to send this rule kicks in. I
> allow login and plain auth.
>
> Is there a know problem with the way pine handles auth that is
> incompatible with exim ?
These two authenticators work for me for "all"[1] MUAs:
(sorry for the long lines, but you did too!)
begin authenticators
login:
driver = plaintext
public_name = LOGIN
server_prompts = Username:::Password::
server_condition = ${if ldapauth \
{ user="cn=${quote_ldap:$1},ou=People,dc=dcs,dc=qmul,dc=ac,dc=uk" \
pass="$2" ldap:/// }{yes}{no}}
server_set_id = $1
plain:
driver = plaintext
public_name = PLAIN
# this is for pine
server_prompts = :
server_condition = ${if ldapauth \
{ user="cn=${quote_ldap:$2},ou=People,dc=dcs,dc=qmul,dc=ac,dc=uk" \
pass="$3" ldap:/// }{yes}{no}}
server_set_id = $2
Note the "server_prompts = :", which Pine wants in order to continue after
auth plain. The RFCs aren't totally clear as to whether this is Right or
not, but a lot of these RFCs were written by the authors of Pine!
HTH (and sorry for the lack of decent explanation--due to my hangover :-/)
Matt
[1] for small values of "all"
