Print
Student Groups
Access your Student Organization Email
The email account is on the Law School's Lotus Notes Email system. You can access it via web browser or Thunderbird, or any other IMAP based client (just like you access your CUNIX email account).
Please be sure to change the password when you first login to the account:
Back to top
Network Account on CLS Computer Network
Recognized student groups and organizations are eligible for one organizational network account, and/or one email account, and/or one web account on the Law School's computer system. Account(s) can be obtained by contacting the Law IT Helpdesk in the back of the 2nd floor computer lab during Helpdesk office hours.
The network account is just like your own student account. Use it to logon to the lab computers when doing your student group/organization administrative work. It has 50MB of space on the H:Drive and 2500 pages of printing per year. The pages cannot be transferred to other accounts, but you can share the account name and password with people in your group.
Law School Username: <organization name>
Law School Password: <some temporary password>
Please be sure to change the password when you first login to the account:
Start -> Law School Applications -> Utilities -> Change Password or visit Lawnet to change your password online.
Back to top
Organization Website
The group/organization must assign a webmaster to the web account. The webmaster will be granted managerial status to a directory accessible by telneting to CUNIX (using his/her CUNIX id and CUNIX password) and typing the following at the prompt:
cd /www/data/cu/law/<organization name>
If you are using ftp software such as Fetch or WS_FTP, that is the path to your directory. The home page file should be named index.html, which has the resulting Web address http://www.columbia.edu/cu/law/<organization name>
Please note that the above directory is to be used only for live Web materials related to your group, and should not exceed 250MB in total size without prior approval of CUIT. Use the UNIX 'du' command to monitor usage.
If you haven't already, please be sure to read our documentation on our Help page:
http://www.columbia.edu/cu/help#WebAdmin
and our Web development guide: http://www.columbia.edu/acis/webdev/ particularly, Columbia Web Style Guidelines: http://www.columbia.edu/acis/webdev/style.html
To allow others in your group to add/delete/modify files, see How to Share Web Files, at:
http://www.columbia.edu/acis/webdev/unixgroups.html
Unfortunately, we have experienced data losses in the past; we advise Web managers to maintain a copy of their data on another machine in case our Web crashes and we lose files.
If your site does not already have a link in ColumbiaWeb, please contact Columbia University Information Technology (CUIT) at Philosophy Hall 102 or 854-1919 or consultant@columbia.edu and let them know when you're ready. Note that directories not linked are considered unofficial and are subject to removal after six months.
If you decide no longer to be Web manager for this site, please email webmaster@columbia.edu with the name of a new manager, his/her uni, and the name of your UNIX group (if any) and we will change the ownership of the directory and any groups to the new person.
Back to top
Mailing Lists
Majordomo is a mailing list manager, a program that automates some functions associated with a mailing list, like handling subscribe and unsubscribe requests, and of course re-mailing messages to the subscribers. Majordomo is free software written in the Perl scripting language. For more details on the software itself, see the Majordomo Archive Site. CUIT supports Majordomo mailing lists for purposes related to schools and departments, recognized student groups, and research interests of faculty. The list owner must be affiliated with Columbia.
The list owner is responsible for following up email from people needing help with the list and email from majordomo itself reporting problems, and for adherence to CUIT and university policies and regulations. To do this, the list owner must subscribe to the list and must check email regularly. Typical problems are people asking how to subscribe or unsubscribe, majordomo reporting an address not accepting mail, majordomo bouncing a message not meeting requirements (such as not from a subscriber, or too long), or flame wars between subscribers.
Optionally, a list can be restricted, so that subscribing requires list owner's approval, or so that articles sent to the list must pass through a moderator for approval.
Note: lists based on student registration, such as lists of students in a class or program, are protected under federal regulations (FERPA). To meet security guidelines, such lists must be handled with Listserv on CUIT host CUVMC. For information, send mail to infoline@columbia.edu. The lists can be generated from registration data. Another way to send mail to students in a class is to use CourseWorks.
Majordomo functions. The general public can:
send a help command for information
send subscribe and unsubscribe commands
send articles to be re-sent to the subscribers on the list
send commands to get archives and indexes of archives, if any
send commands to see who is on a list
List owners get a document describing how they can send commands on behalf of other people, and how they can change many configuration options. Normally, anyone can subscribe to a list and anyone can send mail to a list. Typical customizations include: Subscription approval. Subscribe messages can be sent to the list owner for review. Set by list owner with the config file. Change the variable subscribe_policy. Articles for the subscribers can be sent to the list owner for review, set by list owner with the config file. Change the variable moderate. Restricting posting. Sender can be checked, so articles from subscribers go to the list while others are sent to the list owner for review. Set by list owner with the config file. Change the variable restrict_post and probably also mungedomain. Archive. A copy of each article is kept in an archive, and can be retrieved by users. Archiving must be set up by postmaster on request from list owner. Digest. Digest subscribers get fewer messages: each one contains the text of several original messages sent to the regular list. Majordomo collects the messages and sends the digest. Other than this, the digest list is a separate list with its own subscriber list and its own list configuration file. Digest must be set up by postmaster on request from list owner.
Privacy Limitations
Majordomo is a medium-security mailing list manager. It is designed to prevent messages being sent by mistake, but does not absolutely block people determined to do the wrong thing.
The commands that provide information about subscribers default to relatively private settings, where only list owner or other subscribers can get the information. This can be configured more or less tightly in the list configuration. The default subscribe_policy is now open+confirm. Under this setting, anyone can send a subscribe command for any address, but Majordomo does not subscribe the address immediately. Instead Majordomo sends back a message with an authorization code to the apparent subscriber, who must then send in the authorization to confirm the subscription. This has been done to prevent malicious pranks in which someone subscribes a victim to a lot of irrelevant mailing lists. The only recommended alternative policy to this is closed, where list owner has to review subscription by hand.
Requesting a list
Send a request to postmaster@columbia.edu. The information needed is: Name of the list. Use letters, numbers, hyphen, and underline only; no spaces or other punctuation marks. The name should be long enough to be understandable, but short enough to be reasonable to type; usually 5 to 15 characters long is right. List owner. The list owner should check mail daily (or perhaps less often on a less busy list) for reports from Majordomo about subscriber address problems and for messages from users wanting help with subscribing, unsubscribing, or informationabout the list. The list owner should usually be fulltime officer or staff at Columbia and watch that the list does not violate university guidelines such as those against commercial use and those in the civility code. Purpose. This can be quite brief, just enough to indicate that the list supports a faculty research interest, or work of a university division, or a university club or organization. Archive or digest. An archive is a copy of all list mail kept on the server. A digest is an alternate version of the list mailing fewer messages, because each message mailed contains multiple messages sent to the list. Both archive and digest can be added later to an existing list, but it is convenient to set up either at the start if either is wanted.
Back to top
|
