>That did produce some answers. None valid as far as I can see, but answers.
>If DNS is at fault, well, how did IMail fail to connect to the IP of the
>target SMTP server?
I don't know.
I do know that in summer '97 when I had a colo machine and installed Imail
eval, the colo guy screwed up my tcp/ip settings and Imail got nothing but
mx connnect fail although the logs looked fine, just full of mx connect
fails, apparently having contacted the right destination ip, just like your
situ. And I could receive mail perfectly. Daniel or Eric or somebody at
Ipswitch stuck with me all the way, in the eval period, figured out the DNS
pb, I got the NT tcp/ip settings fixed and all was well. That's why I'm
leaning towards a DNS pb for you, or at least an NT tcp/ip setting
pb. Maybe point your NT and Imail at a totally different DNS?
>But, I will delete then reinstall the network in NT and see if that clears
>the problem.
I'd do just the tcp/ip protocol, not the whole network. As is SOP with
anything MS, reboot everytime you blink.
also, make sure nothing funny has snuck into you NT hosts file, since that
is queried by DNS lookups before DNS is.
Also, in Imail, I tell Imail to use the ip address rather than hostname of
the DNS server. Then I don't understand why my NT DNS settings in 97
affected Imail if Imail has its own DNS setting. Maybe Imail 3 did winsock
lookups vs tcp/ip lookups now?
Are you running SP6a?
>Funny thing is, the machine accepts incoming mail and delivers it so it
>would seem the NIC and network are ok.
Totally different Imail process, SMTPD vs SMTP, no "DNS client/resolver"
involved.
>I love weekend work<g>.
The best time to make progress. I hope to upgrade my Listar server to
latest version, and up Imail to 6.03+ and install Do Ron Ron's web msging
templates this weekend.
Len
Please visit http://www.ipswitch.com/support/mailing-lists.html
to be removed from this list.
