Every project has a default set of core mailing lists.
The despots of a project are the moderators of all lists and will receive administrative messages from time to time from the ezmlm list management system.
Messages sent to the announce@ address get automatically copied to the dev@ and user@ lists. Additionally, a blog entry is added to the Haus News blog.
The user@ list is intended for user-based discussions of the project.
The dev@ list is intended for developer-centric disucssions of project implementation, direction, and management. Using addcommitter to add a committer to a project will also cause the user's @codehaus.org address to be subscribed to the dev@ list.
The scm@ list receives source change notifications and Jira change notifications. Some of the membership of this list is automatically handled using the normal project management tools to control committer access. Using addcommitter to add a commiter to a project will also cause the user's @codehaus.org address to be subscribed to the scm@ list.
The despots@ list acts as a central point-of-contact for all despots of a project. All of the membership of this list is automatically handled using the normal project management tools to control despot priveledges. Using adddespot to add a despot to a project will also cause the user's @codehaus.org address to be subscribed to the despots@ list.
Information about a particular mailing list can be printed with
All administration is done via email. (This only applies for options configurable by subscribers, right?)
Allowed message size
To change the maximum allowed message size edit the
msgsize file in the list directory. If it exists it is assumed to contain
max is the maximum size in bytes of an acceptable message body, and
min the corresponding minimal size. Either will be ignored if zero or omitted. If the
ezmlm-reject command line specifies the list directory, messages not meeting the size criteria are rejected. Default is