Quoting Eben Yong <[log in to unmask]>:

> On Mon, 23 Jul 2007 11:41:02 -0400, Eben Yong <[log in to unmask]>
> wrote:

> I've worked with a number of folks, internally, denizens of HP3000-L, and
> Beechglen, and reached the hypothetical conclusion that the HP3000 is the
> only system that has ended up being impacted by the link aggregation on the
> exchange server, that our HP3000s are somehow confused by the exchange
> server's two MAC addresses and one IP address.  To resolve this, we will
> route emails originating from the HP3000 to an email relay server with only
> one NIC in play, which in turn will relay to the production exchange server.
> A workaround, to be sure, but in any event, I believe, problem solved.

That may be your problem in this instance, however my mail server is also a
firewall and has two NIC cards and two IP addresses. Initially I had problems
with the mail program taking a long time to get the mail server name resolved,
but changing the jobs to use the IP address (internal 172.16.x.x) solved the
problem with long name resolves. I never had any other problems related to the
mail server having two NIC's and two IP addresses.

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *