Using TNRF's list serves

TNRF has a list-serve capability for its members and the general public. List-serves are a convenient and safe way for large groups of people to communicate with each other on-line through their email - without having to know all the email addresses of everyone who they would like to communicate with. Just one email address is used - for example 'member|info@tnrf.org' List-serves are easy to use. 1. General TNRF list serve: When you sign up to the website and join TNRF, you will be automatically subscribed to the general TNRF list-serve 'member|info@tnrf.org', through which we communicate with all our members. 2. Individual 'working group' list serves: In addition, when you subscribe to a working group (i.e. join), you will be automatically subscribed to the corresponding working group's dedicated list-serve, through which working group members communicate with each other. Please click here for more information on managing your working group subscriptions. If you would like to start a list-serve discussion on a particular issue, please send an email to web@tnrf.org. We ask that anyone wishing to start a list-serve be a member of TNRF - which is free. Common List-serve Commands These are the most common commands that users will need for interacting with the list-serves: To query whether you are subscribed mailinglist-query@tnrf.org To get the latest 30 messages from the archive mailinglist-get@tnrf.org 'mailinglist' should be replaced with the name of the mailing list to which you would like to send a command. For example to: Query whether you are subscribed to the 'member|info' list-serve, send an empty email to: member|info-query@tnrf.org Get the latest 30 messages from the 'member|info' list-serve, send an empty email to: member|info-get@tnrf.org More Advanced List-serve Commands These are the most common commands that users will need for interacting with the list-serves: Note: 'mailinglist' should be replaced with the name of the mailing list to which you would like to send a command. mailinglist-get.123@tnrf.org Get message 123 from the archive. If you specify a number that is larger than the highest message number in the archive, you'll receive the latest message. mailinglist-get@tnrf.org Get the latest 30 messages from the archive. If the list has a digest, the messages returned are the messages received since the latest digest (the last message of the latest digest is returned so that there always will be at least one message). mailinglist-get.45_67@tnrf.org Get messages 45-67 from the archive. No more than 100 messages can be returned per request. If the first argument is larger than the highest message number in the archive, you'll instead receive the latest 30 or so messages from the archive. For a list with a digest, you'll get the messages that have arrived since the last digest as well as the last up to 30 messages of that digest. mailinglist-index@tnrf.org Send subject and author name for the last 100-200 messages. No more than 2000 entries are returned per request. mailinglist-index.300_399@tnrf.org Send subject and author of messages 300-399. mailinglist-thread.45@tnrf.org Receive an ordered set of all messages that have the same subject as message 45. ``Re:'', etc, do not make a difference, so the returned set is the usually entire thread. mailinglist-info@tnrf.org Send me some information about this list (the list owner decides how this command is supported). mailinglist-faq@tnrf.org Send me the list of frequently-asked questions (and answers) for this list (the list owner decides how this command is supported). mailinglist-digest-subscribe@tnrf.org You guessed it - subscribe to the digest list for mailinglist@example.org, provided there is one. Digest are usually sent about every other day, but this also depends on the message volume and settings adjusted by the list owner. mailinglist-digest-unsubscribe@tnrf.org Yes, it's that easy!