CyberGraphX Mailing Lists

The following information is what I send out to new CyberGraphX users on the Mailing lists. It is a summary only. Below that is what the lists return when you send them a 'HELP'. TO GET OFF THE LIST you must send the email from the address you subscribed from!


General Mailing List Information

Mailing Lists
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 CGX General Discussion  (qlist+qmail) 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 Setup for discussion of CyberGraphX 

 - To join -
 Email To : cgraphx-request@meanmachine.ch
 Subject  : SUBSCRIBE

 - To unsubscribe (End of subscription) -
 Email To : cgraphx-request@meanmachine.ch
 Subject  : UNSUBSCRIBE  

 - Help -
 Email To : ?????
 InMsgBODY: ?????  

 - Post Msg To List -
 Email To : cgraphx@meanmachine.ch 


 CGX Binary (majordomo) - DEAD
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 Setup for mailing out the CyberGraphX updates and a for
 CyberGraphX PD authors to post there updates and notices
 to people who can get ~1MB uuencoded files in the mail....
 This is an open list 

 THIS LIST IS DEAD. DO NOT USE IT! 


 CGX BUG/BETA Discussion  (best serv) 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 Setup for discussion of CyberGraphX BETAS & BUGS 
 The CGX Betas are not 'public' but the mailing list is
 for bug talk. This list is NOT run on majordomo.

 - To join -
  Email:     cybergfxb-request@lists.best.com
  InMsgBODY: subsingle {email address}

 - To unsubscribe (End of subscription) -
  Email:     cybergfxb-request@lists.best.com
  InMsgBODY: unsubscribe {email address}

 - Post Msg To List -
  Email To : cybergfxb@lists.best.com 




Discussion Mailing List

Run by: David Gerber [dgerber@deckpoint.ch]
NOTE: You MUST unsubscribe from/with the email address you used to subscribe to the list. If you do not, then it might not work.

"Please change all your mailer's configuration and filters accordingly.
If you have any problems/questions, feel free to mail me. The server is
running on an Amiga 4000 under qmail and qlist."
"Many thanks to Philippe Brand for having hosted this list up to now. He will place a forward from cgraphx@colombo.telis-sc.fr to cgraphx@meanmachine.ch to avoid troubles."

***** Text inserted by cgraphx-request@meanmachine.ch * * Hi! This is the qlist program. I'm handling subscriptions for the * cgraphx@meanmachine.ch mailing list. * * My human owner is zapek. * * To the recipient: This message was sent to me on your behalf. (Your * address was listed in the Reply-To or From field.) For security, * I'm forwarding this message to you, along with my notes. * * Anyway, to subscribe, send me an empty message. To unsubscribe, send me * a message with the word UNSUBSCRIBE at the beginning of a line. Remember, * my address is cgraphx-request@meanmachine.ch. * * Now I'll look for requests inside this message... * *****


Discussion Mailing List - CLOSED

Was Run by: Philippe Brand - phb@colombo.telis-sc.fr
NOTE:

"Due to the fact that Philippe Brand can't host the CyberGraphX mailing list
anymore on colombo.telis-sc.fr, it will now be hosted on meanmachine.ch"

Binary Mailing List @ NETCOM - DEAD

I closed my Netcom account. the CGX Binary list is DEAD! DO NOT USE IT!


CGX BETAS & BUGS Mailing List

Run by: Frank & Robert - cgxbugml@vgr.com

The CGX Betas are not 'public' but the mailing list is for bug talk. This list is NOT run on majordomo.

NOTE: You MUST unsubscribe from/with the email address you used to subscribe to the list. If you do not, then it might not work.

From User BestServe Page:

BestServ Documentation - Help file for users

(I) Synopsis of BestServ list aliases
    
 listname - post to the list
 listname-response - authentication responses sent here
 listname-request - send subscribe/unsubscribe/etc...	
 listname-command - send moderator command requests
 listname-errors - (error return for bounces, invisible)
 listname-owner - send mail to the moderator of the list
     
 bestserv-owner - moderator of the whole mailing list manager
 bestserv-errors - (error return for bounces, invisible)
    
(II) Getting This Help File
    
    Email a message to the request address of the list.  For example, if 
    the list is called 'test', you would email a message to
    'test-request@hostname.domain'.  On this server, it would be
    'test-request@lists.best.com'. 
    
    The body of the message should contain a single line, left justified,
    containing the keyword 'help' in lower case.
    
    The list server will generally respond with this help file.
    
(III) Authentication
    
    Many of the requests you make to the list server require authentication.
    The list server authenticates a request by emailing a message back to you
    with a special Subject: line. The message contains complete instructions.
    You normally Reply to the message (such that the original Subject
    is still in the Subject: header, possibly with an Re: in front of
    it).  You must edit the REJECT clause in the Subject: line to
    say ACCEPT if you want to go ahead and run your original command.
    
    You must be sure to leave the ID clause intact or the list manager will
    not be able to authenticate your request.
    
    The purpose of authentication is to ensure that a valid return email
    address exists and to disuade spammers from crashing the list.  The
    moderator has the ability to turn on authentication AND moderation for
    any request, so you may not get an immediate response.
    
(IV) Subscribing
    
    To subscribe to a list you normally send email to the -request address
    of the list, as in 'test-request@hostname.domain'.  The body of the
    message should contain the keyword 'subscribe' alone or, if you want
    to subscribe a third party address, the subscribe keyword may be followed
    by an email address.
    
 subscribe
    
 or
    
 subscribe email-address
    
    By default, you will be subscribed to the digest version of the list.
    To subscribe to the single-message-per-mail version, use the
    'subsingle' command instead of the 'subscribe' command.  The list manager
    may or may not have the list configured to force digest distribution,
    so you may not have a choice.
(V) Third Party Subscribes
    
    A Third Party Subscribe occurs when person A subscribes person B
    rather then just himself.  This is normally allowed.  The list manager
    will most likely have recipient verification turned on, which means
    that person B will be sent an email asking him or her to acknowledge
    the subscription before that person is actually added to the list.
    
    If you receive a third party verification request and you do not want to
    be on the list, simply ignore the mail.
(VI) Posting from multiple email addresses 
    
    By default, most lists only allow subscribed addresses to post to 
    the list.  You can add other addresses to the list with the 
    'alias' command.
    
 alias email-address
    
    This allows you to post to the list from another email-address
    without the list distribution being sent to that address.  You can add
    as many aliases as you like.

(VII) Unsubscribing
    
    To unsubscribe from a list, send the 'unsubscribe' command.  You can
    also unsubscribe third parties by adding an email address.
    
 unsubscribe
    
 or
    
 unsubscribe email-address
    
    Note that if you have several list aliases, you should unsubscribe
    from those aliases as well as the one you are receiving the list on.

(VIII) List Information
    
    You can request list-specific information with the 'info' command.