There are three types of lists:

·         Particular

·         Institutional

·         Departmental

Particular lists

Particular lists are requested by one or more users who are defined as the list responsible and it is them who have control over it (who can send, if files are saved, who can subscribe…); they are, additionally, responsible of the list’s proper functioning as well as the choice of the thematic. When the list is thought to have done its job, it is them who will have to request for it to be removed from the server.

Any person who works at this University and has an email account managed by the Computing Service (server accounts post.uv.es; students’ accounts cannot request it, they cannot act as responsible of an email list, at least for now) can request the creation of a particular email list to deal with a topic of their interest as long as it does not already exist on a list with similar characteristics and the topic is related to research, teaching or cultural activities compatible with the University’s character.

Institutional lists

Institutional lists are created to carry out a function within the University. They have to be officially requested by the Server Department, etc. In this case, the institution names the list’s responsible and can, if necessary, change it or remove the list.

An example of institutional list could be a list that encompassed the lab personnel of a concrete department. It would be used to distribute information within a concrete collective without having to use the departmental list (which can include many more people).

Once the list has been created, particular and institutional, with the initial configuration asked by the requester, he/she will become its responsible and, as so, he will have to take care of its management tasks as well as to maintain the discussion in the list more or less within the topic for which it was created.

Departmental lists

A particular case of an institutional list is that of departmental lists, which are automatically generated in the SIUV and encompass all of the University’s personnel in that department, center, service… These are the only lists in which the Computing Service automatically subscripts addresses. In all other cases (all other institutional lists) subscription has to be done by the interested ones or the list’s responsible (if it is considered appropriate). The center’s responsible has to notify who is going to carry out the managing practice, but it was already created even though it did not have a named responsible.

The Computing Service maintain the lists’ functions and its related tasks (programme update, file security backups, etc.) but it does not take care of the individual lists’ management even though it can help a list’s responsible in particular cases to deal with a concrete problem.