tcp-env is refusing connections for sites that have 2 addresses.
Here is an example:
Mar 8 16:57:28 conductor tcp-env@conductor.synapse.net[24210]: warning:
host name/address mismatch: 194.72.245.189 != ns.zetnet.co.uk
Mar 8 16:57:28 conductor tcp-env@conductor.synapse.net[24210]: refused
connect from 194.72.245.189
Nameservice says:
> 194.72.245.189
Server: conductor.synapse.net
Address: 199.84.54.18
Name: ns.zetnet.co.uk
Address: 194.72.245.189
> ns.zetnet.co.uk
Server: conductor.synapse.net
Address: 199.84.54.18
Non-authoritative answer:
Name: ns.zetnet.co.uk
Addresses: 194.72.245.189, 194.247.47.47
Clearly, the forwards and reverse nameservice are in accordance here.
As an aside, I'm already running qmail-smtpd through tcpd; is there any
need for tcp-env at all?
Evan
Here is an example:
Mar 8 16:57:28 conductor tcp-env@conductor.synapse.net[24210]: warning:
host name/address mismatch: 194.72.245.189 != ns.zetnet.co.uk
Mar 8 16:57:28 conductor tcp-env@conductor.synapse.net[24210]: refused
connect from 194.72.245.189
Nameservice says:
> 194.72.245.189
Server: conductor.synapse.net
Address: 199.84.54.18
Name: ns.zetnet.co.uk
Address: 194.72.245.189
> ns.zetnet.co.uk
Server: conductor.synapse.net
Address: 199.84.54.18
Non-authoritative answer:
Name: ns.zetnet.co.uk
Addresses: 194.72.245.189, 194.247.47.47
Clearly, the forwards and reverse nameservice are in accordance here.
As an aside, I'm already running qmail-smtpd through tcpd; is there any
need for tcp-env at all?
Evan