On 28 Feb 2003, David Bauman wrote:
> However, when I upgraded to Exim 4.12, both of them stopped allowing
> SMTP Authentication, with no changes to the config file... I
> specifically uncommented the following on both servers:
Strange, IIRC nothing changed in this area.
> AUTH_CRAM_MD5=yes
> AUTH_PLAINTEXT=yes
>
> Here's my authenticator's config as well:
>
> begin authenticators
>
> fixed_plain:
> driver = "plaintext"
> public_name = "PLAIN"
> server_prompts = :
> server_condition = ${if crypteq {$3}{${lookup mysql {SELECT
> user.pw_crypt FROM user WHERE username='$2'}}}{yes}{no}}
> server_set_id = $2
>
> login:
> driver = "plaintext"
> public_name = "LOGIN"
> server_prompts = Username:: : Password::
> server_condition = ${if crypteq {$2}{${lookup mysql {SELECT
> user.pw_crypt FROM user WHERE username='$1'}}}{yes}{no}}
> server_set_id = $1
>
>
> Also, when I downgrade back to Exim 4.10, it starts working again... I'm
> wondering what I'm breaking; any help would be much appreciated...
1.) Do you see any logentries?
2.) Are you sure exim is using the right configure-file?
(exim -bP configure_file)
3.) Try to make a debugrun with exim -bh 1.1.1.1 -d and use a fake SMTP
session, does it advertise the auth mechs?
It should show you a line like
250-AUTH PLAIN LOGIN
after you send the EHLO.
What happens if you send
AUTH PLAIN $X
where $X is a base64 encoded "username:password"-string
Nico
