[comp.mail.sendmail] Sun 4.1 sendmail.mx doesn't

josh@saba.cayman.com (Josh Littlefield) (11/04/90)

Has anyone else noticed that Sun 4.1's sendmail.mx doesn't actually
deal with MX records?  All it seems to do is use the resolver instead
of YP, but it only seems to deal with A records, not MX.  We've
retrofitted an older sendmail.mx (4.0.3?) to get around this.  We also
noticed this in the "patched" version of sendmail.mx I grabbed from
somewhere last year to fix a domain macro bug.

Am I just missing something in the setup?  This seems like the kind of
bug people would tend to notice.

-josh

--
------------------------------------------------------------------------------
Josh Littlefield					Cayman Systems, Inc.
							University Park at MIT
josh@cayman.com 					26 Landsdowne Street
(617) 494-1999  					Cambridge, MA  02139
------------------------------------------------------------------------------

sblair@synoptics.com (Steven Blair) (11/04/90)

Sun's 4.1 sendmail.mx can only deal with 1 or 2 deep MX(at best),
and 4.0.3 has the same problem. If you wish to get a hold of
the Berkeley version, with a few enhancements, you can anon ftp it
from us, at 134.177.32.116 in ~ftp's directory.

There's no warranties, but we use it on our gateways, as trying
to deal with other companies' DNS, and mail "designs" get a bit 
bothersome all the time.


--
Steven C. Blair		Network Operations Center
SynOptics Communications Inc. Mountain View, California
INTERNET: sblair@synoptics.com  sblair@excalibur.synoptics.com
PROBLEMS/EMAIL: HOSTMASTER@SYNOPTICS.COM postmaster@synoptics.com
****Bring Back the USENET/ARPA/INET Moderated Backbone, now!!****

marka@dmssyd.syd.dms.CSIRO.AU (Mark Andrews) (11/06/90)

In article <JOSH.90Nov3130909@saba.cayman.com> josh@saba.cayman.com (Josh Littlefield) writes:
|Has anyone else noticed that Sun 4.1's sendmail.mx doesn't actually
|deal with MX records?  All it seems to do is use the resolver instead
|of YP, but it only seems to deal with A records, not MX.  We've
|retrofitted an older sendmail.mx (4.0.3?) to get around this.  We also
|noticed this in the "patched" version of sendmail.mx I grabbed from
|somewhere last year to fix a domain macro bug.
|
|Am I just missing something in the setup?  This seems like the kind of
|bug people would tend to notice.
|
|-josh


	Sun compiled the 4.1 sendmail.mx with NOMXWILDCARD defined. This
	is most probably what you are being caught by. to get around
	this add a period after the fully qualified hostname in rulset
	zero.

	i.e.

	R$*<@$+>$*              $#tcp $@ $2. $: $1@$2$3

	The other solution is to get rid of the wildcard mx record for
	*.cayman.com.

	Sun do have an alternative version of sendmail.mx that you can
	get with this turned off, but they don't garentee to continue
	suppling such a version.

	Mark.