I figured out what the problem was, as described in another post in this
group. By deleting the outside SMTP DNS servers, forcing the server to use
the standard TCP/IP stack, I had no further problems.
> I am having a similar problem to the one described below (I think). I set
> up E2K with all the default settings and yet can not send messages to a
> specific external server (using different email server software). I can
> one server. The status of the delivery reads as "the remote server did
> respond to the connection attempt". I have tried sending to this server
> using different, non-E2K accounts with no problem. Any ideas?
> > Hi, Joe
> > I have the same problem and very happy to hear you'v got a solution. But
> > situation is a bit different. First of all I am using the default SMTP
> > virtual server, secondly I did not configure SMTP connector, the reason
> > based on MS's online help statement: "Routing group configuration
> > necessary only when you need to connect two or more routing groups or
> > you install connectors to foreign messaging systems in your Exchange
> > installation." Do you mean it's abosulately necessary to have SMTP
> > configured and not use the default SMTP virtual server? Your further
> > explanations will be highly appreciated.
> > Thanks
> > Jerry
> > > Thanks to anyone who spent any personal CPU time on my question. The
> > > problem has apparently been identified and I will provide the solution
> > here
> > > in case anyone has this problem in the future:
> > > As a recap, there were many domains that we were unable to deliver
> > to.
> > > We would get Delay Notification messages after the default 12 hours,
> > > after 2 days receive a failure notice. Most domains we had no problem
> > with,
> > > just a few, and they were all on different networks, using different
> > > server software, etc.,.
> > > On our E2K server there was the Default SMTP Virtual Server as well as
> > > another virtual server created for our email purposes
> > > with IIS logic--we didn't want to mess around with the default
> > > In our smtp connector under Routing Groups we had both SMTP Virtual
> > Servers
> > > listed under Local Bridgeheads. By removing the manually created
> > > server and telling our smtp connector to only go out through the
> > > SMTP Virtual Server, and copying the messages from the VS2 folder to
> > VS1
> > > folder, the queued messages were sent out just dandy and we've so far
> > no
> > > further problems.
> > > Joe Grover
> > > ACD.net