On  Wed, 11  Nov 1992  17:46:47 GMT  TIMO HARMO  <[log in to unmask]>
said:
 
>I  have a  list that  is linked  to a  rather fuzzy  conferencing system
>("portacom") and I am having some problems with it.
 
Commiserations. I didn't know we actually *exported* that thing.
 
>Listserv  send  the  messages  it  has received  to  the  conference  in
>portacom, which sends the message back to the list.
 
That is the  problem. Portacom cannot act as a  LISTSERV peer, period. It
is foolish to even try. The solution is to get rid of portacom :-)
 
>The listserv-documents that I have do not say anything about "LOOPCHECK"
>-header.
 
That is the keyword you would use  to tell LISTSERV to accept the message
and start a nice mailing loop instead  of sending an error message to the
poster. I don't think you want to try ;-) A better solution is to get rid
of portacom.
 
>P.S To be able to put in effect  the good advice I hope to get from this
>list, I need one more advice: can I somehow add new owners or update the
>list header via mail?
 
Yes, 'GET listname (HEADER'.
 
>The conferencing system locked up  when it received it's welcome-message
>from listserv, apparently  (so says the sys adm) because  in the TO-line
>there vere several different variations of my e-mail address,
 
Solution: get  rid of portacom  :-) You should  ask your system  admin to
register the machine's  Internet node in the BITEARN  NODES file, though,
so that  LISTSERV can  recognize your Internet  address as  equivalent to
your BITNET address.
 
  Eric