> As far as we know, you followed the instruction correctly. And as far
> as we know, when one does that, the software works. So, as far as we
> know, there's no problem. :-)
>
> Perhaps if you showed us what you actually did, we could tell you if
> it was right.
>
> What *exactly* did you do to enable AutoTURN?
Okay,
qmail alone - passes deliver and receive tests fine.
Add ucspi-tcp, run qmail-smtpd through tcpserver - still passes deliver and
receive tests.
Add serialmail, follow the instructions in AUTOTURN.
Section 3 - if I use sh -c..., I cannot connect to port 25 on the mail
server. Using csh -c, I can connect to port 25.
Send mail to [EMAIL PROTECTED], message goes into
/var/qmail/autoturn/customers.ip/new
Run maildirsmtp command to process test.domain queue e.g. maildirsmtp
1.2.3.4 autoturn-1.2.3.4- 1.2.3.4 AutoTURN, mail is processed and arrives at
ms.test.domain
Send mail from test.domain using qmail.server as relay, mail arrives at
destination, but delivery from qmail.server to ms.test.domain is not
triggered.
At this point the log shows -
Jul 21 16:03:05 post smtpd: 932572985.960112 tcpserver: status: 1/40
Jul 21 16:03:05 post smtpd: 932572985.962587 tcpserver: pid 299 from
1.2.3.4
Jul 21 16:03:05 post smtpd: 932572985.977107 tcpserver: ok 299
qmail.server:1.2.3.3:25 ms.test.domain:1.2.3.4::2162
Jul 21 16:03:06 post smtpd: 932572986.390938 tcpserver: end 299 status
65280
Jul 21 16:03:06 post smtpd: 932572986.391717 tcpserver: status: 0/40
(The above IP's and names are not the actual values on the system)
rc.local looks like -
/usr/local/bin/tcpserver -v -u 503 -g 502 0 smtp csh -c '
/var/qmail/bin/qmail-smtpd
cd /var/qmail/autoturn
exec /usr/local/bin/setlock -nx $TCPREMOTEIP/seriallock \
/usr/local/bin/maildirsmtp $TCPREMOTEIP autoturn-$TCPREMOTEIP-
$TCPREMOTEIP AutoTURN
' 2>&1 | /var/qmail/bin/splogger smtpd 3 &
csh -cf '/var/qmail/rc &'
I have tried /var/qmail/rc both before and after the tcpserver command with
no apparent difference.
Cheers,
Tom
