|
user information |
Subscriber requirementsEach address subscribed to a list must identify an individual. Other lists may not be subscribed! Participants of another list who wish to receive the email can be invited to subscribe individually. Sometimes subscriptions are requested for pipes to files, news systems, etc. If (and only if) these are designed to meet troubleshooting requirements, they might be allowed. See the section on pipes, below. Staying on the listAddresses stay listed until they are
Typical problems include:
The administrator tries to notify users of problems. These efforts often fail, because their email addresses are not reachable. Up to 20% of the list has been pruned without notice each year. The administrator will suspend delivery to a problem address and monitor it for a while before pruning. PipesPipes to files, news systems, etc., should not use unmonitored addresses. If the list administrator sends email to a subscribed address, a response from an individual is expected, even if the pipe breaks. (They usually do, eventually.) This can be achieved by subscribing the individual, then filtering that person's email and diverting the portion that comes from the list. Note: Subscribing the pipe and filtering email that does not appear to come from the list is not equivalent. As long as it works, no one can tell the difference; when it breaks, the administrator can't send notice. If a pipe breaks, and it becomes apparent that it has not meet troubleshooting requirements, the subscription may be deleted. The most reliable way to identify email from the reflector (if your software can use it) is the Sender header field, which has one of these formats:
Some email interfaces may limit the filters to less reliable techniques. With the default subscription options, list email has a subject line tag in brackets (either [802.1 - seq#] or [802-ARCH]) which will not appear on direct mail from the administrator. (Be sure to include at least the opening brackets in the filter pattern; you can expect mail from the administrator to refer to the list.) Ways to join a listPlease note: Subscribing takes multiple steps and involves processing delays. Repeating your request won't help, unless there's doubt it was properly sent. You can subscribe via ListServ Web pages. See the "Web interfaces" page for links to pages handling each of 802.1's lists. You can also subscribe by email. The quick form generates a email subscription request. All the scripted material on these pages uses script-driven methods to hide the list from spammers. To use the list-specific links, your browser must support JavaScript 1.2 and allow scripts to run. If this doesn't work for you, or for any other reason, you may contact the list administrator for help. Subscribing (quick request form)Please note: Subscribing takes multiple steps and involves processing delays. Repeating your request won't help, unless there's doubt it was properly sent. The address you subscribe must meet the requirements and must be working before you begin. A confirmation request, requiring a response, will be sent to that address. Step 1: Fill in your email address in this form, then click the button. Note: You can use this form only with a browser that supports and allows JavaScript 1.2. (Default configurations of Internet Explorer or Netscape Version 4 or later are adequate.) You may skip the form and contact the list administrator with your request, including the address you want to subscribe. After an extra wait, for the administrator to check email and issue the command, you will be able to continue this procedure with Step 2 below. Step 2: You should receive a confirmation request by email, with instructions for responding either by email, or by using a Web link. (The link is easier.) You must respond to continue the procedure. Note: You're told to wait 72 hours for the confirmation request. That's too long; if you haven't received it after 24 hours, contact the list administrator and ask for assistance; your filters probably blocked it. Step 3: After your confirmation response, wait patiently! You should receive a "Welcome" notice from the server. The notice contains useful information; you may want to save it. |
