atom feed11 messages in net.sourceforge.lists.courier-users[courier-users] Courier-MTA on FreeBSD
FromSent OnAttachments
Odhiambo WashingtonJan 14, 2002 7:33 am 
Aly S.P DharshiJan 14, 2002 7:41 am 
Darren SpruellJan 14, 2002 7:51 am 
Odhiambo WashingtonJan 14, 2002 8:06 am 
Odhiambo WashingtonJan 14, 2002 8:09 am 
Sam VarshavchikJan 14, 2002 4:00 pm 
Sam VarshavchikJan 14, 2002 4:01 pm 
YaremaJan 14, 2002 4:06 pm 
Odhiambo WashingtonJan 15, 2002 1:00 am 
Edwin CulpJan 15, 2002 7:30 am 
YaremaJan 15, 2002 7:48 am 
Subject:[courier-users] Courier-MTA on FreeBSD
From:Yarema (yd@CoolRat.org)
Date:Jan 14, 2002 4:06:42 pm
List:net.sourceforge.lists.courier-users

--On Monday, January 14, 2002 19:04:06 +0300 Odhiambo Washington <wa@wananchi.com> wrote:

* Darren Spruell <Darr@sento.com> [20020114 18:55]: wrote:

My OpenBSD 2.9 port came with a sample startup script called startup.sh which worked wonderfully. See if you might have gotten one!

Nope. But mine should also work. Can I take a look at yours? Since you're a close neighbor (BSD) how do I debug authdaemond?

Hi,

I finally have a FreeBSD committer looking at the Courier-MTA port that I rolled a few months ago and submitted as:

http://www.FreeBSD.org/cgi/query-pr.cgi?pr=31473

You can grab a tarball of the 0.37.0 port from http://yds.dppl.com/courier/ and you'll have a working, menu driven build environment that will link authdaemond.ldap with your choice of OpenLDAP1 or OpenLDAP2. Which servers actually get started is controlled through Courier's regular config files. My port also deals with the missing OpenSSL c_rehash script by including a copy with the port since it's only needed at build time. Perhaps the OpenBSD port can employ a similar technique.

Jan. 22 is the FreeBSD 4.5-RELEASE ports tree freeze deadline. So chances are good that this Courier-MTA port will get onto the CDs this release cycle. I'm looking for feedback so I can fix anything that needs be fixed before the deadline.