Mailman at CS

Beginning May, 2014, mailing lists at the CS Department are run on Mailman. (Older CS mailing lists are Majordomo-based.) You can manage your Mailman list memberships from https://www.cs.jhu.edu/mailman for public lists.

For a private list, you'll have to know what the list's name is. The list's name is in the list's email address, so if you send email to and receive email from "listname@cs.jhu.edu", the list's name would be "listname". You can manage your subscription information for such a list at https://www.cs.jhu.edu/mailman/listinfo/listname.

If you need help with a particular list, you can email listname-owner@cs.jhu.edu or, as always, support@cs.jhu.edu. The GNU Mailman User Documentation may also be helpful.

The rest of this page is mostly concerned with information for list owners; people who run a CS-hosted mailing list.

Requesting a CS-Hosted Mailing List

If you need to run a mailing list, please fill out our mailing list request form.

Configuring Your New CS Mailing List

For purposes of illustration, all of the examples here will use a list named "listname".

You should have received an email with your list administration password and links to the webpages for managing your mailing list. In general, a list named "listname" can be managed from the webpages at https://www.cs.jhu.edu/mailman/admin/listname. You should go there now and make sure it's configured the way you will want it.

Things You Should Change

On the "General Options" page, which is the first page you'll see when you go to https://www.cs.jhu.edu/mailman/admin/listname, there are a few items you should definitely change:

  • owner - This is your email address and the email addresses of anyone else who will have complete control over the list (if you're sharing list administrative duties).
  • moderator - If you will have list moderators--people who can approve postings to the list, clear out spam, and other housekeeping tasks without being able to reconfigured the list's settings--put their email addresses here.
  • description - A short description of what your mailing list is for.
  • info - A longer description of what your mailing list is for.

Things You Might Want to Change

Also in the General Options section are these settings, which will probably be okay if you leave them as they are, but which you might want to change to personalize your mailing list:

  • subject_prefix - The text that the mailing list will add to the beginning of the Subject: line for any email sent to the list. We highly recommend that if you have a value here you put it in [square brackets].
  • welcome_msg - This works a bit like the info field described above, but contains a bit of information that will be sent to any new subscriber to your mailing list. If you want to send welcome messages, you'll also have to set send_welcome_msg to "Yes".

On the "Privacy Options > Subscription rules" page, you can control how public your mailing list will be. The most notable settings are:

  • advertised - If you set this to "Yes", your mailing list will appear on the list of CS-based lists at https://www.cs.jhu.edu/mailman.
  • subscribe_policy - The default setting, "Require approval", will require you (or a designated list admin or moderator) to approve each subscription request. This maximizes list privacy, but is more work than most lists require. Setting it to "Confirm" allows anyone to subscribe if they want to.

On the "Archiving Options" page, you can control whether Mailman keeps a history of all the emails sent to your list. (Note that nothing can prevent list subscribers from keeping their own archives if they so choose.) The default setting for archive_private, "private", will only allow list subscribers to see the archives. If you change that to "public", anyone on the Internet will be able to see them.

Special Settings for Announcement Lists

Many lists we host are announcement lists; many people subscribe to these lists, but only a few people have permission to send emails to the list. This is how you set up your mailing list to work similarly:

On the "Privacy options > Sender filters" page (which you get by clicking "Privacy options" in the top menu then clicking "Sender filters"), set the following options:

  • default_member_moderation - Set to "Yes".
  • member_moderation_notice - This is the message that people who are subscribed but not allowed to post will receive if they try to post anyway. We suggest something along the lines of, "This mailing list is only for announcements; you cannot send email to it."
  • accept_these_nonmembers - This is a list of email addresses of people who are allowed to post to the list without being subscribed to it. This would be used for someone who would send messages but who would not necessarily need to receive a copy of every email sent to the list.

To allow a list subscriber to send to the list, go to the "Membership Management > Membership List" page, find the entry for the person you want to allow (either by finding them in the table or by putting their email address into the search field and clicking "Search"), uncheck their box in the "mod" column, and click the "Submit Your Changes" button.

Spam Management

It is a fact of life that eventually someone will try to send spam to your mailing list. Unfortunately, it's also likely that you will eventually have someone who should be allow to post to the list try to send an email from an email address that the list doesn't recognize, which will also look like spam. Mailman has a lot of options to try to deal with these sorts of situations.

By default, if the mailing list gets an email from someone who isn't subscribed to the list then it will hold on to the email until a list admin or moderator comes along and decides what to do with the email. List admins and moderators will get daily emails with lists of held messages and links to the "pending moderator requests" page (https://www.cs.jhu.edu/mailman/admindb/listname). That page makes it pretty easy to deal with spam. You can easily skim through the list of held emails, click to approve any that should be let through, and then click one button to delete the rest.

On the "General Options" page, the admin_immed_notify setting can be changed to "Yes", which will send you an email every time a message is held for review. You can reply to that email with instructions for Mailman. This setting is good for people who like using email to manage their list, want fast turnaround for held messages, and don't mind the additional emails.

On the "Privacy options > Sender filters" page, the generic_nonmember_action setting controls what to do when the list receives an email from an non-subscribed address. The default setting, "Hold", is strongly recommended so that you can help out people who should be able to send to the list but were blocked for some reason. If, however, you're getting a lot of spam and can live with the future management difficulties, you can set it to "Discard". (The other two settings are really not recommended for most lists. "Accept" will end up sending a lot of spam to the mailing list, and "Reject" will bother the people that the spammers are pretending to be.)

About Passwords

By default, your list has one administrative password. Anyone who knows that password can log in and change anything about your list configuration. This means that the way you give someone access to your list is simply to tell them the password. If you need to remove administrative access for someone, you will have to go to the administrative interface at https://www.cs.jhu.edu/mailman/admin/listname, go to the "Passwords" page, change the administrator password, and then share that password with anyone else who still needs to have administrative access.

If you want, you can set a moderator password. Anyone with the moderator password will be able to manage the process of getting emails to or keeping them from the list: they can approve or discard held messages and they can block people from posting to the list. They cannot change much else about the configuration of the list.

When the administrative interface asks for a password, either the administrative password or the moderator password can be used. If the moderator password is used, only the moderator functions will be active.