Re: Feature request to disable CONTROL_PORT
On Wed, 27 May 2009, David Favor wrote: Having qpsmtpd listen on an additional control port creates serious complexity when running multiple copies of qpsmtpd, as each copy has to somehow figure out which control port to use, hope it's free and then connect. I usually just strip this code out of qpsmtpd or comment out the initial connection. A great feature to add is a simple command line option to turn this off. Yeah, this is only on -async anyway. I'm wondering if we should just dump the feature, since it doesn't work when having multiple async children. Matt.
Re: Feature request to disable CONTROL_PORT
On Wed, 27 May 2009, David Favor wrote: Having qpsmtpd listen on an additional control port creates serious complexity when running multiple copies of qpsmtpd, as each copy has to somehow figure out which control port to use, hope it's free and then connect. Please clarify what you mean: $ cd qpsmtpd/ $ grep -r CONTROL_PORT . $ grep -r -i CONTROL_PORT . $ I usually just strip this code out of qpsmtpd or comment out the initial connection. What code do you strip out? A great feature to add is a simple command line option to turn this off. It sounds as though you might be running qpsmtpd with multiple --listen-address options. If so, why are you trying to run multiple copies of qpsmtpd?
