home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: vmsnet.mail.mx
- Path: sparky!uunet!stanford.edu!agate!usenet.ins.cwru.edu!gatech!swrinde!elroy.jpl.nasa.gov!ames!tgv.com!MADISON
- From: madison@tgv.com (Matt Madison)
- Subject: Re: MX and Nameserver
- Message-ID: <1992Nov10.181328.11651@news.arc.nasa.gov>
- Sender: usenet@news.arc.nasa.gov
- Reply-To: madison@tgv.com
- Organization: The Foundation for Dinner Peas
- References: <009636A1.B2B2DF60.9917@PIB1.physik.uni-bonn.de>
- Date: Tue, 10 Nov 1992 18:13:28 GMT
- Lines: 17
-
- In article <009636A1.B2B2DF60.9917@PIB1.physik.uni-bonn.de>, Peter Kobe <system@PIB1.physik.uni-bonn.de> writes:
- >A question to the gurus:
- >How does MX in combination with CMU-TeK lookup Names/Adresses?
-
- For CMU-Tek V6.4, MX does its own DNS lookups for MX records. For later
- versions of CMU-Tek, it will use NAMRES for all DNS lookups, including MX
- record lookups. However, the SYSGEN parameter MAXBUF must be set to at least
- 2300 for this to work.
-
- If MAXBUF is set correctly, try turning on debugging in MX_SMTP and see if
- the resulting trace helps you determine what's going on. If there's any
- debugging stuff you can turn on in NAMRES, that might help as well.
-
- -Matt
- --
- Matthew Madison | madison@tgv.com | +1 408 427 4366
- TGV, Inc. | 603 Mission Street | Santa Cruz, CA 95060 USA
-