I concur with Suresh there. I've had the same happen to me and it was down
to the MS stuff being incorrectly configured.
Scenario: Mail addressed to A.Non.Emous@??? is sent to the MX host
for some.dom.ain (say mta.some.dom.ain running exim) which routes it to
anonuser@??? Unfortunately, the Exchange s/w has been set
up only to handle mail addressed to anonuser@???. When it sees the
address anonuser@??? it looks up the MX record (which just
happens to point to mta.some.dom.ain) and sends it off. The message ends up
bouncing back and forth til the max no. of hops is reached.
Solution:
a) Get exchange fixed to accept mail addressed to
anonuser@???
Hope that helps
Paul Walsh
Senior Systems Administrator, Information Services,
University of Central England, BIRMINGHAM B42 2SU, UK
Tel: +44 (0)121 331 5708 Fax: +44 (0)121 356 2875
-----Original Message-----
From: Suresh Ramasubramanian [
mailto:mallet@efn.org]
Sent: 08 August 2001 15:53
To: Stuart Grimshaw
Cc: exim-users@???
Subject: Re: [Exim] Too many hops.
* [Stuart Grimshaw on 08/08/01 13:30 +0100]
> The error as it is returned to me is below:
> Unable to deliver the message due to a communications failure
> The MTS-ID of the original message is: c=US;a=
> ;p=GLOBALEGACY;l=SERVER0108080803Q354XHC6
> MSEXCH:IMS:GLOBALEGACY:SERVER:SERVER 0 (00120341) Too Many Hops
> As you can see, no hop count :-(
Screwup at the other end - M$ Sexchange, looks like.
--
Suresh Ramasubramanian <----> mallet <at> efn dot org
EMail Sturmbannfuhrer, Lower Middle Class Unix Sysadmin
--
## List details at
http://www.exim.org/mailman/listinfo/exim-users Exim
details at
http://www.exim.org/ ##
