|RemoteAccess Utils Echo Guidelines:                      rev. 12 Apr 17
 Posting Frequency: 1st of the month.
 -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

 These are "not" rules per se', but "ideals" which we
hope you will
 all agree with and shoot for, within this echo.

 -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

 1. When anouncing a file is available, give the pertinent data
    concerning the file:

    RA_262SW.ZIP ------------> FileName
    RA ----------------------> MagicName (if available)
    848,297 -----------------> Filesize
    56K V.90 ----------------> Max baudrate
    1:3634/12 ---------------> Address 1...
    2547:1000/12 ------------> Address 2... (and so on...)
    1-919-774-5930 ----------> System Telephone Number
    Via SDS -----------------> Yes/No (was it released into the SDS?)
    Sanford, NC, USA --------> City, State, Country (where you are)
    Anyone May FREQ 24/7 ----> Or do you allow unlisted nodes to freq?

 2. Before reporting what you believe to be a bug, check and double
    check everything, then make your report (often you will find it is
    operator error and not program error). Include enough information
    (pertinent to your problem) in your message, to enable people to
    understand your problem  and offer solutions. This may include
    configurations (software & hardware), initialization strings,
    possible TSR programs, etc.

 3. When quoting a message, only quote what is pertinent to your
    response, not the whole message (if possible).

 4. Tearlines should be left as the mail proccessor makes/inserts them
    (35 characters max. none if PID is in message).

 5. When discussing your "views" on any program, be descriptive, explain
    what features you like or dislike (and why?), what works or doesn't
    and limit them to programs which work with (in one way or another)
    RemoteAccess, etc. Getting involved with "Mine is better than yours"
    type of conversations, is not productive and has no place here, or
    in any other conference. Try to maintain an objective view so that
    your post does not come across as software or author bashing.

 6. When posting an ad for a new product, make it "descriptive", but try
    to be reasonable.

 Thank  You

|Andrew Leary, 1:320/219, ajleary19{at}gmail.com
 Mark Lewis, 1:3634/12

 Conference Moderators