From 3a258ad5cdd98c5705af6c02ba91993b3d382adc Mon Sep 17 00:00:00 2001 From: Barry Warsaw Date: Wed, 5 Dec 2007 17:23:41 -0500 Subject: Because the admin directory is no longer included, the www directory isn't either, and that's where the generated docs used to live. So now, make this directory include the generated docs, removing the old IPC7 and LISA-98 directories, and the .tex source files. These latter are moved to the admin repository. --- doc/mailman-member/about.html | 112 ++++++++++++ doc/mailman-member/blank.png | Bin 0 -> 1031 bytes doc/mailman-member/contents.html | 159 ++++++++++++++++ doc/mailman-member/contents.png | Bin 0 -> 649 bytes doc/mailman-member/front.html | 110 ++++++++++++ doc/mailman-member/images.pl | 18 ++ doc/mailman-member/img1.png | Bin 0 -> 185 bytes doc/mailman-member/img2.png | Bin 0 -> 163 bytes doc/mailman-member/index.dat | 0 doc/mailman-member/index.html | 171 ++++++++++++++++++ doc/mailman-member/index.png | Bin 0 -> 529 bytes doc/mailman-member/internals.pl | 114 ++++++++++++ doc/mailman-member/intlabels.pl | 3 + doc/mailman-member/labels.pl | 217 ++++++++++++++++++++++ doc/mailman-member/mailman-member.css | 243 +++++++++++++++++++++++++ doc/mailman-member/mailman-member.html | 171 ++++++++++++++++++ doc/mailman-member/modules.png | Bin 0 -> 598 bytes doc/mailman-member/next.png | Bin 0 -> 511 bytes doc/mailman-member/node10.html | 183 +++++++++++++++++++ doc/mailman-member/node11.html | 114 ++++++++++++ doc/mailman-member/node12.html | 111 ++++++++++++ doc/mailman-member/node13.html | 182 +++++++++++++++++++ doc/mailman-member/node14.html | 175 ++++++++++++++++++ doc/mailman-member/node15.html | 122 +++++++++++++ doc/mailman-member/node16.html | 155 ++++++++++++++++ doc/mailman-member/node17.html | 169 +++++++++++++++++ doc/mailman-member/node18.html | 134 ++++++++++++++ doc/mailman-member/node19.html | 114 ++++++++++++ doc/mailman-member/node20.html | 150 ++++++++++++++++ doc/mailman-member/node21.html | 143 +++++++++++++++ doc/mailman-member/node22.html | 119 ++++++++++++ doc/mailman-member/node23.html | 141 +++++++++++++++ doc/mailman-member/node24.html | 147 +++++++++++++++ doc/mailman-member/node25.html | 189 +++++++++++++++++++ doc/mailman-member/node26.html | 108 +++++++++++ doc/mailman-member/node27.html | 144 +++++++++++++++ doc/mailman-member/node28.html | 161 +++++++++++++++++ doc/mailman-member/node29.html | 132 ++++++++++++++ doc/mailman-member/node3.html | 139 ++++++++++++++ doc/mailman-member/node30.html | 185 +++++++++++++++++++ doc/mailman-member/node31.html | 127 +++++++++++++ doc/mailman-member/node32.html | 124 +++++++++++++ doc/mailman-member/node33.html | 111 ++++++++++++ doc/mailman-member/node34.html | 108 +++++++++++ doc/mailman-member/node35.html | 119 ++++++++++++ doc/mailman-member/node36.html | 143 +++++++++++++++ doc/mailman-member/node37.html | 141 +++++++++++++++ doc/mailman-member/node38.html | 109 +++++++++++ doc/mailman-member/node39.html | 112 ++++++++++++ doc/mailman-member/node4.html | 113 ++++++++++++ doc/mailman-member/node40.html | 198 ++++++++++++++++++++ doc/mailman-member/node41.html | 320 +++++++++++++++++++++++++++++++++ doc/mailman-member/node42.html | 266 +++++++++++++++++++++++++++ doc/mailman-member/node5.html | 142 +++++++++++++++ doc/mailman-member/node6.html | 108 +++++++++++ doc/mailman-member/node7.html | 141 +++++++++++++++ doc/mailman-member/node8.html | 121 +++++++++++++ doc/mailman-member/node9.html | 195 ++++++++++++++++++++ doc/mailman-member/previous.png | Bin 0 -> 511 bytes doc/mailman-member/pyfav.png | Bin 0 -> 240 bytes doc/mailman-member/up.png | Bin 0 -> 577 bytes 61 files changed, 7233 insertions(+) create mode 100644 doc/mailman-member/about.html create mode 100644 doc/mailman-member/blank.png create mode 100644 doc/mailman-member/contents.html create mode 100644 doc/mailman-member/contents.png create mode 100644 doc/mailman-member/front.html create mode 100644 doc/mailman-member/images.pl create mode 100644 doc/mailman-member/img1.png create mode 100644 doc/mailman-member/img2.png create mode 100644 doc/mailman-member/index.dat create mode 100644 doc/mailman-member/index.html create mode 100644 doc/mailman-member/index.png create mode 100644 doc/mailman-member/internals.pl create mode 100644 doc/mailman-member/intlabels.pl create mode 100644 doc/mailman-member/labels.pl create mode 100644 doc/mailman-member/mailman-member.css create mode 100644 doc/mailman-member/mailman-member.html create mode 100644 doc/mailman-member/modules.png create mode 100644 doc/mailman-member/next.png create mode 100644 doc/mailman-member/node10.html create mode 100644 doc/mailman-member/node11.html create mode 100644 doc/mailman-member/node12.html create mode 100644 doc/mailman-member/node13.html create mode 100644 doc/mailman-member/node14.html create mode 100644 doc/mailman-member/node15.html create mode 100644 doc/mailman-member/node16.html create mode 100644 doc/mailman-member/node17.html create mode 100644 doc/mailman-member/node18.html create mode 100644 doc/mailman-member/node19.html create mode 100644 doc/mailman-member/node20.html create mode 100644 doc/mailman-member/node21.html create mode 100644 doc/mailman-member/node22.html create mode 100644 doc/mailman-member/node23.html create mode 100644 doc/mailman-member/node24.html create mode 100644 doc/mailman-member/node25.html create mode 100644 doc/mailman-member/node26.html create mode 100644 doc/mailman-member/node27.html create mode 100644 doc/mailman-member/node28.html create mode 100644 doc/mailman-member/node29.html create mode 100644 doc/mailman-member/node3.html create mode 100644 doc/mailman-member/node30.html create mode 100644 doc/mailman-member/node31.html create mode 100644 doc/mailman-member/node32.html create mode 100644 doc/mailman-member/node33.html create mode 100644 doc/mailman-member/node34.html create mode 100644 doc/mailman-member/node35.html create mode 100644 doc/mailman-member/node36.html create mode 100644 doc/mailman-member/node37.html create mode 100644 doc/mailman-member/node38.html create mode 100644 doc/mailman-member/node39.html create mode 100644 doc/mailman-member/node4.html create mode 100644 doc/mailman-member/node40.html create mode 100644 doc/mailman-member/node41.html create mode 100644 doc/mailman-member/node42.html create mode 100644 doc/mailman-member/node5.html create mode 100644 doc/mailman-member/node6.html create mode 100644 doc/mailman-member/node7.html create mode 100644 doc/mailman-member/node8.html create mode 100644 doc/mailman-member/node9.html create mode 100644 doc/mailman-member/previous.png create mode 100644 doc/mailman-member/pyfav.png create mode 100644 doc/mailman-member/up.png (limited to 'doc/mailman-member') diff --git a/doc/mailman-member/about.html b/doc/mailman-member/about.html new file mode 100644 index 00000000..6af1744d --- /dev/null +++ b/doc/mailman-member/about.html @@ -0,0 +1,112 @@ + + + + + + + + + + + + +About this document ... + + +
+
+ + + + + + + + + +
Up one LevelNext PageGNU Mailman - List Member ManualContents
+
+Previous: + +Up: +GNU Mailman - List +
+
+
+ + +

+About this document ... +

+ GNU Mailman - List Member Manual, +December 5, 2007, Release 2.1 +

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. +

+ +
+
+

+ + + + + + + + + +
Up one LevelNext PageGNU Mailman - List Member ManualContents
+
+Previous: + +Up: +GNU Mailman - List +
+
+
+Release 2.1, documentation updated on December 5, 2007. +
+ + + + diff --git a/doc/mailman-member/blank.png b/doc/mailman-member/blank.png new file mode 100644 index 00000000..2af5639b Binary files /dev/null and b/doc/mailman-member/blank.png differ diff --git a/doc/mailman-member/contents.html b/doc/mailman-member/contents.html new file mode 100644 index 00000000..30a3d2f1 --- /dev/null +++ b/doc/mailman-member/contents.html @@ -0,0 +1,159 @@ + + + + + + + + + + + + + + +Contents + + +
+
+ + + + + + + + + +
Up one LevelGNU Mailman - List Member Manual
+
+Previous: + +Up: +GNU Mailman - List +Next: + +
+
+
+ +

+Contents +

+ + + + +

+ +

+
+

+ + + + + + + + + +
Up one LevelGNU Mailman - List Member Manual
+
+Previous: + +Up: +GNU Mailman - List +Next: + +
+
+
+Release 2.1, documentation updated on December 5, 2007. +
+ + + + diff --git a/doc/mailman-member/contents.png b/doc/mailman-member/contents.png new file mode 100644 index 00000000..3429be0c Binary files /dev/null and b/doc/mailman-member/contents.png differ diff --git a/doc/mailman-member/front.html b/doc/mailman-member/front.html new file mode 100644 index 00000000..54f6c1b2 --- /dev/null +++ b/doc/mailman-member/front.html @@ -0,0 +1,110 @@ + + + + + + + + + + + + + + +Front Matter + + +
+
+ + + + + + + + + +
Up one LevelGNU Mailman - List Member ManualContents
+
+Previous: + +Up: +GNU Mailman - List +Next: + +
+
+
+ + +

+
+Front Matter +

+ +

+ +

Abstract:

+
+ +This document describes the list member interface for GNU +Mailman 2.1. It contains instructions for subscribing, unsubscribing, +viewing the archives, editing user options, getting password reminders, +and other subscriber-level tasks. It also answers some common questions +of interest to Mailman list members. +
+

+ +

+ +

+
+

+ + + + + + + + + +
Up one LevelGNU Mailman - List Member ManualContents
+
+Previous: + +Up: +GNU Mailman - List +Next: + +
+
+
+Release 2.1, documentation updated on December 5, 2007. +
+ + + + diff --git a/doc/mailman-member/images.pl b/doc/mailman-member/images.pl new file mode 100644 index 00000000..97299b8a --- /dev/null +++ b/doc/mailman-member/images.pl @@ -0,0 +1,18 @@ +# LaTeX2HTML 2002-2-1 (1.71) +# Associate images original text with physical files. + + +$key = q/>;MSF=1.6;AAT/; +$cached_env_img{$key} = q|$>$|; + +$key = q/<;MSF=1.6;AAT/; +$cached_env_img{$key} = q|$<$|; + +1; + diff --git a/doc/mailman-member/img1.png b/doc/mailman-member/img1.png new file mode 100644 index 00000000..c70e3e94 Binary files /dev/null and b/doc/mailman-member/img1.png differ diff --git a/doc/mailman-member/img2.png b/doc/mailman-member/img2.png new file mode 100644 index 00000000..102217c2 Binary files /dev/null and b/doc/mailman-member/img2.png differ diff --git a/doc/mailman-member/index.dat b/doc/mailman-member/index.dat new file mode 100644 index 00000000..e69de29b diff --git a/doc/mailman-member/index.html b/doc/mailman-member/index.html new file mode 100644 index 00000000..0e84ca05 --- /dev/null +++ b/doc/mailman-member/index.html @@ -0,0 +1,171 @@ + + + + + + + + + + + +GNU Mailman - List Member Manual + + +
+
+ + + + + + + + + +
Previous PageUp one LevelGNU Mailman - List Member ManualContents
+
+Next: + +
+
+
+ + +
+
+

GNU Mailman - List Member Manual

+

Terri Oda

+

terri(at)zone12.com

+

Release 2.1
+December 5, 2007

+

+
+
+ +

+ +


+
+ + + + + +
+ +
+
+

+ + + + + + + + + +
Previous PageUp one LevelGNU Mailman - List Member ManualContents
+
+Next: + +
+
+
+Release 2.1, documentation updated on December 5, 2007. +
+ + + + diff --git a/doc/mailman-member/index.png b/doc/mailman-member/index.png new file mode 100644 index 00000000..cd918afe Binary files /dev/null and b/doc/mailman-member/index.png differ diff --git a/doc/mailman-member/internals.pl b/doc/mailman-member/internals.pl new file mode 100644 index 00000000..984f6770 --- /dev/null +++ b/doc/mailman-member/internals.pl @@ -0,0 +1,114 @@ +# LaTeX2HTML 2002-2-1 (1.71) +# Associate internals original text with physical files. + + +$key = q/sec:changeaddress/; +$ref_files{$key} = "$dir".q|node22.html|; +$noresave{$key} = "$nosave"; + +$key = q/front/; +$ref_files{$key} = "$dir".q|node1.html|; +$noresave{$key} = "$nosave"; + +$key = q/sec:getack/; +$ref_files{$key} = "$dir".q|node24.html|; +$noresave{$key} = "$nosave"; + +$key = q/sec:changename/; +$ref_files{$key} = "$dir".q|node35.html|; +$noresave{$key} = "$nosave"; + +$key = q/contents/; +$ref_files{$key} = "$dir".q|node2.html|; +$noresave{$key} = "$nosave"; + +$key = q/sec:notopic/; +$ref_files{$key} = "$dir".q|node32.html|; +$noresave{$key} = "$nosave"; + +$key = q/about/; +$ref_files{$key} = "$dir".q|node43.html|; +$noresave{$key} = "$nosave"; + +$key = q/sec:nomail/; +$ref_files{$key} = "$dir".q|node20.html|; +$noresave{$key} = "$nosave"; + +$key = q/sec:nodupes/; +$ref_files{$key} = "$dir".q|node21.html|; +$noresave{$key} = "$nosave"; + +$key = q/sec:sometopic/; +$ref_files{$key} = "$dir".q|node31.html|; +$noresave{$key} = "$nosave"; + +$key = q/sec:MIME/; +$ref_files{$key} = "$dir".q|node28.html|; +$noresave{$key} = "$nosave"; + +$key = q/sec:nolist/; +$ref_files{$key} = "$dir".q|node37.html|; +$noresave{$key} = "$nosave"; + +$key = q/sec:global/; +$ref_files{$key} = "$dir".q|node34.html|; +$noresave{$key} = "$nosave"; + +$key = q/sec:email/; +$ref_files{$key} = "$dir".q|node10.html|; +$noresave{$key} = "$nosave"; + +$key = q/sec:password/; +$ref_files{$key} = "$dir".q|node15.html|; +$noresave{$key} = "$nosave"; + +$key = q/sec:digest/; +$ref_files{$key} = "$dir".q|node27.html|; +$noresave{$key} = "$nosave"; + +$key = q/sec:getown/; +$ref_files{$key} = "$dir".q|node23.html|; +$noresave{$key} = "$nosave"; + +$key = q/sec:getpassword/; +$ref_files{$key} = "$dir".q|node16.html|; +$noresave{$key} = "$nosave"; + +$key = q/sec:subscribe/; +$ref_files{$key} = "$dir".q|node13.html|; +$noresave{$key} = "$nosave"; + +$key = q/sec:human/; +$ref_files{$key} = "$dir".q|node11.html|; +$noresave{$key} = "$nosave"; + +$key = q/sec:posttopic/; +$ref_files{$key} = "$dir".q|node30.html|; +$noresave{$key} = "$nosave"; + +$key = q/sec:antispam/; +$ref_files{$key} = "$dir".q|node40.html|; +$noresave{$key} = "$nosave"; + +$key = q/a:commands/; +$ref_files{$key} = "$dir".q|node41.html|; +$noresave{$key} = "$nosave"; + +$key = q/a:options/; +$ref_files{$key} = "$dir".q|node42.html|; +$noresave{$key} = "$nosave"; + +$key = q/sec:web/; +$ref_files{$key} = "$dir".q|node9.html|; +$noresave{$key} = "$nosave"; + +$key = q/sec:unsubscribe/; +$ref_files{$key} = "$dir".q|node14.html|; +$noresave{$key} = "$nosave"; + +$key = q/sec:topics/; +$ref_files{$key} = "$dir".q|node29.html|; +$noresave{$key} = "$nosave"; + +1; + diff --git a/doc/mailman-member/intlabels.pl b/doc/mailman-member/intlabels.pl new file mode 100644 index 00000000..44814752 --- /dev/null +++ b/doc/mailman-member/intlabels.pl @@ -0,0 +1,3 @@ +%internal_labels = (); +1; # hack in case there are no entries + diff --git a/doc/mailman-member/labels.pl b/doc/mailman-member/labels.pl new file mode 100644 index 00000000..e275d403 --- /dev/null +++ b/doc/mailman-member/labels.pl @@ -0,0 +1,217 @@ +# LaTeX2HTML 2002-2-1 (1.71) +# Associate labels original text with physical files. + + +$key = q/sec:changeaddress/; +$external_labels{$key} = "$URL/" . q|node22.html|; +$noresave{$key} = "$nosave"; + +$key = q/front/; +$external_labels{$key} = "$URL/" . q|node1.html|; +$noresave{$key} = "$nosave"; + +$key = q/sec:getack/; +$external_labels{$key} = "$URL/" . q|node24.html|; +$noresave{$key} = "$nosave"; + +$key = q/sec:changename/; +$external_labels{$key} = "$URL/" . q|node35.html|; +$noresave{$key} = "$nosave"; + +$key = q/contents/; +$external_labels{$key} = "$URL/" . q|node2.html|; +$noresave{$key} = "$nosave"; + +$key = q/sec:notopic/; +$external_labels{$key} = "$URL/" . q|node32.html|; +$noresave{$key} = "$nosave"; + +$key = q/about/; +$external_labels{$key} = "$URL/" . q|node43.html|; +$noresave{$key} = "$nosave"; + +$key = q/sec:nomail/; +$external_labels{$key} = "$URL/" . q|node20.html|; +$noresave{$key} = "$nosave"; + +$key = q/sec:sometopic/; +$external_labels{$key} = "$URL/" . q|node31.html|; +$noresave{$key} = "$nosave"; + +$key = q/sec:MIME/; +$external_labels{$key} = "$URL/" . q|node28.html|; +$noresave{$key} = "$nosave"; + +$key = q/sec:nodupes/; +$external_labels{$key} = "$URL/" . q|node21.html|; +$noresave{$key} = "$nosave"; + +$key = q/sec:nolist/; +$external_labels{$key} = "$URL/" . q|node37.html|; +$noresave{$key} = "$nosave"; + +$key = q/sec:global/; +$external_labels{$key} = "$URL/" . q|node34.html|; +$noresave{$key} = "$nosave"; + +$key = q/sec:email/; +$external_labels{$key} = "$URL/" . q|node10.html|; +$noresave{$key} = "$nosave"; + +$key = q/sec:password/; +$external_labels{$key} = "$URL/" . q|node15.html|; +$noresave{$key} = "$nosave"; + +$key = q/sec:digest/; +$external_labels{$key} = "$URL/" . q|node27.html|; +$noresave{$key} = "$nosave"; + +$key = q/sec:getown/; +$external_labels{$key} = "$URL/" . q|node23.html|; +$noresave{$key} = "$nosave"; + +$key = q/sec:getpassword/; +$external_labels{$key} = "$URL/" . q|node16.html|; +$noresave{$key} = "$nosave"; + +$key = q/sec:subscribe/; +$external_labels{$key} = "$URL/" . q|node13.html|; +$noresave{$key} = "$nosave"; + +$key = q/sec:human/; +$external_labels{$key} = "$URL/" . q|node11.html|; +$noresave{$key} = "$nosave"; + +$key = q/sec:posttopic/; +$external_labels{$key} = "$URL/" . q|node30.html|; +$noresave{$key} = "$nosave"; + +$key = q/sec:antispam/; +$external_labels{$key} = "$URL/" . q|node40.html|; +$noresave{$key} = "$nosave"; + +$key = q/a:commands/; +$external_labels{$key} = "$URL/" . q|node41.html|; +$noresave{$key} = "$nosave"; + +$key = q/a:options/; +$external_labels{$key} = "$URL/" . q|node42.html|; +$noresave{$key} = "$nosave"; + +$key = q/sec:web/; +$external_labels{$key} = "$URL/" . q|node9.html|; +$noresave{$key} = "$nosave"; + +$key = q/sec:unsubscribe/; +$external_labels{$key} = "$URL/" . q|node14.html|; +$noresave{$key} = "$nosave"; + +$key = q/sec:topics/; +$external_labels{$key} = "$URL/" . q|node29.html|; +$noresave{$key} = "$nosave"; + +1; + + +# LaTeX2HTML 2002-2-1 (1.71) +# labels from external_latex_labels array. + + +$key = q/sec:changeaddress/; +$external_latex_labels{$key} = q|7.3|; +$noresave{$key} = "$nosave"; + +$key = q/sec:getack/; +$external_latex_labels{$key} = q|7.5|; +$noresave{$key} = "$nosave"; + +$key = q/sec:changename/; +$external_latex_labels{$key} = q|10.2|; +$noresave{$key} = "$nosave"; + +$key = q/sec:notopic/; +$external_latex_labels{$key} = q|9.3|; +$noresave{$key} = "$nosave"; + +$key = q/sec:nomail/; +$external_latex_labels{$key} = q|7.1|; +$noresave{$key} = "$nosave"; + +$key = q/sec:sometopic/; +$external_latex_labels{$key} = q|9.2|; +$noresave{$key} = "$nosave"; + +$key = q/sec:MIME/; +$external_latex_labels{$key} = q|8.2|; +$noresave{$key} = "$nosave"; + +$key = q/sec:nodupes/; +$external_latex_labels{$key} = q|7.2|; +$noresave{$key} = "$nosave"; + +$key = q/sec:nolist/; +$external_latex_labels{$key} = q|10.4|; +$noresave{$key} = "$nosave"; + +$key = q/sec:global/; +$external_latex_labels{$key} = q|10.1|; +$noresave{$key} = "$nosave"; + +$key = q/sec:email/; +$external_latex_labels{$key} = q|3.2|; +$noresave{$key} = "$nosave"; + +$key = q/sec:password/; +$external_latex_labels{$key} = q|6|; +$noresave{$key} = "$nosave"; + +$key = q/sec:digest/; +$external_latex_labels{$key} = q|8.1|; +$noresave{$key} = "$nosave"; + +$key = q/sec:getown/; +$external_latex_labels{$key} = q|7.4|; +$noresave{$key} = "$nosave"; + +$key = q/sec:getpassword/; +$external_latex_labels{$key} = q|6.1|; +$noresave{$key} = "$nosave"; + +$key = q/sec:subscribe/; +$external_latex_labels{$key} = q|5.1|; +$noresave{$key} = "$nosave"; + +$key = q/sec:posttopic/; +$external_latex_labels{$key} = q|9.1|; +$noresave{$key} = "$nosave"; + +$key = q/sec:human/; +$external_latex_labels{$key} = q|4|; +$noresave{$key} = "$nosave"; + +$key = q/sec:antispam/; +$external_latex_labels{$key} = q|11.2|; +$noresave{$key} = "$nosave"; + +$key = q/a:commands/; +$external_latex_labels{$key} = q|A|; +$noresave{$key} = "$nosave"; + +$key = q/a:options/; +$external_latex_labels{$key} = q|B|; +$noresave{$key} = "$nosave"; + +$key = q/sec:topics/; +$external_latex_labels{$key} = q|9|; +$noresave{$key} = "$nosave"; + +$key = q/sec:web/; +$external_latex_labels{$key} = q|3.1|; +$noresave{$key} = "$nosave"; + +$key = q/sec:unsubscribe/; +$external_latex_labels{$key} = q|5.2|; +$noresave{$key} = "$nosave"; + +1; + diff --git a/doc/mailman-member/mailman-member.css b/doc/mailman-member/mailman-member.css new file mode 100644 index 00000000..06a613c2 --- /dev/null +++ b/doc/mailman-member/mailman-member.css @@ -0,0 +1,243 @@ +/* + * The first part of this is the standard CSS generated by LaTeX2HTML, + * with the "empty" declarations removed. + */ + +/* Century Schoolbook font is very similar to Computer Modern Math: cmmi */ +.math { font-family: "Century Schoolbook", serif; } +.math i { font-family: "Century Schoolbook", serif; + font-weight: bold } +.boldmath { font-family: "Century Schoolbook", serif; + font-weight: bold } + +/* + * Implement both fixed-size and relative sizes. + * + * I think these can be safely removed, as it doesn't appear that + * LaTeX2HTML ever generates these, even though these are carried + * over from the LaTeX2HTML stylesheet. + */ +small.xtiny { font-size : xx-small; } +small.tiny { font-size : x-small; } +small.scriptsize { font-size : smaller; } +small.footnotesize { font-size : small; } +big.xlarge { font-size : large; } +big.xxlarge { font-size : x-large; } +big.huge { font-size : larger; } +big.xhuge { font-size : xx-large; } + +/* + * Document-specific styles come next; + * these are added for the Python documentation. + * + * Note that the size specifications for the H* elements are because + * Netscape on Solaris otherwise doesn't get it right; they all end up + * the normal text size. + */ + +body { color: #000000; + background-color: #ffffff; } + +a:link:active { color: #ff0000; } +a:link:hover { background-color: #bbeeff; } +a:visited:hover { background-color: #bbeeff; } +a:visited { color: #551a8b; } +a:link { color: #0000bb; } + +h1, h2, h3, h4, h5, h6 { font-family: avantgarde, sans-serif; + font-weight: bold; } +h1 { font-size: 180%; } +h2 { font-size: 150%; } +h3, h4 { font-size: 120%; } + +/* These are section titles used in navigation links, so make sure we + * match the section header font here, even it not the weight. + */ +.sectref { font-family: avantgarde, sans-serif; } +/* And the label before the titles in navigation: */ +.navlabel { font-size: 85%; } + + +/* LaTeX2HTML insists on inserting
elements into headers which + * are marked with \label. This little bit of CSS magic ensures that + * these elements don't cause spurious whitespace to be added. + */ +h1>br, h2>br, h3>br, +h4>br, h5>br, h6>br { display: none; } + +code, tt { font-family: "lucida typewriter", lucidatypewriter, + monospace; } +var { font-family: times, serif; + font-style: italic; + font-weight: normal; } + +.Unix { font-variant: small-caps; } + +.typelabel { font-family: lucida, sans-serif; } + +.navigation td { background-color: #99ccff; + font-weight: bold; + font-family: avantgarde, sans-serif; + font-size: 110%; } + +div.warning { background-color: #fffaf0; + border: thin solid black; + padding: 1em; + margin-left: 2em; + margin-right: 2em; } + +div.warning .label { font-family: sans-serif; + font-size: 110%; + margin-right: 0.5em; } + +div.note { background-color: #fffaf0; + border: thin solid black; + padding: 1em; + margin-left: 2em; + margin-right: 2em; } + +div.note .label { margin-right: 0.5em; + font-family: sans-serif; } + +address { font-size: 80%; } +.release-info { font-style: italic; + font-size: 80%; } + +.titlegraphic { vertical-align: top; } + +.verbatim pre { color: #00008b; + font-family: "lucida typewriter", lucidatypewriter, + monospace; + font-size: 90%; } +.verbatim { margin-left: 2em; } +.verbatim .footer { padding: 0.05in; + font-size: 85%; + background-color: #99ccff; + margin-right: 0.5in; } + +.grammar { background-color: #99ccff; + margin-right: 0.5in; + padding: 0.05in; } +.grammar-footer { padding: 0.05in; + font-size: 85%; } +.grammartoken { font-family: "lucida typewriter", lucidatypewriter, + monospace; } + +.productions { background-color: #bbeeff; } +.productions a:active { color: #ff0000; } +.productions a:link:hover { background-color: #99ccff; } +.productions a:visited:hover { background-color: #99ccff; } +.productions a:visited { color: #551a8b; } +.productions a:link { color: #0000bb; } +.productions table { vertical-align: baseline; + empty-cells: show; } +.productions > table td, +.productions > table th { padding: 2px; } +.productions > table td:first-child, +.productions > table td:last-child { + font-family: "lucida typewriter", + lucidatypewriter, + monospace; + } +/* same as the second selector above, but expressed differently for Opera */ +.productions > table td:first-child + td + td { + font-family: "lucida typewriter", + lucidatypewriter, + monospace; + vertical-align: baseline; + } +.productions > table td:first-child + td { + padding-left: 1em; + padding-right: 1em; + } +.productions > table tr { vertical-align: baseline; } + +.email { font-family: avantgarde, sans-serif; } +.mailheader { font-family: avantgarde, sans-serif; } +.mimetype { font-family: avantgarde, sans-serif; } +.newsgroup { font-family: avantgarde, sans-serif; } +.url { font-family: avantgarde, sans-serif; } +.file { font-family: avantgarde, sans-serif; } +.guilabel { font-family: avantgarde, sans-serif; } + +.realtable { border-collapse: collapse; + border-color: black; + border-style: solid; + border-width: 0px 0px 2px 0px; + empty-cells: show; + margin-left: auto; + margin-right: auto; + padding-left: 0.4em; + padding-right: 0.4em; + } +.realtable tbody { vertical-align: baseline; } +.realtable tfoot { display: table-footer-group; } +.realtable thead { background-color: #99ccff; + border-width: 0px 0px 2px 1px; + display: table-header-group; + font-family: avantgarde, sans-serif; + font-weight: bold; + vertical-align: baseline; + } +.realtable thead :first-child { + border-width: 0px 0px 2px 0px; + } +.realtable thead th { border-width: 0px 0px 2px 1px } +.realtable td, +.realtable th { border-color: black; + border-style: solid; + border-width: 0px 0px 1px 1px; + padding-left: 0.4em; + padding-right: 0.4em; + } +.realtable td:first-child, +.realtable th:first-child { + border-left-width: 0px; + vertical-align: baseline; + } +.center { text-align: center; } +.left { text-align: left; } +.right { text-align: right; } + +.refcount-info { font-style: italic; } +.refcount-info .value { font-weight: bold; + color: #006600; } + +/* + * Some decoration for the "See also:" blocks, in part inspired by some of + * the styling on Lars Marius Garshol's XSA pages. + * (The blue in the navigation bars is #99CCFF.) + */ +.seealso { background-color: #fffaf0; + border: thin solid black; + padding: 0pt 1em 4pt 1em; } + +.seealso > .heading { font-size: 110%; + font-weight: bold; } + +/* + * Class 'availability' is used for module availability statements at + * the top of modules. + */ +.availability .platform { font-weight: bold; } + + +/* + * Additional styles for the distutils package. + */ +.du-command { font-family: monospace; } +.du-option { font-family: avantgarde, sans-serif; } +.du-filevar { font-family: avantgarde, sans-serif; + font-style: italic; } +.du-xxx:before { content: "** "; + font-weight: bold; } +.du-xxx:after { content: " **"; + font-weight: bold; } + + +/* + * Some specialization for printed output. + */ +@media print { + .online-navigation { display: none; } + } diff --git a/doc/mailman-member/mailman-member.html b/doc/mailman-member/mailman-member.html new file mode 100644 index 00000000..0e84ca05 --- /dev/null +++ b/doc/mailman-member/mailman-member.html @@ -0,0 +1,171 @@ + + + + + + + + + + + +GNU Mailman - List Member Manual + + +
+
+ + + + + + + + + +
Previous PageUp one LevelGNU Mailman - List Member ManualContents
+
+Next: + +
+
+
+ + +
+
+

GNU Mailman - List Member Manual

+

Terri Oda

+

terri(at)zone12.com

+

Release 2.1
+December 5, 2007

+

+
+
+ +

+ +


+
+ + + + + +
+ +
+
+

+ + + + + + + + + +
Previous PageUp one LevelGNU Mailman - List Member ManualContents
+
+Next: + +
+
+
+Release 2.1, documentation updated on December 5, 2007. +
+ + + + diff --git a/doc/mailman-member/modules.png b/doc/mailman-member/modules.png new file mode 100644 index 00000000..8fa8b755 Binary files /dev/null and b/doc/mailman-member/modules.png differ diff --git a/doc/mailman-member/next.png b/doc/mailman-member/next.png new file mode 100644 index 00000000..cfe5e51c Binary files /dev/null and b/doc/mailman-member/next.png differ diff --git a/doc/mailman-member/node10.html b/doc/mailman-member/node10.html new file mode 100644 index 00000000..ac06c6d9 --- /dev/null +++ b/doc/mailman-member/node10.html @@ -0,0 +1,183 @@ + + + + + + + + + + + + + +3.2 The email interface + + +
+
+ + + + + + + + + +
Up one LevelGNU Mailman - List Member ManualContents
+
+Previous: + +Up: +3 Mailman's interfaces +Next: + +
+
+
+ + +

+
+3.2 The email interface +

+Every mailing list has a set of email addresses to which messages can be +sent. There's always one address for posting messages to the list, one +address to which bounces are sent, and addresses for processing email +commands. For a fictional mailing list called +mylist@example.com, you'd find these addresses: + +

+ +

+ +

+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 +address (for example, ). + +

+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.) + +

+ +

+
+

+ + + + + + + + + +
Up one LevelGNU Mailman - List Member ManualContents
+
+Previous: + +Up: +3 Mailman's interfaces +Next: + +
+
+
+Release 2.1, documentation updated on December 5, 2007. +
+ + + + diff --git a/doc/mailman-member/node11.html b/doc/mailman-member/node11.html new file mode 100644 index 00000000..e7efe3c5 --- /dev/null +++ b/doc/mailman-member/node11.html @@ -0,0 +1,114 @@ + + + + + + + + + + + + + + +4 I need to talk to a human! + + +
+
+ + + + + + + + + +
Up one LevelGNU Mailman - List Member ManualContents
+
+Previous: + +Up: +Contents +Next: + +
+
+
+ + +

+
+4 I need to talk to a human! +

+ +

+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 , 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 + +

+ +

+
+

+ + + + + + + + + +
Up one LevelGNU Mailman - List Member ManualContents
+
+Previous: + +Up: +Contents +Next: + +
+
+
+Release 2.1, documentation updated on December 5, 2007. +
+ + + + diff --git a/doc/mailman-member/node12.html b/doc/mailman-member/node12.html new file mode 100644 index 00000000..e998fe55 --- /dev/null +++ b/doc/mailman-member/node12.html @@ -0,0 +1,111 @@ + + + + + + + + + + + + + + +5 Subscribing and unsubscribing + + +
+
+ + + + + + + + + +
Up one LevelGNU Mailman - List Member ManualContents
+
+Previous: + +Up: +Contents +Next: + +
+
+
+ + +

+5 Subscribing and unsubscribing +

+Since subscribing (joining) and unsubscribing (leaving) lists are often the +only things a list member needs to know, these can both be done without +requiring you to know a password. + +

+ +


+
+ +Subsections + + + +
+ +
+
+

+ + + + + + + + + +
Up one LevelGNU Mailman - List Member ManualContents
+
+Previous: + +Up: +Contents +Next: + +
+
+
+Release 2.1, documentation updated on December 5, 2007. +
+ + + + diff --git a/doc/mailman-member/node13.html b/doc/mailman-member/node13.html new file mode 100644 index 00000000..50b4cab5 --- /dev/null +++ b/doc/mailman-member/node13.html @@ -0,0 +1,182 @@ + + + + + + + + + + + + + + +5.1 How do I join a list? (subscribe) + + +
+
+ + + + + + + + + +
Up one LevelGNU Mailman - List Member ManualContents
+
+Previous: + +Up: +5 Subscribing and unsubscribing +Next: + +
+
+
+ + +

+
+5.1 How do I join a list? (subscribe) +

+ +

+There are two common ways you can subscribe to a Mailman mailing list. + +

+Using the web interface: + +

    +
  1. Go to the list information page for the list you want to join. + (This will probably be something like + http://WEBSERVER/mailman/listinfo/LISTNAME) +
    2. +
  2. Look for the section marked "Subscribing to LISTNAME" and fill in the + boxes. You can fill in the following: + +
      +
    • You must enter your email address. +
      • +
    • You may choose to supply your real name. +
      • +
    • You may choose a password. If you do not choose one, Mailman will + generate one for you. + +

      +Warning: +Do NOT use a valuable password, since this + password may be mailed to you in plain text. +

      • +
    • If the list supports more than one language, you may be able to + choose your preferred language. Note: +This setting does not affect + posts to the list, only pre-prepared Mailman texts such as your member + options page. + +
      • +
    +
    3. +
  3. Press the subscribe button. A new page should appear telling you + that your request has been sent. +
    4. +
+ +

+Using the email interface: + +

    +
  1. Open a mail program which sends mail from the address you want to + subscribe. +
    2. +
  2. Send a mail to the list subscription address, which will be in the + form . The subject and body + of the message will be ignored, so it doesn't matter what you put there. +
    3. +
+ +

+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. + +

+ +

+
+

+ + + + + + + + + +
Up one LevelGNU Mailman - List Member ManualContents
+
+Previous: + +Up: +5 Subscribing and unsubscribing +Next: + +
+
+
+Release 2.1, documentation updated on December 5, 2007. +
+ + + + diff --git a/doc/mailman-member/node14.html b/doc/mailman-member/node14.html new file mode 100644 index 00000000..1ba2e183 --- /dev/null +++ b/doc/mailman-member/node14.html @@ -0,0 +1,175 @@ + + + + + + + + + + + + + +5.2 How do I leave a list? (unsubscribe) + + +
+
+ + + + + + + + + +
Up one LevelGNU Mailman - List Member ManualContents
+
+Previous: + +Up: +5 Subscribing and unsubscribing +Next: + +
+
+
+ + +

+
+5.2 How do I leave a list? (unsubscribe) +

+ +

+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: + +

    +
  1. Go to the list information page for the list you want to leave. + (This will probably be something like + http://WEBSERVER/mailman/listinfo/LISTNAME) +
    2. +
  2. Look for the section marked "LISTNAME subscribers" (usually found + near the bottom of the page). +
    3. +
  3. There should be a button marked "Unsubscribe or Edit Options." + Enter your email address in the box beside this button and press the + button. +
    4. +
  4. You should be brought to a new page which has an "Unsubscribe" + button. Press it to unsubscribe and follow the instructions given. +
    5. +
+ +

+Using the email interface: + +

    +
  1. Open a mail program which sends mail from the address you want to + unsubscribe. +
    2. +
  2. Send a mail to the list unsubscribe address, which will be of the form + . + The subject and body + of this message will be ignored, so it doesn't matter what you put there. +
    3. +
+ +

+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. + +

+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. + +

+ +

+
+

+ + + + + + + + + +
Up one LevelGNU Mailman - List Member ManualContents
+
+Previous: + +Up: +5 Subscribing and unsubscribing +Next: + +
+
+
+Release 2.1, documentation updated on December 5, 2007. +
+ + + + diff --git a/doc/mailman-member/node15.html b/doc/mailman-member/node15.html new file mode 100644 index 00000000..01abef0d --- /dev/null +++ b/doc/mailman-member/node15.html @@ -0,0 +1,122 @@ + + + + + + + + + + + + + + +6 Passwords + + +
+
+ + + + + + + + + +
Up one LevelGNU Mailman - List Member ManualContents
+
+Previous: + +Up: +Contents +Next: + +
+
+
+ + +

+
+6 Passwords +

+Your password was either set by you or generated by Mailman when you +subscribed. +You probably got a copy of it in a +welcome message sent when you joined the list, and you may also receive a +reminder of it every month. It is used to verify your identity to Mailman +so that only the holder of the password (you!) and the administrators +can view and change your settings. + +

+Warning: +Do NOT use a valuable password for Mailman, since it can be +sent in plain text to you. + +

+ +


+
+ +Subsections + + + +
+ +
+
+

+ + + + + + + + + +
Up one LevelGNU Mailman - List Member ManualContents
+
+Previous: + +Up: +Contents +Next: + +
+
+
+Release 2.1, documentation updated on December 5, 2007. +
+ + + + diff --git a/doc/mailman-member/node16.html b/doc/mailman-member/node16.html new file mode 100644 index 00000000..ad52a62d --- /dev/null +++ b/doc/mailman-member/node16.html @@ -0,0 +1,155 @@ + + + + + + + + + + + + + + +6.1 How do I get my password? + + +
+
+ + + + + + + + + +
Up one LevelGNU Mailman - List Member ManualContents
+
+Previous: + +Up: +6 Passwords +Next: + +
+
+
+ + +

+
+6.1 How do I get my password? +

+If you've forgotten your password and haven't saved the welcome message or +any reminder messages, you can always get a reminder through the web interface: + +

+ +

    +
  1. Go to the list information page for the list from which you wish to + get your password + (This will probably be something like + http://WEBSERVER/mailman/listinfo/LISTNAME) +
    2. +
  2. Look for the section marked "LISTNAME subscribers" + (this section is usually found near the bottom of the page). +
    3. +
  3. There should be a button marked "Unsubscribe or Edit Options." + Enter your email address in the box beside this button and press the + button. +
    4. +
  4. You should be brought to a new page which has an "Password + Reminder" section. Press the "Remind" button to have your password + emailed to you. +
    5. +
+ +

+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, + +

    +
  1. Send a mail to with the command + password + +

    +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$>$. +

    2. +
+ +

+ +

+
+

+ + + + + + + + + +
Up one LevelGNU Mailman - List Member ManualContents
+
+Previous: + +Up: +6 Passwords +Next: + +
+
+
+Release 2.1, documentation updated on December 5, 2007. +
+ + + + diff --git a/doc/mailman-member/node17.html b/doc/mailman-member/node17.html new file mode 100644 index 00000000..6af4f59c --- /dev/null +++ b/doc/mailman-member/node17.html @@ -0,0 +1,169 @@ + + + + + + + + + + + + + + +6.2 How do I change my password? + + +
+
+ + + + + + + + + +
Up one LevelGNU Mailman - List Member ManualContents
+
+Previous: + +Up: +6 Passwords +Next: + +
+
+
+ + +

+6.2 How do I change my password? +

+ Warning: +Do NOT use a valuable password, since this + password may be mailed to you in plain text. + +

+From the web interface: + +

    +
  1. Log in to your member options page. (See Section 3.1 for + instructions on how to do this.) + +

    +

    2. +
  2. Look for the password changing boxes on the right-hand side of the + page and enter your new password in the appropriate boxes, then press the + button marked "Change My Password." +
    3. +
+ +

+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: + +

    +
  1. Send a mail to with the command + password $<$OLDPASSWORD$>$ $<$NEWPASSWORD$>$. + +

    +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 wanted to change her mylist + password from zirc to miko, but she was sending mail from + her work address , she could send a message + to with the subject set to + password zirc miko address=kathy@here.com. +

    2. +
+ +

+ +

+
+

+ + + + + + + + + +
Up one LevelGNU Mailman - List Member ManualContents
+
+Previous: + +Up: +6 Passwords +Next: + +
+
+
+Release 2.1, documentation updated on December 5, 2007. +
+ + + + diff --git a/doc/mailman-member/node18.html b/doc/mailman-member/node18.html new file mode 100644 index 00000000..3574e495 --- /dev/null +++ b/doc/mailman-member/node18.html @@ -0,0 +1,134 @@ + + + + + + + + + + + + + +6.3 How do I turn password reminders on or off? (reminders option) + + +
+
+ + + + + + + + + +
Up one LevelGNU Mailman - List Member ManualContents
+
+Previous: + +Up: +6 Passwords +Next: + +
+
+
+ + +

+6.3 How do I turn password reminders on or off? (reminders option) +

+If you don't wish to the reminder email including your password every month, +you can disable it from the member options page. (You can always get the +password mailed out when you actually want it. See +Section 6.1 for instructions.) + +

+Using the web interface: + +

    +
  1. Log in to your member options page. (See Section 3.1 for + instructions on how to do this.) +
    2. +
  2. Look for the section marked "Get password reminder email for this + list?" and change the value accordingly. +
    3. +
+ +

+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: + +

    +
  1. Send a mail to with the command + set reminders on or set reminders off. + +

    +Commands can appear + in either the body or the subject of the message. (See + Section 3.2 for more information about sending mail + commands.) +

    2. +
  2. Set it to "on" to receive reminders, and "off" to stop receiving + reminders. +
    3. +
+ +

+ +

+
+

+ + + + + + + + + +
Up one LevelGNU Mailman - List Member ManualContents
+
+Previous: + +Up: +6 Passwords +Next: + +
+
+
+Release 2.1, documentation updated on December 5, 2007. +
+ + + + diff --git a/doc/mailman-member/node19.html b/doc/mailman-member/node19.html new file mode 100644 index 00000000..79064340 --- /dev/null +++ b/doc/mailman-member/node19.html @@ -0,0 +1,114 @@ + + + + + + + + + + + + + + +7 Changing mail delivery + + +
+
+ + + + + + + + + +
Up one LevelGNU Mailman - List Member ManualContents
+
+Previous: + +Up: +Contents +Next: + +
+
+
+ + +

+7 Changing mail delivery +

+ +


+
+ +Subsections + + + +
+ +
+
+

+ + + + + + + + + +
Up one LevelGNU Mailman - List Member ManualContents
+
+Previous: + +Up: +Contents +Next: + +
+
+
+Release 2.1, documentation updated on December 5, 2007. +
+ + + + diff --git a/doc/mailman-member/node20.html b/doc/mailman-member/node20.html new file mode 100644 index 00000000..d4e2629f --- /dev/null +++ b/doc/mailman-member/node20.html @@ -0,0 +1,150 @@ + + + + + + + + + + + + + + +7.1 How do I turn mail delivery on or off? (delivery option) + + +
+
+ + + + + + + + + +
Up one LevelGNU Mailman - List Member ManualContents
+
+Previous: + +Up: +7 Changing mail delivery +Next: + +
+
+
+ + +

+
+7.1 How do I turn mail delivery on or off? + (delivery option) +

+ +

+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: + +

    +
  1. Log in to your options page. (See Section 3.1 for instructions.) +
    2. +
  2. Go down to the section marked "Mail delivery" and select "Disabled" + to stop receiving mail, and "Enabled" to start receiving mail. +
    3. +
+ +

+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: + +

    +
  1. Send a mail to with the command + set delivery off or set delivery on. + +

    +Commands can appear + in either the body or the subject of the message. (See + Section 3.2 for more information about sending mail + commands.) +

    2. +
  2. Set it to "off" to stop receiving posts, and "on" to start + receiving them again. +
    3. +
+ +

+ +

+
+

+ + + + + + + + + +
Up one LevelGNU Mailman - List Member ManualContents
+
+Previous: + +Up: +7 Changing mail delivery +Next: + +
+
+
+Release 2.1, documentation updated on December 5, 2007. +
+ + + + diff --git a/doc/mailman-member/node21.html b/doc/mailman-member/node21.html new file mode 100644 index 00000000..99055444 --- /dev/null +++ b/doc/mailman-member/node21.html @@ -0,0 +1,143 @@ + + + + + + + + + + + + + + +7.2 How can I avoid getting duplicate messages? (duplicates option) + + + +
+
+ + + + + + + + + +
Up one LevelGNU Mailman - List Member ManualContents
+
+Previous: + +Up: +7 Changing mail delivery +Next: + +
+
+
+ + +

+
+7.2 How can I avoid getting duplicate messages? (duplicates option) + +

+ +

+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. + +

+To turn this on or off using the web interface: + +

    +
  1. Log in to your member options page. (See Section 3.1 + for more details on how to do this.) +
    2. +
  2. Scroll down to the bottom of the page to the section marked + "Avoid duplicate copies of messages?" and change the value accordingly. +
    3. +
+ +

+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: + +

    +
  1. Send a mail to with the command + set duplicates on or set duplicates off. + +

    +Commands can appear + in either the body or the subject of the message. (See + Section 3.2 for more information about sending mail + commands.) +

    2. +
  2. Set it to "on" to receive list copies of messages already sent + to you, set it to "off" to avoid receiving these duplicates. +
    3. +
+ +

+ +

+
+

+ + + + + + + + + +
Up one LevelGNU Mailman - List Member ManualContents
+
+Previous: + +Up: +7 Changing mail delivery +Next: + +
+
+
+Release 2.1, documentation updated on December 5, 2007. +
+ + + + diff --git a/doc/mailman-member/node22.html b/doc/mailman-member/node22.html new file mode 100644 index 00000000..a60ec418 --- /dev/null +++ b/doc/mailman-member/node22.html @@ -0,0 +1,119 @@ + + + + + + + + + + + + + + +7.3 How do I change my subscription address? + + +
+
+ + + + + + + + + +
Up one LevelGNU Mailman - List Member ManualContents
+
+Previous: + +Up: +7 Changing mail delivery +Next: + +
+
+
+ + +

+
+7.3 How do I change my subscription address? +

+To change your subscription address, + +
    +
  1. Log in to your member options page. (See Section 3.1 + for more details on how to do this.) +
    2. +
  2. In the section marked "Changing your LISTNAME membership information," + enter your new address. +
    3. +
  3. If you wish to change your address for all subscriptions using the + old address, select the "Change globally" box. If you have subscriptions + under another address or for lists on a different domain, these will have + to be done separately. See Section 10.1 for more + information about changing settings globally. +
    4. +
+ +

+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.) + +

+ +

+
+

+ + + + + + + + + +
Up one LevelGNU Mailman - List Member ManualContents
+
+Previous: + +Up: +7 Changing mail delivery +Next: + +
+
+
+Release 2.1, documentation updated on December 5, 2007. +
+ + + + diff --git a/doc/mailman-member/node23.html b/doc/mailman-member/node23.html new file mode 100644 index 00000000..86eef9fd --- /dev/null +++ b/doc/mailman-member/node23.html @@ -0,0 +1,141 @@ + + + + + + + + + + + + + + +7.4 How do I stop or start getting copies of my own posts? (myposts option) + + +
+
+ + + + + + + + + +
Up one LevelGNU Mailman - List Member ManualContents
+
+Previous: + +Up: +7 Changing mail delivery +Next: + +
+
+
+ + +

+
+7.4 How do I stop or start getting copies of my own posts? (myposts + option) +

+By default in Mailman, you get a copy of every post you send to the list. +Some people like this since it lets them know when the post has gone through +and means they have a copy of their own words with the rest of a discussion, +but others don't want to bother downloading copies of their own posts. + +

+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: + +

    +
  1. Log in to your member options page. (See Section 3.1 + for more details on how to do this.) +
    2. +
  2. Look for the section marked "Receive your own posts to the list?" + Set it to "Yes" to receive copies of your own posts, and "No" to avoid + receiving them. +
    3. +
+ +

+To set this using the email interface: + +

    +
  1. Send a mail to with the command + set myposts on or set myposts off. + +

    +Commands can appear + in either the body or the subject of the message. (See + Section 3.2 for more information about sending mail + commands.) +

    2. +
  2. Set it to "on" to receive copies of your own posts, and "off" + to avoid receiving them. +
    3. +
+ +

+ +

+
+

+ + + + + + + + + +
Up one LevelGNU Mailman - List Member ManualContents
+
+Previous: + +Up: +7 Changing mail delivery +Next: + +
+
+
+Release 2.1, documentation updated on December 5, 2007. +
+ + + + diff --git a/doc/mailman-member/node24.html b/doc/mailman-member/node24.html new file mode 100644 index 00000000..e3a03ee0 --- /dev/null +++ b/doc/mailman-member/node24.html @@ -0,0 +1,147 @@ + + + + + + + + + + + + + + +7.5 How can I get Mailman to tell me when my post has been received +by the list? (ack option) + + +
+
+ + + + + + + + + +
Up one LevelGNU Mailman - List Member ManualContents
+
+Previous: + +Up: +7 Changing mail delivery +Next: + +
+
+
+ + +

+
+7.5 How can I get Mailman to tell me when my post has been received +by the list? (ack option) +

+ +

+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: + +

    +
  1. Log in to your member options page. (See Section 3.1 + for more details on how to do this.) +
    2. +
  2. Look for the section marked "Receive acknowledgement mail when you + send mail to the list?" + Set it to "Yes" to receive a mail letting you know your post has been + received, and "No" to avoid receiving such an acknowledgement. +
    3. +
+ +

+To set this using the email interface: + +

    +
  1. Send a mail to with the command + set ack on or set ack off. + +

    +Commands can appear + in either the body or the subject of the message. (See + Section 3.2 for more information about sending mail + commands.) +

    2. +
  2. Set it to "on" if you wish to receive mail letting you know your + post has been received, and "off" to avoid receiving such an + acknowledgement. +
    3. +
+ +

+ +

+
+

+ + + + + + + + + +
Up one LevelGNU Mailman - List Member ManualContents
+
+Previous: + +Up: +7 Changing mail delivery +Next: + +
+
+
+Release 2.1, documentation updated on December 5, 2007. +
+ + + + diff --git a/doc/mailman-member/node25.html b/doc/mailman-member/node25.html new file mode 100644 index 00000000..7c5e1241 --- /dev/null +++ b/doc/mailman-member/node25.html @@ -0,0 +1,189 @@ + + + + + + + + + + + + + +7.6 I don't seem to be getting mail from the lists. What should I do? + + +
+
+ + + + + + + + + +
Up one LevelGNU Mailman - List Member ManualContents
+
+Previous: + +Up: +7 Changing mail delivery +Next: + +
+
+
+ + +

+7.6 I don't seem to be getting mail from the lists. What should + I do? +

+There are a few common reasons for this: + + + +

+ +

+
+

+ + + + + + + + + +
Up one LevelGNU Mailman - List Member ManualContents
+
+Previous: + +Up: +7 Changing mail delivery +Next: + +
+
+
+Release 2.1, documentation updated on December 5, 2007. +
+ + + + diff --git a/doc/mailman-member/node26.html b/doc/mailman-member/node26.html new file mode 100644 index 00000000..6fec44f6 --- /dev/null +++ b/doc/mailman-member/node26.html @@ -0,0 +1,108 @@ + + + + + + + + + + + + + + +8 Digests + + +
+
+ + + + + + + + + +
Up one LevelGNU Mailman - List Member ManualContents
+
+Previous: + +Up: +Contents +Next: + +
+
+
+ + +

+8 Digests +

+ +


+
+ +Subsections + + + +
+ +
+
+

+ + + + + + + + + +
Up one LevelGNU Mailman - List Member ManualContents
+
+Previous: + +Up: +Contents +Next: + +
+
+
+Release 2.1, documentation updated on December 5, 2007. +
+ + + + diff --git a/doc/mailman-member/node27.html b/doc/mailman-member/node27.html new file mode 100644 index 00000000..6abb8708 --- /dev/null +++ b/doc/mailman-member/node27.html @@ -0,0 +1,144 @@ + + + + + + + + + + + + + + +8.1 How can I start or stop getting the list posts grouped into one big email? (digest option) + + +
+
+ + + + + + + + + +
Up one LevelGNU Mailman - List Member ManualContents
+
+Previous: + +Up: +8 Digests +Next: + +
+
+
+ + +

+
+8.1 How can I start or stop getting the list posts grouped into one +big email? (digest option) +

+ +

+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, + +

    +
  1. Log in to your member options page. (See Section 3.1 + for more details on how to do this.) +
    2. +
  2. Look for the section marked "Set Digest Mode." + +

    +Set it to "On" to + receive messages bundled together in digests. Set it to "Off" to + receive posts separately. +

    3. +
+ +

+To turn digest mode on or off using the email interface, + +

    +
  1. Send a mail to with the command + set digest plain or set digest mime or set digest off. + +

    +Commands can appear + in either the body or the subject of the message. (See + Section 3.2 for more information about sending mail + commands.) +

    2. +
  2. Set it to "off" if you wish to receive individual posts separately, + and to "plain" or "mime" to receive posts grouped into one large mail. + See Section 8.2 for more information on plain versus MIME + digests. +
    3. +
+ +

+ +

+
+

+ + + + + + + + + +
Up one LevelGNU Mailman - List Member ManualContents
+
+Previous: + +Up: +8 Digests +Next: + +
+
+
+Release 2.1, documentation updated on December 5, 2007. +
+ + + + diff --git a/doc/mailman-member/node28.html b/doc/mailman-member/node28.html new file mode 100644 index 00000000..4c58c01d --- /dev/null +++ b/doc/mailman-member/node28.html @@ -0,0 +1,161 @@ + + + + + + + + + + + + + +8.2 What are MIME and Plain Text Digests? How do I change which one +I get? (digest option) + + +
+
+ + + + + + + + + +
Up one LevelGNU Mailman - List Member ManualContents
+
+Previous: + +Up: +8 Digests +Next: + +
+
+
+ + +

+
+8.2 What are MIME and Plain Text Digests? How do I change which one +I get? (digest option) +

+ +

+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: + +

    +
  1. Log in to your member options page. (See Section 3.1 + for more details on how to do this.) +
    2. +
  2. Look for the section marked "Get MIME or Plain Text Digests?." + +

    +Set it to "MIME" to receive digests in MIME format, or "Plain text" to + receive digests in plain text format. +

    3. +
+ +

+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, + +

    +
  1. Send a mail to with the command + set digest plain or set digest mime. + +

    +Commands can appear + in either the body or the subject of the message. (See + Section 3.2 for more information about sending mail + commands.) +

    2. +
  2. Set it to "plain" to get posts bundled into a plain text digest, + or "mime" to get posts bundled together into a MIME digest. +
    3. +
+ +

+ +

+
+

+ + + + + + + + + +
Up one LevelGNU Mailman - List Member ManualContents
+
+Previous: + +Up: +8 Digests +Next: + +
+
+
+Release 2.1, documentation updated on December 5, 2007. +
+ + + + diff --git a/doc/mailman-member/node29.html b/doc/mailman-member/node29.html new file mode 100644 index 00000000..ffbca818 --- /dev/null +++ b/doc/mailman-member/node29.html @@ -0,0 +1,132 @@ + + + + + + + + + + + + + + +9 Mailing list topics + + +
+
+ + + + + + + + + +
Up one LevelGNU Mailman - List Member ManualContents
+
+Previous: + +Up: +Contents +Next: + +
+
+
+ + +

+
+9 Mailing list topics +

+ +

+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 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 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. + +

+ +


+
+ +Subsections + + + +
+ +
+
+

+ + + + + + + + + +
Up one LevelGNU Mailman - List Member ManualContents
+
+Previous: + +Up: +Contents +Next: + +
+
+
+Release 2.1, documentation updated on December 5, 2007. +
+ + + + diff --git a/doc/mailman-member/node3.html b/doc/mailman-member/node3.html new file mode 100644 index 00000000..e36bf987 --- /dev/null +++ b/doc/mailman-member/node3.html @@ -0,0 +1,139 @@ + + + + + + + + + + + + + + +1 Introduction + + +
+
+ + + + + + + + + +
Up one LevelGNU Mailman - List Member ManualContents
+
+Previous: + +Up: +Contents +Next: + +
+
+
+ + +

+1 Introduction +

+ +

+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. + +

+ +


+
+ +Subsections + + + +
+ +
+
+

+ + + + + + + + + +
Up one LevelGNU Mailman - List Member ManualContents
+
+Previous: + +Up: +Contents +Next: + +
+
+
+Release 2.1, documentation updated on December 5, 2007. +
+ + + + diff --git a/doc/mailman-member/node30.html b/doc/mailman-member/node30.html new file mode 100644 index 00000000..0e1607f5 --- /dev/null +++ b/doc/mailman-member/node30.html @@ -0,0 +1,185 @@ + + + + + + + + + + + + + + +9.1 How do I make sure that my post has the right topic? + + +
+
+ + + + + + + + + +
Up one LevelGNU Mailman - List Member ManualContents
+
+Previous: + +Up: +9 Mailing list topics +Next: + +
+
+
+ + +

+
+9.1 How do I make sure that my post has the right + topic? +

+ +

+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. +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. + +

+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 expressionMatching lines
zuffKeywords: zuff
zuffKeywords: ZUFF
zuffKeywords: Zuff
zuffKeywords: amaryllis, zuff, applesauce
zuffSubject: [zuff] Do you have the right stuff for zuff?
zuffSubject: Do you have the right stuff for zuff?
zuffSubject: 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: + +

+ +

+ +

+
+

+ + + + + + + + + +
Up one LevelGNU Mailman - List Member ManualContents
+
+Previous: + +Up: +9 Mailing list topics +Next: + +
+
+
+Release 2.1, documentation updated on December 5, 2007. +
+ + + + diff --git a/doc/mailman-member/node31.html b/doc/mailman-member/node31.html new file mode 100644 index 00000000..80ac9948 --- /dev/null +++ b/doc/mailman-member/node31.html @@ -0,0 +1,127 @@ + + + + + + + + + + + + + + +9.2 How do I subscribe to all or only some topics on a list? + + +
+
+ + + + + + + + + +
Up one LevelGNU Mailman - List Member ManualContents
+
+Previous: + +Up: +9 Mailing list topics +Next: + +
+
+
+ + +

+
+9.2 How do I subscribe to all or only some topics on a + list? +

+ +

+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. + +

+ +

    +
  1. Log in to your member options page. (See Section 3.1 + for more details on how to do this.) +
    2. +
  2. Look for the section marked "Which topic categories would you like + to subscribe to?" + +

    +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. +

    3. +
+ +

+You probably also want to look at Section 9.3 which discusses +changing your settings for messages where no topic is set. + +

+ +

+
+

+ + + + + + + + + +
Up one LevelGNU Mailman - List Member ManualContents
+
+Previous: + +Up: +9 Mailing list topics +Next: + +
+
+
+Release 2.1, documentation updated on December 5, 2007. +
+ + + + diff --git a/doc/mailman-member/node32.html b/doc/mailman-member/node32.html new file mode 100644 index 00000000..d7e1c619 --- /dev/null +++ b/doc/mailman-member/node32.html @@ -0,0 +1,124 @@ + + + + + + + + + + + + + +9.3 How do I get or avoid getting messages with no topic set? + + + +
+
+ + + + + + + + + +
Up one LevelGNU Mailman - List Member ManualContents
+
+Previous: + +Up: +9 Mailing list topics +Next: + +
+
+
+ + +

+
+9.3 How do I get or avoid getting messages with no topic set? + +

+If you wish to get all messages sent to the list, make sure you are +not subscribed to any specific topic. (See Section 9.2.) + +

+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, + +

    +
  1. Log in to your member options page. (See Section 3.1 + for more details on how to do this.) +
    2. +
  2. Look for the section marked "Do you want to receive message that do + not match any topic filter?" + +

    +If you wish to receive messages with no topic set, select "Yes." If you + do not wish to receive such messages, choose "No." +

    3. +
+ +

+This setting has no effect if you are not subscribed to any topics. + +

+ +

+
+

+ + + + + + + + + +
Up one LevelGNU Mailman - List Member ManualContents
+
+Previous: + +Up: +9 Mailing list topics +Next: + +
+
+
+Release 2.1, documentation updated on December 5, 2007. +
+ + + + diff --git a/doc/mailman-member/node33.html b/doc/mailman-member/node33.html new file mode 100644 index 00000000..653867b8 --- /dev/null +++ b/doc/mailman-member/node33.html @@ -0,0 +1,111 @@ + + + + + + + + + + + + + + +10 Setting other options + + +
+
+ + + + + + + + + +
Up one LevelGNU Mailman - List Member ManualContents
+
+Previous: + +Up: +Contents +Next: + +
+
+
+ + +

+10 Setting other options +

+ +

+ +


+
+ +Subsections + + + +
+ +
+
+

+ + + + + + + + + +
Up one LevelGNU Mailman - List Member ManualContents
+
+Previous: + +Up: +Contents +Next: + +
+
+
+Release 2.1, documentation updated on December 5, 2007. +
+ + + + diff --git a/doc/mailman-member/node34.html b/doc/mailman-member/node34.html new file mode 100644 index 00000000..91b16d87 --- /dev/null +++ b/doc/mailman-member/node34.html @@ -0,0 +1,108 @@ + + + + + + + + + + + + + + +10.1 Change Globally? Set Globally? What does that mean? + + +
+
+ + + + + + + + + +
Up one LevelGNU Mailman - List Member ManualContents
+
+Previous: + +Up: +10 Setting other options +Next: + +
+
+
+ + +

+
+10.1 Change Globally? Set Globally? What does that mean? + +

+ +

+For some of the options given in your member options page, there is a +tick-box 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 list +subscriptions with the same address to lists 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. + +

+ +

+
+

+ + + + + + + + + +
Up one LevelGNU Mailman - List Member ManualContents
+
+Previous: + +Up: +10 Setting other options +Next: + +
+
+
+Release 2.1, documentation updated on December 5, 2007. +
+ + + + diff --git a/doc/mailman-member/node35.html b/doc/mailman-member/node35.html new file mode 100644 index 00000000..c278f976 --- /dev/null +++ b/doc/mailman-member/node35.html @@ -0,0 +1,119 @@ + + + + + + + + + + + + + + +10.2 How do I change my name as Mailman knows it? + + +
+
+ + + + + + + + + +
Up one LevelGNU Mailman - List Member ManualContents
+
+Previous: + +Up: +10 Setting other options +Next: + +
+
+
+ + +

+
+10.2 How do I change my name as Mailman knows it? + +

+ +

+To change your subscription name, + +

    +
  1. Log in to your member options page. (See Section 3.1 + for more details on how to do this.) +
    2. +
  2. In the section marked "Changing your LISTNAME membership information," + enter your new name in the appropriate box. +
    3. +
+ +

+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. + +

+ +

+
+

+ + + + + + + + + +
Up one LevelGNU Mailman - List Member ManualContents
+
+Previous: + +Up: +10 Setting other options +Next: + +
+
+
+Release 2.1, documentation updated on December 5, 2007. +
+ + + + diff --git a/doc/mailman-member/node36.html b/doc/mailman-member/node36.html new file mode 100644 index 00000000..33f2dbf9 --- /dev/null +++ b/doc/mailman-member/node36.html @@ -0,0 +1,143 @@ + + + + + + + + + + + + + + +10.3 How do I set my preferred language? + + +
+
+ + + + + + + + + +
Up one LevelGNU Mailman - List Member ManualContents
+
+Previous: + +Up: +10 Setting other options +Next: + +
+
+
+ + +

+10.3 How do I set my preferred language? +

+ +

+Mailman is available with many different languages. +(For a complete listing see http://mailman.sourceforge.net/i18n.html.) This means that, 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, + +

    +
  1. Log in to your member options page. (See Section 3.1 for + instructions on how to do this.) +
    2. +
  2. Go to the section marked "What language do you prefer?" and choose + the appropriate language from the drop-down list. If there is no + drop-down list of languages, the list you are on probably only supports + one language. +
    3. +
+ +

+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. +(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.") + +

+ +

+
+

+ + + + + + + + + +
Up one LevelGNU Mailman - List Member ManualContents
+
+Previous: + +Up: +10 Setting other options +Next: + +
+
+
+Release 2.1, documentation updated on December 5, 2007. +
+ + + + diff --git a/doc/mailman-member/node37.html b/doc/mailman-member/node37.html new file mode 100644 index 00000000..0f4a0c61 --- /dev/null +++ b/doc/mailman-member/node37.html @@ -0,0 +1,141 @@ + + + + + + + + + + + + + +10.4 How do I avoid having my name appear on the subscribers list? (the hide option) + + +
+
+ + + + + + + + + +
Up one LevelGNU Mailman - List Member ManualContents
+
+Previous: + +Up: +10 Setting other options +Next: + +
+
+
+ + +

+
+10.4 How do I avoid having my name appear on the subscribers list? + (the hide option) +

+ +

+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 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: + +

    +
  1. Log in to your member options page. (See Section 3.1 for + instructions on how to do this.) +
    2. +
  2. Go to the section marked "Conceal yourself from subscriber list?" and + choose "Yes" to hide your name from the list, or "No" to allow your name + to appear on the list. +
    3. +
+ +

+To change this setting using the email interface: + +

    +
  1. Send a mail to with the command + set hide on or set hide off. + +

    +Commands can appear + in either the body or the subject of the message. (See + Section 3.2 for more information about sending mail + commands.) +

    2. +
  2. Set it to "on" to conceal your email address from the membership + list, or "off" to stop concealing your address. +
    3. +
+ +

+ +

+
+

+ + + + + + + + + +
Up one LevelGNU Mailman - List Member ManualContents
+
+Previous: + +Up: +10 Setting other options +Next: + +
+
+
+Release 2.1, documentation updated on December 5, 2007. +
+ + + + diff --git a/doc/mailman-member/node38.html b/doc/mailman-member/node38.html new file mode 100644 index 00000000..1af269e7 --- /dev/null +++ b/doc/mailman-member/node38.html @@ -0,0 +1,109 @@ + + + + + + + + + + + + + + +11 Other common questions + + +
+
+ + + + + + + + + +
Up one LevelGNU Mailman - List Member ManualContents
+
+Previous: + +Up: +Contents +Next: + +
+
+
+ + +

+11 Other common questions +

+ +

+ +


+
+ +Subsections + + + +
+ +
+
+

+ + + + + + + + + +
Up one LevelGNU Mailman - List Member ManualContents
+
+Previous: + +Up: +Contents +Next: + +
+
+
+Release 2.1, documentation updated on December 5, 2007. +
+ + + + diff --git a/doc/mailman-member/node39.html b/doc/mailman-member/node39.html new file mode 100644 index 00000000..dc032e20 --- /dev/null +++ b/doc/mailman-member/node39.html @@ -0,0 +1,112 @@ + + + + + + + + + + + + + + +11.1 How do I view the list archives? + + +
+
+ + + + + + + + + +
Up one LevelGNU Mailman - List Member ManualContents
+
+Previous: + +Up: +11 Other common questions +Next: + +
+
+
+ + +

+11.1 How do I view the list archives? +

+If the list has archives, they can be viewed by going to a web page address. +This address usually linked from the list information page and can be found in +the List-Archive: of every list message unless your list +administrator has disabled these headers. (Many mail programs hide the +List-Archive: mail header, so you may have to tell your +mail program to allow you to view full headers before you will be able to +see it.) + +

+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. + +

+ +

+
+

+ + + + + + + + + +
Up one LevelGNU Mailman - List Member ManualContents
+
+Previous: + +Up: +11 Other common questions +Next: + +
+
+
+Release 2.1, documentation updated on December 5, 2007. +
+ + + + diff --git a/doc/mailman-member/node4.html b/doc/mailman-member/node4.html new file mode 100644 index 00000000..f00b627b --- /dev/null +++ b/doc/mailman-member/node4.html @@ -0,0 +1,113 @@ + + + + + + + + + + + + + + +1.1 Acknowledgements + + +
+
+ + + + + + + + + +
Up one LevelGNU Mailman - List Member ManualContents
+
+Previous: + +Up: +1 Introduction +Next: + +
+
+
+ + +

+1.1 Acknowledgements +

+ +

+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. + +

+Proofreading thanks go to Margaret McCarthy and Jason Walton. + +

+ +

+
+

+ + + + + + + + + +
Up one LevelGNU Mailman - List Member ManualContents
+
+Previous: + +Up: +1 Introduction +Next: + +
+
+
+Release 2.1, documentation updated on December 5, 2007. +
+ + + + diff --git a/doc/mailman-member/node40.html b/doc/mailman-member/node40.html new file mode 100644 index 00000000..4c75cb55 --- /dev/null +++ b/doc/mailman-member/node40.html @@ -0,0 +1,198 @@ + + + + + + + + + + + + + +11.2 What does Mailman do to help protect me from unsolicited bulk email +(spam)? + + +
+
+ + + + + + + + + +
Up one LevelGNU Mailman - List Member ManualContents
+
+Previous: + +Up: +11 Other common questions +Next: + +
+
+
+ + +

+
+11.2 What does Mailman do to help protect me from unsolicited bulk email +(spam)? +

+ +

+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 many ways. List administrators +must walk a fine line between protecting subscribers and making it difficult +for people to get in touch. + +

+ +

+ +

+Of course, many address-obscuring methods can be circumvented by determined +people, so be aware that the protections used may not be enough. + +

+ +

+
+

+ + + + + + + + + +
Up one LevelGNU Mailman - List Member ManualContents
+
+Previous: + +Up: +11 Other common questions +Next: + +
+
+
+Release 2.1, documentation updated on December 5, 2007. +
+ + + + diff --git a/doc/mailman-member/node41.html b/doc/mailman-member/node41.html new file mode 100644 index 00000000..4f1997b1 --- /dev/null +++ b/doc/mailman-member/node41.html @@ -0,0 +1,320 @@ + + + + + + + + + + + + + + +1 Email commands quick reference + + +
+
+ + + + + + + + + +
Up one LevelGNU Mailman - List Member ManualContents
+
+Previous: + +Up: +Contents +Next: + +
+
+
+ + +

+
+1 Email commands quick reference +

+ + + +

+ +

+
+

+ + + + + + + + + +
Up one LevelGNU Mailman - List Member ManualContents
+
+Previous: + +Up: +Contents +Next: + +
+
+
+Release 2.1, documentation updated on December 5, 2007. +
+ + + + diff --git a/doc/mailman-member/node42.html b/doc/mailman-member/node42.html new file mode 100644 index 00000000..d21eed72 --- /dev/null +++ b/doc/mailman-member/node42.html @@ -0,0 +1,266 @@ + + + + + + + + + + + + + +2 Member options quick reference + + +
+
+ + + + + + + + + +
Up one LevelGNU Mailman - List Member ManualContents
+
+Previous: + +Up: +Contents +Next: + +
+
+
+ + +

+
+2 Member options quick reference +

+ +

+ +

+ +

+ +

+
+

+ + + + + + + + + +
Up one LevelGNU Mailman - List Member ManualContents
+
+Previous: + +Up: +Contents +Next: + +
+
+
+Release 2.1, documentation updated on December 5, 2007. +
+ + + + diff --git a/doc/mailman-member/node5.html b/doc/mailman-member/node5.html new file mode 100644 index 00000000..4b4e34ec --- /dev/null +++ b/doc/mailman-member/node5.html @@ -0,0 +1,142 @@ + + + + + + + + + + + + + + +1.2 What is a mailing list? + + +
+
+ + + + + + + + + +
Up one LevelGNU Mailman - List Member ManualContents
+
+Previous: + +Up: +1 Introduction +Next: + +
+
+
+ + +

+1.2 What is a mailing list? +

+ +

+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 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 a mailing list +to let their fan base know about their upcoming concerts. + +

+A discussion list is used to allow 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 mailing list to share tips about model construction and flying. + +

+Some common terms: + +

+
+
+

+ + + + + + + + + +
Up one LevelGNU Mailman - List Member ManualContents
+
+Previous: + +Up: +1 Introduction +Next: + +
+
+
+Release 2.1, documentation updated on December 5, 2007. +
+ + + + diff --git a/doc/mailman-member/node6.html b/doc/mailman-member/node6.html new file mode 100644 index 00000000..b9fa7ad8 --- /dev/null +++ b/doc/mailman-member/node6.html @@ -0,0 +1,108 @@ + + + + + + + + + + + + + +1.3 GNU Mailman + + +
+
+ + + + + + + + + +
Up one LevelGNU Mailman - List Member ManualContents
+
+Previous: + +Up: +1 Introduction +Next: + +
+
+
+ + +

+1.3 GNU Mailman +

+ +

+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. + +

+ +

+
+

+ + + + + + + + + +
Up one LevelGNU Mailman - List Member ManualContents
+
+Previous: + +Up: +1 Introduction +Next: + +
+
+
+Release 2.1, documentation updated on December 5, 2007. +
+ + + + diff --git a/doc/mailman-member/node7.html b/doc/mailman-member/node7.html new file mode 100644 index 00000000..8e722813 --- /dev/null +++ b/doc/mailman-member/node7.html @@ -0,0 +1,141 @@ + + + + + + + + + + + + + + +2 Translating from our examples to real lists + + +
+
+ + + + + + + + + +
Up one LevelGNU Mailman - List Member ManualContents
+
+Previous: + +Up: +Contents +Next: + +
+
+
+ + +

+2 Translating from our examples to real lists +

+ +

+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 + 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: + +

+

+
LISTNAME
+
The name of your list. + +
+
DOMAIN
+
The name of the mail server which handles that list. + +
+
WEBSERVER
+
The name of the web server which handles the list web interface. This may be the same as DOMAIN, and often refers to the same machine, but does not have to be identical. +
+
+ +

+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 + +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. + +

+ +

+
+

+ + + + + + + + + +
Up one LevelGNU Mailman - List Member ManualContents
+
+Previous: + +Up: +Contents +Next: + +
+
+
+Release 2.1, documentation updated on December 5, 2007. +
+ + + + diff --git a/doc/mailman-member/node8.html b/doc/mailman-member/node8.html new file mode 100644 index 00000000..5004cdf6 --- /dev/null +++ b/doc/mailman-member/node8.html @@ -0,0 +1,121 @@ + + + + + + + + + + + + + + +3 Mailman's interfaces + + +
+
+ + + + + + + + + +
Up one LevelGNU Mailman - List Member ManualContents
+
+Previous: + +Up: +Contents +Next: + +
+
+
+ + +

+3 Mailman's interfaces +

+Mailman has two different interfaces for the list subscriber: the web +interface and the email interface. Most discussion list subscribers use +the email interface, since this includes the email address you use to send +mail to all the subscribers of that list. + +

+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. + +

+ +


+
+ +Subsections + + + +
+ +
+
+

+ + + + + + + + + +
Up one LevelGNU Mailman - List Member ManualContents
+
+Previous: + +Up: +Contents +Next: + +
+
+
+Release 2.1, documentation updated on December 5, 2007. +
+ + + + diff --git a/doc/mailman-member/node9.html b/doc/mailman-member/node9.html new file mode 100644 index 00000000..f0a2c836 --- /dev/null +++ b/doc/mailman-member/node9.html @@ -0,0 +1,195 @@ + + + + + + + + + + + + + + +3.1 The web interface + + +
+
+ + + + + + + + + +
Up one LevelGNU Mailman - List Member ManualContents
+
+Previous: + +Up: +3 Mailman's interfaces +Next: + +
+
+
+ + +

+
+3.1 The web interface +

+The web interface of Mailman is its selling point for many administrators, +since it makes it much easier for subscribers and administrators to see +which options are available, and what these options do. + +

+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. + +

+

+
List information (listinfo) page
+
+ +

+

+
Member options page
+
    +
  • Usually found at http://WEBSERVER/mailman/options/LISTNAME/EMAIL (For example, http://lists.example.com/mailman/options/mylist/kathy@here.com) + +

    +

    • +
  • This page can also be accessed by going to the listinfo page + and entering your email address into the box beside the button + marked "Unsubscribe or Edit Options" (this is near the bottom of the + page). + +

    +

    • +
  • The member options page allows you to log in/out and change your + list settings, as well as unsubscribe or get a copy of your password + mailed to you. + +

    +

    • +
  • To log in to your member options page: + If you are not already logged in, there will be a box near the top for + you to enter your password. (If you do not know your password, see + Section 6.1 for more information on getting your + password.) Enter your password in the box and press the button. + +

    +

    • +
  • Once you are logged in, you will be able to view and change + all your list settings. + +

    +

    • +
+ +
+
List Archives
+
+
+
+ +

+ +

+
+

+ + + + + + + + + +
Up one LevelGNU Mailman - List Member ManualContents
+
+Previous: + +Up: +3 Mailman's interfaces +Next: + +
+
+
+Release 2.1, documentation updated on December 5, 2007. +
+ + + + diff --git a/doc/mailman-member/previous.png b/doc/mailman-member/previous.png new file mode 100644 index 00000000..497def42 Binary files /dev/null and b/doc/mailman-member/previous.png differ diff --git a/doc/mailman-member/pyfav.png b/doc/mailman-member/pyfav.png new file mode 100644 index 00000000..d2d8669d Binary files /dev/null and b/doc/mailman-member/pyfav.png differ diff --git a/doc/mailman-member/up.png b/doc/mailman-member/up.png new file mode 100644 index 00000000..a90e0284 Binary files /dev/null and b/doc/mailman-member/up.png differ -- cgit v1.2.3