Sorry about the headers in that last message (if it made it through,
hopefully the list software will reject it because of a wrong From
address) - I have nothing to do with equifax.com.  To make a long story
short, I accidentally sent it from a Pine role I had setup to test a
procmail rule I had setup so that our SSL certificates would be delivered
to another user while I was away on vacation :)  The rule worked, the SSL
certificates got installed while I was away but sometimes I forget the
role is there in Pine and haphazardly answer yes to all the prompts
without reading them.  I've disabled that role.

---------- Forwarded message ----------
Date: Wed, 26 Sep 2001 10:24:42 -0400 (EDT)
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Possible altconfig bug in 2.1CVS (was)Re: Which versio to upgrade
    to?

On Wed, 26 Sep 2001, Ken Murchison wrote:

> I'm not going to make any recommendations, other than to say that I have
> been running the current CVS of IMAP 2.1 and SASL 1.5 for weeks/months
> on my production server without any problems (other than those caused by
> myself while coding).

I may have found a bug in 2.1, although I haven't been able to nail down 
that the problem isn't caused by some stale file I missed when upgrading 
my test machine.  The problem is this:  using the alternate config option 
(i.e <service> -C /path/to/config), I have been unable to get the master 
process to answer requests on anything more than one socket.  In other 
words, if I set up two imap services, one bound to 10.0.0.1 and one bound 
to 10.0.0.2, master will spawn an imapd process when I connect to 10.0.0.1 
but will not spawn a process when I connect to 10.0.0.2.  netstat shows 
that the master process is listening on both addresses but when I connect 
to the second address, I never get a login prompt.  Further, running a 
strace on the master process shows no activity whatsoever - its as if 
master is binding that socket and then totally ignoring it.

As I said, there could be some stale files floating around from 2.0.X, but
I'm fairly certain its not a config file issue since master is binding
multiple sockets and no error messages are logged.  If anyone is using the
altconfig option and is in a position to test 2.1 from CVS, could you see
if the above situation works for you?

System is running Red Hat Linux, based on their 7.1 release with some 
updates from Roswell(7.2 beta)/Rawhide.  Kernel is 2.4.7.

-- 
Kevin M. Myer
Systems Administrator
Lancaster-Lebanon Intermediate Unit 13
(717)-560-6140



Reply via email to