[comp.mail.uucp] Problems with site with same UUCP name

jiro@shaman.com (Jiro Nakamura) (05/16/91)

Hiya -
	I was wondering if anyone could offer me any advice. I'm sysadmin,  
postmaster, and everything else for our site, shaman, which is registered as  
shaman.com (SHAMAN-DOM) in the NIC maps and as <shaman> in the uucp maps.
	There happens to be another UUCP site <shaman>, however, which is  
unregistered. The person doesn't have a domain name because he's two hops down  
a UUCP line, ie. he's <foo!shaman!username@bar.com> or  
<bar!foo!shaman!username> for you UUCP folk. 
	He isn't real careful sometimes, and I just recently got a whole load  
of BITFTP junk from princeton.edu that the guy had requested, but some mailer  
had misdirected to our <shaman> site rather than his. 
	I've been trying to tell him that his mail is coming to our site by  
mistake (it bounces to postmaster-me). But he isn't being very responsive.  
Basically his attitude is "it's your problem." Well, it is my problem if he is  
sending large BITFTP's to my site by mistake and I'm paying UUNET the  
equivalent of $3 a megabyte.
	What can I do? Should I send mail to <root@foo> to tell him to convince  
the other shaman to change his UUCP name to something that doesn't conflict?  
That would make me a pretty bad net.citizen and world.citizen. But at the same  
time, I don't like getting mail that ain't intended for me. 
	Any advice would be helpful. Thanks!

  - Jiro Nakamura
    jiro@shaman.com
-- 
Jiro Nakamura				jiro@shaman.com
Shaman Consulting			(607) 253-0687 VOICE
"Bring your dead, dying shamans here!"	(607) 253-7809 FAX/Modem

jiro@shaman.com (Jiro Nakamura) (05/21/91)

A week or so ago, I posted a request to this newsgroup. I was having
problems with a site that (illegally) had the same UUCP name as I,
even though my site was registered. As a result, I was getting his
sites e-mail occasionally when smart-mailers would out-guess his
routing.

About ten or so people replied. Many, many thanks to you. I've named
you at the end of this article.

Here's the summary. Basically the course of action recommended by all
was about the same:

	1) Contact him and tell him to change his name.
           My site was registered correctly, thus it is his responsibility
	   to change it and fix things, not mine.
        2) Contact his feed site and tell them to convice him to change
           his name.
        

I will try to convice either or both of the sysadmins to fix things. I'm
sure he won't relish giving up his site name, but .......

Some other reponses were:

	1) Send him my UUNET bill.
	2) Since I have Shaman.com registered, then I should relinquish
	   my claim on the UUCP name shaman. I should change my UUCP name
 	   to something computer generated, <s34ma99h.uucp> for example,
	   send in a new map entry and NIC MX forwarding widget. Then
	   everything would be dandy.
	3) Another strong arm tactic: Get a friend on the net to send me
	   the sources to EMACS's "accidentally" to the other shaman.
	4) Contact the sites that are overriding the UUCP bang addresses
	   (i.e., someone's site is changing foo!shaman!user@bar.com to
 	   user!shaman.uucp, which is the source of all this mess).
	5) Let the UUCP map person know about the problem.
		Problems: 1) Who is the map person?
			  2) What good would that do? The problem
			     is that the maps work fine, mail addressed
			     to UUCP site <shaman> is getting there, to
			     my site.

What I think I will do is get hold of his feeder and him at the same time
and try to convince him to change his name. This seems the most rational
and least harmful solution. 

Again, many many thanks to all those who sent me suggestions. I deeply
appreciate this. I received e-mail from:
	

	Brendan Kehoe		Michael Richardson
	Paul Ebersman		Tim Endres
	Brian Kantor		Bill Fenner
	Paul Revell		Bob Weissman
	Dave Platt		John Harkin
	Chris Daves


	- Jiro Nakamura
	jiro@shaman.com
d
-- 
Jiro Nakamura				jiro@shaman.com
Shaman Consulting			(607) 253-0687 VOICE
"Bring your dead, dying shamans here!"	(607) 253-7809 FAX/Modem