ListProc MAILING-LIST archives
[Refer to Section VI of the ListProc Owners Manual]
This is the common type of ListProc archives used at Shamash. Messages are sent to a mailing list and are archived on the Shamash system. Archives may not be modified ; they are an accurate representation of what transpired on a mailing list and are very useful when looking up previous list discussions. Listowners have many choices about who can access their archives:
- World Wide Web Accessible Archives
List archives may be placed either on the world wide web or may be placed in another private location on Shamash which is not accessible by the web.
Web Accessible Archives are found at:
http://shamash.org/listarchives/LISTNAME (Replace LISTNAME with the name of your mailing list.)
- Gopher and Anonymous FTP Archives
Gopher archives are a remnant of the days when Gopher was popular, before the World Wide Web (WWW) became widely available (prior to 1994). Shamash offers minimal support for existing gopher archives and plans to phase these out in the near future, so please encourage your list members to use the WWW accessible archives. We have already phased out much of our Anonymous File Transfer Protocol (AFTP) archives.
- ListProc Retrievable Archives
List archives may be retrieved via e-mail using ListProc. As a list-owner you may determine who may retrieve your archives through e-mail via ListProc. To do this, send e-mail to firstname.lastname@example.org and have the message (not the subject) read:
config LISTNAME LISTPASSWORD archives-to-???
(Replace LISTNAME with the name of your list. Replace LISTPASSWORD with your listowners password. Replace ??? with one of the following: OWNERS, SUBSCRIBERS, or ALL. OWNERS lets just you as the owner request the archives, SUBSCRIBERS lets the owners and subscribers request the archives and ALL lets anyone in the world request the archives from ListProc.)
The commands for e-mail archive searching and archive requests are available on http://shamash.org/help/listuser-t.shtml
and also on the Listproc User FAQ, at
- ListProc ARCHIVE archives
[Refer to section VII of the ListProc Owners Manual]
At Shamash, this is an infrequently used option. The purpose here is to maintain text files for distribution. Usually, we find that making files accessable on the World Wide Web is a much better way to provide resources, although there certainly are several appropriate uses of ListProc ARCHIVE archives.
- These files may be archived at Shamash, and may be requested through e-mail via ListProc.
- Additionally, ListProc can employ Automatic File Distribution (afd) to send out the archive files, when they are updated, to the archive subscribers (which is a group of people, much like subscribers on a mailing list) .
- Alternately, ListProc can just e-mail the archive subscribers and let them know that the files have been updated, so they can request them if they would like.
- Lastly, at Shamash, all of the files in ListProc ARCHIVE archives may be accessible through the web, if an archive-owner chooses.
I keep getting error messages from different people's e-mail addresses, but I'm not sure what the different error types mean. What should I do?
- This problem exists frequently, as many users change email addresses, but
continue to deliver or forward mail to the old address for a period of time. It also
occurs for a few other reasons. Please see the web page
regarding Bounce messages we have describing solutions to this question.
What does it mean when I get a message that says a message has been rejected from my list because of "suspicious subject" or "suspicious address" or
because the "system sensed the following request which may have been inadvertently sent to list"?
- All three of these errors occur because ListProc has made the assumption that the original message was not intended to be distributed to every member of your list, so it routes the message only to you, the list owner. (or to the individual who receives the delivery-errors, if someone has been defined.)
- Listproc prevents messages from going to lists which contain certain keywords in the Subject: line. These include, but are not limited to: test, remove me, add me, confirmation, RCPT. By doing this, these types of messages are kept off your list, because they are "suspicious subjects".
- "Suspicious addresses" errors are generated when Listproc gets mail from an addressee which ListProc believes would not send mail to a mailing list, for example root, majordomo, admin, mailer_daemon and many others.
- A message like "system sensed the following request which may have been inadvertently sent to list" usually means that someone sent a message to your list, with the first word of the message being a ListProc command (like subscribe, join, delete or any of the others). This prevents your list from receiving these messages.
- Frequently these messages are generated when the message content is legitimate. Since listproc is not a person, it can only do so much to filter out messages like this; that is why ListProc sends the messages to you, the listowner, to make the final decision about these types of messages.
I have list members who cannot read mail that comes in digest mode. All they get is a blank message. What is wrong?
There have been some problems with certain mail clients reading
digests mailed through ListProc. The digests themselves are actually
reaching you, but are not being processed by your mailer.
Tell the user to send a message to email@example.com and have the message (not the subject) read:
set LISTNAME mail DIGEST-NOMIME
I am getting spam and other unwanted mail on my list. What can I do?
- Report all mailbombing, spamming and other breaches of Netquitte to firstname.lastname@example.org and our staff will look into the situation. Shamash has a zero tolerance policy against spamming and mailbombing.
- Check your list configurations; you may need to change some of your list's options to protect your list from unwanted mail:
(In all of these examples, replace LISTNAME with the name of your list. Replace LISTPASSWORD with your listowner's password. )
- Make sure only list subscribers can mail to your list by sending the following to email@example.com:
config LISTNAME LISTPASSWORD send-by-subscribers
- Make sure a confirmation message goes out to your subscribers before they join. The subscriber will have to confirm that they want to join the list, before actually being subscribed to it. To set this option, send the following to firstname.lastname@example.org:
config LISTNAME LISTPASSWORD confirm-all-subscriptions
- If you would like to take a more proactive stance, you may start manually approving all new subscribers to you list. To do this, send e-mail to
email@example.com and have the message read:
config LISTNAME LISTPASSWORD owner-subscriptions
You will then be notified when someone wants to join your list and you can then manually add them.
- If manually adding all new subscribers sounds like too much work to you, you can just be notified when every new subscriber joins your list, by sending the following message to firstname.lastname@example.org:
set LISTNAME preference ccsubscribe
- The final way to stop spam from entering a list it to make the list moderated, but that means you (or the moderator(s) you designate) will have to approve each message before it is sent to the list. To do this send the following message to
config LISTNAME LISTPASSWORD moderated-no-edit
To return the list to unmoderated mode send the following message to
config LISTNAME LISTPASSWORD unmoderated
I would like to add an info file to my list. How do I?
Every list, including private ones, need to have an info file. This file may be short.
To add an info file (assuming your list does not have one), email email@example.com
and have your message read:
put LISTNAME info
The LISTNAME list is a private list for the
This list is a part of Shamash: The Jewish Internet
Consortium. For more information about Shamash lists
send a message to firstname.lastname@example.org with one word
in it, LISTS. Shamash is also reachable via World Wide
Web at http://shamash.org
Replace LISTNAME with the name of your list, replace ABC with the name of your
organization. If the list is not private, just change the first sentance to
explain the list's purpose briefly. Your info file can say whatever you want it to, the
example above is a VERY simple example. More generally, have the first line read
put LISTNAME info, then the rest of the text can be whatever you would like it
to be. If
you include a signature in your message, that signature will become part of your info
file (this is not advised).
How can I understand all those error messages from ListProc?
Please see the help file Understanding ListProc's Bounce Messages
which addresses this and related questions.
How can I add an "alias" to my list?
The reference to this question is here in the manual
The manual states:
For a list named "mylist" whose owner password is "foo" the user
email@example.com has informed the list owner that occasionally she would
like to be able to send commands to ListProc from another machine but
doesn't want to have to subscribe from that machine also. The list
owner complied by setting up an alias for the second account.
That means you email firstname.lastname@example.org and have your message read:
alias mylist foo email@example.com firstname.lastname@example.org
alias LISTNAME LISTPASSWORD EMAIL-ALIAS REAL-EMAIL
Replace the following:
You may use fancy regular expression matching patterns as discussed further in the manual.
I hope this helps.
- LISTNAME - your list's name
- LISTPASSWORD - your list's password
- EMAIL-ALIAS - when mail comes in with this address, listproc will pretend that it came from REAL-EMAIL
- REAL-EMAIL - the email address which the person is subscribed to your list. You'd like mail coming
from EMAIL-ALIAS to appear as though it came from REAL-EMAIL
How do I add or remove a new moderator to my list?
To add a new moderator, email email@example.com and have your message
config LISTNAME LISTPASSWORD moderated-edit EMAIL@ADDRESS
Replace LISTNAME with the name of the list, LISTPASSWORD with the list's
password, and EMAIL@ADDRESS with the address you want to add as a
moderator. If you choose moderated-no-edit, you can replace
"moderated-edit" with "moderated-no-edit" in the above command.
To remove a moderator, email firstname.lastname@example.org and have your message
config LISTNAME LISTPASSWORD remove-moderator EMAIL@ADDRESS
Replace LISTNAME with the name fo the list, LISTPASSWORD with the list's
password, and EMAIL@ADDRESS with the address you want to remove as a
How to I add or remove an extra list owner? How do I change owners for my list?
To add a new owner email email@example.com and have your message read:
config LISTNAME LISTPASSWORD owners NEWEMAIL@ADDRESS.XXX
To remove an owner email firstname.lastname@example.org and have your message read:
config LISTNAME LISTPASSWORD remove-owners OLDEMAIL@ADDRESS.XXX
Replace LISTNAME with the name of the list
Replace LISTPASSWORD with the list owners password
Replace NEWEMAIL@ADDRESS.XXX or OLDEMAIL@ADDRESS.XXX with the
email address of the new owner and the owner you want to remove,
Be sure to communicate with the new list owner and pass along the listproc
password. We can also send them some into instructions if you let us know
who the new owner will be by mailing his/her address to email@example.com
How can I use Eudora to moderate my moderated-edit list?
In order to use Eudora for moderated-edit lists, you need to edit
the eudora.ini file to allow for forwarded messages to not
have the ">" prepended to each line. The eudora.ini file can be found in
the same directory as your Eudora application (both on macs and windows
operating systems). When editing the eudora.ini file, simply add the line
in the [Settings] section. As a result, nothing will be then be inserted
by Eudora when you FORWARD a message.
If you want the same to be true when replying to messages, you can edit the
ReplyPrefix. If you don't change the variable ReplyPrefix, then REPLY will
continue to add the ">" character at the beginning of each line, which will
be fine for ListProc.
I would like to shut down my list. Who do I ask?
e-mail to firstname.lastname@example.org and we'll take care of it for you.
If you have ideas for changes or improvements in this page please contact email@example.com
For questions not answered here, send e-mail to
This page has been viewed
times since August 1, 1997.
Web Author: firstname.lastname@example.org
Last modified: (none)
Go to the HTML version of the Listowners'
Go to the RTF version of the Listowners' Reference Card (which can be viewed on any word processor).
Go to the Shamash List
Go to the Shamash
Copyright © 1990-2014 Shamash: The Jewish Network. All rights reserved.