On Wed, 20 Oct 1999 yann.golanski@??? wrote:
> Quoting Hugh Sasse (Wed, Oct 20, 1999 at 10:20:44AM +0100)
> > Nearly all of the entries that were in my reject log have "cannot route to
> > sender" in them. I have:
>
> Have you tried using exim -d 9 -bh <IP> and seeing what outpout you are
> getting? generaly this is VERY usefull for spotting those things.
>
Not sure how this will help here. macondo is our mail hub,
and I have lots of successful connections to it. Mail routed
to outside sites always goes out from my machine via macondo,
so mail to user@???, for example, will be routed via
macondo anyway, so exim -bh 146.227.1.4 will be fine. The logs
had, among others: (usernames ####'ed out unless I mssed some):
1999-10-19 14:00:18 11dYsA-0002zv-00 rejected from macondo.dmu.ac.uk
[146.227.1.4]: cannot route to sender <#####@lancaster.ac.uk>
Recipients: #######@brains.eng.dmu.ac.uk
P Received: from macondo.dmu.ac.uk ([146.227.1.4])
by brains.eng.dmu.ac.uk with esmtp (Exim 3.02 #6)
id 11dYsA-0002zv-00
for ######@brains.eng.dmu.ac.uk; Tue, 19 Oct 1999 14:00:14 +0100
P Received: from alliance.lancs.ac.uk nce.lancs.ac.uk [148.88.17.8])
by macondo.dmu.ac.uk (8.8.8/8.8.8) with SMTP id NAA24166
for <#######@dmu.ac.uk>; Tue, 19 Oct 1999 13:10:19 GMT
P Received: from mail.lancs.ac.uk ([148.88.16.100]
helo=mail-atm.lancs.ac.uk)
by alliance.lancs.ac.uk with esmtp (Exim 3.03 #1)
id 11dYrz-0002G1-00
for #######@dmu.ac.uk; Tue, 19 Oct 1999 14:00:03 +0100
P Received: from unixc.lancs.ac.uk (unixc.lancs.ac.uk [148.88.16.116]) by
mail-atm.lancs.ac.uk
with SpooMTA 1.31; Tue, 19 Oct 1999 14:00:03 +0000
P Received: (from ######@localhost)
by unixc.lancs.ac.uk (8.9.1b+Sun/8.9.1) id OAA26925
for #######@dmu.ac.uk; Tue, 19 Oct 1999 14:00:03 +0100 (BST)
* From: ######## <#####@lancaster.ac.uk>
F From: ######## <#####@lancaster.ac.uk>
I Message-Id: <199910191300.OAA26925@???>
Subject: Re: ############
* To: #######@dmu.ac.uk (### ####)
T To: #######@dmu.ac.uk (### ####)
Date: Tue, 19 Oct 1999 14:00:02 +0100 (BST)
In-Reply-To: <Pine.GSO.4.20.9910191311470.8722-100000@brains> from "###
####" at Oct 19, 1999 01:12:46 PM
X-Mailer: ELM [version 2.5 PL0]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding:
7bit
* X-rewrote-sender: #####@lancaster.ac.uk
---------------------------------------------
Indeed, from exim -d9 -bh 146.227.1.4 I get :
[...]
routing ######@lancaster.ac.uk, domain lancaster.ac.uk
anything router called for ######@lancaster.ac.uk
route_domain = lancaster.ac.uk
routelist_item = * macondo.dmu.ac.uk
after handling route_lists items, matched = 1
original hostlist=macondo.dmu.ac.uk options=
expanded hostlist="macondo.dmu.ac.uk" options=
anything router passed, rewriting lancaster.ac.uk as macondo.dmu.ac.uk
lookuphost router called for ######@lancaster.ac.uk
dns lookup: route_domain = macondo.dmu.ac.uk
DNS lookup of macondo.dmu.ac.uk (MX) succeeded
fully qualified name = macondo.dmu.ac.uk
host_find_bydns yield = HOST_FOUND (2); returned hosts:
macondo.dmu.ac.uk 146.227.1.4 10 1026
queued for remote_smtp transport:
[...]
so it would succeed now, but I cannot tell why it didn't then. I can
only guess that there was a temporary dns failure so it could not
find macondo.dmu.ac.uk, but I have no evidence to support this, only
that dns seems wobbly at times. If it was something else, how can I
know, unless I set logging to be always really high which I don't
really want to do?
> --
> Yann Golanski Internet Systems Developer
> yann.golanski@??? The Planet Online
>
Thank you,
Hugh
hgs@???
