These are the responsibilities of UMS Listserv list owners and sponsors.
Detailed Information
UMS IT provides hardware and software enabling members of the UMS community to provide mailing lists. These lists are "owned" by the staff member who requested the list (additional people may participate in the operation/ ownership of the list, but the "owner" must remain involved in the list's day to day operation). In short: we provide the infrastructure, you run the list. So, what does owning a list entail? The list owner should …
- Make initial configuration choices for the list. Typically this is done when you request the list. New lists can be requested here at the following link. All list options are explained there. Request Listserv List Form
- Advertise the list and detail why it exists. US:IT will provide a brief "list of lists." We list every UMS list not marked "confidential" (confidential lists are hidden from public view). As the list owner, you will want to tell people about your list. You can do this by email, or on a web page. If you expect your list to have broad public appeal, you might advertise it on another (existing) list. Also tell people how to subscribe! You can point people to our https://listserv@lists.maine.edu, or we can provide you with custom links for your own list. We're also happy to proofread any instructions you draft for potential subscribers.
- Serve as the primary point-of-contact for subscribers. If your subscribers are having trouble subscribing, unsubscribing, posting, receiving, etc., they should contact you first. The traditional way of contacting the real, live person/people "behind" a list is to email using this address syntax: listname-request@lists.maine.edu. For example, for the MY-GREAT-LIST list, you can reach the list owners at my-great-list-request@lists.maine.edu. Make sure that you read any mail from subscribers and reply to them. If you need help diagnosing problems, please submit a help ticket (help@maine.edu) on the subscriber's behalf, and we will give you whatever help is necessary to resolve the problem. If a subscriber contacts US:IT directly, we will in most cases pass the request directly on to the -request address.
- Watch for, and correct, delivery errors.
- Daily Error Monitoring Report (DEMR) If Listserv cannot deliver mail to a subscriber, that subscriber winds up on the DEMR. Subscribers remain on the DEMR for a number of days or for a total number of bounced messages, whichever occurs sooner (these parameters vary from list to list). After that, if Listserv still cannot deliver mail to the subscriber, he or she is removed from the list. As list owner, you should eyeball the DEMR for obvious errors (such as a typo in an address, like htomail.com, yhoo.com, main.edu, etc.) and correct them if you can. Please feel free to contact US:IT for assistance in deciphering the DEMR
- Additional Error Reports The Additional Error Report lists posting errors that were not revealed to the original poster. If a non-member tries to post, or someone posts a duplicate posting, or an oversized attachment, their post will not be distributed to the list. But, they may not be notified (this is a way of controlling "backscatter" spam). As list owner, you should scan the nightly AER for legitimate errors. Most will be the result of spam attempts and will require no action on your part. However, some will indicate a "real" subscriber having difficulty; you may wish to contact these people directly.
- Individual Bounces If Listserv cannot "understand" the format of a particular error, it will pass it on to you for action. The action you take depends on the nature of the error, the volume of your list, and your individual level of patience. Address generating permanent errors should be corrected, set to NOMAIL, or removed from the list.
Environment