OK - from my last message it appears that even some of you who use
saslauthd don't realise that it can authenticate with IMAP. So - here's
how it works.
When a user makes an authentication call, saslauthd make a call to a
IMAP server passing on the name and password. The IMAP server will
either authenticate it or fail and that is passed back to the SMTP AUTH.
This way anyone who has an IMAP login can use that for SMTP login.
Here's how you config it.
First you run:
saslauthd -a rimap -O localhost
This tells saslauthd to use IMAP login authentication.
Then you add this to your exim.conf file:
######################################################################
# AUTHENTICATION CONFIGURATION #
######################################################################
begin authenticators
plain:
driver = plaintext
public_name = PLAIN
server_condition = ${if saslauthd{{$2}{$3}}{1}{0}}
server_set_id = $2
login_cram:
driver = cram_md5
public_name = CRAM-MD5
server_secret = ${if saslauthd{{$1}{$2}}{1}{0}}
server_set_id = $1
login:
driver = plaintext
public_name = LOGIN
server_prompts = "Username:: : Password::"
server_condition = ${if saslauthd{{$1}{$2}}{1}{0}}
server_set_id = $1
Finally - you need to compile Exim with saslauthd support. It's one of
the compile options you need to uncomment.
So far it works great. I feel like I died and went to heavan. And - I'm
running a very odd virtual email domain system.
