University of Essex Homepage Computing Service - Go to Home Page
. . . .
CONTENTS A-Z   |   SEARCH   |   CHANGE YOUR PASSWORD  |  ANNOUNCEMENTS  |  STATUS MESSAGES
. . . .

Use of large student email lists
Guidance to staff sending messages

ugall, ug-colchester, ug-loughton, and ug-southend,
pgall, pg-colchester, pg-loughton, and pg-southend

Student membership of the appropriate versions of these lists is mandatory. They cannot opt out.

Limited to important University business only - should be related to academic studies, administrative procedures, health and safety, and security issues.

Must not be used for marketing or promoting events or optional activities/opportunities not related to study. (This is a requirement specified by the Information Commissioner’s Office).

These lists have a very restricted set of staff authorised to send to them.

Examples of messages expected to be sent to ug-all and/or pg-all, etc

ugall-info, ug-colchester-info, ug-loughton-info, and ug-southend-info
pgall-info, pg-colchester-info, pg-loughton-info, and pg-southend-info

per-departmental, school or centre opt-out lists (e.g. lawugall-info, lawpgt-info, and lawpgr-info) - see Departmental Opt-out lists for a complete list

Students may opt out of these lists. Care should be taken not to overuse these lists as this is very likely to increase student opt outs.

Should only be used for University (or Students’ Union) business. Can be used for information which is likely to be applicable to large numbers of students.

Should not be used to advertise - use smallads-student for this.

These lists have a limited set of staff authorised to send to them.

Examples of messages expected to be sent to ug-all-info and/or pg-all-info, etc

In all cases

Please note

Other lists and groups - including departmental lists, and other methods of communicating with students will be reviewed in due course. Comments would be welcome on how the University can maintain effective communication with students (http://www2.essex.ac.uk/forms/restricted/service-comments/default.asp?source) . February 2008

. . . .