Back to Public Web

ECell: Info, Procedures and Archives

On these pages, you'll find information regarding

Current ECell Members

If you need temporary assistance or advice, contact:

Responsibilities and Resources

  1. Our current web/domain host information.
  2. Login information.
  3. Billing
  4. Getting onto the Server - FTP and "secure shell".
  5. ECell and Reclaiming Email
  6. YahooGroups List Ownership/Management.
  7. Web page administration.
  8. Concensus decisions.
  9. What else is expected of you as an ECell member.

1. Our Current Web/Domain Host Information

Our current web and domain host is This is a Unix-based server. Experience with command-line Unix is recommended, but not necessary. Draknet's configuration and support docs are great, see

2. Login Information

Here's the login info for the

name: ecell
pswd: owu3w3f

This login works for ssh/terminal, ftp, pine (email via ssh terminal session), webmail, and Draknet's configuration utility, Brain (on For billing login, see #3 below.

3. Billing

Draknet sends billing once a year to "", which is forwarded to our YahooGroup address (see "Email" below). One of us has to spring for the amount, or else have the Wheel cut a check. A check reimbursement pdf is in our YahooGroups files section, and in this directory. The login at for all billing issues is "1428", and the password is "3559" (no quotes, but you already knew that).

4. Getting Onto the Server - FTP and "Secure Shell"

If part of your responsibility is editing the web pages, you'll need to access the web server. There are two ways you can go about this: using FTP software, or using secure-shell client software.

A regular FTP client is fine for file transfers. For Mac OSX, try Fugu. For Mac OS 9, Fetch works well. For PC's, WS_FTP and CuteFTP are good. If you use a web editor such as BBEdit, GoLive, Dreamweaver, etc. there are often FTP clients built-in to that software. If you use a command-line, know that Draknet sets up many directories as symbolic links. Both "www" and "WWW" go to our htdocs root.

[Insert new ftp support pages link here]

If you're comfortable using the command-line and would rather do things that way, you'll need to use a secure-shell client (or command-line "ssh") if you want a terminal session. does not allow regular telnet access. Most ssh command-line sessions will look like the following:

{prompt}:ssh -l ecell

** Newbie Note: Some free/shareware secure-shell clients are "putty" for PC's, and FUGU for Macs. If you're interested in working with command-line Unix, see for more information.

5. ECell and Reclaiming Email:

The Ecell receives email in two different ways: thru our YahooGroups list, or thru "". Any email going to is automatically redirected to "" (if you're curious, see the .redirect file at our server root, or use the Brain through your web browser). The exception is for the RQ; they get the email directly, and we get a copy.

Altho all the email is -supposed- to be redirected to the recell@yahoogroups address, sometimes things will slip through the cracks. It's good to check the email at least once a week. You can do so using pine (via ssh/terminal), or webmail ( We also use the "" address as our YahooGroups owner, and so it gets alot of administrative messages that should be cleaned out regularly - for more on that, see "YahooGroups List Management". Remember to delete any administrative email that you have already taken care of.

6. YahooGroups List Ownership/Management:

All SF Reclaiming-sponsored discussion groups are moderated by ECell members, but are currently owned by a generic YahooGroups login ID - "reclaiming_sanfrancisco". Why do this? So that if an ECell member dies, converts to another religion, gets amnesia, what-have-you, the group will still have a single owner, and not be tied to any one person (and their personal ID/email). This will also provide a modicum of privacy... you won't be forced to reply to admin issues or users with your personal email address.

The YahooGroups ID "reclaiming_sanfrancisco" has the YahooGroups password "summerfun", and uses the email address "". You can manage admin issues either through the webmail (see info below), or login to YahooGroups with this ID, and manage through their web interface.

Due to a Yahoo parameter, list-owner/moderator email cannot be forwarded from one YahooGroups list to a differing YahooGroups list, so we won't receive admin email at our address. In order to cut down on using personal email, an option is for everyone to check the mailbox at least once a week.

- If you decide to check email by POP mail, be sure to set your retrieval to "leave messages on server". As each administrative email/issue is resolved, delete that particular email from the queue thru webmail ( This way, if others check, they'll know that the admin emails left in the queue will still need attention.

- You can also work solely from webmail, deleting admin email as each is addressed.

- You can also check email via PINE, by logging in thru a terminal/ssh session, and typing "pine" at the command prompt. Delete admin email as each is addressed.

** Newbie Note: for more information on how to moderate YahooGroups discussion lists, see,, and Scroll down to where it says "Moderator Questions".

7. Web Page Administration

We are in the process of streamlining our web content, and the structure of the web site will be changing soon. In the meantime, you'll want to follow these guidelines:

-> Avoid using FrontPage if possible. Altho the newer versions write cleaner code, the older versions were nasty, and left alot of stuff behind in our directories. Use something like GoLive, Dreamweaver, HomePage, etc. if you need a WYSIWYG editor; use a regular text editor if you're old-school and like to code it raw.

-> When receiving requests for web updates, be sure to let the list know if you're going to take it (so no one else steps over your work), and then reply to the requestor & cc the list once its done.

-> Even tho most of us are old pros at this, try to remember to use the latest version of the page, and NOT the one you've stored on your hard-drive. It's easy to forget and accidently overwrite someone else's recent work. A quick way to do this: direct your browser to the page that needs to be updated, and click on "View Source" in your menu bar (you may have to hunt for it in a sub-menu). Highlight all of the raw HTML code/text, copy it, then paste it into whatever HTML editor you're using. Then edit the code, and upload. Simple! (says she who has overwritten other's pages several times).

8. Concensus Decisions

[Taken originally from]

Posted consensus due dates are at the very earliest, the Friday following the post, but with at least seven days to discuss things. If an ECell member does not reply, they are considered "not at the meeting".

e.g., ECell: changing biblio page, CONSENSUS 10/04/01

The only exception to this rule is when we're consensing on NEW MEMBERS then we require 100% "attendance".

9. What Else is Expected of You

[Taken originally from]

Mail: We agree to read our mail at least once a week, by Friday, and to post consensus dates as appropriate.

Absence: We agree to notify the cell when we are going off-line so it doesn't gum up consensus, so other cell members know that our responsibilities will not be covered during our absence, and so the cell can decide if someone else needs to cover them temporarily. We also agree to give priority to clearing ECell messages when returning from absence.

Accountability: We agree the most important thing to be in agreement about is the timeliness of our updates. We realize that this is a volunteer group and that we all lead busy lives, however, it is imperative that our ECell responsibilities do not take a backseat to other activities that come up.

Okay, that said, we also believe there is no shame in asking for help, taking a break, or bowing out completely when we are unable, or unwilling, to continue with this cell. Otherwise, we have found the consequences, both personally and to the cell, can exact a heavy toll.

Reimbursement Form

Download the .pdf file.

Archived "Old" Web Site

Before revamping the site, a copy of the entire 17MB site was downloaded and compressed it into a 5MB zip file. If you ever need to comb through for any esoterica (or requests), you can download the zip file to your local hard drive and peruse from there.