Re: [exim] auth fails, yet lookup succeeds

Top Page
Delete this message
Reply to this message
Author: Philip Hazel
Date:  
To: Rob Lingelbach
CC: exim-users
New-Topics: Re: [exim] auth fails, yet lookup succeeds [FIXED]
Subject: Re: [exim] auth fails, yet lookup succeeds
On Tue, 10 Oct 2006, Rob Lingelbach wrote:

> 24848 file lookup required for rob
> 24848 in /etc/exim/auth
> 24848 lookup yielded: $1$JP6E/woL
> $Nk8edI1IXRyp4Bt.ZI4yW0:13392:0:99999:7:::
> 24848 crypteq: using crypt()
> 24848 subject=$1$JP6E/woL$zpu//FDOm3pWUX4GtnxsL.
> 24848 crypted=$1$JP6E/woL$Nk8edI1IXRyp4Bt.ZI4yW0
> 24848 fixed_login authenticator:
> 24848 $1 = rob
> 24848 $2 = [password suppressed]
> 24848 expanded string: 0
> 24848 SMTP>> 535 Incorrect authentication data
> 24848 LOG: MAIN REJECT
>
> it all seems to work just fine above -- the file lookup, the decrypt,
> etc. until SMTP gives the 535 Incorrect error.


Notice that the value of "subject" is not the same as the value of
"crypted". That's why the authentication is rejected. The first is the
value obtained by encrypting the first argument of crypteq; the second
is the value of the second argument.

You might like to play with "exim -be" to do some expansion tests to try
to figure out what's happening.

-- 
Philip Hazel            University of Cambridge Computing Service
Get the Exim 4 book:    http://www.uit.co.uk/exim-book