Email and user accounts

Faculty	CS email assigned	CS account/s provided
Staff	CS email assigned	CS account/s provided
CS Grad Student	CS email assigned	CS account/s provided
CS Researcher	opt-in for CS email	CS account/s provided
CS undergrad major	opt-in for CS email	CS account/s provided
other undergrad not a researcher not a major	no CS email	CS account/s provided

Overview

Only the CS email service will accept email.
Non-email systems operated by CS will allow email to be sent, not relay email, be mx’ed to email.cs.rutgers.edu, and possibly have port 25 blocked at lcsr-gw.
Non-email systems include
- faculty, research, grad, ugrad, and ilab servers and clients

IMAP/POP will be our supported email interface
- IMAP/POP email clients will be supported
- A web interface will be available
Old email interfaces will be decommissioned
- mm will not be available
  - It is no longer supported and requires we run solaris
- mail and rmail in emacs will be available as unsupported software
  - rmail and mail work under current linux releases
  - We’ll provide a machine, a linux OS, and the email software.
  - Users will need to accept responsibility for maintaining the OS and software.

between 6/1/06 and 8/1/07 mail received by paul, research, remus, and aramis will be forwarded cs
- mail sent to user@{paul,research...} will generate an autorepsonse informing the sender of the new email address (i.e., user@cs)
- the incoming mail message will be delivered to user@cs.rutgers.edu
- forwading will only work from paul, research, remus, and aramis if you have a dragon account
- only paul, research, remus, and aramis will forward email
- forwarding will be terminated on 8/1/07
- implementation of forwarding will be managed by dragon
Except for this temporary forwarding email to a non-email machine will be rejected with a message that
- tells the user the machine does not accept email
- refers to a web page with instruction on how to contact the intended addressee.
We will inform users that mail to special addresses such as root, abuse, and postmaster should be sent to help@problems.cs.rutgers.edu
We will inform users that mail to generic addresses should be sent to either user@cs.rutgers.edu or user@rutgers.edu.

5/1/06 Notify users of plan
5/1/06 migration of users to dragon begins
6/1/06 move of rack containing email servers complete
6/1/06 14 months of email forwarding for paul, research, remus, and aramis initiated
6/15/06 migration of users to dragon complete
7/1/06 rmail and mail interfaces complete
7/1/06 connect SANS file system to email servers
7/15/06 mapping of local emails complete
7/15/06 OTRS routing of reports complete
8/1/06 mx and rejection instructions installed
8/1/06 old email services discontinued
8/1/07 email forwarding terminated

We need to make sure we have effective mappings for
- help@cs, help@research, help@grad.cs, help@remus, help@ilab.cs, operator@cs, printers@cs, terminals@cs, wireless@cs, keycards@cs, keys@cs, oracle-help@cs, oracle-help@remus, voslab@cs, web@cs
Should operators be the first line filter on all help request
- Send all help to help@cs.rutgers.edu

Handling email to users who do not have a CS email account
- option A: rejected the message
- option B: send the message to an email resolving machine that checks to see if the user has an account on some CS machine.
  - If the user has no account, mail is rejected
  - If the user has an account, mail is forwarded user@rutgers.edu

Spam is being marked as “closed successfully”
It should be deleted
- It is not a problem report
- We did not successfully resolve it
Should we set up an operator-delete queue that accept message to be deleted?