LSTOWN-L Archives

LISTSERV List Owners' Forum

LSTOWN-L

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Topic: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
"M. Richmond/AFRICA-L/ASTROL-L/CELTIC-L/fnoz/MARINE-L/PACIFIC/UFO-L/21st-C-L" <[log in to unmask]>
Thu, 25 Aug 1994 11:37:07 EST
text/plain (40 lines)
I am also a multiple co-owner of lists, many of which originated at a
single South American (Brazilian) listserv and were later 'peered' to
campuses in the USA (for the most part).  Some time ago, the peer
process was somehow broken, and now the several parts are separated
and operating singly, while maintaining the original list descriptor
and earlier versions of the co-owner listings.  Initially, after setting
in motion the descriptor, and in combing the nets for a co-owner, I
was invited to set the  lists up at BRUFPB.BITNET in Brazil, but then
I was not given co-ownership.  It took (true) 4 years to break throgh
this error.  I now have co-ownershp, but not technical co-ownership.
 
Efforts to redress the peer process seem to be failing (largely due
to language barrier and the problem of distance, I suspect).  In one
instance, even the peer site was changed to another Listserver.  Anyway
the list which is so fragmented is AFRICA-L and efforts to straighten
this out with the current co-owners and to bring up to date the
ownership details, etc. fall into total silence and lack of reply
from one site, and an inability to correct the situation from another.
 
What cane be done, please?
 
Mel
--
>
> Dear friends and colleagues,
>
> I have a relatively large list with eight peers, six of them linked to
> PSUVM as "central" node. This has been working fine so far, but since
> a few weeks ago, my subscribers are getting rejection messages from
> PSUVM telling them their mail has been rejected since it appears to have
> been sent before. As it seems, all six peers linked to PSUVM send every
> single mail they have received from PSUVM back to PSUVM. I have checked
> all the lists and cannot find any fault at all - there is no loop, and each
> peer list is found in the list as "<list>@<node> Peer Distribution".
>
> Can anybody help me?
>
> Thomas Zielke
>

ATOM RSS1 RSS2