From 7a7b033fb746f60cfa3c6d1fd674ea827b760d02 Mon Sep 17 00:00:00 2001 From: <> Date: Tue, 7 Oct 2003 22:26:58 +0000 Subject: This commit was manufactured by cvs2svn to create branch 'Release_2_1-maint'. --- admin/www/mailman-member.pdf | Bin 0 -> 91496 bytes admin/www/mailman-member/about.html | 116 ++++++++++ admin/www/mailman-member/blank.gif | Bin 0 -> 1958 bytes admin/www/mailman-member/contents.gif | Bin 0 -> 438 bytes admin/www/mailman-member/contents.html | 165 ++++++++++++++ admin/www/mailman-member/front.html | 115 ++++++++++ admin/www/mailman-member/img1.gif | Bin 0 -> 134 bytes admin/www/mailman-member/img2.gif | Bin 0 -> 134 bytes admin/www/mailman-member/index.gif | Bin 0 -> 289 bytes admin/www/mailman-member/index.html | 173 ++++++++++++++ admin/www/mailman-member/mailman-member.css | 158 +++++++++++++ admin/www/mailman-member/mailman-member.html | 173 ++++++++++++++ admin/www/mailman-member/modules.gif | Bin 0 -> 385 bytes admin/www/mailman-member/next.gif | Bin 0 -> 253 bytes admin/www/mailman-member/node10.html | 182 +++++++++++++++ admin/www/mailman-member/node11.html | 119 ++++++++++ admin/www/mailman-member/node12.html | 116 ++++++++++ admin/www/mailman-member/node13.html | 190 ++++++++++++++++ admin/www/mailman-member/node14.html | 181 +++++++++++++++ admin/www/mailman-member/node15.html | 127 +++++++++++ admin/www/mailman-member/node16.html | 160 +++++++++++++ admin/www/mailman-member/node17.html | 174 ++++++++++++++ admin/www/mailman-member/node18.html | 139 ++++++++++++ admin/www/mailman-member/node19.html | 119 ++++++++++ admin/www/mailman-member/node20.html | 155 +++++++++++++ admin/www/mailman-member/node21.html | 151 +++++++++++++ admin/www/mailman-member/node22.html | 129 +++++++++++ admin/www/mailman-member/node23.html | 146 ++++++++++++ admin/www/mailman-member/node24.html | 153 +++++++++++++ admin/www/mailman-member/node25.html | 201 +++++++++++++++++ admin/www/mailman-member/node26.html | 113 ++++++++++ admin/www/mailman-member/node27.html | 149 ++++++++++++ admin/www/mailman-member/node28.html | 167 ++++++++++++++ admin/www/mailman-member/node29.html | 137 +++++++++++ admin/www/mailman-member/node3.html | 144 ++++++++++++ admin/www/mailman-member/node30.html | 196 ++++++++++++++++ admin/www/mailman-member/node31.html | 132 +++++++++++ admin/www/mailman-member/node32.html | 132 +++++++++++ admin/www/mailman-member/node33.html | 116 ++++++++++ admin/www/mailman-member/node34.html | 113 ++++++++++ admin/www/mailman-member/node35.html | 124 ++++++++++ admin/www/mailman-member/node36.html | 156 +++++++++++++ admin/www/mailman-member/node37.html | 146 ++++++++++++ admin/www/mailman-member/node38.html | 114 ++++++++++ admin/www/mailman-member/node39.html | 117 ++++++++++ admin/www/mailman-member/node4.html | 122 ++++++++++ admin/www/mailman-member/node40.html | 208 +++++++++++++++++ admin/www/mailman-member/node41.html | 325 +++++++++++++++++++++++++++ admin/www/mailman-member/node42.html | 271 ++++++++++++++++++++++ admin/www/mailman-member/node5.html | 149 ++++++++++++ admin/www/mailman-member/node6.html | 113 ++++++++++ admin/www/mailman-member/node7.html | 146 ++++++++++++ admin/www/mailman-member/node8.html | 126 +++++++++++ admin/www/mailman-member/node9.html | 200 +++++++++++++++++ admin/www/mailman-member/previous.gif | Bin 0 -> 252 bytes admin/www/mailman-member/pyfav.gif | Bin 0 -> 125 bytes admin/www/mailman-member/up.gif | Bin 0 -> 316 bytes 57 files changed, 7058 insertions(+) create mode 100644 admin/www/mailman-member.pdf create mode 100644 admin/www/mailman-member/about.html create mode 100644 admin/www/mailman-member/blank.gif create mode 100644 admin/www/mailman-member/contents.gif create mode 100644 admin/www/mailman-member/contents.html create mode 100644 admin/www/mailman-member/front.html create mode 100644 admin/www/mailman-member/img1.gif create mode 100644 admin/www/mailman-member/img2.gif create mode 100644 admin/www/mailman-member/index.gif create mode 100644 admin/www/mailman-member/index.html create mode 100644 admin/www/mailman-member/mailman-member.css create mode 100644 admin/www/mailman-member/mailman-member.html create mode 100644 admin/www/mailman-member/modules.gif create mode 100644 admin/www/mailman-member/next.gif create mode 100644 admin/www/mailman-member/node10.html create mode 100644 admin/www/mailman-member/node11.html create mode 100644 admin/www/mailman-member/node12.html create mode 100644 admin/www/mailman-member/node13.html create mode 100644 admin/www/mailman-member/node14.html create mode 100644 admin/www/mailman-member/node15.html create mode 100644 admin/www/mailman-member/node16.html create mode 100644 admin/www/mailman-member/node17.html create mode 100644 admin/www/mailman-member/node18.html create mode 100644 admin/www/mailman-member/node19.html create mode 100644 admin/www/mailman-member/node20.html create mode 100644 admin/www/mailman-member/node21.html create mode 100644 admin/www/mailman-member/node22.html create mode 100644 admin/www/mailman-member/node23.html create mode 100644 admin/www/mailman-member/node24.html create mode 100644 admin/www/mailman-member/node25.html create mode 100644 admin/www/mailman-member/node26.html create mode 100644 admin/www/mailman-member/node27.html create mode 100644 admin/www/mailman-member/node28.html create mode 100644 admin/www/mailman-member/node29.html create mode 100644 admin/www/mailman-member/node3.html create mode 100644 admin/www/mailman-member/node30.html create mode 100644 admin/www/mailman-member/node31.html create mode 100644 admin/www/mailman-member/node32.html create mode 100644 admin/www/mailman-member/node33.html create mode 100644 admin/www/mailman-member/node34.html create mode 100644 admin/www/mailman-member/node35.html create mode 100644 admin/www/mailman-member/node36.html create mode 100644 admin/www/mailman-member/node37.html create mode 100644 admin/www/mailman-member/node38.html create mode 100644 admin/www/mailman-member/node39.html create mode 100644 admin/www/mailman-member/node4.html create mode 100644 admin/www/mailman-member/node40.html create mode 100644 admin/www/mailman-member/node41.html create mode 100644 admin/www/mailman-member/node42.html create mode 100644 admin/www/mailman-member/node5.html create mode 100644 admin/www/mailman-member/node6.html create mode 100644 admin/www/mailman-member/node7.html create mode 100644 admin/www/mailman-member/node8.html create mode 100644 admin/www/mailman-member/node9.html create mode 100644 admin/www/mailman-member/previous.gif create mode 100644 admin/www/mailman-member/pyfav.gif create mode 100644 admin/www/mailman-member/up.gif (limited to 'admin') diff --git a/admin/www/mailman-member.pdf b/admin/www/mailman-member.pdf new file mode 100644 index 00000000..df667e6b Binary files /dev/null and b/admin/www/mailman-member.pdf differ diff --git a/admin/www/mailman-member/about.html b/admin/www/mailman-member/about.html new file mode 100644 index 00000000..aed4a760 --- /dev/null +++ b/admin/www/mailman-member/about.html @@ -0,0 +1,116 @@ + + +
+ + + + + + + + + + + + + +This document was generated using the + LaTeX2HTML translator. +
+ ++ LaTeX2HTML is Copyright © + 1993, 1994, 1995, 1996, 1997, Nikos + Drakos, Computer Based Learning Unit, University of + Leeds, and Copyright © 1997, 1998, Ross + Moore, Mathematics Department, Macquarie University, + Sydney. +
+ +The application of + LaTeX2HTML to the Python + documentation has been heavily tailored by Fred L. Drake, + Jr. Original navigation icons were contributed by Christopher + Petrilli. +
+ + + + + + diff --git a/admin/www/mailman-member/blank.gif b/admin/www/mailman-member/blank.gif new file mode 100644 index 00000000..2e31f4ed Binary files /dev/null and b/admin/www/mailman-member/blank.gif differ diff --git a/admin/www/mailman-member/contents.gif b/admin/www/mailman-member/contents.gif new file mode 100644 index 00000000..6d299c4c Binary files /dev/null and b/admin/www/mailman-member/contents.gif differ diff --git a/admin/www/mailman-member/contents.html b/admin/www/mailman-member/contents.html new file mode 100644 index 00000000..ec1b239b --- /dev/null +++ b/admin/www/mailman-member/contents.html @@ -0,0 +1,165 @@ + + + + + + + + + + + + + + + + + + ++ +
+ + + + diff --git a/admin/www/mailman-member/front.html b/admin/www/mailman-member/front.html new file mode 100644 index 00000000..115fc0f5 --- /dev/null +++ b/admin/www/mailman-member/front.html @@ -0,0 +1,115 @@ + + + + + + + + + + + + + + + + + + ++ +
+ +
+ +
+ + + + diff --git a/admin/www/mailman-member/img1.gif b/admin/www/mailman-member/img1.gif new file mode 100644 index 00000000..0f206516 Binary files /dev/null and b/admin/www/mailman-member/img1.gif differ diff --git a/admin/www/mailman-member/img2.gif b/admin/www/mailman-member/img2.gif new file mode 100644 index 00000000..1dc21b52 Binary files /dev/null and b/admin/www/mailman-member/img2.gif differ diff --git a/admin/www/mailman-member/index.gif b/admin/www/mailman-member/index.gif new file mode 100644 index 00000000..32eecfb4 Binary files /dev/null and b/admin/www/mailman-member/index.gif differ diff --git a/admin/www/mailman-member/index.html b/admin/www/mailman-member/index.html new file mode 100644 index 00000000..6bc50017 --- /dev/null +++ b/admin/www/mailman-member/index.html @@ -0,0 +1,173 @@ + + + + + + + + + + + + + + + +Terri Oda
+terri(at)zone12.com
+Release 2.1
+7 October 2003
+ +
Terri Oda
+terri(at)zone12.com
+Release 2.1
+7 October 2003
+ +
+ +
+
+
+
+
+
+
+There's also an -admin address which also reaches the list administrators, +but this address only exists for compatibility with older versions of +Mailman. + +
+For changing options, we use the LISTNAME-request +address (for example, mylist-request@example.com). + +
+Commands can appear in the subject line or the body of the message. Each +command should be on a separate line. If your mail program automatically +appends a signature to your messages, you may want to put the word +``end'' (without the quotes) on a separate line after your other commands. +The end command tells Mailman not to process the email after that +point. + +
+The most important command is probably the ``help'' command, since it +makes Mailman return a message full of useful information about the +email commands and directions to the web interface. + +
+Quick references to the subscriber commands have been provided in +Appendices A and B. (These have been slightly +adapted from the output of the help command.) + +
+ +
+ + + + diff --git a/admin/www/mailman-member/node11.html b/admin/www/mailman-member/node11.html new file mode 100644 index 00000000..cc07efef --- /dev/null +++ b/admin/www/mailman-member/node11.html @@ -0,0 +1,119 @@ + + + + + + + + + + + + + + + + + + ++If you have any trouble with any of these commands, you can always reach the +person or people in charge of a list by using the list administrator email address. +The list administrators can help you figure out +how to do something, subscribe/unsubscribe you, or change your +settings if you are unable to change them yourself for some reason. Please +remember that many mailing list administrators are volunteers who are donating +their spare time to run the list, and they may be very busy people. + +
+This list administrator email address is in the form LISTNAME-owner@DOMAIN, where LISTNAME is the name of the list (eg: mailman-users) and DOMAIN is +the name of the server (eg: python.org). +This email address, +along with the email addresses of specific administrators, is given on the +bottom of the list information pages. See Section 3.1 for more +information on finding the list information page for your list + +
+ +
+ + + + diff --git a/admin/www/mailman-member/node12.html b/admin/www/mailman-member/node12.html new file mode 100644 index 00000000..ea407afe --- /dev/null +++ b/admin/www/mailman-member/node12.html @@ -0,0 +1,116 @@ + + + + + + + + + + + + + + + + + + ++ +
+There are two common ways you can subscribe to a Mailman mailing list. + +
+Using the web interface: + +
+Warning: +Do NOT use a valuable password, since this + password may occasionally be mailed to you in plain text. +
+Using the email interface: + +
+After following one of these sets of instructions (you don't need to do +both!), there are a few possible outcomes depending upon the settings for +that list. + +
+Once this is done, you will likely receive another message welcoming you to +the list. This message contains some useful information including your list +password and some quick links for changing your options, so you may want to +save it for later reference. + +
+Note: +Subscribing can be done in other ways as well. See +Appendix A for more advanced email subscribing commands. + +
+ +
+ + + + diff --git a/admin/www/mailman-member/node14.html b/admin/www/mailman-member/node14.html new file mode 100644 index 00000000..0ace379b --- /dev/null +++ b/admin/www/mailman-member/node14.html @@ -0,0 +1,181 @@ + + + + + + + + + + + + + + + + + ++Don't want to be on a list any more? If you're just going on vacation or +are too busy to read mails and want to temporarily turn them off, you may want +to stop mail delivery rather than unsubscribing. This means you keep your +password and other settings so you can, for example, still have access to +private list archives. If this is what you'd +prefer, see Section 7.1 for instructions on disabling mail +delivery temporarily. + +
+If you actually want to leave the list, there are two common ways you can +unsubscribe from a Mailman mailing list. + +
+Using the web interface: + +
+Using the email interface: + +
+After following one of these sets of instructions (you don't need to do +both!), you will be sent a confirmation mail and must follow the +instructions given in that mail to complete the unsubscription. This is to +stop people from unsubscribing you without your permission. In addition, a +moderator may need to approve your unsubscription. (Administrator-approved +unsubscriptions are uncommon.) + +
+If you do not receive this confirmation mail with instructions, make sure +that you typed your email address correctly (if you were using the web +interface to unsubscribe) and that the address you tried +to unsubscribe is, indeed, actually subscribed to that list. For security +reasons, Mailman generates the same member options page regardless of +whether the address entered is subscribed or not. This means that people +cannot use this part of the web interface to find out if someone is +subscribed to the list, but it also means that it's hard to tell if you just +made a typo. + +
+Once your unsubscription has been processed, you will will probably receive +another message confirming your unsubscription from the list, and at that +point you should stop receiving messages. + +
+If you wish to skip the confirmation process (for example, you might be +unsubscribing an address which no longer works), it is possible to bypass it by +using your password instead and either logging in to your options page using +it (See Section 3.1), or sending it with your email commands to +LISTNAME-request (See Appendix A for advanced email +unsubscription commands). See Section 6.1 for more +information on getting your password. + +
+ +
+ + + + diff --git a/admin/www/mailman-member/node15.html b/admin/www/mailman-member/node15.html new file mode 100644 index 00000000..0df3e1b1 --- /dev/null +++ b/admin/www/mailman-member/node15.html @@ -0,0 +1,127 @@ + + + + + + + + + + + + + + + + + + ++Warning: +Do NOT use a valuable password for Mailman, since it can be +sent in plain text to you. + +
+ +
+ +
+If you do not receive the password reminder email after doing this, make sure +that you typed your +email address correctly and that the address you used is, indeed, actually +subscribed to that list. For security reasons, Mailman generates the same +member options page regardless of whether the address entered is subscribed +or not. This means that people cannot use this part of the web interface to +find out if someone is subscribed to the list, but it also means that it's +hard to tell if you just made a typo. + +
+You can also get a reminder using the email interface, + +
+Commands can appear + in either the body or the subject of the message. (See + Section 3.2 for more information about sending mail + commands.) + +
+If you are not sending mail from your subscribed address, you can also
+ specify this address by sending the command password address=ADDRESS
.
+
+ +
+ + + + diff --git a/admin/www/mailman-member/node17.html b/admin/www/mailman-member/node17.html new file mode 100644 index 00000000..8f1ad534 --- /dev/null +++ b/admin/www/mailman-member/node17.html @@ -0,0 +1,174 @@ + + + + + + + + + + + + + + + + + + ++From the web interface: + +
+
+This can also be changed for multiple lists at the same time if you are subscribed to +more than one list on the same domain. See Section 10.1 for +information about changing settings globally. + +
+From the email interface: + +
+Commands can appear + in either the body or the subject of the message. (See + Section 3.2 for more information about sending mail + commands.) + +
+If you are not sending mail from your membership address, you can also
+ specify this address with address=ADDRESS
after
NEWPASSWORD
.
+
+
+For example, if kathy@here.com wanted to change her mylist + password from zirc to miko, but she was sending mail from + her work address kathy@work.com, she could send a message + to mylist-request@example.com with the subject set to + password zirc miko address=kathy@here.com. +
+ +
+ + + + diff --git a/admin/www/mailman-member/node18.html b/admin/www/mailman-member/node18.html new file mode 100644 index 00000000..b33fc960 --- /dev/null +++ b/admin/www/mailman-member/node18.html @@ -0,0 +1,139 @@ + + + + + + + + + + + + + + + + + ++Using the web interface: + +
+This can also be changed for multiple lists at the same time if you are subscribed to +more than one list on the same domain. See Section 10.1 for +information about changing settings globally. + +
+Using the email interface: + +
+Commands can appear + in either the body or the subject of the message. (See + Section 3.2 for more information about sending mail + commands.) +
+ +
+ + + + diff --git a/admin/www/mailman-member/node19.html b/admin/www/mailman-member/node19.html new file mode 100644 index 00000000..2f5934bd --- /dev/null +++ b/admin/www/mailman-member/node19.html @@ -0,0 +1,119 @@ + + + + + + + + + + + + + + + + + + ++You may wish to temporarily stop getting messages from the +list without having to unsubscribe. +If you disable mail delivery, you will no longer receive messages, but will +still be a subscriber and will retain your password and other settings. + +
+This can be handy in a many different cases. For example, you could be +going on vacation or need a break from the list because you're too busy to +read any extra mail. +Many mailing lists also allow only subscribers to post to the list, so if you +commonly send mail from more than one address (eg, one address for at home +and another for when you're travelling), you may want to have more than +one subscribed account, but have only one of them actually receive mail. +You can also use this as a way to read private archives even on a list which +may be too busy for you to have sent directly to your mailbox. All you need to do is subscribe, disable mail delivery, and use your password and email to +log in to the archives. + +
+To disable/enable mail delivery using the web interface: + +
+This can also be changed for multiple lists at the same time if you are subscribed to +more than one list on the same domain. See Section 10.1 for +information about changing settings globally. + +
+To disable/enable mail delivery using the email interface: + +
+Commands can appear + in either the body or the subject of the message. (See + Section 3.2 for more information about sending mail + commands.) +
+ +
+ + + + diff --git a/admin/www/mailman-member/node21.html b/admin/www/mailman-member/node21.html new file mode 100644 index 00000000..82ba4100 --- /dev/null +++ b/admin/www/mailman-member/node21.html @@ -0,0 +1,151 @@ + + + + + + + + + + + + + + + + + + ++Mailman can't completely stop you from getting duplicate messages, but it +can help. One common reason people get multiple copies of a mail is that +the sender has used a ``group reply'' function to send mail to both the list +and some number of individuals. If you want to avoid getting these messages, +Mailman can be set to check and see if you are in the To: or +CC: lines of the message. If your address appears there, then +Mailman can be told not to deliver another copy to you. This means you get +only the copy sent by the original sender, and not a copy which been altered by +Mailman (to include headers and footers, strip attachments, etc.). + +
+To turn this on or off using the web interface: + +
+This can also be changed for multiple lists at the same time if you are subscribed to +more than one list on the same domain. See Section 10.1 for +information about changing settings globally. + +
+To turn this on or off using the email interface: + +
+Commands can appear + in either the body or the subject of the message. (See + Section 3.2 for more information about sending mail + commands.) +
+ +
+ + + + diff --git a/admin/www/mailman-member/node22.html b/admin/www/mailman-member/node22.html new file mode 100644 index 00000000..d751a49c --- /dev/null +++ b/admin/www/mailman-member/node22.html @@ -0,0 +1,129 @@ + + + + + + + + + + + + + + + + + + ++A confirmation message will be sent to your new address, and the change will +not happen until you confirm the change by following the instructions in that +message. + +
+There is no special way to do this from the email interface, but you can +subscribe and unsubscribe for more or less the same effect. (See +Sections 5.1 and 5.2 for more information +on subscribing and unsubscribing.) + +
+ +
+ + + + diff --git a/admin/www/mailman-member/node23.html b/admin/www/mailman-member/node23.html new file mode 100644 index 00000000..bc099468 --- /dev/null +++ b/admin/www/mailman-member/node23.html @@ -0,0 +1,146 @@ + + + + + + + + + + + + + + + + + + ++Note: +This option has no effect if you are receiving digests. + +
+You may also want to see Section 7.5, which discusses +acknowledgement emails for posts sent to the list. + +
+To set this using the web interface: + +
+To set this using the email interface: + +
+Commands can appear + in either the body or the subject of the message. (See + Section 3.2 for more information about sending mail + commands.) +
+ +
+ + + + diff --git a/admin/www/mailman-member/node24.html b/admin/www/mailman-member/node24.html new file mode 100644 index 00000000..96b043db --- /dev/null +++ b/admin/www/mailman-member/node24.html @@ -0,0 +1,153 @@ + + + + + + + + + + + + + + + + + + ++On most lists, you will simply receive a copy of your mail when it has gone +through the list software, but if this is disabled (See +Section 7.4), your list mail delivery is disabled (See +Section 7.1), you are not subscribed to that topic (See +Section 9.2) or you +simply want an extra acknowledgement from the system, this option may +be useful to you. + +
+Note: +If you are not subscribed to the list, this option cannot be used. +You must either check the archives yourself (if the list has public archives), +ask someone who is subscribed to the list, or subscribe to use this option. + +
+To set this using the web interface: + +
+To set this using the email interface: + +
+Commands can appear + in either the body or the subject of the message. (See + Section 3.2 for more information about sending mail + commands.) +
+ +
+ + + + diff --git a/admin/www/mailman-member/node25.html b/admin/www/mailman-member/node25.html new file mode 100644 index 00000000..fcc04864 --- /dev/null +++ b/admin/www/mailman-member/node25.html @@ -0,0 +1,201 @@ + + + + + + + + + + + + + + + + + ++To check if this is the case, try visiting the archives of the list + (assuming that the list has archives). If the list has no archives, you + may have to ask another subscriber. (See Section 3.1 for help + in finding the list archives.) + +
+Note: +Generally, it is considered + impolite to send test messages to the entire list. + If you feel a need to test that the list is working and for some reason you + cannot simply compose a regular message to the list, it is less disruptive + to send a help message to + the list request address (LISTNAME-request@DOMAIN) to see if that works, + or to contact the list + administrator (LISTNAME-owner@DOMAIN) to ask if the list is working. + +
+
+If your mail provider ``bounces'' too many messages (that is, it tells + Mailman that the message could not be delivered) + Mailman eventually stops trying to send you mail. This feature allows + Mailman to gracefully handle addresses which no longer exist (for example, + the subscriber has found a new Internet service provider and forgot to + unsubscribe the old address), as well + as addresses which are temporarily out-of-service (for example, the + subscriber has used up all of the allotted space for his or her email + account, or the subscriber's mail provider is experiencing difficulties). + +
+Even if you are unaware of any difficulties with your mail provider, it + is a good idea to check this. Some popular webmail providers and + internet servers are not as reliable as one might assume, nor is the + internet as a whole. You may want to also send yourself a test message + from another account or ask a friend to send you a test message to make + sure your subscribed address is working. + +
+To check if this may be the reason you are not receiving messages, log in + to the your options page (See + Section 3.1 for more details on how to do this) and + look at your options. + If your subscription has been disabled or Mailman has received bounces from + your email address, there will be a big banner at the top of this page. + +
+To re-enable mail delivery, look for an option marked ``Mail Delivery'' and + set it to ``Enabled'' to start receiving mail again. + To get rid of your bounce score, you can disable and then re-enable delivery. + For more instructions on disabling or enabling mail delivery, + see Section 7.1. + +
+Note: +Even if you have not been disabled at the time you check, you could be + bouncing messages and not have reached the threshold for your + subscription to be disabled. You may need to check again. + +
+
+No matter what many of us would like, the internet is not 100% + reliable, nor is it always fast. Sometimes, messages simply take a long + time to get to you. Try to be patient, especially if the server is far + (in terms of networks, not geography, although often one implies the other) + from your internet service provider. + +
+To check if this might be causing your problem, you can try pinging + the list server or tracing the route between you and it. (Instructions + on how to do this varies from platform to platform, so you may want to + use a search engine to find those appropriate for you.) + +
+
+To test if this is a case, try visiting the list's web interface and + try sending a message to LISTNAME-request@DOMAIN with the command + ``help'' (without the quotes) in the Subject:. If + neither of these works after a reasonable length of time, this may be + the problem. You may wish to contact either the list or site + administrator(s). +
+ +
+ + + + diff --git a/admin/www/mailman-member/node26.html b/admin/www/mailman-member/node26.html new file mode 100644 index 00000000..c6fedcee --- /dev/null +++ b/admin/www/mailman-member/node26.html @@ -0,0 +1,113 @@ + + + + + + + + + + + + + + + + + + ++Groups of posts are called ``digests'' in Mailman. Rather than get messages +one at a time, you can get messages grouped together. On a moderately busy +list, this typically means you get one email per day, although it may be +more or less frequent depending upon the list. + +
+You may also want to look at Section 8.2 which discusses MIME +and plain text digests. + +
+To turn digest mode on or off using the web interface, + +
+Set it to ``On'' to + receive messages bundled together in digests. Set it to ``Off'' to + receive posts separately. +
+To turn digest mode on or off using the email interface, + +
+Commands can appear + in either the body or the subject of the message. (See + Section 3.2 for more information about sending mail + commands.) +
+ +
+ + + + diff --git a/admin/www/mailman-member/node28.html b/admin/www/mailman-member/node28.html new file mode 100644 index 00000000..19241ad7 --- /dev/null +++ b/admin/www/mailman-member/node28.html @@ -0,0 +1,167 @@ + + + + + + + + + + + + + + + + + ++MIME is short for Multipurpose Internet Mail Extensions. It is used to +send things by email which are not necessarily simple plain text. (For +example, MIME would be used if you were sending a picture of your dog to +a friend.) + +
+A MIME digest has each message as an attachment inside the message, along +with a summary table of contents. + +
+A plain text digest is a simpler form of digest, which should be readable +even in mail readers which don't support MIME. The messages are simply put +one after the other into one large text message. + +
+Most modern mail programs do support MIME, so you only need to choose +plain text digests if you are having trouble reading the MIME ones. + +
+Note: +This option has no effect if you are not receiving mail bunched +as digests. (See Section 8.1 for more information on +receiving mail as digests.) + +
+To set your digest type using the web interface: + +
+Set it to ``MIME'' to receive digests in MIME format, or ``Plain text'' to + receive digests in plain text format. +
+This can also be changed for multiple lists at the same time if you are subscribed to +more than one list on the same domain. See Section 10.1 for +information about changing settings globally. + +
+To set your digest type using the email interface, + +
+Commands can appear + in either the body or the subject of the message. (See + Section 3.2 for more information about sending mail + commands.) +
+ +
+ + + + diff --git a/admin/www/mailman-member/node29.html b/admin/www/mailman-member/node29.html new file mode 100644 index 00000000..b4c9710d --- /dev/null +++ b/admin/www/mailman-member/node29.html @@ -0,0 +1,137 @@ + + + + + + + + + + + + + + + + + + ++Some lists are set up so that different topics are handled by Mailman. +For example, the courses list on Linuxchix.org is a discussion list for +courses being run by linuxchix members, and often there are several courses +being run at the same time. +(eg: Networking for beginners, C programming, LATEX document mark up.) +Each of the courses being run is associated with a separate topic on the list so that people +can choose only to receive the course they want to take. + +
+These +topics must be configured by the list administrator, but it is the +responsibility of each poster to make sure that their post is put with +the correct topic. Usually, this means adding a word or tag of some type to the +subject line (eg: [Networking] What type of cables do I need?) or making +sure the Keywords: line has the right information. (By default, +you can put a Keywords: section in the beginning of the body +of your message, but this can be configured by your list administrator.) +Note that these tags are case-insensitive. + +
+ +
+This document is intended to help the members of a Mailman 2.1 mailing list +learn to use the features available to them. It covers the use of the +web and email interfaces for subscribing and unsubscribing, changing +member options, getting password reminders and other subscriber-level +tasks. It also answers some common questions of interest to Mailman list +members. + +
+Information for list and site administrators is provided in +other documents. + +
+This document need not be read in order. If you are simply looking for +an answer to a specific question, jump to the appropriate place and +references to other sections will be provided if necessary or potentially +helpful. + +
+Note: +For the purposes of this document, +we assume that the reader is familiar with common terms related to email (eg: +Subject line, body of the message) and web sites (eg: drop-down box, button) or +can look them up. We also assume that the reader can already use his or her +email program and web browser well enough that instructions such as ``send email +to this address'' or ``visit this web page'' or ``fill in the form provided'' are +clear. If you are not familiar with these actions, you may want to consult +other documentation to learn how to do these things with your particular +setup. + +
+ +
+When a list administrator defines a topic, he or she sets three things: + +
+You can view this information by logging in to your member options page. + (See Section 3.1 for more details on how to do this.) and +clicking on the ``details'' link for any topic that interests you. + +
+To post on a given topic, you need to make sure that the +Keywords: or Subject: headers in a message +match the regular expression for that topic. +A regular expression is a pattern which may match more than one thing. +Regular expressions can actually be fairly complex, so you may want to +just ask the list administrator if you don't know how to make +heads or tails of the expression given. + +
+If you really want to know more about regular expressions, read on, but for the +most part, your list administrator should include in the topic description what +you need to add to your Keywords or Subject line to match the topic pattern. + +
+Most Mailman topic expressions will be fairly simple regular expressions, so +in this document we will simply give you some common examples. Regular +expressions are a bit too complex to teach in a few lines here, so if you +really want to understand how the regular expressions work, you should +find a tutorial or reference elsewhere. (For example, DevShed has a decent +tutorial at +http://www.devshed.com/Server_Side/Administration/RegExp/) + +
+Here are some examples of possible regular expressions and matching lines: + +
+
Regular expression | +Matching lines | +
---|---|
zuff | +Keywords: zuff | +
zuff | +Keywords: ZUFF | +
zuff | +Keywords: Zuff | +
zuff | +Keywords: amaryllis, zuff, applesauce | +
zuff | +Subject: [zuff] Do you have the right stuff for zuff? | +
zuff | +Subject: Do you have the right stuff for zuff? | +
zuff | +Subject: What is zuff? | + +
\[zuff\] | +Keywords: [zuff] | +
\[zuff\] | +Subject: [zuff] Do you have the right stuff? | +
\[zuff\] | +Subject: Online zuff tutorials (was Re: [zuff] What is zuff?) |
+A few notes: + +
+ +
+ + + + diff --git a/admin/www/mailman-member/node31.html b/admin/www/mailman-member/node31.html new file mode 100644 index 00000000..d86e781e --- /dev/null +++ b/admin/www/mailman-member/node31.html @@ -0,0 +1,132 @@ + + + + + + + + + + + + + + + + + + ++If topics have been set up by your mailing list administrator, you can +choose to subscribe to only part of a list by selecting the topics you +want to receive. + +
+If you wish to get all messages sent to the list, make sure you +are not subscribed to any topics. + +
+ +
+If any topics are defined, you can select those you wish. If you do + not select any topics of interest, you will receive all posts + sent to the list. +
+You probably also want to look at Section 9.3 which discusses +changing your settings for messages where no topic is set. + +
+ +
+ + + + diff --git a/admin/www/mailman-member/node32.html b/admin/www/mailman-member/node32.html new file mode 100644 index 00000000..dadb89ae --- /dev/null +++ b/admin/www/mailman-member/node32.html @@ -0,0 +1,132 @@ + + + + + + + + + + + + + + + + + ++If you are only subscribed to some topics, you can either choose to either +receive or not receive messages with no topic set, much the way you can +choose to subscribe only to certain topics. + +
+To change this setting, + +
+If you wish to receive messages with no topic set, select ``Yes.'' If you + do not wish to receive such messages, choose ``No.'' +
+This setting has no effect if you are not subscribed to any topics. + +
+ +
+ + + + diff --git a/admin/www/mailman-member/node33.html b/admin/www/mailman-member/node33.html new file mode 100644 index 00000000..3afbee2d --- /dev/null +++ b/admin/www/mailman-member/node33.html @@ -0,0 +1,116 @@ + + + + + + + + + + + + + + + + + + ++ +
+For some of the options given in your member options page, there is a +checkbox which says ``Change Globally'' or ``Set Globally.'' +This means that if you change this +option, you can also have the change made for all your other +subscriptions on the same domain. +This can be handy if, for example, you +want to make sure all your passwords are the same, or you are going on +vacation and want to turn off mail delivery from all the lists. + +
+ +
+ + + + diff --git a/admin/www/mailman-member/node35.html b/admin/www/mailman-member/node35.html new file mode 100644 index 00000000..059234c8 --- /dev/null +++ b/admin/www/mailman-member/node35.html @@ -0,0 +1,124 @@ + + + + + + + + + + + + + + + + + + ++To change your subscription name, + +
+This can also be changed for multiple lists at the same time if you are subscribed to +more than one list on the same domain. See Section 10.1 for +information about changing settings globally. + +
+Note: +You do not need to have a subscription name set. + +
+ +
+ + + + diff --git a/admin/www/mailman-member/node36.html b/admin/www/mailman-member/node36.html new file mode 100644 index 00000000..848e24a3 --- /dev/null +++ b/admin/www/mailman-member/node36.html @@ -0,0 +1,156 @@ + + + + + + + + + + + + + + + + + + ++Mailman is multi-lingual, meaning its interface has been translated to many +different languages. Your list administrator can enable various languages for +their use when interacting with Mailman. +(For a complete listing of the languages see +http://www.list.org/i18n.html.) If your list has other languages +enabled, you may be able to have the web interface, etc. in a language of your +choice. + +
+Note: +This does NOT necessarily mean that all the posts sent to the list will +be in the language you selected. Only the pre-prepared texts presented by +Mailman will be affected by this setting. Posts are in whatever language the +poster uses. + +
+Your preferred language is set when you subscribe (see +Section5.1), and can be changed later if the list supports +more than one language. + +
+To change your preferred language in Mailman, + +
+If your list does not support the language you would prefer to use, you may +contact the list administrator (LISTNAME-owner@DOMAIN) to see if it can be +added, but remember that this may mean some work that the list and/or site +administrator(s) do not have time or the ability to do. + +
+If your language of choice is not available because no translation +exists for Mailman, please consider volunteering your time as a translator. +For more information you may want to consult the mailman-i18n mailing +list at http://mail.python.org/mailman/listinfo/mailman-i18n. The +current status of internationalization efforts is available at +http://www.list.org/i18n.html. + +
+Note: +i18n is a common short-hand for ``internationalization'' because the word +starts with an i, ends with an n, and has 18 letters in between. If you mumble +a bit, i18n even sounds a bit like ``internationalization.'' + +
+ +
+ + + + diff --git a/admin/www/mailman-member/node37.html b/admin/www/mailman-member/node37.html new file mode 100644 index 00000000..de575912 --- /dev/null +++ b/admin/www/mailman-member/node37.html @@ -0,0 +1,146 @@ + + + + + + + + + + + + + + + + + ++If you do not want to have your email address show up on the subscriber list +for any reason, you can opt to have it concealed. + +
+Common reasons for doing this include avoiding unsolicited bulk email (spam). +By default, the subscribers list is obscured to hinder spam harvesters, +but if you feel this is insufficient it's easy enough to remove your address +from the subscriber list given in the information pages or by email request. +(Note that this does not conceal your address from the list administrators.) +You may wish to see Section 11.2 for more information on what +Mailman can do to help avoid spam. + +
+To change this setting using the web interface: + +
+To change this setting using the email interface: + +
+Commands can appear + in either the body or the subject of the message. (See + Section 3.2 for more information about sending mail + commands.) +
+ +
+ + + + diff --git a/admin/www/mailman-member/node38.html b/admin/www/mailman-member/node38.html new file mode 100644 index 00000000..013b15cf --- /dev/null +++ b/admin/www/mailman-member/node38.html @@ -0,0 +1,114 @@ + + + + + + + + + + + + + + + + + + ++ +
+Public archives usually have addresses of the form +http://WEBSERVER/pipermail/LISTNAME/ and private archives usually +have addresses of the form http://WEBSERVER/mailman/private/LISTNAME. + +
+See Section 3.1 for more information on finding the addresses of a +list. + +
+ +
+ + + + diff --git a/admin/www/mailman-member/node4.html b/admin/www/mailman-member/node4.html new file mode 100644 index 00000000..f246a379 --- /dev/null +++ b/admin/www/mailman-member/node4.html @@ -0,0 +1,122 @@ + + + + + + + + + + + + + + + + + + ++Sections of this document have been borrowed from the List Administrator Manual +found in Mailman CVS, which was written by Barry A. Warsaw, and from the in-line +help for Mailman 2.1. + +
+The rest of this manual has been written by Terri Oda. +Terri has been maintaining mailing lists since the year she attained +voting age in Canada, although the two are not related. She currently +oversees the mailing lists at Linuxchix.org, as well as several smaller +servers. In the world outside of list administration, Terri is doing +work with an artificial life spam detector, and is actually more of a +programmer than technical writer. + +
+Thanks to Margaret McCarthy, Jason Walton and Barry Warsaw for their help +in proofreading and otherwise improving this manual. + +
+Thanks also to Ikeda Soji, who has made a Japanese translation of this document. + +
+ +
+ + + + diff --git a/admin/www/mailman-member/node40.html b/admin/www/mailman-member/node40.html new file mode 100644 index 00000000..4b084bb4 --- /dev/null +++ b/admin/www/mailman-member/node40.html @@ -0,0 +1,208 @@ + + + + + + + + + + + + + + + + + ++A technical list's archives may include answers to a range of +different questions. Often, the people who have posted these answers would +be happy to help someone who doesn't quite understand the answer, and don't +mind giving their address out for that purpose. But +although it would be wonderful if everyone could contact each other easily, +we also want to make sure that the list and list archives are not abused by +people who send spam. + +
+To make a range of options available to list administrators, Mailman allows +a variety of configurations to help protect email addresses. +Many of these settings are optional to the list administrator, so your +particular list may be set up in different ways. List administrators +must walk a fine line between protecting subscribers and making it difficult +for people to get in touch. + +
+ +
+
+Warning: +This does not stop other members from quoting your posts, + possibly even including your email address. + +
+
+
+Of course, many address-obscuring methods can be circumvented by determined +people, so be aware that the protections used may not be enough. + +
+ +
+ + + + diff --git a/admin/www/mailman-member/node41.html b/admin/www/mailman-member/node41.html new file mode 100644 index 00000000..c856ebc3 --- /dev/null +++ b/admin/www/mailman-member/node41.html @@ -0,0 +1,325 @@ + + + + + + + + + + + + + + + + + + ++
+
+
+
+
+
+Use `set help' (without the quotes) to get a more detailed list of the + options you can change. This list is also given in + Appendix B. + +
+Use `set show' (without the quotes) to view your current option + settings. + +
+
+The next argument may be either: `nodigest' or `digest' (no quotes!).
+ If you wish to subscribe an address other than the address you sent
+ this request from, you may specify `address=ADDRESS
' (no brackets
+ around the email address, and no quotes!)
+
+
+
+
+ +
+ + + + diff --git a/admin/www/mailman-member/node42.html b/admin/www/mailman-member/node42.html new file mode 100644 index 00000000..d597ce11 --- /dev/null +++ b/admin/www/mailman-member/node42.html @@ -0,0 +1,271 @@ + + + + + + + + + + + + + + + + + ++ +
+
+
+
+
+
+
+
+
+
+ +
+ + + + diff --git a/admin/www/mailman-member/node5.html b/admin/www/mailman-member/node5.html new file mode 100644 index 00000000..0f48713f --- /dev/null +++ b/admin/www/mailman-member/node5.html @@ -0,0 +1,149 @@ + + + + + + + + + + + + + + + + + + ++A mailing list is simply a list of addresses to which the same information +is being sent. If you were a magazine publisher, you would have a list of +the mailing addresses of all the subscribers to the magazine. In the case +of an electronic mailing list, we use a list of email addresses from people +interested in hearing about or discussing a given topic. + +
+Two common types of email mailing lists are announcement lists and discussion +lists. + +
+Announcement lists are used so that one person or group can send +announcements to a group of people, much like a magazine publisher's mailing +list is used to send out magazines. For example, a band may use an +announcement mailing list to let their fan base know about their upcoming +concerts. + +
+A discussion list allows a group of people to discuss topics amongst +themselves, with everyone able to send mail to the list and have it distributed +to everyone in the group. This discussion may also be moderated, so only +selected posts are sent on to the group as a whole, or only certain people are +allowed to send to the group. For example, a group of model plane enthusiasts +might use a discussion mailing list to share tips about model construction and +flying. + +
+Some common terms: + +
+GNU Mailman is software that lets you manage electronic mailing lists. It +supports a wide range of mailing list types, such as general discussion +lists and announce-only lists. Mailman has extensive features which make it +good for list subscribers, such as easy subscription and unsubscription, +privacy options, and the ability to temporarily stop getting posts from the +list. The list member features are covered in this document. + +
+Mailman also has many features which make it attractive to list and site +administrators. These features are covered in the list and site administrator +manuals. + +
+ +
+ + + + diff --git a/admin/www/mailman-member/node7.html b/admin/www/mailman-member/node7.html new file mode 100644 index 00000000..98a78051 --- /dev/null +++ b/admin/www/mailman-member/node7.html @@ -0,0 +1,146 @@ + + + + + + + + + + + + + + + + + + ++Often, it's easier to simply give an example than explain exactly how +to find the address for your specific list. As such, we'll frequently +give examples for a fictional list called +LISTNAME@DOMAIN whose list information page can be found at +http://WEBSERVER/mailman/listinfo/LISTNAME. + +
+Neither of these are +real addresses, but they show the form of a typical list address. +The capital letters used for the list-specific parts of each address should +make it easier to see what should be changed for each +list. Although specific list configurations may be different, you will +probably be able to just replace the words given in capital letters with the +appropriate values for a real list: + +
+
+As a real-life example, if you are interested in the mailman-users list, you'd +make the following substitutions: LISTNAME=mailman-users, DOMAIN=python.org, WEBSERVER=mail.python.org. As such, for the +mailman-users@python.org +mailing list, the list information page can be found at the URL +http://mail.python.org/mailman/listinfo/mailman-users. (These, unlike +most of the examples given in this document, are real addresses.) + +
+Most lists will have this information stored in the List-*: +headers. Many +mail programs will hide these by default, so you may have to choose to view +full headers before you can see these informational headers. + +
+ +
+ + + + diff --git a/admin/www/mailman-member/node8.html b/admin/www/mailman-member/node8.html new file mode 100644 index 00000000..77941505 --- /dev/null +++ b/admin/www/mailman-member/node8.html @@ -0,0 +1,126 @@ + + + + + + + + + + + + + + + + + + ++The interface you use for changing options is largely +a matter of preference, since most (but not all) of the options which can +be changed from the web interface can also be changed by email. + Usually it is easier to use the web interface for +changing options, since the web interface provides instructions as you go, but +there are times when people may prefer the email interface, so both are +provided. + +
+ +
+Every mailing list is also accessible by a number of web pages. Note that +the exact URLs are configurable by the site administrator, so they may be +different than what's described below. We'll describe the most common +configuration, but check with your site administrator or hosting +service for details. + +
+
+
+
+
+
+
+
+
+
+
+
+
+ +
+ + + + diff --git a/admin/www/mailman-member/previous.gif b/admin/www/mailman-member/previous.gif new file mode 100644 index 00000000..de1da160 Binary files /dev/null and b/admin/www/mailman-member/previous.gif differ diff --git a/admin/www/mailman-member/pyfav.gif b/admin/www/mailman-member/pyfav.gif new file mode 100644 index 00000000..58271ede Binary files /dev/null and b/admin/www/mailman-member/pyfav.gif differ diff --git a/admin/www/mailman-member/up.gif b/admin/www/mailman-member/up.gif new file mode 100644 index 00000000..a9d3e13e Binary files /dev/null and b/admin/www/mailman-member/up.gif differ -- cgit v1.2.3