Path: utzoo!mnetor!tmsoft!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!rpi!bu.edu!cs.bu.edu!ckd From: ckd@cs.bu.edu (Christopher Davis) Newsgroups: comp.mail.misc Subject: Re: PLEASE NOTE: CS is an official top level domain now!!! Message-ID: Date: 21 Dec 90 03:04:06 GMT References: <2058@mcsun.eu.net> <1990Dec19.145937.3094@cs.widener.edu> <1990Dec20.212439.4507@cunixf.cc.columbia.edu> <1990Dec20.232606.1302@mp.cs.niu.edu> Sender: news@bu.edu.bu.edu Organization: 1000000011000101, Inc. Lines: 23 In-reply-to: rickert@mp.cs.niu.edu's message of 20 Dec 90 23:26:06 GMT Neil> rickert@mp.cs.niu.edu (Neil Rickert) writes: Neil> The only reliable approach is to qualify in the local domain only if the Neil> domain name is completely unqualified (no periods). Otherwise treat the Neil> name as already fully qualified. In other words, don't use RES_DNSRCH Neil> in domain lookups. Assuming that your mailer is broken in this manner, you can always "anchor" the root domain in such a way as to keep it from completing to the local domain. (For example, one of the local machines is named "bu.edu"; this sometimes tries to resolve to "bu.edu.bu.edu" instead. I just use "bu.edu." (note the extra period to anchor the root)--and all is well. So mail to user@foo.cs. if you really have to. --Chris -- [ Christopher Davis - - <..!bu.edu!cs.bu.edu!ckd> ] A message destined for delivery in *your* domain is fair game for anything you may want to do, up to and including translating the entire message, header and all, into Swahili. -- chip@tct.uucp (Chip Salzenberg)