qpsmtpd-async authenticated relaying direction request
I'm currently running qpsmtpd-async. I host many domains and I'd like to protect them all against backscatter using something like this: http://psg.com/~brian/software/authbounce/configure-authbounce.txt to add a bounce key to each outgoing message of the form: X-bounce-key: $mx-$number;$sender;$timestamp;$key This requires all mail sent by every user to go through qpsmtpd + exim on my local machine. This appears to require I setup another instance of qpsmtpd which will allow people to connect to the port via SSL, then somehow authenticate their connection once, then each time they send email their outgoing email will enter qpsmtpd. If the message is to be delivered locally, then it is. If the message is external, it will be queued to exim for delivery immediately or next queue run. So my questions are: 1) Can this be done using qpsmtpd-async or is it best to use qpsmtpd-forkserver 2) I find many partial discussions about how to set this up, can someone point me to a step-by-step which covers start to finish how to get this working 3) Can someone point me to a specific discussion of debugging this setup, maybe using swaks Many thanks in advance. - David -- Love feeling your best ever, all day, every day? Click http://RadicalHealth.com for the easy way!
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?
