- Gordon Soukoreff <[EMAIL PROTECTED]>:
| Jan 1 01:36:31 blahblah smtpd: 915183391.413662 tcpserver: ok 19689
| blablah.blah.net:211.123.239.112:25
| onlymail2.oneandonly.com:211.123.239.112::1825
| Jan 1 01:36:31 blahblah smtpd: 915183391.421722 tcpcontrol: ok 19689
| blahblah.blah.net:211.123.239.112:25
| onlymail2.oneandonly.com:206.50.219.157::1825
Hey, this looks strange. First, it looks like you are running a
recent tcpserver (from ucspitcp 0.84?) which does its own filtering
based on IP address. Then it runs tcpcontrol, which is certainly
redundant. Tcpcontrol is not part of the newer ucspitcp versions, as
its functions are handled by tcpserver.
What is even more curious is that tcpserver believes the connection
came from 211.123.239.112 but still looked it up and got
onlymail2.oneandonly.com (which is wrong), while tcpcontrol believes
it came from 206.50.219.157 (which really *is*
onlymail2.oneandonly.com).
Please go and check your log entries again. Are you sure you copied
it right, or did you make a mistake while sanitizing it? (That
blblah.blah.net doesn't look right to me.)
Also, check your tcpserver startup line. Throw away the tcpcontrol
part, and use the -x flag to tcpserver to tell it about your
relaycontrol file.
Sorry I didn't notice all this strangeness in my former reply.
- Harald
