Re: [exim] Multiple authentications acting as a client

Top Page
Delete this message
Reply to this message
Author: Phil Pennock
Date:  
To: Reinaldo Matukuma
CC: exim-users
Subject: Re: [exim] Multiple authentications acting as a client
On 2011-08-18 at 16:13 -0300, Reinaldo Matukuma wrote:
> This returns me:
>
> 2011-08-18 16:05:23 Exim configuration error:
> two client authenticators (client_plain_1 and client_plain_2) have the same public name (PLAIN)
> 2011-08-18 16:05:23 Exim configuration error:
> two client authenticators (client_plain_1 and client_plain_2) have the same public name (PLAIN)
>
> But, if i change to use only one host with authentication (lefting the another routing and transporting yet, but without act as client auth) it's work.


The authenticators define "how do you implement authentication for this
mechanism". They don't have per-host restrictions.

What you can do is have an external file which contains data, like:

example.com: user=user1 pass=sekret1
example.nl: user=user2 pass=hidden2 otherdata=foo

Then on the Routers which route the mail, you include:

address_data = ${lookup{$domain}partial()lsearch*{/path/to/datafile}}

Then in your one client_plain authenticator, you would use:

client_send = ^${extract{user}{$address_data}{$value}fail}^${extract{pass}{$address_data}{$value}fail}

More simply, that's:
client_send = ^${extract{user}{$address_data}}^${extract{pass}{$address_data}}
but we force failure, in case the data is missing.

This way, you keep secret data out of your exim configuration, where
users can dump it (exim -bP), and make it easy to look up, to add to,
etc.

-Phil