Note that the current mail server (mail.inf) is crunchie (but it has been flakey and nutty and so you may see references to those). so any of the commands and paths below related to that machine. And the virtual mail relay (virtualrelay.inf) is beeknow.
IMPORTANT - The @inf address space overlaps the UUN username space, therefore care must be taken when a request is received for a mail alias/address/list such as 'buid@inf'.
Now that's out of the way, onto the fun stuff!
The alias files are in /opt/sendmail on the mailhost.
The aliases file (on which the newaliases command works) is built from several smaller files using the make aliases command from within the sendmail directory. All these files are under RCS control.
|aliases-head||header for main aliases file|
|aliases-local||miscellaneous aliases - postmaster etc.|
|aliases-inf||official informatics aliases - hod, hopu etc.|
|aliases-fullnames||for full names - NOT IN OPERATION.|
|aliases-sms||for exceptions to sms - ideally empty, but just in case.|
|aliases-mailman||mailman lists - no other lists allowed|
|aliases-legacyredirect||users opting out of inf addresses - again ideally this will be empty|
To add an alias:
If you have created a mailing list, the lines that you will have to paste will be similar to:
# ai1reps mailing list
## created: 07-Nov-2002 mailman
ai1reps: "|/var/mailman/mail/wrapper post ai1reps"
ai1reps-admin: "|/var/mailman/mail/wrapper mailowner ai1reps"
ai1reps-request: "|/var/mailman/mail/wrapper mailcmd ai1reps"
See the section below on creating a mailing list for more information.
Remember the -u option in the ci command. This will leave a copy of the file and not delete it.
First make sure you've read the important bit at the top of this page.
All mailing lists are now mailman lists. The list must be created or deleted using mailman commands (in /var/mailman/bin, or ~mailman/bin). Then the list must be added to (or removed from) the sendmail aliases file so that sendmail knows what to do with mail sent to the list.
To add a mailman list
/var/mailman/bin/newlist mailing_list_nameNote - do not qualify the list name.
/disk/mailraid/scripts/addantispam mailing_list_nameas the mailman user.
To remove a list:
cp -rip /opt/mailman/lists/foo-list /opt/mailman/deleted/lists cp -rip /opt/mailman/archives/private/foo-list.mbox /opt/mailman/deleted/private
mailmanissue the command:
/var/mailman/bin/rmlist -a foo-list
The -a option deletes the list archives, so don't use it if you want to keep the archives. Generally we would remove the archives as well unless requested. Though remember if the archives were only accessible to list members, then if you've removed the list from mailman, then people will not be able to authenticate to view them!
ITO Lists - student classes, and groups of lecturers and tutors and so on, are owned by email@example.com. And should have a standard set of settings, eg privacy settings, HTML pages to remove unsubscribe options (as the membership is driven from the database). There is a long standing action to agree and state these settings, but for now cloning and existing similar list seems sensible.
There is now a wrapper script /disk/mailraid/scripts/newstudentclasslist which you should use instead of the normal /var/mailman/bin/newlist script for ITO lists. This sets up the list settings as I believe they are intended. See the script for details, basically it clones the "students@inf" list, sets the listowner, password, pivacy settings and uses the spamwrapper. You still need to paste the entries into the sendmail aliases file.
We also need to clear out old list postings at the beginning of each new session. Again this needs to be stated and formalised somewhere!
Update Nov 2006: There is now a wiki page detailing the setup of ITO lists: https://wiki.inf.ed.ac.uk/DICE/ServicesUnitITOLists. The newstudentclass script will do the right thing for new student lists, but not for course/class related staff lists. eg inf1a-tutors. It nearly does, but the posting permissions are different. So you'll need to fix them.
There is a now a
/opt/mailman/inf_scripts/capability2list which is
run along with the other daily mailman scripts that can synchronise a
list's membership with the list of UUNs with the specified
capability. The script is the documentation!
To create a BAYES or SICSA email lists, you do that on virtual mail relay (beeknow) by editting /opt/mail/virtusertable (under RCS control). Note that there's is a script to make sicsa mailing lists. As mailman on crunchie run:
note the missing leading "bayes" or "sicsa" prefix . The scripts will actually create a list called bayes-directors (or sicsa-maa-leader) and configure the list to expect to be called firstname.lastname@example.org (or email@example.com)
You then need to paste the output as normal into aliases-mailman, but also add two variations of it into
beeknow:/opt/mail/virtusertable, to cover all the various possible names that might get used/leakout.
firstname.lastname@example.org email@example.com similarily for bayes.ed.ac.uk lists.
To create an INFORMATICS-VENTURES alias for a new member of commercialisation team, you do that on virtual mail relay (beeknow) by editing /opt/mail/virtusertable (under RCS control)
This is also where legacy aliases live, e.g. @dai, @cogsci, @dcs should they ever need modified.
Please contact us with any comments or corrections.
Unless explicitly stated otherwise, all material is copyright The University of Edinburgh