Re: [Exim] help - building 4.34 w/ SASL support

トップ ページ
このメッセージを削除
このメッセージに返信
著者: gbrotherton
日付:  
To: Matt Bernstein
CC: exim-users
題目: Re: [Exim] help - building 4.34 w/ SASL support
Thanks for the reply, Matt.

Before I did the 4.34 compile, I did apt-get install of the latest libc6-dev libraries, the open-ssl dev-libraries and Open SSL, the pam-dev libraries, then PAM, then the saslauth-dev package (I don't remember the name in the apt-get list). The Exim 4.34 compile went fine after that. So, all should be latest versions. I know I should remove those dev libraries and just stick with the run times.

I didn't check to see if saslauthd had started and I wasn't aware that a test option was available. I've never used saslauth in the past.

This is the first time I've started up a mail server. It's only being used at home, I don't do this for a living. (Possibly one day? I would like to add this to my resume.)

I have been going through the ACL options in chapters 37 and 38. But essentially, yes, I needed a "recipe" or at least good guidence to set up Exim and get familiar with it's features. I would rather use the encryption, such as MD5, rather than plain text.

I'll check up on that saslauthd at boot time and get back to you.

Thanks again for the reply.

-Gene

----- Original Message -----
From: Matt Bernstein <mb@???>
Date: Thursday, June 10, 2004 3:19 am
Subject: Re: [Exim] help - building 4.34 w/ SASL support

> On Jun 9 gbrotherton@??? wrote:
>
> >I just successfully compiled 4.34 on Debian 3.0 r1 Woody and
> chose to
> >uncomment the saslauthd option in the Local/Makefile. Do any of
> the
> >other authenticator options need to be enabled in conjunction
> with
> >saslauthd in order to get SMTP Auth working? And for the
> authenticators,
> Three obvious questions:
>
> 1. Is cyrus-sasl >= 2.1 ? (not the case by default in debian stable)
> 2. Is saslauthd running?
> 3. Does "testsaslauthd" work?
>
> >can one of the examples (plain text, cram_md5, etc.) be copied
> from the
> >4.3x spec and placed into the config file's Authentication
> Configuration
> >section directly?
>
> You mean you want a recipe?
>
> plain:
>         driver = plaintext
>         public_name = PLAIN
> # this is for pine
>         server_prompts = :
>         server_condition = ${if saslauthd{{$2}{$3}{exim}{}}{yes}{no}}
>         server_set_id = $2

>