Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!decwrl!bacchus.pa.dec.com!hollie.rdg.dec.com!jch From: jch@dyfed.rdg.dec.com (John Haxby) Newsgroups: comp.unix.ultrix Subject: Re: Ultrix 4.0 sendmail MX handling Message-ID: <1990Oct12.155744.12658@hollie.rdg.dec.com> Date: 12 Oct 90 15:57:44 GMT References: <1990Sep5.134625.16191@ni.umd.edu> <412@vtserf.cc.vt.edu> Sender: news@hollie.rdg.dec.com (USENET News System) Reply-To: jch@dyfed.rdg.dec.com (John Haxby) Organization: Digital Equipment Corporation Lines: 34 In article <412@vtserf.cc.vt.edu>, marchany@vtserf.cc.vt.edu (Randy Marchany) writes: |> In article <1990Sep5.134625.16191@ni.umd.edu> louie@sayshell.umd.edu (Louis A. Mamakos) writes: |> >Has anyone else noticed problems with MX forwarding in sendmail? Here's |> >the problem that I've had: |> > |> >In the DNS, there are some MX records for TRANTOR.UMD.EDU: |> > |> >TRANTOR.UMD.EDU IN MX 10 TRANTOR.UMD.EDU. |> > IN MX 20 CAMELOT.UMD.EDU. |> > |> >louie |> |> He goes on to state that whenever TRANTOR goes down, CAMELOT tries to |> deliver to TRANTOR and on failure, opens a 'connected to itself' which is |> the problem. Apparently, the list of MX forwarders is not trimmed to |> those with lower preferences than itself. This used to work on Ultrix |> 3.1. |> |> We've run into the same problem here at our site MX records work without any problems in V4, provided that you don't that an MX record for a host doesn't include itself :-( However, the good news is that the reason for this is that the $w macro is defined to be the unqualified name of the host (eg TRANTOR) instead of the FQDN (eg TRANTOR.UMD.EDU) -- the solution is to define $w to be the FQDN explicitly in the sendmail config file; this, of course, may throw up problems in the config file because it assumes that $w is unqualified. -- -- John Haxby Digital Reading, England <...!ukc!wessex!jch>