Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!apple!tahoe!malc
From: malc@tahoe.unr.edu (Malcolm L. Carlock)
Newsgroups: comp.mail.sendmail
Subject: Re: 5.61 wierdness on our machines
Summary: fixed, works like a champ
Keywords: munged headers, host unknown
Message-ID: <2346@tahoe.unr.edu>
Date: 9 Jul 89 06:05:27 GMT
References: <2336@tahoe.unr.edu> <2736@cveg.uucp>
Reply-To: malc@tahoe.unr.edu.UUCP (Malcolm L. Carlock)
Organization: Univ. of Nev., Reno-Mathematics
Lines: 43

-In article <2336@tahoe.unr.edu>, I wrote:
->[munged headers always, a la Bject, Om, Nder, etc.;
-> and "host unknown" for all off-host destinations]

In article <2736@cveg.uucp> dws@cseg.uucp (David W. Summers) writes:
- [in capitalize(), in utils.c, change
-   *p++ = toupper(*s++);
- to
-   *p++ = toupper(*s);
-   s++;
-
-I think that the 'toupper' macro may be implemented differently on different
-machines.

Sure enough, it's implemented as a macro in the 4.3 version we're using here.
Your fix did the trick.

I received a couple of suggestions via email concerning the "host unknown"
problem.  One suggestion:

-1) In ruleset 0, when you resolve an address, be sure to use the
-   fully qualified official domain name for the machine name (the
-   "$@" value).
-OR
-2) In the sendmail module "deliver.c", at about line 377 and again at
-   line 437, is code changing "_res.options".  (The lines are marked
-   with "/* XXX */")  Delete those two lines and recompile.  The lines
-   to be deleted are:
-   (at about line 377:
-      _res.options &= ~(RES_DEFNAMES | RES_DNSRCH);           /* XXX */
-   (at about line 437:
-   _res.options |= RES_DEFNAMES | RES_DNSRCH;      /* XXX */

I implemented the second solution, for the time being.

sendmail is working correctly now on both of the target machines.  Thanks (!)
to all who sent or posted replies.


Malcolm L. Carlock

malc@unrvax.unr.edu
uunet!unrvax!malc