Xref: utzoo news.admin:15427 comp.mail.misc:5771 Path: utzoo!utgpu!watserv1!watmath!att!linac!pacific.mps.ohio-state.edu!zaphod.mps.ohio-state.edu!ncar!news.miami.edu!mthvax!wb8foz From: wb8foz@mthvax.cs.miami.edu (David Lesher) Newsgroups: news.admin,comp.mail.misc Subject: Bogus .UUCP addresses, was: Is UUNET going to upgrade? Message-ID: <1991Jun21.214642.8746@mthvax.cs.miami.edu> Date: 21 Jun 91 21:46:42 GMT References: <1991Jun13.140345.2680@shaman.com> <9106151249.48@rmkhome.UUCP> <1991Jun21.025904.3563@osh3.OSHA.GOV> Reply-To: wb8foz@mthvax.cs.miami.edu (David Lesher) Distribution: na Organization: NRK Clinic for habitual NetNews Abusers Lines: 34 others comment about .UUCP addresses. point 1) There are lots of declared, valid, .UUCP addresses. Comment: If your mailer is too stupid to handle MX's and .UUCP addresses, it should at least be smart enough to pass the job off to a site that can do the job. That does NOT mean uunet, unless you are the uunet customer. There does seem to be at least one Major Manufacturer whose main gateway can't. That says lots to me about xyz.com - none good. point 2) There are lots of people who post .UUCP addresses that are NOT declared in the maps. Comment: Update your map entry. If you can't afford to post a map entry, unplug your mail system. If at all possible, get an MX address. point 3) Far, far too many people post bogus, or semi-bogus addresses. Comment: There come in several flavors. A) Old rn that assumes your domain is .UUCP, and uses it instead of FQDN's. Upgrade it, grep the source for .UUCP and edit it, or replace rn with nn {blatant plug} as a newsreader. B) If you're part of a FQD, use it. For some reason, several major net-companies seem to post long, convoluted bang paths rather than a simple MX FQDN, even when the MX is properly declared. I'd *love* an explanation for this.. C) Don't count on hiding an address in your .sig. Fix your Reply-to header. Now can we go back to arguing about header lines ;-? -- A host is a host from coast to coast.....wb8foz@mthvax.cs.miami.edu & no one will talk to a host that's close............(305) 255-RTFM Unless the host (that isn't close)......................pob 570-335 is busy, hung or dead....................................33257-0335