[Exim] (still) problems with condition for auth

Page principale
Supprimer ce message
Répondre à ce message
Auteur: Frank Elsner
Date:  
À: Exim users list
Sujet: [Exim] (still) problems with condition for auth
Back to my problem with the condition of my authenticator which is still
unsolved. BTW, it's an exim 3.36.

The OLD authenticator was

plain:
driver = plaintext
public_name = PLAIN
server_condition = \
"${if or {\
{crypteq {$3} {${lookup{$2}dbm{DBM/auth/asmtp}{$value}{junk}}}}\
{crypteq {$3} {${lookup{$2}dbm{DBM/auth/mailszrz}{$value}{junk}}}}\
{crypteq {$3} {${lookup{$2}dbm{DBM/auth/linux}{$value}{junk}}}}\
{crypteq {$3} {${lookup{$2}dbm{DBM/auth/sp}{$value}{junk}}}}\
{crypteq {$3} {${lookup{$2}dbm{DBM/auth/chili}{$value}{junk}}}}\
}{yes}{no} }"
server_set_id = $2

and the NEW is

plain:
driver = plaintext
public_name = PLAIN
server_condition = \
${if crypteq {$3} {${lookup{$2}dbm{DBM/auth/asmtp}{$value}{:fail:}}{yes}{no}}
server_set_id = $2


The OLD authenticator gives (from the -24 output)

lookup yielded: sN8AxHSObS.yU
plain authenticator:
$1 =
$2 = ********
$3 = ********

expanded string: yes                                 <--

SMTP>> 235 Authentication succeeded

235 Authentication succeeded

but the NEW one says
lookup yielded: sN8AxHSObS.yU
plain authenticator:
$1 =
$2 = ********
$3 = ********

expanded string:                                    <--

SMTP>> 535 Incorrect authentication data

535 Incorrect authentication data

The values replaces by "*" are the correct ones and identical for both cases.

I wonder abount the empty expanded string for the NEW authenticator.

--Frank Elsner