7 messages in net.sourceforge.lists.courier-usersRe: [courier-users] Re: [courier-anno...
FromSent OnAttachments
Sam VarshavchikOct 13, 2002 4:47 pm 
Brian CandlerOct 14, 2002 3:56 am 
Brian CandlerOct 14, 2002 7:03 am 
David HumphreyOct 14, 2002 7:41 am 
Brian CandlerOct 14, 2002 8:00 am 
Brian CandlerOct 15, 2002 1:19 am 
David HumphreyOct 15, 2002 6:06 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: [courier-users] Re: [courier-announce] Courier 20021013.RC1Actions...
From:Brian Candler (B.Ca@pobox.com)
Date:Oct 15, 2002 1:19:40 am
List:net.sourceforge.lists.courier-users

On Mon, Oct 14, 2002 at 10:41:45AM -0400, David Humphrey wrote:

Hmmm... Better apply that patch to the imapd-ssl config. build as well. It has the same problem.

The patch I posted did include imapd.rc.in

I thought it was a substitution that arose with the install script that forgot to grab this ${bindir} and replace it with the configured bindir for the build.

I wonder which is the case?

Changing @BINDIR@ to ${bindir} was my suggestion from a little while ago. This follows the DRY (don't repeat yourself) principle.

In my case, I am allowing multiple versions of courier installed under /usr/local/software-1.00/courier-imap/... /usr/local/software-1.01/courier-imap/... etc and having a hard-coded path to COURIERTLS in the config files meant that config file changes were needed every time I switched versions; picking up the bindir environment variable which was already set in pop3d.rc/imapd.rc fixes that problem.

It might be better just to set COURIERTLS in {pop3,imap}d-ssl.rc, since I doubt anyone is going to change it, any more than they would change the path to couriertcpd (say).

Regards,

Brian.