Re: [exim] Opposing RFCs ? - Case In/Sensitive AUTH SASL Met…

Top Page
Delete this message
Reply to this message
Author: Nicola Tiling
Date:  
To: exim-users
Subject: Re: [exim] Opposing RFCs ? - Case In/Sensitive AUTH SASL Methode
> So in configuring Exim, use upper-case, but Exim should match anyway.

First I think the same. But it seems that the passus entends the
argument itself
> Exim doesn't offer AUTH MSN, unless that's coming from a cyrus_sasl
> driver?
>
> So I think that the server the client is talking to is not Exim;
> perhaps
> some proxy?



100% pure Exim !


######################################################################
#                   AUTHENTICATION CONFIGURATION                     #
######################################################################


# There are no authenticator specifications in this default
configuration file.

begin authenticators

plain_login:
   driver          = plaintext
   public_name     = PLAIN
   server_condition =  ${if crypteq {$3}{\{crypt\}${lookup pgsql  
{AUTH_PLAIN}}}{yes}{no}}
   server_set_id   = $2


fixed_login:
   driver          = plaintext
   public_name     = LOGIN
   server_prompts  = Username:: : Password::
   server_condition = ${if crypteq {$2}{\{crypt\}${lookup pgsql  
{AUTH_FIXED}}}{yes}{no}}
   server_set_id   = $1
   client_send     = CLIENTAUTHLOGIN


fixed_cram:
   driver          = cram_md5
   public_name     = CRAM-MD5
   server_secret   =  ${lookup pgsql {AUTH_CRAM}{$value}fail}
   server_set_id   = $1


microsoft:
  driver           = spa
  public_name      = MSN
  client_username  = ${lookup pgsql{AUTH_MSN_USER} {yes}{no}}
  client_password  = ${lookup pgsql{AUTH_MSN_CLEAR}{yes}{no}}
  client_domain    = ${lookup pgsql{AUTH_MSN_DOM}{yes}{no}}