atom feed15 messages in net.sourceforge.lists.courier-users[courier-users] Re: Problems using au...
FromSent OnAttachments
ccOct 2, 2002 7:20 pm 
Sam VarshavchikOct 2, 2002 7:45 pm 
Zenon PanoussisOct 2, 2002 8:16 pm 
Barry HensleyOct 2, 2002 8:47 pm 
ccOct 3, 2002 4:13 am 
Sam VarshavchikOct 3, 2002 4:47 am 
Brian CandlerOct 3, 2002 5:59 am 
ccOct 3, 2002 7:15 am 
Brian CandlerOct 3, 2002 9:05 am 
ccOct 3, 2002 9:46 am 
Sam VarshavchikOct 3, 2002 2:48 pm 
ccOct 3, 2002 3:21 pm 
Bill SchindlerOct 3, 2002 3:35 pm 
Jonas Printzén (Hemma)Oct 4, 2002 1:37 am 
ccOct 4, 2002 3:47 pm 
Subject:[courier-users] Re: Problems using authenticated ESMTP
From:cc (cc@dsc.net)
Date:Oct 4, 2002 3:47:41 pm
List:net.sourceforge.lists.courier-users

Bill Schindler writes:

From the Install document at http://courier.sourceforge.net/install.html under the bold "OPTIONAL: Configure ESMTP authentication and SSL" heading...

"Courier supports authenticated ESMTP in order to grant ESMTP relaying privileges to remote users. The following steps set up authenticated ESMTP:

Which is followed by the instructions on enabling it.

Sorry Bill, I misunderstood. I thought Sam was talking about the configuration file generated by running 'configure'. *That* was what I couldn't find a reference to in the INSTALL file (i.e. what option to pass to ./configure to enable ESMTP). I was thrown by his comment because I mentioned earlier in the thread that I had set up the esmtpd configuration as instructed (and posted it) and also I understood that enabling authentication for incoming SMTP was not what I wanted as that would mean *all* connections needed authentication. For these reasons I didn't think he was talking about the esmtpd configuration file, which is indeed documented as you describe.

Anyway, as I said elsewhere, it works now, since I generated that certificate. I see someone else on the list found a solution by building via the RPM's, so perhaps there is a glitch in regular build process?

Thanks for your timely responses anyway.