looping - exim not recognising mx is to local machine

Página superior
Eliminar este mensaje
Responder a este mensaje
Autor: John Henders
Fecha:  
A: exim-users
Asunto: looping - exim not recognising mx is to local machine

I'm trying to get exim running on a couple of BSDI machines and I'm
having a problem that I've never seen before. When the BSDI machine I'm
trying to get exim working on is a secondary MX for a host that is down,
exim doesn't appear to recognise that it is the machine refered to and
it loops until the message bounces.

In this case, the machine is marlowe.wimsey.com and that is what the
primary_hostname in configuration is set to. I try to send mail to
whiskey.wimsey.com, which has a primary MX of whiskey.poste.com and a
backup MX pointing at marlowe.wimsey.com. Marlowe recieves the message
and attempts to make a connection to whiskey.poste.com, which times out
as it's down. Then exim makes an smtp connection to itself on
marlowe.wimsey.com and delivers the mail to itself. I have not seen this
problem on linux, solaris or sco. The configuration file is identical to
the one I run on my linux machine except for the difference in the
primary_hostname, of course. I tried commenting out the primary_hostname
entry to let exim determine the hostname itself but it still doesn't
seem to recognise that it is an mx host and it continues to fail. Has
anyone seen this problem?

Here's the relevant part of the debug output.
Delivery address list:
  sl@???
opened DB file /var/spool/exim/db/retry: flags=0 fd = 6
locked
unique=sl@???
sl@???: queued for routing
After directing:
  Local addresses:
  Remote addresses:
  Failed addresses:
  Addresses to be routed:
    sl@???
  Deferred addresses:
routing sl@???, domain whiskey.wimsey.com
lookuphost router called for sl@???: dns lookup: route_domain = whiskey.wim
sey.com
DNS lookup of whiskey.wimsey.com (MX) succeeded
fully qualified name = whiskey.wimsey.com
host_find_bydns yield = 2 returned hosts:
  whiskey.poste.com 192.48.234.2 100 10092
  marlowe.wimsey.com 204.191.160.3 150 15067
lookuphost router succeeded
routed by lookuphost router:
  deliver to sl@???
  transport: remote_smtp
  host whiskey.poste.com [192.48.234.2] MX=100
  host marlowe.wimsey.com [204.191.160.3] MX=150
search_tidyup called

>>> Local deliveries >>>

search_tidyup called
>>> Remote deliveries >>>

remote_smtp transport entered
opened DB file /var/spool/exim/db/retry: flags=0 fd = 7
locked
whiskey.poste.com [192.48.234.2] status = unusable
opened DB file /var/spool/exim/db/retry: flags=0 fd = 7
locked
marlowe.wimsey.com [204.191.160.3] status = usable
delivering 0wAleZ-0002zH-00 to marlowe.wimsey.com [204.191.160.3] (sl@???)s
et_process_info: 11489 1.60 delivering 0wAleZ-0002zH-00 to marlowe.wimsey.com [204.191.160
.3] (sl@???)
Connecting to marlowe.wimsey.com [204.191.160.3] ... connected
SMTP response timeout = 300
SMTP<< 220 marlowe.wimsey.com Exim 1.60 #1 ready at Fri, 28 Mar 1997 16:05:51 -0800
SMTP>> HELO marlowe.wimsey.com


....


-- 
      Artificial Intelligence stands no chance against Natural Stupidity.
                GAT d- -p+(--) c++++ l++ u++ t- m--- W--- !v
                     b+++ e* s-/+ n-(?) h++ f+g+ w+++ y*