diff options
Diffstat (limited to '')
57 files changed, 9094 insertions, 1402 deletions
diff --git a/doc/mailman-admin.dvi b/doc/mailman-admin.dvi Binary files differnew file mode 100644 index 00000000..6bf73dae --- /dev/null +++ b/doc/mailman-admin.dvi diff --git a/doc/mailman-admin.pdf b/doc/mailman-admin.pdf Binary files differnew file mode 100644 index 00000000..7ead51d6 --- /dev/null +++ b/doc/mailman-admin.pdf diff --git a/doc/mailman-admin.ps b/doc/mailman-admin.ps new file mode 100644 index 00000000..863ea552 --- /dev/null +++ b/doc/mailman-admin.ps @@ -0,0 +1,1957 @@ +%!PS-Adobe-2.0 +%%Creator: dvips(k) 5.96.1 Copyright 2007 Radical Eye Software +%%Title: mailman-admin.dvi +%%CreationDate: Wed Dec 5 17:20:42 2007 +%%Pages: 17 +%%PageOrder: Ascend +%%BoundingBox: 0 0 595 842 +%%DocumentFonts: Helvetica Helvetica-Oblique Times-Roman Times-Bold +%%+ Times-Italic CMSY10 Courier +%%DocumentPaperSizes: a4 +%%EndComments +%DVIPSWebPage: (www.radicaleye.com) +%DVIPSCommandLine: dvips -N0 -o mailman-admin.ps mailman-admin +%DVIPSParameters: dpi=600 +%DVIPSSource: TeX output 2007.12.05:1720 +%%BeginProcSet: tex.pro 0 0 +%! +/TeXDict 300 dict def TeXDict begin/N{def}def/B{bind def}N/S{exch}N/X{S +N}B/A{dup}B/TR{translate}N/isls false N/vsize 11 72 mul N/hsize 8.5 72 +mul N/landplus90{false}def/@rigin{isls{[0 landplus90{1 -1}{-1 1}ifelse 0 +0 0]concat}if 72 Resolution div 72 VResolution div neg scale isls{ +landplus90{VResolution 72 div vsize mul 0 exch}{Resolution -72 div hsize +mul 0}ifelse TR}if Resolution VResolution vsize -72 div 1 add mul TR[ +matrix currentmatrix{A A round sub abs 0.00001 lt{round}if}forall round +exch round exch]setmatrix}N/@landscape{/isls true N}B/@manualfeed{ +statusdict/manualfeed true put}B/@copies{/#copies X}B/FMat[1 0 0 -1 0 0] +N/FBB[0 0 0 0]N/nn 0 N/IEn 0 N/ctr 0 N/df-tail{/nn 8 dict N nn begin +/FontType 3 N/FontMatrix fntrx N/FontBBox FBB N string/base X array +/BitMaps X/BuildChar{CharBuilder}N/Encoding IEn N end A{/foo setfont}2 +array copy cvx N load 0 nn put/ctr 0 N[}B/sf 0 N/df{/sf 1 N/fntrx FMat N +df-tail}B/dfs{div/sf X/fntrx[sf 0 0 sf neg 0 0]N df-tail}B/E{pop nn A +definefont setfont}B/Cw{Cd A length 5 sub get}B/Ch{Cd A length 4 sub get +}B/Cx{128 Cd A length 3 sub get sub}B/Cy{Cd A length 2 sub get 127 sub} +B/Cdx{Cd A length 1 sub get}B/Ci{Cd A type/stringtype ne{ctr get/ctr ctr +1 add N}if}B/CharBuilder{save 3 1 roll S A/base get 2 index get S +/BitMaps get S get/Cd X pop/ctr 0 N Cdx 0 Cx Cy Ch sub Cx Cw add Cy +setcachedevice Cw Ch true[1 0 0 -1 -.1 Cx sub Cy .1 sub]{Ci}imagemask +restore}B/D{/cc X A type/stringtype ne{]}if nn/base get cc ctr put nn +/BitMaps get S ctr S sf 1 ne{A A length 1 sub A 2 index S get sf div put +}if put/ctr ctr 1 add N}B/I{cc 1 add D}B/bop{userdict/bop-hook known{ +bop-hook}if/SI save N @rigin 0 0 moveto/V matrix currentmatrix A 1 get A +mul exch 0 get A mul add .99 lt{/QV}{/RV}ifelse load def pop pop}N/eop{ +SI restore userdict/eop-hook known{eop-hook}if showpage}N/@start{ +userdict/start-hook known{start-hook}if pop/VResolution X/Resolution X +1000 div/DVImag X/IEn 256 array N 2 string 0 1 255{IEn S A 360 add 36 4 +index cvrs cvn put}for pop 65781.76 div/vsize X 65781.76 div/hsize X}N +/p{show}N/RMat[1 0 0 -1 0 0]N/BDot 260 string N/Rx 0 N/Ry 0 N/V{}B/RV/v{ +/Ry X/Rx X V}B statusdict begin/product where{pop false[(Display)(NeXT) +(LaserWriter 16/600)]{A length product length le{A length product exch 0 +exch getinterval eq{pop true exit}if}{pop}ifelse}forall}{false}ifelse +end{{gsave TR -.1 .1 TR 1 1 scale Rx Ry false RMat{BDot}imagemask +grestore}}{{gsave TR -.1 .1 TR Rx Ry scale 1 1 false RMat{BDot} +imagemask grestore}}ifelse B/QV{gsave newpath transform round exch round +exch itransform moveto Rx 0 rlineto 0 Ry neg rlineto Rx neg 0 rlineto +fill grestore}B/a{moveto}B/delta 0 N/tail{A/delta X 0 rmoveto}B/M{S p +delta add tail}B/b{S p tail}B/c{-4 M}B/d{-3 M}B/e{-2 M}B/f{-1 M}B/g{0 M} +B/h{1 M}B/i{2 M}B/j{3 M}B/k{4 M}B/w{0 rmoveto}B/l{p -4 w}B/m{p -3 w}B/n{ +p -2 w}B/o{p -1 w}B/q{p 1 w}B/r{p 2 w}B/s{p 3 w}B/t{p 4 w}B/x{0 S +rmoveto}B/y{3 2 roll p a}B/bos{/SS save N}B/eos{SS restore}B end + +%%EndProcSet +%%BeginProcSet: 8r.enc 0 0 +% File 8r.enc TeX Base 1 Encoding Revision 2.0 2002-10-30 +% +% @@psencodingfile@{ +% author = "S. Rahtz, P. MacKay, Alan Jeffrey, B. Horn, K. Berry, +% W. Schmidt, P. Lehman", +% version = "2.0", +% date = "27nov06", +% filename = "8r.enc", +% email = "tex-fonts@@tug.org", +% docstring = "This is the encoding vector for Type1 and TrueType +% fonts to be used with TeX. This file is part of the +% PSNFSS bundle, version 9" +% @} +% +% The idea is to have all the characters normally included in Type 1 fonts +% available for typesetting. This is effectively the characters in Adobe +% Standard encoding, ISO Latin 1, Windows ANSI including the euro symbol, +% MacRoman, and some extra characters from Lucida. +% +% Character code assignments were made as follows: +% +% (1) the Windows ANSI characters are almost all in their Windows ANSI +% positions, because some Windows users cannot easily reencode the +% fonts, and it makes no difference on other systems. The only Windows +% ANSI characters not available are those that make no sense for +% typesetting -- rubout (127 decimal), nobreakspace (160), softhyphen +% (173). quotesingle and grave are moved just because it's such an +% irritation not having them in TeX positions. +% +% (2) Remaining characters are assigned arbitrarily to the lower part +% of the range, avoiding 0, 10 and 13 in case we meet dumb software. +% +% (3) Y&Y Lucida Bright includes some extra text characters; in the +% hopes that other PostScript fonts, perhaps created for public +% consumption, will include them, they are included starting at 0x12. +% These are /dotlessj /ff /ffi /ffl. +% +% (4) hyphen appears twice for compatibility with both ASCII and Windows. +% +% (5) /Euro was assigned to 128, as in Windows ANSI +% +% (6) Missing characters from MacRoman encoding incorporated as follows: +% +% PostScript MacRoman TeXBase1 +% -------------- -------------- -------------- +% /notequal 173 0x16 +% /infinity 176 0x17 +% /lessequal 178 0x18 +% /greaterequal 179 0x19 +% /partialdiff 182 0x1A +% /summation 183 0x1B +% /product 184 0x1C +% /pi 185 0x1D +% /integral 186 0x81 +% /Omega 189 0x8D +% /radical 195 0x8E +% /approxequal 197 0x8F +% /Delta 198 0x9D +% /lozenge 215 0x9E +% +/TeXBase1Encoding [ +% 0x00 + /.notdef /dotaccent /fi /fl + /fraction /hungarumlaut /Lslash /lslash + /ogonek /ring /.notdef /breve + /minus /.notdef /Zcaron /zcaron +% 0x10 + /caron /dotlessi /dotlessj /ff + /ffi /ffl /notequal /infinity + /lessequal /greaterequal /partialdiff /summation + /product /pi /grave /quotesingle +% 0x20 + /space /exclam /quotedbl /numbersign + /dollar /percent /ampersand /quoteright + /parenleft /parenright /asterisk /plus + /comma /hyphen /period /slash +% 0x30 + /zero /one /two /three + /four /five /six /seven + /eight /nine /colon /semicolon + /less /equal /greater /question +% 0x40 + /at /A /B /C + /D /E /F /G + /H /I /J /K + /L /M /N /O +% 0x50 + /P /Q /R /S + /T /U /V /W + /X /Y /Z /bracketleft + /backslash /bracketright /asciicircum /underscore +% 0x60 + /quoteleft /a /b /c + /d /e /f /g + /h /i /j /k + /l /m /n /o +% 0x70 + /p /q /r /s + /t /u /v /w + /x /y /z /braceleft + /bar /braceright /asciitilde /.notdef +% 0x80 + /Euro /integral /quotesinglbase /florin + /quotedblbase /ellipsis /dagger /daggerdbl + /circumflex /perthousand /Scaron /guilsinglleft + /OE /Omega /radical /approxequal +% 0x90 + /.notdef /.notdef /.notdef /quotedblleft + /quotedblright /bullet /endash /emdash + /tilde /trademark /scaron /guilsinglright + /oe /Delta /lozenge /Ydieresis +% 0xA0 + /.notdef /exclamdown /cent /sterling + /currency /yen /brokenbar /section + /dieresis /copyright /ordfeminine /guillemotleft + /logicalnot /hyphen /registered /macron +% 0xB0 + /degree /plusminus /twosuperior /threesuperior + /acute /mu /paragraph /periodcentered + /cedilla /onesuperior /ordmasculine /guillemotright + /onequarter /onehalf /threequarters /questiondown +% 0xC0 + /Agrave /Aacute /Acircumflex /Atilde + /Adieresis /Aring /AE /Ccedilla + /Egrave /Eacute /Ecircumflex /Edieresis + /Igrave /Iacute /Icircumflex /Idieresis +% 0xD0 + /Eth /Ntilde /Ograve /Oacute + /Ocircumflex /Otilde /Odieresis /multiply + /Oslash /Ugrave /Uacute /Ucircumflex + /Udieresis /Yacute /Thorn /germandbls +% 0xE0 + /agrave /aacute /acircumflex /atilde + /adieresis /aring /ae /ccedilla + /egrave /eacute /ecircumflex /edieresis + /igrave /iacute /icircumflex /idieresis +% 0xF0 + /eth /ntilde /ograve /oacute + /ocircumflex /otilde /odieresis /divide + /oslash /ugrave /uacute /ucircumflex + /udieresis /yacute /thorn /ydieresis +] def + + +%%EndProcSet +%%BeginProcSet: texps.pro 0 0 +%! +TeXDict begin/rf{findfont dup length 1 add dict begin{1 index/FID ne 2 +index/UniqueID ne and{def}{pop pop}ifelse}forall[1 index 0 6 -1 roll +exec 0 exch 5 -1 roll VResolution Resolution div mul neg 0 0]FontType 0 +ne{/Metrics exch def dict begin Encoding{exch dup type/integertype ne{ +pop pop 1 sub dup 0 le{pop}{[}ifelse}{FontMatrix 0 get div Metrics 0 get +div def}ifelse}forall Metrics/Metrics currentdict end def}{{1 index type +/nametype eq{exit}if exch pop}loop}ifelse[2 index currentdict end +definefont 3 -1 roll makefont/setfont cvx]cvx def}def/ObliqueSlant{dup +sin S cos div neg}B/SlantFont{4 index mul add}def/ExtendFont{3 -1 roll +mul exch}def/ReEncodeFont{CharStrings rcheck{/Encoding false def dup[ +exch{dup CharStrings exch known not{pop/.notdef/Encoding true def}if} +forall Encoding{]exch pop}{cleartomark}ifelse}if/Encoding exch def}def +end + +%%EndProcSet +%%BeginFont: CMSY10 +%!PS-AdobeFont-1.1: CMSY10 1.0 +%%CreationDate: 1991 Aug 15 07:20:57 +% Copyright (C) 1997 American Mathematical Society. All Rights Reserved. +11 dict begin +/FontInfo 7 dict dup begin +/version (1.0) readonly def +/Notice (Copyright (C) 1997 American Mathematical Society. All Rights Reserved) readonly def +/FullName (CMSY10) readonly def +/FamilyName (Computer Modern) readonly def +/Weight (Medium) readonly def +/ItalicAngle -14.035 def +/isFixedPitch false def +end readonly def +/FontName /CMSY10 def +/PaintType 0 def +/FontType 1 def +/FontMatrix [0.001 0 0 0.001 0 0] readonly def +/Encoding 256 array +0 1 255 {1 index exch /.notdef put} for +dup 15 /bullet put +readonly def +/FontBBox{-29 -960 1116 775}readonly def +currentdict end +currentfile eexec +D9D66F633B846A97B686A97E45A3D0AA052F09F9C8ADE9D907C058B87E9B6964 +7D53359E51216774A4EAA1E2B58EC3176BD1184A633B951372B4198D4E8C5EF4 +A213ACB58AA0A658908035BF2ED8531779838A960DFE2B27EA49C37156989C85 +E21B3ABF72E39A89232CD9F4237FC80C9E64E8425AA3BEF7DED60B122A52922A +221A37D9A807DD01161779DDE7D31FF2B87F97C73D63EECDDA4C49501773468A +27D1663E0B62F461F6E40A5D6676D1D12B51E641C1D4E8E2771864FC104F8CBF +5B78EC1D88228725F1C453A678F58A7E1B7BD7CA700717D288EB8DA1F57C4F09 +0ABF1D42C5DDD0C384C7E22F8F8047BE1D4C1CC8E33368FB1AC82B4E96146730 +DE3302B2E6B819CB6AE455B1AF3187FFE8071AA57EF8A6616B9CB7941D44EC7A +71A7BB3DF755178D7D2E4BB69859EFA4BBC30BD6BB1531133FD4D9438FF99F09 +4ECC068A324D75B5F696B8688EEB2F17E5ED34CCD6D047A4E3806D000C199D7C +515DB70A8D4F6146FE068DC1E5DE8BC5703711DA090312BA3FC00A08C453C609 +C627A8BECD6E1FA14A3B02476E90AAD8B4700C400380BC9AFFBF7847EB28661B +9DC3AA0F44C533F2E07DCC4DE19D367BF223E33DC321D0247A0E6EF6ABC8FA52 +15AE044094EF678A8726CD7C011F02BFF8AB6EAEEE391AD837120823BED0B5D8 +F8B15245377871A64F78378BB4330149D6941F7A86FBFFC49B93C94155F5FA7D +F22E7214511C0A92693F4CDBF38411651540572F2DD70D924AE0F18E1CD581F3 +C871399127FF5D07A868885B5FF7CDEB50B8323B2533DEF8DC973B1AE84FA0A2 + +0000000000000000000000000000000000000000000000000000000000000000 +0000000000000000000000000000000000000000000000000000000000000000 +0000000000000000000000000000000000000000000000000000000000000000 +0000000000000000000000000000000000000000000000000000000000000000 +0000000000000000000000000000000000000000000000000000000000000000 +0000000000000000000000000000000000000000000000000000000000000000 +0000000000000000000000000000000000000000000000000000000000000000 +0000000000000000000000000000000000000000000000000000000000000000 +cleartomark +%%EndFont +TeXDict begin 39139632 55387786 1000 600 600 (mailman-admin.dvi) +@start /Fa 130[40 1[40 4[40 40 40 40 40 2[40 40 40 40 +2[40 3[40 40 2[40 1[40 58[40 36[{TeXBase1Encoding ReEncodeFont}17 +66.4176 /Courier rf /Fb 130[45 1[45 1[45 45 2[45 45 45 +45 1[45 45 45 45 45 1[45 45 45 45 45 45 45 45 45 45 1[45 +1[45 45 45 2[45 45 2[45 45 2[45 45 1[45 45 1[45 1[45 +2[45 45 2[45 6[45 4[45 1[45 4[45 45 45 1[45 45 45 45 +1[45 37[{TeXBase1Encoding ReEncodeFont}51 74.7198 /Courier +rf /Fc 134[33 1[48 33 33 18 26 22 33 33 33 33 52 18 33 +1[18 33 33 22 29 33 29 33 29 9[63 1[48 41 37 2[37 2[59 +6[37 4[48 18[17 22 17 4[22 36[37 2[{TeXBase1Encoding ReEncodeFont}36 +66.4176 /Times-Roman rf /Fd 202[25 25 25 25 25 49[{ +TeXBase1Encoding ReEncodeFont}5 49.8132 /Times-Roman +rf /Fe 202[29 29 29 29 29 49[{TeXBase1Encoding ReEncodeFont}5 +58.1154 /Times-Roman rf /Ff 133[50 50 50 50 50 50 50 +50 50 50 50 50 50 50 50 1[50 50 50 50 50 50 50 50 50 +50 1[50 1[50 1[50 10[50 1[50 50 50 11[50 5[50 10[50 50 +50 2[50 50 50 2[50 37[{TeXBase1Encoding ReEncodeFont}41 +83.022 /Courier rf /Fg 134[42 1[60 42 46 23 42 28 1[46 +46 46 69 18 2[18 46 46 1[46 46 42 46 46 11[60 51 55 60 +1[55 65 60 69 46 2[23 1[65 51 1[60 60 55 55 7[46 46 46 +46 46 46 46 46 46 46 23 23 28 42[42 2[{TeXBase1Encoding ReEncodeFont}50 +83.022 /Helvetica rf /Fh 134[37 2[37 42 21 37 25 1[42 +42 42 62 17 37 17 17 42 42 1[42 42 37 42 42 8[50 2[54 +46 50 54 1[50 1[54 62 42 2[21 2[46 1[54 54 50 50 6[21 +10[21 21 25 45[{TeXBase1Encoding ReEncodeFont}40 74.7198 +/Helvetica rf /Fi 240[42 15[{}1 83.022 /CMSY10 rf /Fj +133[32 37 37 55 37 42 23 32 32 42 42 42 42 60 23 37 23 +23 42 42 23 37 42 37 42 42 7[46 1[69 2[46 1[51 1[51 1[55 +69 4[60 60 51 51 60 55 1[51 76 17[21 28 3[28 28 28 35[42 +3[{TeXBase1Encoding ReEncodeFont}47 83.022 /Times-Italic +rf /Fk 134[50 1[72 50 55 28 50 33 1[55 55 55 83 22 2[22 +55 55 1[55 55 50 55 55 9[94 2[61 1[72 1[66 78 72 83 55 +4[78 61 66 72 72 66 66 7[55 55 55 55 55 55 55 55 55 55 +28 28 33 5[22 39[{TeXBase1Encoding ReEncodeFont}49 99.6264 +/Helvetica rf /Fl 133[37 42 42 60 42 46 28 32 37 46 46 +42 46 69 23 1[28 23 46 42 28 37 46 37 46 42 11[60 55 +1[60 1[51 1[60 78 55 2[32 65 65 1[55 60 60 1[60 1[42 +5[42 1[42 42 42 42 42 42 42 46[46 2[{TeXBase1Encoding ReEncodeFont}49 +83.022 /Times-Bold rf /Fm 136[54 37 37 21 29 25 1[37 +37 37 58 21 2[21 37 37 25 33 37 33 37 33 11[54 46 5[54 +66 3[25 1[54 20[37 37 2[19 1[19 4[25 36[42 2[{ +TeXBase1Encoding ReEncodeFont}32 74.7198 /Times-Roman +rf /Fn 139[25 29 33 14[33 42 37 31[54 65[{TeXBase1Encoding ReEncodeFont} +7 74.7198 /Times-Bold rf /Fo 105[42 1[37 37 10[28 13[37 +42 42 60 42 42 23 32 28 42 42 42 42 65 23 42 23 23 42 +42 28 37 42 37 42 37 28 6[60 1[78 60 60 51 46 55 1[46 +60 60 74 51 1[32 28 60 60 46 51 60 55 55 60 76 4[23 23 +42 42 42 42 42 42 42 42 42 42 23 21 28 21 2[28 28 28 +3[42 1[28 29[46 46 2[{TeXBase1Encoding ReEncodeFont}77 +83.022 /Times-Roman rf /Fp 134[60 60 86 1[66 33 60 40 +66 66 66 66 100 27 2[27 66 66 1[66 66 60 66 66 9[113 +1[86 73 1[86 1[80 1[86 100 66 2[33 86 93 1[80 86 86 80 +80 10[66 66 66 66 66 66 2[33 43[60 2[{TeXBase1Encoding ReEncodeFont}45 +119.552 /Helvetica rf /Fq 140[50 6[22 6[55 3[55 14[72 +31[55 55 2[28 46[{TeXBase1Encoding ReEncodeFont}8 99.6264 +/Helvetica-Oblique rf /Fr 138[115 57 103 69 2[115 115 +172 46 2[46 4[115 2[115 11[149 6[149 172 115 4[161 5[138 +19[69 45[{TeXBase1Encoding ReEncodeFont}18 206.559 /Helvetica +rf end +%%EndProlog +%%BeginSetup +%%Feature: *Resolution 600dpi +TeXDict begin +%%PaperSize: A4 + end +%%EndSetup +%%Page: 1 1 +TeXDict begin 1 0 bop 0 83 3901 9 v 2 357 a Fr(GNU)57 +b(Mailman)g(-)g(List)h(Administr)n(ation)f(Man)n(ual)3368 +504 y Fq(Release)30 b(2.1)3007 859 y Fp(Barr)t(y)i(A.)h(W)-5 +b(arsa)n(w)3289 1213 y Fo(December)19 b(5,)h(2007)1811 +1435 y Fn(Abstract)208 1586 y Fm(This)e(document)i(describes)f(the)g +(list)f(administrator')l(s)h(interf)o(ace)g(for)g(GNU)f(Mailman)h(2.1.) +k(It)18 b(contains)i(information)f(a)g(list)f(o)n(wner)208 +1677 y(w)o(ould)k(need)h(to)f(con\002gure)h(their)f(list,)g(either)g +(through)h(the)f(web)h(interf)o(ace)f(or)g(through)i(email.)32 +b(It)21 b(also)i(co)o(v)o(ers)f(the)h(moderator')l(s)208 +1768 y(interf)o(ace)d(for)g(appro)o(ving)i(held)e(messages)i(and)e +(subscription)i(notices,)e(and)h(the)f(web)g(interf)o(ace)h(for)f +(creating)h(ne)n(w)f(mailing)g(lists.)208 1860 y(In)d(general,)h(it)e +(does)i(not)g(co)o(v)o(er)f(the)h(command)g(line)f(interf)o(ace)h(to)f +(Mailman,)h(installing)f(Mailman,)h(or)f(interacting)h(with)f(Mailman) +208 1951 y(from)h(the)h(point)h(of)f(vie)n(w)g(of)g(the)g(user)l(.)k +(That)c(information)g(is)g(co)o(v)o(ered)g(in)g(other)h(manuals.)0 +2231 y Fp(Contents)0 2417 y Fl(1)83 b(Intr)o(oduction)19 +b(to)h(GNU)g(Mailman)2644 b(2)125 2516 y Fo(1.1)85 b(A)21 +b(List')-5 b(s)21 b(Email)g(Addresses)41 b(.)g(.)g(.)h(.)f(.)g(.)g(.)h +(.)f(.)g(.)g(.)h(.)f(.)g(.)h(.)f(.)g(.)g(.)h(.)f(.)g(.)g(.)h(.)f(.)g(.) +g(.)h(.)f(.)g(.)g(.)h(.)f(.)g(.)h(.)f(.)g(.)g(.)h(.)f(.)g(.)g(.)143 +b(2)125 2616 y(1.2)85 b(Administrati)n(v)o(e)19 b(Roles)59 +b(.)42 b(.)f(.)g(.)g(.)h(.)f(.)g(.)g(.)h(.)f(.)g(.)g(.)h(.)f(.)g(.)h(.) +f(.)g(.)g(.)h(.)f(.)g(.)g(.)h(.)f(.)g(.)g(.)h(.)f(.)g(.)g(.)h(.)f(.)g +(.)h(.)f(.)g(.)g(.)h(.)f(.)g(.)g(.)143 b(3)125 2715 y(1.3)85 +b(A)21 b(List')-5 b(s)21 b(W)-7 b(eb)21 b(P)o(ages)52 +b(.)41 b(.)h(.)f(.)g(.)g(.)h(.)f(.)g(.)g(.)h(.)f(.)g(.)g(.)h(.)f(.)g(.) +h(.)f(.)g(.)g(.)h(.)f(.)g(.)g(.)h(.)f(.)g(.)g(.)h(.)f(.)g(.)g(.)h(.)f +(.)g(.)h(.)f(.)g(.)g(.)h(.)f(.)g(.)g(.)143 b(3)125 2815 +y(1.4)85 b(Basic)22 b(Architectural)c(Ov)o(ervie)n(w)23 +b(.)42 b(.)f(.)g(.)g(.)h(.)f(.)g(.)g(.)h(.)f(.)g(.)h(.)f(.)g(.)g(.)h(.) +f(.)g(.)g(.)h(.)f(.)g(.)g(.)h(.)f(.)g(.)g(.)h(.)f(.)g(.)h(.)f(.)g(.)g +(.)h(.)f(.)g(.)g(.)143 b(3)0 2998 y Fl(2)83 b(The)21 +b(List)g(Con\002guration)e(P)o(ages)2693 b(4)125 3097 +y Fo(2.1)85 b(The)20 b(General)g(Options)g(Cate)o(gory)53 +b(.)41 b(.)g(.)g(.)h(.)f(.)g(.)g(.)h(.)f(.)g(.)h(.)f(.)g(.)g(.)h(.)f(.) +g(.)g(.)h(.)f(.)g(.)g(.)h(.)f(.)g(.)g(.)h(.)f(.)g(.)h(.)f(.)g(.)g(.)h +(.)f(.)g(.)g(.)143 b(4)315 3197 y(General)20 b(list)h(personality)50 +b(.)41 b(.)g(.)g(.)h(.)f(.)g(.)g(.)h(.)f(.)g(.)g(.)h(.)f(.)g(.)h(.)f(.) +g(.)g(.)h(.)f(.)g(.)g(.)h(.)f(.)g(.)g(.)h(.)f(.)g(.)g(.)h(.)f(.)g(.)h +(.)f(.)g(.)g(.)h(.)f(.)g(.)g(.)143 b(5)315 3297 y(Reply-T)-7 +b(o)20 b(header)f(munging)78 b(.)41 b(.)h(.)f(.)g(.)g(.)h(.)f(.)g(.)g +(.)h(.)f(.)g(.)h(.)f(.)g(.)g(.)h(.)f(.)g(.)g(.)h(.)f(.)g(.)g(.)h(.)f(.) +g(.)g(.)h(.)f(.)g(.)h(.)f(.)g(.)g(.)h(.)f(.)g(.)g(.)143 +b(6)315 3396 y(Umbrella)20 b(list)h(settings)53 b(.)42 +b(.)f(.)g(.)g(.)h(.)f(.)g(.)g(.)h(.)f(.)g(.)g(.)h(.)f(.)g(.)h(.)f(.)g +(.)g(.)h(.)f(.)g(.)g(.)h(.)f(.)g(.)g(.)h(.)f(.)g(.)g(.)h(.)f(.)g(.)h(.) +f(.)g(.)g(.)h(.)f(.)g(.)g(.)143 b(6)315 3496 y(Noti\002cations)23 +b(.)41 b(.)g(.)h(.)f(.)g(.)h(.)f(.)g(.)g(.)h(.)f(.)g(.)g(.)h(.)f(.)g(.) +g(.)h(.)f(.)g(.)h(.)f(.)g(.)g(.)h(.)f(.)g(.)g(.)h(.)f(.)g(.)g(.)h(.)f +(.)g(.)g(.)h(.)f(.)g(.)h(.)f(.)g(.)g(.)h(.)f(.)g(.)g(.)143 +b(7)315 3596 y(Additional)19 b(settings)72 b(.)41 b(.)h(.)f(.)g(.)g(.)h +(.)f(.)g(.)g(.)h(.)f(.)g(.)g(.)h(.)f(.)g(.)h(.)f(.)g(.)g(.)h(.)f(.)g(.) +g(.)h(.)f(.)g(.)g(.)h(.)f(.)g(.)g(.)h(.)f(.)g(.)h(.)f(.)g(.)g(.)h(.)f +(.)g(.)g(.)143 b(7)125 3695 y(2.2)85 b(The)20 b(P)o(assw)o(ords)h(Cate) +o(gory)64 b(.)41 b(.)g(.)h(.)f(.)g(.)g(.)h(.)f(.)g(.)g(.)h(.)f(.)g(.)h +(.)f(.)g(.)g(.)h(.)f(.)g(.)g(.)h(.)f(.)g(.)g(.)h(.)f(.)g(.)g(.)h(.)f(.) +g(.)h(.)f(.)g(.)g(.)h(.)f(.)g(.)g(.)143 b(8)125 3795 +y(2.3)85 b(The)20 b(Language)e(Options)i(Cate)o(gory)51 +b(.)41 b(.)g(.)h(.)f(.)g(.)g(.)h(.)f(.)g(.)h(.)f(.)g(.)g(.)h(.)f(.)g(.) +g(.)h(.)f(.)g(.)g(.)h(.)f(.)g(.)g(.)h(.)f(.)g(.)h(.)f(.)g(.)g(.)h(.)f +(.)g(.)g(.)143 b(9)125 3894 y(2.4)85 b(The)20 b(Membership)f +(Management)f(Cate)o(gory)37 b(.)k(.)g(.)h(.)f(.)g(.)h(.)f(.)g(.)g(.)h +(.)f(.)g(.)g(.)h(.)f(.)g(.)g(.)h(.)f(.)g(.)g(.)h(.)f(.)g(.)h(.)f(.)g(.) +g(.)h(.)f(.)g(.)g(.)143 b(9)125 3994 y(2.5)85 b(The)20 +b(Non-digest)f(Options)h(Cate)o(gory)71 b(.)41 b(.)h(.)f(.)g(.)g(.)h(.) +f(.)g(.)h(.)f(.)g(.)g(.)h(.)f(.)g(.)g(.)h(.)f(.)g(.)g(.)h(.)f(.)g(.)g +(.)h(.)f(.)g(.)h(.)f(.)g(.)g(.)h(.)f(.)g(.)g(.)143 b(9)125 +4094 y(2.6)85 b(The)20 b(Digest)h(Options)f(Cate)o(gory)36 +b(.)42 b(.)f(.)g(.)g(.)h(.)f(.)g(.)g(.)h(.)f(.)g(.)h(.)f(.)g(.)g(.)h(.) +f(.)g(.)g(.)h(.)f(.)g(.)g(.)h(.)f(.)g(.)g(.)h(.)f(.)g(.)h(.)f(.)g(.)g +(.)h(.)f(.)g(.)g(.)102 b(11)125 4193 y(2.7)85 b(The)20 +b(Pri)n(v)n(ac)o(y)f(Options)h(Cate)o(gory)68 b(.)41 +b(.)g(.)g(.)h(.)f(.)g(.)g(.)h(.)f(.)g(.)h(.)f(.)g(.)g(.)h(.)f(.)g(.)g +(.)h(.)f(.)g(.)g(.)h(.)f(.)g(.)g(.)h(.)f(.)g(.)h(.)f(.)g(.)g(.)h(.)f(.) +g(.)g(.)102 b(12)315 4293 y(Subscription)19 b(rules)37 +b(.)k(.)g(.)h(.)f(.)g(.)g(.)h(.)f(.)g(.)g(.)h(.)f(.)g(.)g(.)h(.)f(.)g +(.)h(.)f(.)g(.)g(.)h(.)f(.)g(.)g(.)h(.)f(.)g(.)g(.)h(.)f(.)g(.)g(.)h(.) +f(.)g(.)h(.)f(.)g(.)g(.)h(.)f(.)g(.)g(.)102 b(13)315 +4393 y(Sender)20 b(\002lters)74 b(.)41 b(.)h(.)f(.)g(.)h(.)f(.)g(.)g(.) +h(.)f(.)g(.)g(.)h(.)f(.)g(.)g(.)h(.)f(.)g(.)h(.)f(.)g(.)g(.)h(.)f(.)g +(.)g(.)h(.)f(.)g(.)g(.)h(.)f(.)g(.)g(.)h(.)f(.)g(.)h(.)f(.)g(.)g(.)h(.) +f(.)g(.)g(.)102 b(13)315 4492 y(Recipient)20 b(Filters)26 +b(.)42 b(.)f(.)g(.)h(.)f(.)g(.)g(.)h(.)f(.)g(.)g(.)h(.)f(.)g(.)g(.)h(.) +f(.)g(.)h(.)f(.)g(.)g(.)h(.)f(.)g(.)g(.)h(.)f(.)g(.)g(.)h(.)f(.)g(.)g +(.)h(.)f(.)g(.)h(.)f(.)g(.)g(.)h(.)f(.)g(.)g(.)102 b(15)315 +4592 y(Spam)20 b(Filters)31 b(.)41 b(.)g(.)h(.)f(.)g(.)h(.)f(.)g(.)g(.) +h(.)f(.)g(.)g(.)h(.)f(.)g(.)g(.)h(.)f(.)g(.)h(.)f(.)g(.)g(.)h(.)f(.)g +(.)g(.)h(.)f(.)g(.)g(.)h(.)f(.)g(.)g(.)h(.)f(.)g(.)h(.)f(.)g(.)g(.)h(.) +f(.)g(.)g(.)102 b(15)125 4691 y(2.8)85 b(The)20 b(Bounce)g(Processing)f +(Cate)o(gory)28 b(.)41 b(.)g(.)h(.)f(.)g(.)g(.)h(.)f(.)g(.)h(.)f(.)g(.) +g(.)h(.)f(.)g(.)g(.)h(.)f(.)g(.)g(.)h(.)f(.)g(.)g(.)h(.)f(.)g(.)h(.)f +(.)g(.)g(.)h(.)f(.)g(.)g(.)102 b(15)125 4791 y(2.9)85 +b(The)20 b(Archi)n(ving)f(Options)g(Cate)o(gory)44 b(.)d(.)g(.)h(.)f(.) +g(.)g(.)h(.)f(.)g(.)h(.)f(.)g(.)g(.)h(.)f(.)g(.)g(.)h(.)f(.)g(.)g(.)h +(.)f(.)g(.)g(.)h(.)f(.)g(.)h(.)f(.)g(.)g(.)h(.)f(.)g(.)g(.)102 +b(16)125 4891 y(2.10)43 b(The)20 b(Mail/Ne)n(ws)h(Gate)n(w)o(ay)f(Cate) +o(gory)44 b(.)d(.)h(.)f(.)g(.)g(.)h(.)f(.)g(.)h(.)f(.)g(.)g(.)h(.)f(.)g +(.)g(.)h(.)f(.)g(.)g(.)h(.)f(.)g(.)g(.)h(.)f(.)g(.)h(.)f(.)g(.)g(.)h(.) +f(.)g(.)g(.)102 b(17)125 4990 y(2.11)43 b(The)20 b(Auto-responder)d +(Cate)o(gory)79 b(.)41 b(.)g(.)g(.)h(.)f(.)g(.)g(.)h(.)f(.)g(.)h(.)f(.) +g(.)g(.)h(.)f(.)g(.)g(.)h(.)f(.)g(.)g(.)h(.)f(.)g(.)g(.)h(.)f(.)g(.)h +(.)f(.)g(.)g(.)h(.)f(.)g(.)g(.)102 b(17)125 5090 y(2.12)43 +b(The)20 b(Content)g(Filtering)g(Cate)o(gory)30 b(.)41 +b(.)g(.)g(.)h(.)f(.)g(.)g(.)h(.)f(.)g(.)h(.)f(.)g(.)g(.)h(.)f(.)g(.)g +(.)h(.)f(.)g(.)g(.)h(.)f(.)g(.)g(.)h(.)f(.)g(.)h(.)f(.)g(.)g(.)h(.)f(.) +g(.)g(.)102 b(17)125 5190 y(2.13)43 b(The)20 b(T)-7 b(opics)20 +b(Cate)o(gory)69 b(.)42 b(.)f(.)g(.)g(.)h(.)f(.)g(.)g(.)h(.)f(.)g(.)g +(.)h(.)f(.)g(.)h(.)f(.)g(.)g(.)h(.)f(.)g(.)g(.)h(.)f(.)g(.)g(.)h(.)f(.) +g(.)g(.)h(.)f(.)g(.)h(.)f(.)g(.)g(.)h(.)f(.)g(.)g(.)102 +b(17)0 5372 y Fl(3)83 b(Membership)21 b(Management)2753 +b(17)p eop end +%%Page: 2 2 +TeXDict begin 2 1 bop 0 83 a Fl(4)83 b(T)-8 b(ending)21 +b(to)f(P)n(ending)h(Moderator)e(Requests)2258 b(17)0 +266 y(5)83 b(Editing)20 b(the)h(Public)g(HTML)g(P)o(ages)2553 +b(17)0 448 y(6)83 b(Deleting)19 b(the)i(Mailing)f(List)2810 +b(17)0 631 y(A)65 b(This)21 b(is)g(an)g(A)n(ppendix)2986 +b(17)p 0 778 3901 9 v 0 1200 a Fp(1)120 b(Introduction)36 +b(to)e(GNU)g(Mailman)0 1433 y Fo(GNU)20 b(Mailman)f(is)h(softw)o(are)f +(that)h(lets)g(you)f(manage)f(electronic)g(mailing)h(lists.)26 +b(It)20 b(supports)f(a)g(wide)h(range)e(of)i(mailing)e(list)j(types,)0 +1533 y(such)k(as)g(general)f(discussion)h(lists)h(and)f(announce-only)c +(lists.)41 b(Mailman)24 b(has)h(e)o(xtensi)n(v)o(e)f(features)g(for)g +(controlling)f(the)i(pri)n(v)n(ac)o(y)0 1632 y(of)f(your)g(lists,)i +(distrib)n(uting)e(your)f(list)i(as)h(personalized)c(postings)i(or)h +(digests,)g(gate)n(w)o(aying)e(postings)g(to)i(and)f(from)g(Usenet,)h +(and)0 1732 y(pro)o(viding)e(automatic)j(bounce)e(detection.)42 +b(Mailman)25 b(pro)o(vides)g(a)h(b)n(uilt-in)g(archi)n(v)o(er)m(,)f +(multiple)h(natural)f(languages,)h(as)h(well)g(as)0 1832 +y(adv)n(anced)18 b(content)h(and)h(topic)g(\002ltering.)0 +1979 y(Mailman)i(pro)o(vides)e(se)n(v)o(eral)i(interf)o(aces)g(to)g +(its)i(functionality)-5 b(.)29 b(Most)23 b(list)g(administrators)e +(will)i(primarily)e(use)i(the)f(web)g(interf)o(ace)0 +2078 y(to)h(customize)f(their)g(lists.)33 b(There)22 +b(is)i(also)e(a)h(limited)g(email)f(command)f(interf)o(ace)h(to)g(the)h +(administrati)n(v)o(e)e(functions,)g(as)j(well)f(as)g(a)0 +2178 y(command)d(line)i(interf)o(ace)f(if)h(you)g(ha)n(v)o(e)f(shell)h +(access)h(on)e(the)h(Mailman)g(serv)o(er)-5 b(.)30 b(This)22 +b(document)e(does)h(not)h(co)o(v)o(er)f(the)h(command)0 +2277 y(line)e(interf)o(ace;)g(see)g(the)h(GNU)f(Mailman)g(site)h +(administrator')-5 b(s)19 b(manual)g(for)g(more)h(details.)0 +2558 y Fk(1.1)100 b(A)28 b(List')-5 b(s)28 b(Email)h(Addresses)0 +2761 y Fo(Ev)o(ery)22 b(mailing)h(list)i(has)f(a)g(set)h(of)e(email)h +(addresses)f(that)h(messages)g(can)f(be)h(sent)g(to.)36 +b(There')-5 b(s)23 b(al)o(w)o(ays)h(one)f(address)g(for)h(posting)0 +2860 y(messages)k(to)g(the)g(list,)j(one)c(address)h(that)g(bounces)e +(will)j(be)f(sent)g(to,)i(and)d(addresses)h(for)f(processing)g(email)h +(commands.)46 b(F)o(or)0 2960 y(e)o(xample,)19 b(for)g(a)i(mailing)e +(list)i(called)f Fj(mylist@e)n(xample)o(.com)p Fo(,)f(you')l(d)g +(\002nd)h(these)g(addresses:)125 3164 y Fi(\017)41 b +Fo(mylist@e)o(xample.com)17 b(\226)j(this)h(is)g(the)f(email)h(address) +e(people)h(should)f(use)h(for)g(ne)n(w)g(postings)f(to)i(the)f(list.) +125 3320 y Fi(\017)41 b Fo(mylist-join@e)o(xample.com)34 +b(\226)k(by)g(sending)f(a)i(message)f(to)h(this)f(address,)k(a)d(ne)n +(w)f(member)f(can)h(request)g(subscrip-)208 3420 y(tion)f(to)h(the)h +(list.)79 b(Both)38 b(the)g Fh(Subject:)59 b Fo(header)37 +b(and)h(body)e(of)i(such)g(a)g(message)g(are)g(ignored.)77 +b(Note)38 b(that)g(mylist-)208 3519 y(subscribe@e)o(xample.com)16 +b(is)21 b(an)f(alias)h(for)f(the)g(-join)g(address.)125 +3675 y Fi(\017)41 b Fo(mylist-lea)n(v)o(e@e)o(xample.com)16 +b(\226)21 b(by)f(sending)f(a)i(message)g(to)f(this)h(address,)f(a)h +(member)e(can)i(request)f(unsubscription)e(from)208 3775 +y(the)24 b(list.)40 b(As)25 b(with)g(the)g(-join)f(address,)h(the)g +Fh(Subject:)33 b Fo(header)23 b(and)i(body)e(of)h(the)h(message)g(is)g +(ignored.)37 b(Note)25 b(that)g(mylist-)208 3875 y(unsubscribe@e)o +(xample.com)15 b(is)21 b(an)f(alias)h(for)f(the)g(-lea)n(v)o(e)g +(address.)125 4030 y Fi(\017)41 b Fo(mylist-o)n(wner@e)o(xample.com)15 +b(\226)20 b(This)h(address)f(reaches)f(the)h(list)i(o)n(wner)d(and)h +(list)h(moderators)d(directly)-5 b(.)125 4186 y Fi(\017)41 +b Fo(mylist-request@e)o(xample.com)14 b(\226)k(This)h(address)f +(reaches)g(a)h(mail)g(robot)e(which)h(processes)g(email)h(commands)e +(that)h(can)h(be)208 4286 y(used)g(to)i(set)g(member)e(subscription)f +(options,)h(as)i(well)g(as)g(process)f(other)f(commands.)125 +4442 y Fi(\017)41 b Fo(mylist-bounces@e)o(xample.com)21 +b(\226)26 b(This)g(address)f(recei)n(v)o(es)h(bounces)e(from)h(members) +g(who')-5 b(s)26 b(addresses)f(ha)n(v)o(e)h(become)208 +4542 y(either)f(temporarily)f(or)h(permanently)e(inacti)n(v)o(e.)41 +b(The)25 b(-bounces)f(address)h(is)i(also)f(a)g(mail)g(robot)f(that)h +(processes)f(bounces)208 4641 y(and)e(automatically)g(disables)h(or)g +(remo)o(v)o(es)f(members)g(as)i(con\002gured)d(in)i(the)g(bounce)f +(processing)g(settings.)37 b(An)o(y)23 b(bounce)208 4741 +y(messages)i(that)g(are)g(either)g(unrecognized,)d(or)j(do)g(not)f +(seem)i(to)f(contain)f(member)g(addresses,)h(are)g(forw)o(arded)e(to)i +(the)g(list)208 4840 y(administrators.)125 4996 y Fi(\017)41 +b Fo(mylist-con\002rm@e)o(xample.com)21 b(\226)27 b(This)f(address)g +(is)h(another)e(email)h(robot,)h(which)e(processes)h(con\002rmation)e +(messages)208 5096 y(for)19 b(subscription)g(and)g(unsubscription)f +(requests.)0 5300 y(There')-5 b(s)18 b(also)h(an)f(-admin)f(address)h +(which)g(also)g(reaches)g(the)g(list)i(administrators,)d(b)n(ut)h(this) +h(address)f(only)g(e)o(xists)g(for)g(compatibility)0 +5400 y(with)i(older)g(v)o(ersions)f(of)h(Mailman.)p 0 +5549 3901 4 v 0 5649 a Fg(2)2654 b(1)84 b(Introduction)23 +b(to)h(GNU)e(Mailman)p eop end +%%Page: 3 3 +TeXDict begin 3 2 bop 0 83 a Fk(1.2)100 b(Administr)o(ativ)n(e)29 +b(Roles)0 286 y Fo(There)d(are)i(tw)o(o)f(primary)f(administrati)n(v)o +(e)g(roles)h(for)g(each)g(mailing)f(list,)k(a)e(list)g(o)n(wner)f(and)f +(a)i(list)h(moderator)-5 b(.)44 b(A)28 b(list)g(o)n(wner)f(is)0 +386 y(allo)n(wed)20 b(to)i(change)d(v)n(arious)h(settings)i(of)f(the)g +(list,)h(such)f(as)h(the)f(pri)n(v)n(ac)o(y)e(and)i(archi)n(ving)e +(policies,)i(the)g(content)f(\002ltering)h(settings,)0 +485 y(etc.)34 b(The)23 b(list)h(o)n(wner)e(is)i(also)g(allo)n(wed)e(to) +i(subscribe)e(or)h(in)m(vite)f(members,)h(unsubscribe)e(members,)i(and) +f(change)g(an)o(y)h(member')-5 b(s)0 585 y(subscription)19 +b(options.)0 732 y(The)i(list)h(moderator)d(on)h(the)i(other)e(hand,)g +(is)i(only)e(allo)n(wed)g(to)i(appro)o(v)o(e)c(or)j(reject)g(postings)f +(and)h(subscription)f(requests.)27 b(The)20 b(list)0 +831 y(moderator)14 b(can)i(also)g(do)f(things)h(lik)o(e)g(clear)g(a)g +(member')-5 b(s)15 b(moderation)f(\003ag,)j(or)f(add)f(an)h(address)f +(to)i(a)f(list)h(of)f(appro)o(v)o(ed)d(non-member)0 931 +y(posters.)0 1078 y(Normally)-5 b(,)17 b(the)h(list)i(o)n(wner)d(and)h +(list)h(moderator)d(are)j(the)f(same)h(person.)k(In)18 +b(f)o(act,)g(the)h(list)g(o)n(wner)f(can)g(al)o(w)o(ays)h(do)e(all)i +(the)g(tasks)g(a)f(list)0 1177 y(moderator)d(can)i(do.)23 +b(Access)18 b(to)f(both)f(the)h(o)n(wner')-5 b(s)16 b(con\002guration)f +(pages,)i(and)f(the)h(moderation)e(pages)h(are)h(protected)f(by)g(the)h +(same)0 1277 y(passw)o(ord.)29 b(Ho)n(we)n(v)o(er)m(,)20 +b(if)i(the)f(list)i(o)n(wner)e(w)o(ants)h(to)g(dele)o(gate)e(posting)h +(and)g(subscription)f(appro)o(v)n(al)g(authority)g(to)i(other)e +(people,)h(a)0 1377 y(separate)f(list)h(moderator)d(passw)o(ord)h(can)h +(be)g(set,)h(gi)n(ving)e(moderators)f(access)j(to)f(the)h(appro)o(v)n +(al)d(pages,)h(b)n(ut)h(not)g(the)g(con\002guration)0 +1476 y(pages.)25 b(In)19 b(this)i(setup,)f(list)h(o)n(wners)f(can)g +(still)h(moderate)e(the)h(list,)h(of)f(course.)0 1623 +y(In)26 b(the)g(sections)g(that)h(follo)n(w)-5 b(,)26 +b(we')o(ll)g(often)g(use)g(the)g(terms)g(list)i(o)n(wner)d(and)g(list)j +(administrator)c(interchangably)-5 b(,)24 b(meaning)g(both)0 +1723 y(roles.)h(When)20 b(necessary)-5 b(,)19 b(we')o(ll)h(distinguish) +f(the)i(list)g(moderator)d(e)o(xplicitly)-5 b(.)0 2008 +y Fk(1.3)100 b(A)28 b(List')-5 b(s)28 b(W)m(eb)g(P)l(ages)0 +2211 y Fo(Ev)o(ery)j(mailing)h(list)h(is)h(also)f(accessible)f(by)g(a)h +(number)e(of)h(web)g(pages.)62 b(Note)32 b(that)h(the)f(e)o(xact)g +(urls)h(is)g(con\002gurable)d(by)j(the)0 2310 y(site)28 +b(administrator)m(,)f(so)h(the)o(y)f(may)g(be)g(dif)n(ferent)f(than)h +(what')-5 b(s)27 b(described)f(belo)n(w)-5 b(.)46 b(W)-7 +b(e')o(ll)28 b(describe)f(the)g(most)h(common)d(def)o(ault)0 +2410 y(con\002guration,)17 b(b)n(ut)j(check)g(with)g(your)f(site)i +(administrator)e(or)h(hosting)f(service)h(for)f(details.)0 +2557 y(Mailman)g(pro)o(vides)f(a)i(set)h(of)e(web)h(pages)f(that)h +(list)g(members)f(use)h(to)g(get)f(information)f(about)g(the)i(list,)h +(or)e(manage)g(their)g(member)n(-)0 2656 y(ship)j(options.)28 +b(There)21 b(are)h(also)g(list)h(archi)n(v)o(e)d(pages,)i(for)f(bro)n +(wsing)f(an)i(online)f(web-based)f(archi)n(v)o(e)h(of)g(the)h(list)h +(traf)n(\002c.)29 b(These)22 b(are)0 2756 y(described)d(in)h(more)g +(detail)g(in)g(the)g(GNU)h(Mailman)f(user')-5 b(s)20 +b(manual.)0 2903 y(Mailman)c(also)h(pro)o(vides)e(a)i(set)h(of)f(pages) +f(for)g(con\002guring)e(an)j(indi)n(vidual)e(list,)j(as)g(well)f(as)h +(a)f(set)g(of)g(pages)f(for)g(disposing)g(of)h(posting)0 +3002 y(and)j(subscription)e(requests.)0 3149 y(F)o(or)j(a)h(mailing)f +(list)h(called)g Fj(mylist)i Fo(hosted)c(at)i(the)g(domain)e +Fj(lists.e)n(xample)o(.com)p Fo(,)h(you)f(w)o(ould)h(typically)g +(access)h(the)f(administrati)n(v)o(e)0 3249 y(pages)29 +b(by)f(going)g(to)h Ff(http://lists.example.com/mailman/adm)o(in/my)o +(list)p Fo(.)46 b(The)28 b(\002rst)i(time)f(you)f(visit)i(this)0 +3349 y(page,)25 b(you)g(will)g(be)h(presented)d(with)j(a)f(login)g +(page,)g(asking)f(for)h(the)g(list)h(o)n(wner')-5 b(s)25 +b(passw)o(ord.)39 b(When)25 b(you)f(enter)g(the)i(passw)o(ord,)0 +3448 y(Mailman)19 b(will)h(store)f(a)h(session)f(cookie)g(in)g(your)f +(bro)n(wser)m(,)g(so)i(you)e(don')o(t)g(ha)n(v)o(e)g(to)i +(re-authenticate)d(for)i(e)n(v)o(ery)f(action)h(you)f(w)o(ant)h(to)0 +3548 y(tak)o(e.)25 b(This)20 b(cookie)f(is)j(stored)d(only)h(until)g +(you)f(e)o(xit)h(your)f(bro)n(wser)-5 b(.)0 3695 y(T)e(o)15 +b(access)h(the)f(administrati)n(v)o(e)f(requests)h(page,)g(you')l(d)e +(visit)j Ff(http://lists.example.com/mailman/adm)o(indb/)o(mylist)0 +3794 y Fo(\(note)21 b(the)h Fj(admindb)e Fo(url)h(as)h(opposed)e(to)i +(the)g Fj(admin)f Fo(url\).)29 b(Again,)21 b(the)h(\002rst)g(time)g +(you)f(visit)h(this)g(page,)g(you')o(ll)e(be)i(presented)e(with)0 +3894 y(a)j(login)e(page,)h(on)g(which)g(you)f(can)h(enter)g(either)g +(the)g(list)h(moderator)d(passw)o(ord)i(or)g(the)g(list)h(o)n(wner)f +(passw)o(ord.)30 b(Again,)21 b(a)i(session)0 3994 y(cookie)d(is)i +(dropped)d(in)j(your)e(bro)n(wser)-5 b(.)27 b(Note)22 +b(also)f(that)h(if)f(you')l(v)o(e)e(pre)n(viously)h(logged)f(in)j(as)g +(the)f(list)i(o)n(wner)m(,)d(you)g(do)h(not)g(need)f(to)0 +4093 y(re-login)f(to)h(access)h(the)f(administrati)n(v)o(e)e(requests)i +(page.)0 4378 y Fk(1.4)100 b(Basic)28 b(Architectur)o(al)i(Ov)n(er)s +(vie)n(w)0 4581 y Fo(This)23 b(section)f(will)h(outline)f(the)g(basic)h +(architecture)e(of)h(GNU)h(Mailman,)f(such)h(as)g(ho)n(w)f(messages)g +(are)h(processed)e(by)h(the)h(sytem.)0 4681 y(W)m(ithout)29 +b(going)f(into)h(lots)h(of)f(detail,)i(this)f(information)d(will)j +(help)f(you)f(understand)g(ho)n(w)g(the)i(con\002guration)c(options)j +(control)0 4780 y(Mailman')-5 b(s)20 b(functionality)-5 +b(.)0 4927 y(When)23 b(mail)h(enters)g(the)f(system)h(from)f(your)f +(mail)i(serv)o(er)m(,)f(it)h(is)h(dropped)c(into)j(one)f(of)g(se)n(v)o +(eral)g(Mailman)g Fj(queues)g Fo(depending)e(on)0 5027 +y(the)g(address)h(the)f(message)g(w)o(as)i(sent)e(to.)29 +b(F)o(or)21 b(e)o(xample,)g(if)g(your)g(system)g(has)h(a)g(mailing)f +(list)h(named)f Fj(mylist)i Fo(and)e(your)g(domain)f(is)0 +5126 y Fj(e)n(xample)o(.com)p Fo(,)k(people)g(can)h(post)g(messages)g +(to)g(your)f(list)i(by)e(sending)g(them)h(to)g Fj(mylist@e)n(xample)o +(.com)p Fo(.)38 b(These)25 b(messages)g(will)0 5226 y(be)c(dropped)d +(into)j(the)g Fj(incoming)e Fo(queue,)h(which)g(is)i(also)f +(colloquially)e(called)i(the)g Fj(moder)o(ate-and-mung)o(e)16 +b Fo(queue.)26 b(The)20 b(incoming)0 5326 y(queue)e(is)j(where)e(most)h +(of)f(the)h(appro)o(v)n(al)d(process)i(occurs,)g(and)g(it')-5 +b(s)21 b(also)f(where)f(the)g(message)h(is)g(prepared)e(for)h(sending)f +(out)i(to)g(the)p 0 5549 3901 4 v 0 5649 a Fg(1.2)83 +b(Administr)o(ativ)n(e)25 b(Roles)2902 b(3)p eop end +%%Page: 4 4 +TeXDict begin 4 3 bop 0 83 a Fo(list)21 b(membership.)0 +230 y(There)e(are)h(separate)f(queues)g(for)g(the)h(b)n(uilt-in)f +(archi)n(v)o(er)m(,)f(the)i(bounce)e(processor)m(,)g(the)i(email)f +(command)f(processor)m(,)g(as)j(well)f(as)h(the)0 330 +y(outgoing)d(email)j(and)e(ne)n(ws)i(queues.)k(There')-5 +b(s)20 b(also)g(a)h(queue)e(for)h(messages)h(generated)d(by)i(the)h +(Mailman)f(system.)25 b(Each)20 b(of)g(these)0 429 y(queues)26 +b(typically)g(has)g(one)h Fj(queue)e(runner)h Fo(\(or)g +(\223qrunner\224\))e(that)j(processes)f(messages)h(in)g(the)g(queue.)43 +b(The)26 b(qrunners)f(are)h(idle)0 529 y(when)20 b(there)f(are)h(no)g +(messages)h(to)f(process.)0 676 y(Ev)o(ery)f(message)i(in)g(the)f +(queues)g(are)h(represented)e(by)h(tw)o(o)h(\002les,)h(a)f(message)f +(\002le)i(and)e(a)h(metadata)f(\002le.)27 b(Both)21 b(of)f(these)h +(\002les)h(share)0 775 y(the)g(same)h(base)f(name,)g(which)f(is)i(a)g +(combination)d(of)i(a)g(unique)f(hash)h(and)g(the)g(Unix)g(time)g(that) +g(the)h(message)f(w)o(as)h(recei)n(v)o(ed.)29 b(The)0 +875 y(metadata)23 b(\002le)h(has)f(a)h(suf)n(\002x)f(of)g(`)p +Fh(.db)p Fo(')f(and)h(the)g(message)g(\002le)h(has)f(a)h(suf)n(\002x)f +(of)g(either)g(`)p Fh(.msg)p Fo(')g(if)h(stored)e(in)i(plain)f(te)o +(xt,)h(or)f(`)p Fh(.pc)o(k)p Fo(')f(if)0 975 y(stored)e(in)g(a)h(more)e +(ef)n(\002cient)h(internal)f(representation)1596 944 +y Fe(1)1627 975 y Fo(.)0 1121 y(As)30 b(a)g(message)g(mo)o(v)o(es)e +(through)g(the)h(incoming)f(queue,)j(it)f(performs)e(v)n(arious)g +(checks)h(on)h(the)f(message,)j(such)d(as)h(whether)f(it)0 +1221 y(matches)20 b(one)g(of)h(the)g(moderation)d(criteria,)i(or)h +(contains)f(disallo)n(wed)g(MIME)g(types.)26 b(Once)21 +b(a)g(message)f(is)i(appro)o(v)o(ed)c(for)i(sending)0 +1321 y(to)g(the)g(list)g(membership,)e(the)i(message)f(is)i(prepared)c +(for)i(sending)g(by)g(deleting,)g(adding,)f(or)h(changing)f(message)h +(headers,)g(adding)0 1420 y(footers,)g(etc.)25 b(Messages)c(in)f(the)g +(incoming)f(queue)g(may)h(also)g(be)g(stored)g(for)f(appending)f(to)i +(digests.)0 1748 y Fp(2)120 b(The)34 b(List)f(Con\002gur)o(ation)j(P)-5 +b(ages)0 1981 y Fo(After)22 b(logging)e(into)h(the)h(list)h +(con\002guration)c(pages,)j(you')o(ll)e(see)j(the)f(con\002guration)d +(options)i(for)g(the)h(list,)h(grouped)c(in)j(cate)o(gories.)0 +2080 y(All)d(the)g(administrati)n(v)o(e)d(pages)i(ha)n(v)o(e)g(some)g +(common)f(elements.)24 b(In)18 b(the)h(upper)e(section,)h(you')o(ll)f +(see)i(tw)o(o)g(columns)e(labeled)h(\223Con-)0 2180 y(\002guration)24 +b(Cate)o(gories\224.)39 b(Some)25 b(cate)o(gories)f(ha)n(v)o(e)g +(sub-cate)o(gories)f(which)i(are)g(only)f(visible)h(when)g(you)f(click) +h(on)g(the)g(cate)o(gory)0 2279 y(link.)35 b(The)23 b(\002rst)h(page)f +(you)f(see)i(after)g(logging)d(in)j(will)g(be)g(the)f(\223General)g +(Options\224)g(cate)o(gory)-5 b(.)32 b(The)23 b(speci\002c)h(option)e +(settings)i(for)0 2379 y(each)c(cate)o(gory)e(are)i(described)f(belo)n +(w)-5 b(.)0 2526 y(On)24 b(the)g(right)g(side)g(of)g(the)g(top)g +(section,)g(you')o(ll)g(see)g(a)h(column)d(labeled)i(\223Other)f +(Administrati)n(v)o(e)g(Acti)n(vities\224.)37 b(Here)24 +b(you')o(ll)f(\002nd)0 2626 y(some)d(other)f(things)h(you)f(can)h(do)f +(to)i(your)d(list,)j(as)g(well)g(as)f(con)m(v)o(enient)e(links)i(to)g +(the)g(list)h(information)d(page)h(and)h(the)g(list)h(archi)n(v)o(es.)0 +2725 y(Note)f(the)h(big)f(\223Logout\224)e(link;)i(use)h(this)g(if)f +(you')l(re)f(\002nished)h(con\002guring)d(your)j(list)h(and)f(don')o(t) +e(w)o(ant)j(to)f(lea)n(v)o(e)h(the)f(session)h(cookie)0 +2825 y(acti)n(v)o(e)f(in)g(your)f(bro)n(wser)-5 b(.)0 +2972 y(Belo)n(w)24 b(this)h(common)d(header)m(,)h(you')o(ll)g(\002nd)h +(a)g(list)h(of)f(this)g(cate)o(gory')-5 b(s)23 b(con\002guration)e(v)n +(ariables,)j(arranged)d(in)k(tw)o(o)f(columns.)35 b(In)0 +3071 y(the)26 b(left)f(column)g(is)h(a)g(brief)f(description)f(of)i +(the)f(option,)h(which)f(also)h(contains)e(a)j(\223details\224)e(link.) +41 b(F)o(or)25 b(man)o(y)g(of)g(the)h(v)n(ariables,)0 +3171 y(more)21 b(details)h(are)g(a)n(v)n(ailable)f(describing)f(the)i +(semantics)f(of)h(the)f(v)n(arious)g(a)n(v)n(ailable)g(settings,)h(or)g +(information)d(on)i(the)h(interaction)0 3271 y(between)29 +b(this)h(setting)f(and)g(other)g(list)i(options.)52 b(Clicking)29 +b(on)g(the)g(details)h(link)f(brings)g(up)g(a)h(page)f(which)g +(contains)g(only)g(the)0 3370 y(information)18 b(for)h(that)i(option,)d +(as)j(well)g(as)g(a)f(b)n(utton)g(for)f(submitting)g(your)g(setting,)h +(and)g(a)g(link)g(back)g(to)g(the)g(cate)o(gory)f(page.)0 +3517 y(On)27 b(the)g(right)f(side)h(of)g(the)g(tw)o(o-column)e +(section,)j(you')o(ll)e(see)h(the)g(v)n(ariable')-5 b(s)26 +b(current)g(v)n(alue.)44 b(Some)26 b(v)n(ariables)h(may)f(present)g(a)0 +3617 y(limited)h(set)g(of)f(v)n(alues,)i(via)f(radio)f(b)n(utton)g(or)g +(check)g(box)g(arrays.)44 b(Other)26 b(v)n(ariables)g(may)g(present)g +(te)o(xt)h(entry)f(box)o(es)f(of)i(one)f(or)0 3716 y(multiple)18 +b(lines.)24 b(Most)19 b(v)n(ariables)e(control)g(settings)h(for)g(the)g +(operation)e(of)i(the)g(list,)i(b)n(ut)e(others)f(perform)g(immediate)g +(actions)h(\(these)0 3816 y(are)i(clearly)g(labeled\).)0 +3963 y(At)25 b(the)g(bottom)e(of)h(the)h(page,)f(you')o(ll)g(\002nd)g +(a)h(\223Submit\224)e(b)n(utton)h(and)g(a)h(footer)e(with)i(some)f +(more)g(useful)g(links)g(and)g(a)h(fe)n(w)f(logos.)0 +4062 y(Hitting)e(the)h(submit)f(b)n(utton)f(commits)h(your)f(list)j +(settings,)f(after)f(the)o(y')l(v)o(e)e(been)i(v)n(alidated.)30 +b(An)o(y)22 b(in)m(v)n(alid)f(v)n(alues)h(will)h(be)f(ignored)0 +4162 y(and)g(an)h(error)f(message)h(will)g(be)g(displayed)f(at)h(the)g +(top)f(of)h(the)g(resulting)f(page.)32 b(The)22 b(results)i(page)e +(will)h(al)o(w)o(ays)h(be)f(the)f(cate)o(gory)0 4262 +y(page)e(that)g(you)f(submitted.)0 4547 y Fk(2.1)100 +b(The)28 b(Gener)o(al)i(Options)e(Categor)s(y)0 4749 +y Fo(The)23 b(General)g(Options)f(cate)o(gory)g(is)i(where)f(you)f(can) +h(set)h(a)g(v)n(ariety)e(of)h(v)n(ariables)f(that)i(af)n(fect)e(basic)i +(beha)n(vior)e(and)g(public)h(infor)n(-)0 4849 y(mation.)35 +b(In)24 b(the)g(descriptions)f(that)h(follo)n(w)-5 b(,)23 +b(the)h(v)n(ariable)f(name)g(is)i(gi)n(v)o(en)e(\002rst,)i(along)e +(with)h(an)g(o)o(v)o(ervie)n(w)e(and)h(a)h(description)f(of)0 +4949 y(what)d(that)g(v)n(ariable)g(controls.)p 0 5003 +1560 4 v 90 5059 a Fd(1)120 5082 y Fc(Speci\002cally)l(,)f(a)e(Python)h +(pickle)p 0 5549 3901 4 v 0 5649 a Fg(4)2658 b(2)84 b(The)23 +b(List)g(Con\002gur)o(ation)h(P)m(ages)p eop end +%%Page: 5 5 +TeXDict begin 5 4 bop 0 83 a Fg(Gener)o(al)24 b(list)f(personality)0 +286 y Fo(These)c(v)n(ariables,)g(grouped)e(under)h(the)h(general)g +(list)h(personality)e(section,)h(control)g(some)g(public)f(information) +f(about)i(the)g(mailing)0 386 y(list.)0 615 y Fl(r)o(eal)p +143 615 25 4 v 29 w(name)41 b Fo(Ev)o(ery)23 b(mailing)h(list)i(has)g +(both)e(a)h Fj(posting)f(name)g Fo(and)g(a)i Fj(r)m(eal)f(name)p +Fo(.)38 b(The)25 b(posting)f(name)g(sho)n(ws)h(up)f(in)h(urls)g(and)f +(in)208 715 y(email)16 b(addresses,)i(e.g.)23 b(the)17 +b Ff(mylist)f Fo(in)h Ff(mylist@example.com)p Fo(.)k(The)c(posting)f +(name)g(is)i(al)o(w)o(ays)f(presented)f(in)h(lo)n(wer)208 +815 y(case,)22 b(with)h(alphanumeric)c(characters)i(and)h(no)g(spaces.) +31 b(The)22 b(list')-5 b(s)23 b(real)f(name)g(is)h(used)f(in)g(some)g +(public)f(information)f(and)208 914 y(email)j(responses,)g(such)g(as)i +(in)e(the)h(general)e(list)i(o)o(v)o(ervie)n(w)-5 b(.)32 +b(The)23 b(real)h(name)f(can)g(dif)n(fer)f(from)g(the)i(posting)e(name) +h(by)g(case)208 1014 y(only)-5 b(.)23 b(F)o(or)d(e)o(xample,)f(if)h +(the)g(posting)g(name)f(is)i Ff(mylist)p Fo(,)f(the)g(real)g(name)g +(can)g(be)g Ff(Posting)p Fo(.)0 1180 y Fl(o)o(wner)41 +b Fo(This)24 b(v)n(ariable)e(contains)h(a)h(list)h(of)e(email)h +(addresses,)g(one)f(address)g(per)g(line,)i(of)e(the)h(list)g(o)n +(wners.)35 b(These)23 b(addresses)h(are)208 1280 y(used)18 +b(whene)n(v)o(er)f(the)i(list)h(o)n(wners)e(need)g(to)h(be)g +(contacted,)e(either)i(by)f(the)h(system)g(or)g(by)f(end)h(users.)24 +b(Often,)19 b(these)g(addresses)208 1379 y(are)h(used)g(in)g +(combination)e(with)i(the)g Ff(moderator)f Fo(addresses)h(\(see)h(belo) +n(w\).)0 1545 y Fl(moderator)40 b Fo(This)33 b(v)n(ariable)f(contains)g +(a)i(list)g(of)e(email)i(addresses,)h(one)e(address)f(per)h(line,)j(of) +d(the)g(list)h(moderators.)62 b(These)208 1645 y(addresses)46 +b(are)h(often)f(used)h(in)g(combination)d(with)j(the)g +Ff(owner)g Fo(addresses.)105 b(F)o(or)46 b(e)o(xample,)52 +b(when)47 b(you)f(email)208 1745 y Ff(mylist-owner@example.com)p +Fo(,)23 b(both)i(the)h(o)n(wner)f(and)h(moderator)e(addresses)h(will)i +(recei)n(v)o(e)e(a)i(cop)o(y)e(of)h(the)g(mes-)208 1844 +y(sage.)0 2010 y Fl(description)41 b Fo(In)27 b(the)h(general)e(list)i +(o)o(v)o(ervie)n(w)e(page,)i(which)f(sho)n(ws)g(you)g(e)n(v)o(ery)e(a)n +(v)n(ailable)i(mailing)g(list,)j(each)d(list)h(is)h(displayed)208 +2110 y(with)22 b(a)i(short)e(description.)31 b(The)22 +b(contents)g(of)g(this)i(v)n(ariable)d(is)j(that)f(description.)31 +b(Note)22 b(that)h(in)g(emails)g(from)f(the)g(mailing)208 +2209 y(list,)h(this)f(description)f(is)i(also)f(used)g(in)g(the)g +(comment)e(section)i(of)g(the)f Fh(T)-9 b(o:)29 b Fo(address.)g(This)23 +b(te)o(xt)e(should)g(be)h(relati)n(v)o(ely)f(short)208 +2309 y(and)e(no)h(longer)f(than)h(one)f(line.)0 2475 +y Fl(inf)n(o)41 b Fo(This)24 b(v)n(ariable)g(contains)g(a)g(longer)g +(description)f(of)h(the)g(mailing)g(list.)39 b(It)24 +b(is)i(included)d(at)i(the)f(top)g(of)h(the)f(list')-5 +b(s)26 b(information)208 2575 y(page,)g(and)f(it)h(can)f(contain)g +(HTML.)g(Ho)n(we)n(v)o(er)m(,)g(blank)f(lines)i(will)h(be)e +(automatically)f(con)m(v)o(erted)f(into)i(paragraph)f(breaks.)208 +2674 y(Pre)n(vie)n(w)e(your)g(HTML)i(though,)e(because)g(unclosed)g(or) +i(in)m(v)n(alid)e(HTML)h(can)g(pre)n(v)o(ent)f(display)g(of)h(parts)h +(of)f(the)g(list)i(infor)n(-)208 2774 y(mation)19 b(page.)0 +2940 y Fl(subject)p 259 2940 V 30 w(pr)o(e\002x)40 b +Fo(This)26 b(is)g(a)g(string)e(that)i(will)g(be)f(prepended)e(to)i(the) +h Fh(Subject:)33 b Fo(header)25 b(of)g(an)o(y)f(message)h(posted)g(to)g +(the)h(list.)41 b(F)o(or)208 3040 y(e)o(xample,)18 b(if)j(a)f(message)g +(is)h(posted)f(to)g(the)g(list)i(with)e(a)h Fh(Subject:)i +Fo(lik)o(e:)623 3173 y Fb(Subject:)44 b(This)g(is)g(a)h(message)208 +3536 y Fo(and)19 b(the)i Ff(subject_prefix)d Fo(is)j +Ff([My)49 b(List])70 b Fo(\(note)20 b(the)g(trailing)g(space!\),)f +(then)h(the)g(message)g(will)h(be)g(recei)n(v)o(ed)d(lik)o(e)208 +3636 y(so:)623 3860 y Fb(Subject:)44 b([My)g(List])g(This)g(is)h(a)f +(message)208 4224 y Fo(If)21 b(you)f(lea)n(v)o(e)i Ff(subject_prefix)d +Fo(empty)-5 b(,)20 b(no)i(pre\002x)e(will)i(be)g(added)e(to)i(the)f +Fh(Subject:)p Fo(.)28 b(Mailman)20 b(is)j(careful)d(not)h(to)h(add)208 +4324 y(a)28 b(pre\002x)f(when)h(the)g(header)f(already)g(has)h(one,)h +(as)g(is)g(the)f(case)h(in)f(replies)g(for)f(e)o(xample.)47 +b(The)28 b(pre\002x)f(can)h(also)h(contain)208 4423 y(characters)19 +b(in)h(the)g(list')-5 b(s)22 b(preferred)c(language.)23 +b(In)d(this)g(case,)h(because)e(of)h(v)n(agarities)f(of)h(the)g(email)g +(standards,)f(you)g(may)h(or)208 4523 y(may)f(not)h(w)o(ant)g(to)h(add) +e(a)i(trailing)f(space.)0 4689 y Fl(anonymous)p 412 4689 +V 29 w(list)41 b Fo(This)25 b(v)n(ariable)e(allo)n(ws)i(you)e(to)i +(turn)e(on)h(some)g(simple)h(anon)o(ymizing)c(features)i(of)i(Mailman.) +36 b(When)24 b(you)g(set)208 4788 y(this)k(option)e(to)i +Fj(Y)-8 b(es)p Fo(,)31 b(Mailman)c(will)i(remo)o(v)o(e)d(or)h(replace)g +(the)h Fh(F)m(rom:)p Fo(,)h Fh(Sender)r(:)p Fo(,)f(and)f +Fh(Reply-T)-9 b(o:)39 b Fo(\002elds)28 b(of)g(an)o(y)f(message)208 +4888 y(posted)19 b(to)h(the)h(list.)208 5021 y(Note)e(that)g(this)h +(option)d(is)k(simply)d(an)h(aid)h(for)e(anon)o(ymization,)e(it)k +(doesn')o(t)e(guarantee)f(it.)25 b(F)o(or)19 b(e)o(xample,)f(a)h +(poster')-5 b(s)19 b(identity)208 5121 y(could)i(be)i(e)n(vident)e(in)i +(their)f(signature,)g(or)g(in)h(other)e(mail)i(headers,)f(or)g(e)n(v)o +(en)g(in)g(the)h(style)g(of)f(the)h(content)e(of)h(the)h(message.)208 +5220 y(There')-5 b(s)19 b(little)i(Mailman)f(can)g(do)g(about)f(this)i +(kind)e(of)h(identity)f(leakage.)p 0 5549 3901 4 v 0 +5649 a Fg(2.1)83 b(The)24 b(Gener)o(al)f(Options)g(Categor)r(y)2524 +b(5)p eop end +%%Page: 6 6 +TeXDict begin 6 5 bop 0 83 a Fg(Reply-T)-10 b(o)23 b(header)g(m)o +(unging)0 286 y Fo(This)d(section)g(controls)g(what)g(happens)f(to)h +(the)g Fh(Reply-T)-9 b(o:)24 b Fo(headers)19 b(of)h(messages)g(posted)g +(through)e(your)h(list.)0 433 y(Be)n(w)o(are!)32 b Fh(Reply-T)-9 +b(o:)28 b Fo(munging)20 b(is)j(considered)e(a)h(religious)g(issue)h +(and)f(the)g(policies)g(you)g(set)h(here)f(can)g(ignite)g(some)g(of)g +(the)h(most)0 532 y(heated)i(of)n(f-topic)f(\003ame)i(w)o(ars)g(on)f +(your)g(mailing)g(lists.)43 b(W)-7 b(e')o(ll)27 b(try)f(to)g(stay)g(as) +h(agnostic)e(as)h(possible,)h(b)n(ut)f(our)f(biases)h(may)f(still)0 +632 y(peak)20 b(through.)0 779 y Fh(Reply-T)-9 b(o:)33 +b Fo(is)26 b(a)f(header)f(that)h(is)h(commonly)d(used)i(to)g(redirect)f +(replies)h(to)g(messages.)39 b(Exactly)24 b(what)h(happens)f(when)g +(your)g(uses)0 879 y(reply)e(to)h(such)f(a)h(message)f(depends)g(on)g +(the)h(mail)f(readers)g(your)g(users)g(use,)i(and)e(what)g(functions)g +(the)o(y)f(pro)o(vide.)31 b(Usually)-5 b(,)22 b(there)0 +978 y(is)h(both)e(a)i(\223reply)e(to)h(sender\224)f(b)n(utton)g(and)h +(a)g(\223reply)f(to)i(all\224)f(b)n(utton.)30 b(If)22 +b(people)e(use)j(these)f(b)n(uttons)f(correctly)-5 b(,)21 +b(you)g(will)i(probably)0 1078 y(ne)n(v)o(er)c(need)g(to)i(munge)d +Fh(Reply-T)-9 b(o:)p Fo(,)19 b(so)h(the)h(def)o(ault)e(v)n(alues)h +(should)f(be)h(\002ne.)0 1225 y(Since)i(an)f(informed)f(decision)g(is)j +(al)o(w)o(ays)f(best,)g(here)f(are)g(links)h(to)g(tw)o(o)f(articles)h +(that)g(discuss)g(the)f(opposing)f(vie)n(wpoints)g(in)i(great)0 +1324 y(detail:)125 1554 y Fi(\017)41 b Fo(Reply-T)-7 +b(o)19 b(Munging)f(Considered)h(Harmful)125 1720 y Fi(\017)41 +b Fo(Reply-T)-7 b(o)19 b(Munging)f(Considered)h(Useful)0 +1950 y(The)24 b(three)g(options)f(in)i(this)g(section)f(w)o(ork)f +(together)g(to)i(pro)o(vide)d(enough)h(\003e)o(xibility)g(to)i(do)f +(whate)n(v)o(er)e Fh(Reply-T)-9 b(o:)32 b Fo(munging)22 +b(you)0 2050 y(might)e(\(misguidingly)d(:\))26 b(feel)20 +b(you)f(need)h(to)g(do.)0 2280 y Fl(\002rst)p 148 2280 +25 4 v 30 w(strip)p 344 2280 V 30 w(r)o(eply)p 558 2280 +V 29 w(to)40 b Fo(This)18 b(v)n(ariable)d(controls)i(whether)f(an)o(y)g +Fh(Reply-T)-9 b(o:)22 b Fo(header)16 b(already)g(present)g(in)h(the)g +(posted)g(message)g(should)208 2379 y(get)22 b(remo)o(v)o(ed)e(before)h +(an)o(y)h(other)g(munging)e(occurs.)32 b(Stripping)21 +b(this)i(header)e(will)j(be)e(done)g(re)o(gardless)f(of)h(whether)g(or) +g(not)208 2479 y(Mailman)d(will)i(add)f(its)h(o)n(wn)f +Fh(Reply-T)-9 b(o:)23 b Fo(header)c(to)h(the)h(message.)208 +2612 y(If)d(this)i(option)d(is)j(set)g(to)f Fj(No)p Fo(,)g(then)g(an)o +(y)f(e)o(xisting)g Fh(Reply-T)-9 b(o:)23 b Fo(header)18 +b(will)h(be)g(retained)f(in)h(the)g(posted)f(message.)24 +b(If)19 b(Mailman)208 2711 y(adds)g(its)h(o)n(wn)f(header)m(,)f(it)i +(will)g(contain)f(addresses)g(which)g(are)g(the)g(union)g(of)g(the)g +(original)f(header)h(and)g(the)g(Mailman)g(added)208 +2811 y(addresses.)28 b(The)21 b(mail)h(standards)e(specify)h(that)h(a)f +(message)h(may)f(only)f(ha)n(v)o(e)h(one)g Fh(Reply-T)-9 +b(o:)26 b Fo(header)m(,)20 b(b)n(ut)i(that)f(that)h(header)208 +2911 y(may)d(contain)g(multiple)h(addresses.)0 3077 y +Fl(r)o(eply)p 189 3077 V 29 w(goes)p 371 3077 V 29 w(to)p +470 3077 V 29 w(list)42 b Fo(This)29 b(v)n(ariable)f(controls)g +(whether)f(Mailman)i(will)g(add)g(its)h(o)n(wn)e Fh(Reply-T)-9 +b(o:)41 b Fo(header)m(,)30 b(and)e(if)h(so,)j(what)d(the)208 +3176 y(v)n(alue)19 b(of)h(that)g(header)f(will)i(be)f(\(not)g(counting) +e(original)h(header)g(stripping)g(\226)h(see)h(abo)o(v)o(e\).)208 +3309 y(When)g(you)f(set)j(this)f(v)n(ariable)e(to)i Fj(P)-7 +b(oster)p Fo(,)22 b(no)f(additional)f Fh(Reply-T)-9 b(o:)27 +b Fo(header)20 b(will)i(be)g(added)e(by)h(Mailman.)28 +b(This)22 b(setting)g(is)208 3409 y(strongly)c(recommended.)208 +3542 y(When)24 b(you)f(set)i(this)g(v)n(ariable)e(to)h +Fj(This)h(list)p Fo(,)h(a)f Fh(Reply-T)-9 b(o:)31 b Fo(header)23 +b(pointing)g(back)h(to)g(your)f(list')-5 b(s)26 b(posting)d(address)h +(will)h(be)208 3641 y(added.)208 3774 y(When)17 b(you)g(set)h(this)g(v) +n(ariable)e(to)i Fj(Explicit)f(addr)m(ess)p Fo(,)h(the)f(v)n(alue)g(of) +g(the)h(v)n(ariable)e Ff(reply_to_address)g Fo(\(see)h(belo)n(w\))g +(will)208 3874 y(be)h(added.)23 b(Note)c(that)g(this)g(is)h(one)e +(situation)g(where)g Fh(Reply-T)-9 b(o:)23 b Fo(munging)16 +b(may)j(ha)n(v)o(e)f(a)h(le)o(gitimate)f(purpose.)23 +b(Say)18 b(you)g(ha)n(v)o(e)208 3973 y(tw)o(o)23 b(lists)h(at)f(your)e +(site,)j(an)f(announce)d(list)k(and)e(a)h(discussion)g(list.)33 +b(The)23 b(announce)d(list)k(might)e(allo)n(w)h(postings)f(only)g(from) +208 4073 y(a)f(small)h(number)d(of)i(appro)o(v)o(ed)d(users;)k(the)f +(general)f(list)j(membership)c(probably)g(can')o(t)h(post)h(to)g(this)h +(list.)29 b(But)22 b(you)e(w)o(ant)h(to)208 4173 y(allo)n(w)g(comments) +g(on)g(announcements)e(to)i(be)h(posted)f(to)h(the)f(general)g +(discussion)g(list)i(by)e(an)o(y)g(list)i(member)-5 b(.)28 +b(In)21 b(this)h(case,)208 4272 y(you)d(can)h(set)h(the)f +Fh(Reply-T)-9 b(o:)24 b Fo(header)19 b(for)g(the)h(announce)e(list)k +(to)e(point)f(to)i(the)f(discussion)g(list')-5 b(s)21 +b(posting)f(address.)0 4438 y Fl(r)o(eply)p 189 4438 +V 29 w(to)p 288 4438 V 29 w(addr)o(ess)41 b Fo(This)20 +b(is)h(the)e(address)h(that)g(will)g(be)g(added)e(in)i(the)g +Fh(Reply-T)-9 b(o:)24 b Fo(header)18 b(if)i Ff(reply_goes_to_list)d +Fo(is)k(set)f(to)208 4538 y Fj(Explicit)g(addr)m(ess)p +Fo(.)0 4806 y Fg(Umbrella)k(list)g(settings)0 5009 y +Fo(TBD.)d(Note)f(that)g(umbrella)f(lists)i(are)g(deprecated)d(and)i +(will)g(be)h(replace)e(with)h(a)h(better)f(mechanism)f(for)g(Mailman)h +(3.0.)p 0 5549 3901 4 v 0 5649 a Fg(6)2658 b(2)84 b(The)23 +b(List)g(Con\002gur)o(ation)h(P)m(ages)p eop end +%%Page: 7 7 +TeXDict begin 7 6 bop 0 83 a Fg(Noti\002cations)0 286 +y Fo(Mailman)17 b(sends)g(noti\002cations)g(to)g(the)g(list)i +(administrators)d(or)h(list)h(members)e(under)g(a)i(number)e(of)h(dif)n +(ferent)e(circumstances.)23 b(Most)0 386 y(of)f(these)g +(noti\002cations)f(can)g(be)h(con\002gured)d(in)j(this)h(section,)f(b)n +(ut)f(see)i(the)f(Bounce)f(Processing)g(and)g(Auto-responder)e(cate)o +(gories)0 485 y(for)h(other)f(noti\002cations)g(that)i(Mailman)e(can)h +(send.)0 715 y Fl(send)p 166 715 25 4 v 30 w(r)o(eminders)42 +b Fo(By)26 b(def)o(ault)f(Mailman)g(sends)g(all)h(list)h(members)d(a)i +(monthly)e(passw)o(ord)h(reminder)-5 b(.)40 b(This)26 +b(notice)f(serv)o(es)g(tw)o(o)208 814 y(purposes.)d(First,)e(it)e +(reminds)f(people)g(about)h(all)g(the)g(lists)i(the)o(y)d(may)h(be)g +(subscribed)e(to)j(on)e(this)i(domain,)e(including)f(the)i(lists)208 +914 y(where)25 b(their)g(subscription)f(may)i(be)f(disabled.)41 +b(Second,)26 b(it)g(reminds)f(people)g(about)g(their)g(passw)o(ords)h +(for)f(these)h(lists,)i(as)208 1014 y(well)19 b(as)g(the)g(url)f(for)g +(their)g(personal)g(options)g(pages,)g(so)h(that)g(the)o(y)e(can)i +(more)f(easily)h(con\002gure)d(their)j(subscription)e(options.)208 +1147 y(Some)j(people)h(get)g(anno)o(yed)e(with)i(these)h(monthly)d +(reminders,)h(and)h(the)o(y)f(can)h(disable)g(the)h(reminders)d(via)j +(their)f(subscrip-)208 1246 y(tion)f(options)g(page.)26 +b(F)o(or)21 b(some)f(lists,)j(the)e(monthly)e(reminders)g(aren')o(t)h +(appropriate)e(for)i(an)o(y)g(of)h(the)g(members,)f(so)h(you)f(can)208 +1346 y(disable)g(them)f(list-wide)i(by)e(setting)i(the)f +Ff(send_reminders)e Fo(v)n(ariable)h(to)h Fj(No)p Fo(.)0 +1512 y Fl(welcome)p 310 1512 V 29 w(msg)42 b Fo(When)26 +b(ne)n(w)h(members)e(are)i(subscribed)e(to)i(the)g(list,)i(either)e(by) +f(their)g(o)n(wn)h(action,)g(or)g(the)f(action)h(of)f(a)h(list)h(ad-) +208 1611 y(ministrator)m(,)18 b(a)h(welcome)g(message)h(can)f(be)g +(sent)h(to)g(them.)k(The)19 b(welcome)g(message)g(contains)g(some)g +(common)f(boilerplate)208 1711 y(information,)e(such)i(as)h(the)f(name) +g(of)g(the)g(list,)i(instructions)d(for)h(posting)g(to)g(the)g(list,)i +(and)e(the)g(member')-5 b(s)18 b(subscription)e(pass-)208 +1811 y(w)o(ord.)28 b(Y)-9 b(ou)21 b(can)h(add)f(additional)f +(information)f(to)j(the)g(welcome)f(message)g(by)g(typing)g(the)g(te)o +(xt)h(into)f(the)h Ff(welcome_msg)208 1910 y Fo(te)o(xt)e(box.)k(Note)c +(that)g(because)g(this)g(te)o(xt)g(is)h(sent)g(as)g(part)f(of)g(an)g +(email,)g(it)h(should)e Fl(not)h Fo(contain)f(HTML.)0 +2076 y Fl(send)p 166 2076 V 30 w(welcome)p 501 2076 V +30 w(msg)41 b Fo(This)20 b(\003ag)h(controls)e(whether)g(or)h(not)g +(the)g(welcome)g(message)g(is)h(sent)f(to)h(ne)n(w)f(subscribers.)0 +2242 y Fl(goodby)o(e)p 301 2242 V 28 w(msg)42 b Fo(Lik)o(e)22 +b(the)g Ff(welcome_msg)p Fo(,)e(a)j(\223goodbye\224)c(message)j(can)g +(be)f(sent)i(to)f(members)f(when)g(the)o(y)g(unsubscribe)g(from)208 +2342 y(the)f(list.)25 b(Unlik)o(e)20 b(the)g(welcome)f(message,)h +(there')-5 b(s)20 b(no)f(boilerplate)g(for)g(the)h(goodbye)e(message.) +24 b(Enter)c(the)g(entire)f(goodbye)208 2441 y(message)h(you')l(d)e +(lik)o(e)i(unsubscribing)e(members)h(to)h(recei)n(v)o(e)f(into)h(the)h +Ff(goodbye_msg)d Fo(te)o(xt)i(box.)0 2607 y Fl(send)p +166 2607 V 30 w(goodby)o(e)p 492 2607 V 29 w(msg)41 b +Fo(This)20 b(\003ag)h(controls)e(whether)g(or)h(not)g(the)g(goodbye)e +(message)i(is)h(sent)g(to)f(unsubscribing)d(members.)0 +2773 y Fl(admin)p 231 2773 V 30 w(immed)p 505 2773 V +30 w(notify)40 b Fo(List)32 b(moderators)c(get)j(noti\002cations)f(of)g +(pending)f(administrati)n(v)o(e)f(actions,)33 b(such)d(as)i +(subscription)d(or)208 2873 y(unsubscription)20 b(requests)j(that)g +(require)f(moderator)f(appro)o(v)n(al,)g(or)i(posted)f(messages)h(that) +h(are)f(being)f(held)g(for)h(moderator)208 2973 y(appro)o(v)n(al.)49 +b(List)30 b(moderators)e(will)i(al)o(w)o(ays)f(get)h(a)f(daily)g +(summary)f(of)h(such)g(pending)e(requests,)k(b)n(ut)e(the)o(y)g(can)g +(also)h(get)208 3072 y(immediate)18 b(noti\002cations)g(when)g(such)h +(a)g(request)g(is)h(made.)k(The)18 b Ff(admin_immed_notify)f +Fo(v)n(ariable)h(controls)g(whether)208 3172 y(these)i(immediate)f +(noti\002cations)g(are)i(sent)f(or)g(not.)25 b(It')-5 +b(s)20 b(generally)f(a)i(good)e(idea)h(to)g(lea)n(v)o(e)g(this)h(set)g +(to)f Fj(Y)-8 b(es)p Fo(.)0 3338 y Fl(admin)p 231 3338 +V 30 w(notify)p 470 3338 V 28 w(mchanges)41 b Fo(This)26 +b(v)n(ariable)e(controls)g(whether)g(the)h(list)h(administrators)e +(should)g(get)h(noti\002cations)f(when)g(mem-)208 3437 +y(bers)c(join)g(or)f(lea)n(v)o(e)h(the)h(list.)0 3603 +y Fl(r)o(espond)p 290 3603 V 29 w(to)p 389 3603 V 29 +w(post)p 566 3603 V 30 w(r)o(equests)41 b Fo(This)28 +b(v)n(ariable)e(controls)h(whether)f(the)i(original)e(sender)h(of)g(a)h +(posting)f(gets)h(a)g(notice)f(when)g(their)208 3703 +y(message)20 b(is)h(held)e(for)h(moderator)e(appro)o(v)n(al.)0 +3971 y Fg(Additional)26 b(settings)0 4174 y Fo(This)20 +b(section)g(contains)g(some)g(miscellaneous)f(settings)h(for)g(your)f +(mailing)g(list.)0 4404 y Fl(emer)o(gency)40 b Fo(When)24 +b(this)h(option)e(is)i(enabled,)f(all)h(list)g(traf)n(\002c)f(is)i +(emer)o(genc)o(y)21 b(moderated,)i(i.e.)37 b(held)24 +b(for)g(moderation.)35 b(T)l(urn)23 b(this)208 4503 y(option)c(on)g +(when)h(your)f(list)i(is)g(e)o(xperiencing)d(a)i(\003ame)n(w)o(ar)g +(and)g(you)f(w)o(ant)h(a)h(cooling)e(of)n(f)g(period.)0 +4669 y Fl(new)p 148 4669 V 30 w(member)p 473 4669 V 30 +w(options)41 b Fo(Each)18 b(member)g(has)i(a)f(set)h(of)f(subscription) +f(options)g(which)g(the)o(y)h(can)g(use)g(to)h(control)e(ho)n(w)g(the)o +(y)h(recei)n(v)o(e)208 4769 y(messages)e(and)g(otherwise)g(interact)g +(with)h(the)f(list.)26 b(While)18 b(the)f(members)g(can)g(change)f +(these)i(settings)g(by)f(logging)f(into)h(their)208 4869 +y(personal)k(options)g(page,)h(you)g(might)g(w)o(ant)g(to)h(set)g(the)g +(def)o(ault)e(for)h(a)h(number)e(of)h(the)g(member)g(options.)30 +b(Y)-9 b(ou)22 b(can)g(do)g(that)208 4968 y(with)e(this)h(v)n(ariable,) +d(b)n(ut)j(see)f(also)h(the)f(other)g(cate)o(gories)f(for)g(other)h +(member)e(def)o(aults)i(you)f(can)h(set.)208 5101 y(This)g(v)n(ariable) +g(presents)g(a)h(set)g(of)g(checkbox)o(es)d(which)i(control)f(the)i +(def)o(aults)f(for)g(some)g(of)g(the)h(member)e(options.)25 +b Fj(Conceal)208 5201 y(the)31 b(member')m(s)h(addr)m(ess)f +Fo(speci\002es)h(whether)f(or)g(not)h(the)g(address)f(is)i(displayed)d +(in)i(the)g(list)h(roster)-5 b(.)59 b Fj(Ac)n(knowledg)o(e)31 +b(the)208 5300 y(member')m(s)22 b(posting)g Fo(controls)h(whether)f(or) +h(not)f(Mailman)h(sends)g(an)g(ackno)n(wledgement)d(to)j(a)g(member)f +(when)h(the)o(y)f(post)h(a)208 5400 y(message)e(to)i(the)f(list.)31 +b Fj(Do)22 b(not)g(send)g(a)g(copy)f(of)i(a)f(member')m(s)f(own)h(post) +g Fo(speci\002es)h(whether)e(a)h(member)f(posting)g(to)h(the)g(list)p +0 5549 3901 4 v 0 5649 a Fg(2.1)83 b(The)24 b(Gener)o(al)f(Options)g +(Categor)r(y)2524 b(7)p eop end +%%Page: 8 8 +TeXDict begin 8 7 bop 208 83 a Fo(will)18 b(get)f(a)h(cop)o(y)f(of)g +(their)h(o)n(wn)f(posting.)23 b Fj(F)l(ilter)18 b(out)f(duplicate)f +(messa)o(g)o(es)i(to)g(list)h(member)o(s)f(\(if)g(possible\))f +Fo(speci\002es)h(whether)208 183 y(members)g(who)h(are)h(e)o(xplicitly) +e(listed)i(as)g(a)g(recipient)f(of)g(a)h(message)g(\(e.g.)k(via)19 +b(the)h Fh(Cc:)25 b Fo(header\))18 b(will)j(also)e(get)h(a)g(cop)o(y)f +(from)208 282 y(Mailman.)208 415 y(Of)h(course,)f(members)g(can)h(al)o +(w)o(ays)h(o)o(v)o(erride)d(these)i(def)o(aults)g(by)g(making)e +(changes)i(on)f(their)h(membership)f(options)g(page.)0 +581 y Fl(administri)o(via)41 b Fo(This)20 b(option)e(speci\002es)i +(whether)f(Mailman)g(will)h(search)f(posted)g(messages)h(for)f +Fj(admimistrivia)p Fo(,)h(in)f(other)g(w)o(ords,)208 +681 y(email)f(commands)f(which)h(usually)g(should)g(be)h(posted)f(to)g +(the)h Ff(-request)f Fo(address)g(for)g(the)h(list.)25 +b(Setting)19 b(this)g(to)g Fj(Y)-8 b(es)20 b Fo(helps)208 +780 y(pre)n(v)o(ent)e(such)i(things)g(as)h(unsubscribe)d(messages)i +(getting)g(erroneously)d(posted)j(to)g(the)g(list.)208 +913 y(If)g(a)g(message)g(seems)h(to)f(contain)f(administri)n(via,)g(it) +i(is)g(held)f(for)f(moderator)f(appro)o(v)n(al.)0 1079 +y Fl(max)p 158 1079 25 4 v 29 w(message)p 478 1079 V +29 w(size)42 b Fo(This)20 b(option)f(speci\002es)h(a)g(maximum)e +(message)i(size,)g(in)g(kilobytes,)f(o)o(v)o(er)f(which)h(the)h +(message)g(will)g(be)g(held)208 1179 y(for)f(moderator)f(appro)o(v)n +(al.)0 1345 y Fl(host)p 153 1345 V 29 w(name)42 b Fo(This)29 +b(option)e(speci\002es)i(the)g(host)g(name)f(part)g(of)h(email)g +(addresses)f(used)h(by)f(this)h(list.)52 b(F)o(or)28 +b(e)o(xample,)i(this)f(is)h(the)208 1445 y Ff(example.com)18 +b Fo(part)i(of)g(the)g(posting)f(address)h Ff(mylist@example.com)p +Fo(.)208 1577 y(It')-5 b(s)25 b(generally)f(not)g(a)i(good)e(idea)g(to) +i(change)d(this)j(v)n(alue,)f(since)g(its)h(def)o(ault)f(v)n(alue)f(is) +i(speci\002ed)f(when)f(the)h(mailing)g(list)h(is)208 +1677 y(created.)d(Changing)18 b(this)h(to)g(an)g(incorrect)e(v)n(alue)i +(could)f(mak)o(e)g(it)i(dif)n(\002cult)e(to)h(contact)f(your)g(mailing) +g(list.)26 b(Also)19 b(not)g(that)g(the)208 1777 y(url)j(used)h(to)g +(visit)g(the)g(list')-5 b(s)24 b(pages)e(is)i(not)e(con\002gurable)f +(through)f(the)j(web)g(interf)o(ace.)31 b(This)23 b(is)h(because)e(if)h +(you)f(messed)h(it)208 1876 y(up,)c(you')l(d)f(ha)n(v)o(e)i(to)g(ha)n +(v)o(e)g(the)g(site)h(administrator)e(\002x)h(it.)0 2042 +y Fl(include)p 263 2042 V 30 w(rfc2369)p 563 2042 V 28 +w(headers)41 b Fo(RFC)25 b(2369)d(is)i(an)f(internet)g(standard)f(that) +i(describes)f(a)h(b)n(unch)e(of)h(headers)g(that)g(mailing)g(list)h +(man-)208 2142 y(agers)30 b(should)g(add)g(to)h(messages)g(to)g(mak)o +(e)g(it)g(easier)g(for)g(people)e(to)i(interact)g(with)g(the)g(list.)58 +b(Mail)31 b(reading)e(programs)208 2242 y(which)c(support)g(this)i +(standard)e(may)h(pro)o(vide)f(b)n(uttons)g(for)h(easy)g(access)h(to)g +(the)f(list')-5 b(s)28 b(archi)n(v)o(es,)f(or)f(for)f(subscribing)g +(and)208 2341 y(unsubscribing)19 b(to)k(the)g(list.)32 +b(It')-5 b(s)24 b(generally)d(a)h(good)g(idea)g(to)h(enable)e(these)i +(headers)f(as)h(it)g(pro)o(vides)e(for)g(an)i(impro)o(v)o(ed)d(user)208 +2441 y(e)o(xperience.)i(These)e(headers)g(are)g(often)f(called)h(the)g +Ff(List-)2010 2456 y(*)2080 2441 y Fo(headers.)208 2574 +y(Ho)n(we)n(v)o(er)m(,)f(not)h(all)i(mail)f(readers)f(are)h(standards)f +(compliant)f(yet,)i(and)g(if)g(you)f(ha)n(v)o(e)g(a)i(lar)o(ge)e +(number)f(of)h(members)g(who)h(are)208 2673 y(using)i(non-compliant)d +(mail)k(readers,)g(the)o(y)f(may)g(be)g(anno)o(yed)f(at)i(these)g +(headers.)35 b(Y)-9 b(ou)23 b(should)f(\002rst)j(try)e(to)h(educate)f +(your)208 2773 y(members)j(as)h(to)h(why)e(these)h(headers)f(e)o(xist,) +j(and)e(ho)n(w)f(to)i(hide)e(them)h(in)g(their)g(mail)g(clients.)46 +b(As)28 b(a)g(last)g(resort)f(you)f(can)208 2873 y(disable)20 +b(these)g(headers,)f(b)n(ut)h(this)h(is)g(not)f(recommended.)0 +3039 y Fl(include)p 263 3039 V 30 w(list)p 399 3039 V +30 w(post)p 577 3039 V 30 w(header)41 b Fo(The)18 b Fh(List-P)l(ost:)24 +b Fo(header)18 b(is)i(one)f(of)g(the)g(headers)f(recommended)e(by)j +(RFC)h(2369.)k(Ho)n(we)n(v)o(er)17 b(for)i(some)208 3138 +y(announce-only)d(mailing)j(lists,)i(only)e(a)i(v)o(ery)e(select)h +(group)f(of)g(people)g(are)h(allo)n(wed)g(to)g(post)g(to)g(the)g(list;) +h(the)f(general)f(mem-)208 3238 y(bership)j(is)i(usually)f(not)g(allo)n +(wed)g(to)g(post)h(to)f(such)g(lists.)36 b(F)o(or)23 +b(lists)i(of)e(this)h(nature,)f(the)h Fh(List-P)l(ost:)30 +b Fo(header)23 b(is)h(misleading.)208 3337 y(Select)31 +b Fj(No)g Fo(to)h(disable)e(the)h(inclusion)f(of)h(this)g(header)-5 +b(.)57 b(\(This)31 b(does)f(not)h(af)n(fect)f(the)h(inclusion)f(of)h +(the)g(other)f Ff(List-)3851 3352 y(*)208 3437 y Fo(headers.\))0 +3722 y Fk(2.2)100 b(The)28 b(P)l(ass)m(w)o(ords)h(Categor)s(y)0 +3925 y Fo(As)22 b(mentioned)d(abo)o(v)o(e,)g(there)h(are)h(tw)o(o)h +(primary)d(administrati)n(v)o(e)g(roles)i(for)f(mailing)h(lists.)28 +b(In)21 b(this)g(cate)o(gory)e(you)i(can)f(specify)h(the)0 +4025 y(passw)o(ord)e(for)h(these)g(roles.)0 4171 y(The)25 +b(list)i(o)n(wner)e(has)h(total)g(control)f(o)o(v)o(er)f(the)i +(con\002guration)d(of)j(their)f(mailing)g(list)i(\(within)e(some)h +(bounds)e(as)j(speci\002ed)e(by)h(the)0 4271 y(site)32 +b(administrator\).)54 b(Note)31 b(that)g(on)f(this)h(page,)h(for)f +(historical)f(reasons,)i(the)f(list)h(o)n(wner)e(role)g(is)i(described) +d(here)h(as)i(the)e Fj(list)0 4371 y(administr)o(ator)p +Fo(.)36 b(Y)-9 b(ou)24 b(can)g(set)h(the)g(list)g(o)n(wner')-5 +b(s)24 b(passw)o(ord)f(by)h(entering)f(it)i(in)g(the)f(passw)o(ord)g +(\002eld)g(on)g(the)g(left.)38 b(Y)-9 b(ou)24 b(must)g(type)0 +4470 y(it)30 b(twice)g(for)e(con\002rmation.)50 b(Note)30 +b(that)f(if)g(you)g(for)o(get)e(this)j(passw)o(ord,)h(the)e(only)f(w)o +(ay)i(for)e(you)h(to)g(get)h(back)e(into)h(your)f(list')-5 +b(s)0 4570 y(administrati)n(v)o(e)18 b(pages)i(is)h(to)g(ask)f(the)g +(site)h(administrator)e(to)h(reset)h(it)g(for)e(you)h(\(there')-5 +b(s)19 b(no)h(passw)o(ord)g(reminders)e(for)i(list)h(o)n(wners\).)0 +4717 y(If)h(you)f(w)o(ant)h(to)h(dele)o(gate)d(list)j(moderation)d(to)j +(someone)d(else,)j(you)f(can)f(enter)h(a)h(dif)n(ferent)d(moderator)g +(passw)o(ord)h(in)i(the)f(\002eld)g(on)0 4816 y(the)k(right)e(\(typed)h +(twice)g(for)g(con\002rmation\).)39 b(Note)25 b(that)h(if)g(you)e +(aren')o(t)g(going)h(to)g(dele)o(gate)f(moderation,)h(and)f(the)i(same) +g(people)0 4916 y(are)19 b(going)f(to)h(both)f(con\002gure)f(the)i +(list)i(and)d(moderate)g(postings)g(to)h(the)g(list,)i(don')o(t)c +(enter)i(an)o(ything)e(into)h(the)h(moderator)e(passw)o(ord)0 +5016 y(\002elds.)24 b(If)17 b(you)e(do)i(enter)f(a)h(separate)f +(moderator)f(passw)o(ord,)h(be)h(sure)f(to)h(\002ll)g(in)g(the)g +Ff(moderator)e Fo(v)n(ariable)h(in)h(the)f Fj(Gener)o(al)h(options)0 +5115 y Fo(cate)o(gory)h(page.)p 0 5549 3901 4 v 0 5649 +a Fg(8)2658 b(2)84 b(The)23 b(List)g(Con\002gur)o(ation)h(P)m(ages)p +eop end +%%Page: 9 9 +TeXDict begin 9 8 bop 0 83 a Fk(2.3)100 b(The)28 b(Language)j(Options)d +(Categor)s(y)0 286 y Fo(Mailman)22 b(is)i(multilingual)e(and)g +(internationalized,)f(meaning)h(you)g(can)h(set)g(up)g(your)f(list)i +(so)f(that)g(members)f(can)h(interact)g(with)g(it)0 386 +y(in)d(an)o(y)g(of)g(a)g(number)f(of)h(natural)f(languages.)k(Of)e +(course,)e(Mailman)g(w)o(on')o(t)h(translate)g(list)h(postings.)j(:\))0 +532 y(Ho)n(we)n(v)o(er)m(,)18 b(if)i(your)f(site)h(administrator)e(has) +j(enabled)d(its)j(support,)d(you)h(can)h(set)h(your)d(list)j(up)f(to)g +(support)e(an)o(y)h(of)h(about)f(tw)o(o)h(dozen)0 632 +y(languages,)i(such)h(as)g(German,)g(Italian,)g(Japanese,)g(or)f +(Spanish.)33 b(Y)-9 b(our)22 b(list)i(members)e(can)h(then)f(choose)g +(an)o(y)g(of)h(your)f(supported)0 732 y(languages)27 +b(as)i(their)g Fj(pr)m(eferr)m(ed)f(langua)o(g)o(e)e +Fo(for)i(interacting)f(with)i(the)g(list.)51 b(Such)28 +b(things)g(as)h(their)f(member)f(options)h(page)g(will)0 +831 y(be)f(displayed)e(in)i(this)g(language.)43 b(Each)26 +b(mailing)g(list)i(also)f(has)g(its)h(o)n(wn)e Fj(pr)m(eferr)m(ed)h +(langua)o(g)o(e)d Fo(which)i(is)i(the)f(language)e(the)h(list)0 +931 y(supports)19 b(if)i(no)e(other)h(language)e(conte)o(xt)h(is)i(kno) +n(wn.)0 1078 y(These)f(v)n(ariables)f(control)g(the)i(language)d +(settings)i(for)g(your)f(mailing)g(list:)0 1308 y Fl(pr)o(eferr)o(ed)p +345 1308 25 4 v 28 w(language)40 b Fo(This)20 b(is)h(the)f(list')-5 +b(s)22 b(preferred)17 b(language,)i(which)g(is)i(the)f(language)e(that) +j(the)f(list)h(administrati)n(v)o(e)d(pages)i(will)208 +1407 y(be)e(displayed)f(in.)25 b(Also)19 b(an)o(y)e(messages)i(sent)g +(to)f(the)h(list)h(o)n(wners)d(by)h(Mailman)g(will)i(be)e(sent)h(in)f +(this)h(language.)k(This)c(option)208 1507 y(is)i(presented)e(as)h(a)h +(drop-do)n(wn)c(list)k(containing)e(the)h(language)e(enabled)h(in)i +(the)f Ff(available_languages)d Fo(v)n(ariable.)0 1673 +y Fl(a)n(v)o(ailable)p 322 1673 V 28 w(languages)40 b +Fo(This)23 b(set)g(of)f(checkbox)o(es)d(contains)j(all)h(the)f(natural) +f(languages)g(that)h(your)f(site)i(administrator)e(has)h(made)208 +1773 y(a)n(v)n(ailable)g(to)h(your)f(mailing)h(lists.)35 +b(Select)23 b(an)o(y)f(language)g(that)h(you')l(d)e(either)i(lik)o(e)g +(your)f(members)g(to)h(be)g(able)g(to)h(vie)n(w)f(the)208 +1872 y(list)e(in,)f(or)g(that)g(you')l(d)e(lik)o(e)j(to)f(be)g(able)g +(to)h(use)f(in)h(your)d(list')-5 b(s)22 b Ff(preferred_language)c +Fo(v)n(ariable.)0 2038 y Fl(encode)p 250 2038 V 29 w(ascii)p +436 2038 V 30 w(pr)o(e\002xes)41 b Fo(If)21 b(your)f(mailing)h(list')-5 +b(s)23 b(preferred)c(language)g(uses)j(a)g(non-ASCII)e(character)g(set) +i(and)f(the)h Ff(subject_-)208 2138 y(prefix)d Fo(contains)h(non-ASCII) +f(characters,)g(the)h(pre\002x)f(will)i(al)o(w)o(ays)g(be)f(encoded)f +(according)f(to)i(the)h(rele)n(v)n(ant)e(standards.)208 +2238 y(Ho)n(we)n(v)o(er)m(,)26 b(if)i(your)e(subject)h(pre\002x)f +(contains)h(only)f(ASCII)h(characters,)h(you)e(may)h(w)o(ant)g(to)h +(set)g(this)f(option)f(to)i Fj(Ne)o(ver)f Fo(to)208 2337 +y(disable)c(pre\002x)g(encoding.)34 b(This)24 b(can)g(mak)o(e)f(the)h +(subject)g(headers)f(slightly)g(more)g(readable)g(for)g(users)h(with)g +(mail)g(readers)208 2437 y(that)c(don')o(t)e(properly)g(handle)h +(non-ASCII)g(encodings.)208 2570 y(Note)k(ho)n(we)n(v)o(er)m(,)f(that)i +(if)g(your)e(mailing)h(list)i(recei)n(v)o(es)e(both)g(encoded)f(and)h +(unencoded)e(subject)i(headers,)h(you)e(might)h(w)o(ant)208 +2669 y(to)h(choose)f Fj(As)i(needed)p Fo(.)35 b(Using)24 +b(this)g(setting,)h(Mailman)e(will)i(not)f(encode)e(ASCII)j(pre\002x)o +(es)e(when)g(the)h(rest)h(of)f(the)g(header)208 2769 +y(contains)k(only)f(ASCII)i(characters,)h(b)n(ut)f(if)g(the)f(original) +g(header)g(contains)f(non-ASCII)h(characters,)h(it)h(will)f(encode)f +(the)208 2869 y(pre\002x.)50 b(This)30 b(a)n(v)n(oids)f(an)g(ambiguity) +e(in)i(the)g(standards)g(which)f(could)g(cause)h(some)g(mail)g(readers) +g(to)g(display)g(e)o(xtra,)h(or)208 2968 y(missing)20 +b(spaces)g(between)f(the)i(pre\002x)e(and)h(the)g(original)f(header)-5 +b(.)0 3253 y Fk(2.4)100 b(The)28 b(Membership)i(Management)g(Categor)s +(y)0 3456 y Fo(The)21 b Fj(Member)o(ship)h(Mana)o(g)o(ement)e +Fo(cate)o(gory)g(is)i(unlik)o(e)f(the)h(other)f(administrati)n(v)o(e)f +(cate)o(gories.)28 b(It)22 b(doesn')o(t)f(contain)f(con\002guration)0 +3556 y(v)n(ariables)h(or)g(list)h(settings.)29 b(Instead,)21 +b(it)h(presents)f(a)h(number)e(of)h(pages)g(that)g(allo)n(w)h(you)e(to) +i(manage)e(the)i(membership)d(of)i(you)g(list.)0 3655 +y(This)27 b(includes)g(pages)f(for)h(subscribing)e(and)i(unsubscribing) +d(members,)k(and)e(for)h(searching)f(for)g(members,)i(and)e(for)h +(changing)0 3755 y(v)n(arious)19 b(member)n(-speci\002c)g(settings.)0 +3902 y(More)h(details)g(on)g(membership)e(management)g(are)i(described) +f(in)h(the)h(Membership)d(Management)g(section.)0 4187 +y Fk(2.5)100 b(The)28 b(Non-digest)i(Options)e(Categor)s(y)0 +4389 y Fo(Mailman)19 b(deli)n(v)o(ers)g(messages)i(to)f(users)g(via)g +(tw)o(o)g(modes.)k(List)d(members)e(can)h(elect)g(to)g(recei)n(v)o(e)f +(postings)g(in)i(b)n(undles)e(call)h Fj(dig)o(ests)0 +4489 y Fo(one)i(or)h(a)g(fe)n(w)f(times)h(a)g(day)-5 +b(,)23 b(or)f(the)o(y)g(can)g(recei)n(v)o(e)g(messages)h(immediately)e +(whene)n(v)o(er)g(the)h(message)h(is)g(posted)f(to)h(the)g(list.)33 +b(This)0 4589 y(latter)19 b(deli)n(v)o(ery)e(mode)h(is)i(also)f(called) +f Fj(non-dig)o(est)f(delivery)p Fo(.)25 b(There)18 b(are)g(tw)o(o)h +(administrati)n(v)o(e)e(cate)o(gories)h(a)n(v)n(ailable)g(for)g +(separately)0 4688 y(controlling)g(digest)i(and)g(non-digest)e(deli)n +(v)o(ery)-5 b(.)23 b(Y)-9 b(ou)20 b(can)g(e)n(v)o(en)f(disable)h(one)f +(or)h(the)g(other)g(forms)f(of)h(deli)n(v)o(ery)f(\(b)n(ut)g(not)h +(both\).)0 4835 y(Both)i(kinds)g(of)g(deli)n(v)o(ery)f(can)h(ha)n(v)o +(e)g(list-speci\002c)h(headers)e(and)h(footers)f(added)g(to)i(them)f +(which)g(can)g(contain)f(other)h(useful)g(infor)n(-)0 +4935 y(mation)c(you)h(w)o(ant)g(your)f(list)i(members)e(to)h(see.)26 +b(F)o(or)18 b(e)o(xample,)g(you)g(can)h(include)g(instructions)f(for)g +(unsubscribing,)f(or)i(a)g(url)g(to)h(the)0 5034 y(lists)i(digest,)d +(or)h(an)o(y)g(other)f(information.)0 5181 y(Non-digest)28 +b(deli)n(v)o(eries)h(can)h(also)g(be)f Fj(per)o(sonalized)g +Fo(which)g(means)h(certain)f(parts)h(of)f(the)h(message)g(can)f +(contain)g(information)0 5281 y(tailored)c(to)g(the)h(member)e(recei)n +(ving)g(the)h(message.)40 b(F)o(or)25 b(e)o(xample,)h(the)f +Fh(T)-9 b(o:)35 b Fo(header)24 b(will)j(contain)d(the)h(address)g(of)h +(the)f(member)p 0 5549 3901 4 v 0 5649 a Fg(2.3)83 b(The)24 +b(Language)g(Options)f(Categor)r(y)2449 b(9)p eop end +%%Page: 10 10 +TeXDict begin 10 9 bop 0 83 a Fo(when)21 b(deli)n(v)o(eries)f(are)i +(personalized.)k(F)o(ooters)21 b(and)g(headers)g(can)g(contain)f +(personalized)g(information)f(as)j(well,)g(such)f(as)h(a)g(link)f(to)0 +183 y(the)f(indi)n(vidual)f(user')-5 b(s)20 b(options)f(page.)0 +330 y(In)33 b(addition,)j(personalized)31 b(messages)j(will)h(contain)d +(e)o(xtra)h(information)e(that)j(Mailman)f(can)g(use)h(to)g +(unambiguously)c(track)0 429 y(bounces)c(from)g(members.)45 +b(Ordinarily)-5 b(,)27 b(Mailman)f(does)h(some)g(pattern)g(recognition) +e(on)h(bounce)g(messages)h(to)h(determine)d(list)0 529 +y(members)18 b(whose)g(addresses)g(are)h(no)f(longer)g(v)n(alid,)g(b)n +(ut)h(because)f(of)g(the)h(v)n(agaries)e(of)i(mail)f(systems,)i(and)e +(the)h(countless)f(forw)o(ards)0 628 y(people)23 b(can)h(put)g(in)g +(place,)h(it')-5 b(s)25 b(often)e(the)h(case)h(that)f(bounce)e +(messages)j(don')o(t)d(contain)h(an)o(y)g(useful)h(information)e(in)i +(them.)36 b(Per)n(-)0 728 y(sonalized)25 b(messages)i(a)n(v)n(oid)f +(this)g(problem)f(by)h(encoding)e(information)g(in)i(certain)g(headers) +f(that)i(unambiguously)22 b(identify)k(the)0 828 y(recipient)19 +b(of)h(a)h(message.)k(If)20 b(that)g(message)g(bounces,)e(Mailman)i +(will)h(kno)n(w)e(e)o(xactly)g(which)h(member)f(it)i(w)o(as)g(intended) +d(for)-5 b(.)0 975 y(Note)21 b(that)g(because)g(personalization)e +(requires)h(e)o(xtra)h(system)g(resources,)f(it)i(must)f(be)g(enabled)f +(by)h(the)g(site)h(administrator)e(before)0 1074 y(you)f(can)h(choose)g +(it.)0 1221 y(Here)g(are)g(the)g(v)n(ariables)g(which)f(control)g +(non-digest)g(deli)n(v)o(ery:)0 1451 y Fl(nondigestable)41 +b Fo(This)29 b(option)f(controls)g(whether)g(members)h(can)g(recei)n(v) +o(e)f(immediate)g(deli)n(v)o(ery)g(or)g(not.)52 b(If)29 +b(not,)i(the)o(y)e(will)h(be)208 1551 y(forced)18 b(to)j(recei)n(v)o(e) +e(messages)h(in)g(digests.)26 b(Y)-9 b(ou)19 b(can')o(t)g(disable)h +(non-digest)f(deli)n(v)o(ery)f(if)j(digests)f(are)g(already)f +(disabled.)0 1717 y Fl(personalize)41 b Fo(This)20 b(option)f(turns)h +(on)g(message)g(personalization.)0 1883 y Fl(msg)p 148 +1883 25 4 v 30 w(header)41 b Fo(This)21 b(te)o(xt)f(box)g(lets)h(you)f +(enter)g(information)f(that)h(will)i(be)e(included)f(in)i(the)g(header) +e(of)i(e)n(v)o(ery)e(non-digest)g(message)208 1982 y(sent)h(through)e +(the)i(list.)208 2115 y(See)h(belo)n(w)f(for)g(more)g(information)e(on) +i(what)h(can)g(go)f(in)h(the)f(headers)g(and)g(footers.)26 +b(If)21 b(you)e(lea)n(v)o(e)i(this)g(te)o(xt)g(box)f(empty)-5 +b(,)19 b(no)208 2215 y(header)g(will)h(be)h(added.)0 +2381 y Fl(msg)p 148 2381 V 30 w(f)n(ooter)39 b Fo(Just)20 +b(lik)o(e)f(with)h(the)f(header)m(,)e(you)h(can)h(add)g(a)g(footer)f +(to)h(e)n(v)o(ery)f(message.)24 b(The)19 b(same)g(rules)g(apply)f(to)i +(footers)e(as)i(apply)208 2480 y(to)g(headers.)0 2710 +y(Headers)26 b(and)h(footers)e(can)i(contain)f(an)o(y)g(te)o(xt)g(you)g +(w)o(ant.)45 b(F)o(or)26 b(non-English)f(lists,)k(the)e(headers)f(and)g +(footers)g(can)h(contain)e(an)o(y)0 2810 y(character)g(in)h(the)g +(character)e(set)j(of)f(the)g(list')-5 b(s)27 b(preferred)d(language.) +40 b(The)26 b(headers)f(and)g(footers)h(can)f(also)i(contain)d +Fj(substitution)0 2910 y(variables)f Fo(which)h(Mailman)f(will)h +(\002ll)h(in)f(with)g(information)d(tak)o(en)i(from)g(the)h(mailing)f +(list.)36 b(These)24 b(substitutions)f(are)h(in)g(Python)0 +3009 y(string)f(interpolation)e(format,)h(where)h(something)f(lik)o(e)h +Ff(\045\(list_name\)s)e Fo(is)k(substituted)d(with)i(he)f(name)f(of)h +(the)g(mailing)g(list.)0 3109 y(Note)d(that)g(the)h(trailing)e(`)p +Ff(s)p Fo(')h(is)h(required)1191 3079 y Fe(2)1222 3109 +y Fo(.)0 3256 y(F)o(or)f(e)o(xample,)e(a)j(footer)e(containing)f(the)i +(follo)n(wing)f(te)o(xt:)236 3494 y Fb(This)44 b(is)h(the)f +(\\\045\(list_name\)s)f(mailing)g(list)236 3585 y(Description:)g +(\\\045\(description\)s)0 3872 y Fo(might)20 b(get)g(attached)f(to)h +(postings)g(lik)o(e)g(so:)236 4110 y Fb(This)44 b(is)h(the)f(Example)g +(mailing)g(list)236 4201 y(Description:)f(An)i(example)e(of)i(Mailman)e +(mailing)h(lists)0 4488 y Fo(Here)20 b(is)h(the)f(list)i(of)e +(substitution)f(v)n(ariables)g(a)n(v)n(ailable)h(for)g(your)f(headers)g +(and)g(footers:)0 4718 y Fl(r)o(eal)p 143 4718 V 29 w(name)41 +b Fo(This)20 b(is)h(the)g(v)n(alue)e(of)h(the)g Ff(real_name)f +Fo(con\002guration)f(v)n(ariable)h(in)h(the)g(General)g(options)f(cate) +o(gory)-5 b(.)0 4884 y Fl(list)p 111 4884 V 30 w(name)41 +b Fo(This)21 b(is)g(the)f(canonical)f(name)g(of)h(the)g(mailing)g +(list.)26 b(In)20 b(other)f(w)o(ords)h(it')-5 b(s)21 +b(the)g(posting)e(address)h(of)f(the)i(list)3509 4854 +y Fe(3)3542 4884 y Fo(.)0 5050 y Fl(host)p 153 5050 V +29 w(name)42 b Fo(This)20 b(is)h(the)f(domain)f(name)h(part)g(of)g(the) +g(email)g(address)g(for)f(this)i(list.)p 0 5121 1560 +4 v 90 5176 a Fd(2)120 5200 y Fc(The)15 b(site)h(administrator)i(can)e +(con\002gure)h(lists)f(to)f(use)h(a)f(simpler)h(interpolation)k +(format,)15 b(where)i Fa($list_name)c Fc(or)i Fa(${list_name})e +Fc(w)o(ould)k(be)e(substituted)0 5279 y(with)j(the)f(mailing)i(list')l +(s)f(name.)j(Ask)c(your)g(site)h(administrator)i(if)d(the')m(v)o(e)h +(con\002gured)h(your)e(list)h(this)g(w)o(ay)l(.)90 5336 +y Fd(3)120 5360 y Fc(F)o(or)e(backw)o(ard)k(compatibility)l(,)g(the)d +(v)n(ariable)j Fa(_internal_name)15 b Fc(is)i(equi)n(v)n(alent.)p +0 5549 3901 4 v 0 5649 a Fg(10)2612 b(2)84 b(The)23 b(List)g +(Con\002gur)o(ation)h(P)m(ages)p eop end +%%Page: 11 11 +TeXDict begin 11 10 bop 0 83 a Fl(web)p 148 83 25 4 v +30 w(page)p 345 83 V 29 w(url)41 b Fo(This)16 b(is)g(the)f(base)h(url)f +(for)g(contacting)e(the)j(list)g(via)g(the)f(web)m(.)23 +b(It)15 b(can)g(be)h(appended)d(with)i Ff(listinfo/\045\(list_-)208 +183 y(name\)s)k Fo(to)i(yield)e(the)i(general)e(list)i(information)d +(page)h(for)h(the)g(mailing)f(list.)0 346 y Fl(description)41 +b Fo(The)20 b(brief)g(description)e(of)i(the)g(mailing)g(list.)0 +508 y Fl(inf)n(o)41 b Fo(This)20 b(is)h(the)g(full)f(description)e(of)i +(the)g(mailing)g(list.)0 671 y Fl(cgiext)40 b Fo(This)23 +b(is)h(the)f(e)o(xtension)e(added)h(to)h(CGI)h(scripts.)33 +b(It)23 b(might)f(be)h(the)g(empty)f(string,)h Ff(.cgi)p +Fo(,)g(or)g(something)f(else)h(depending)208 771 y(on)c(ho)n(w)h(your)f +(site)i(is)g(con\002gured.)0 993 y(Note)k(that)h Ff(real_name)p +Fo(,)f Ff(host_name)p Fo(,)g Ff(description)p Fo(,)g(and)g +Ff(info)g Fo(substitution)f(v)n(ariables)h(tak)o(e)g(their)g(v)n(alues) +g(from)g(the)0 1093 y(list)c(con\002guration)d(v)n(ariables)h(of)h(the) +g(same)h(name.)0 1240 y(When)f(personalization)e(is)j(enabled,)e(the)h +(follo)n(wing)f(substitution)g(v)n(ariables)g(are)h(also)h(a)n(v)n +(ailable:)0 1462 y Fl(user)p 157 1462 V 30 w(addr)o(ess)41 +b Fo(The)20 b(address)g(of)g(the)g(recipient)f(of)h(the)g(message,)g +(coerced)f(to)h(lo)n(wer)g(case.)0 1625 y Fl(user)p 157 +1625 V 30 w(deli)o(v)o(er)o(ed)p 512 1625 V 29 w(to)41 +b Fo(The)20 b(case-preserv)o(ed)d(address)j(that)h(the)f(user)g +(subscribed)f(to)h(the)g(mailing)g(list)h(with)3134 1594 +y Fe(4)3167 1625 y Fo(.)0 1787 y Fl(user)p 157 1787 V +30 w(passw)o(ord)41 b Fo(The)20 b(user')-5 b(s)21 b(passw)o(ord,)e(in)h +(clear)g(te)o(xt.)0 1950 y Fl(user)p 157 1950 V 30 w(name)41 +b Fo(The)20 b(user')-5 b(s)21 b(full)f(name.)0 2113 y +Fl(user)p 157 2113 V 30 w(optionsurl)41 b Fo(The)20 b(url)g(to)g(the)g +(user')-5 b(s)21 b(personal)e(options)g(page.)0 2397 +y Fk(2.6)100 b(The)28 b(Digest)g(Options)g(Categor)s(y)0 +2600 y Fo(Digest)d(deli)n(v)o(ery)d(is)j(a)g(w)o(ay)f(to)g(b)n(undle)f +(man)o(y)g(articles)i(together)e(into)h(one)f(package,)h(which)f(can)h +(be)g(deli)n(v)o(ered)f(once)g(per)h(day)g(\(if)0 2699 +y(there)e(were)g(an)o(y)g(posted)g(articles\),)g(or)g(whene)n(v)o(er)f +(the)h(package)f(is)i(bigger)e(than)h(a)h(speci\002ed)f(limit.)32 +b(Some)22 b(users)h(may)f(prefer)f(this)0 2799 y(style)g(of)e(deli)n(v) +o(ery)g(for)h(higher)e(traf)n(\002c)i(lists)i(since)e(the)o(y)g(will)h +(recei)n(v)o(e)e(fe)n(wer)g(messages.)0 2946 y(Mailman)k(supports)f(tw) +o(o)i(standard)e(digest)i(formats,)f(and)g(if)g(digests)h(are)f +(enabled,)g(users)h(can)f(select)h(which)f(of)g(the)h(tw)o(o)f(formats) +0 3045 y(the)o(y)g(recei)n(v)o(e.)33 b(One)23 b(is)h(MIME)f(digests,)h +(where)f(each)f(message)i(is)g(an)f(attachment)f(inside)h(a)h +Fh(m)o(ultipar)s(t/digest)p Fo(.)31 b(This)23 b(format)f(also)0 +3145 y(contains)16 b(a)h(summary)e(table)i(of)f(contents,)g(and)g(of)h +(course)f(the)g(an)h(optional)e(header)g(and)h(footer)m(,)g(and)g(it)h +(retains)g(most)g(of)f(the)g(headers)0 3245 y(of)k(the)g(original)f +(messages.)0 3392 y(The)30 b(second)e(type)i(is)h(called)e(\223plainte) +o(xt\224)g(digests)h(because)f(the)o(y)g(are)h(readable)f(in)h(mail)g +(readers)f(that)h(don')o(t)e(support)g(MIME.)0 3491 y(Actually)-5 +b(,)21 b(the)o(y)g(adhere)g(to)h(the)f(RFC)j(1153)c(digest)i(standard.) +28 b(The)21 b(retain)h(some,)g(b)n(ut)f(not)h(all)g(of)g(the)f +(original)g(messages,)h(b)n(ut)g(can)0 3591 y(also)f(include)e(a)h +(summary)f(and)h(headers)f(and)h(footers.)0 3738 y(Lik)o(e)g +(non-digest)e(deli)n(v)o(ery)-5 b(,)18 b(you)h(can)h(enable)f(or)h +(disable)f(digest)h(deli)n(v)o(ery)-5 b(,)18 b(b)n(ut)i(you)f(cannot)g +(disable)h(both)f(types)h(of)f(deli)n(v)o(ery)-5 b(.)23 +b(Y)-9 b(ou)0 3837 y(can)17 b(specify)g(dif)n(ferent)f(headers)h(and)g +(footers)g(for)g(digest)g(and)h(non-digest)d(deli)n(v)o(eries.)23 +b(Y)-9 b(ou)17 b(cannot)g(personalize)f(digest)i(deli)n(v)o(eries.)0 +3984 y(As)33 b(list)g(administrator)m(,)f(you)f(may)h(w)o(ant)g(to)g +(send)f(an)h(ur)o(gent)e(message)i(to)g(all)g(list)h(members,)h +(bypassing)c(the)i(normal)f(digest)0 4084 y(b)n(undling.)25 +b(T)-7 b(o)21 b(do)g(this,)g(send)g(the)g(message)g(with)g(a)g +Fh(Urgent:)26 b Fo(header)m(,)19 b(where)h(the)h(v)n(alue)g(of)f(the)h +(header)f(is)i(the)f(list)h(administrator')-5 b(s)0 4183 +y(passw)o(ord.)41 b(Non-digest)24 b(members)g(will)j(recei)n(v)o(e)d +(the)i(message)f(lik)o(e)h(normal,)g(b)n(ut)f(digest)h(members)e(will)j +(recei)n(v)o(e)d(the)i(message)0 4283 y(immediately)417 +4253 y Fe(5)448 4283 y Fo(.)0 4430 y(Here)20 b(are)g(the)g(v)n +(ariables)g(which)f(control)g(digest)h(deli)n(v)o(ery:)0 +4652 y Fl(digestable)41 b Fo(The)24 b(option)g(controls)g(whether)g +(members)g(can)h(recei)n(v)o(e)e(digest)i(deli)n(v)o(eries)f(or)h(not.) +39 b(If)25 b(not,)g(the)o(y)f(will)i(be)f(forced)e(to)208 +4752 y(recei)n(v)o(e)c(immediate)g(deli)n(v)o(eries.)24 +b(Y)-9 b(ou)19 b(can')o(t)h(disable)g(digests)g(if)h(non-digests)d(are) +i(already)f(disabled.)0 4915 y Fl(digest)p 213 4915 V +29 w(is)p 297 4915 V 31 w(default)40 b Fo(Controls)27 +b(which)g(style)g(of)g(deli)n(v)o(ery)f(is)i(the)f(def)o(ault)f(for)h +(ne)n(w)g(members.)44 b(Y)-9 b(ou)27 b(can)g(choose)f +Fj(Re)m(gular)g Fo(\(non-)208 5014 y(digest\))19 b(or)h +Fj(Dig)o(est)h Fo(deli)n(v)o(ery)-5 b(.)p 0 5082 1560 +4 v 90 5138 a Fd(4)120 5161 y Fc(Usually)19 b(it)f(mak)o(es)h(no)f(dif) +n(ference)j(which)d(of)g Fa(user_address)e Fc(and)i Fa +(user_delivered_to)d Fc(is)j(used,)g(b)o(ut)g(it')l(s)h(important)h(to) +e(remember)h(that)g(the)o(y)g(can)0 5240 y(be)d(dif)n(ferent.)23 +b(When)16 b(the)o(y')m(re)h(dif)n(ferent,)h(Mailman)f(al)o(w)o(ays)h +(uses)d(the)i(lo)n(wer)g(case)f(address)h(as)e(the)i(k)o(e)o(y)f(to)g +(the)h(member')l(s)f(subscription)i(information,)g(b)o(ut)e(it)g(al)o +(w)o(ays)0 5319 y(deli)n(v)o(ers)j(messages)f(to)f(the)h(case-preserv)o +(ed)i(v)o(ersion.)90 5377 y Fd(5)120 5400 y Fc(The)o(y')o(ll)e(also)g +(recei)n(v)o(e)h(the)f(message)g(in)f(the)h(digest.)p +0 5549 3901 4 v 0 5649 a Fg(2.6)83 b(The)24 b(Digest)f(Options)g +(Categor)r(y)2537 b(11)p eop end +%%Page: 12 12 +TeXDict begin 12 11 bop 0 83 a Fl(mime)p 203 83 25 4 +v 30 w(is)p 288 83 V 30 w(default)p 568 83 V 29 w(digest)41 +b Fo(If)26 b(a)g(member)e(is)i(allo)n(wed)f(to)g(choose)g(digests,)i +(this)e(v)n(ariable)g(controls)f(which)h(is)i(the)e(def)o(ault)g +(digest)208 183 y(style)20 b(the)o(y)g(will)h(recei)n(v)o(e.)i +Fj(Plain)d Fo(digests)g(are)h(RFC)g(1153)e(format)g(as)i(described)e +(abo)o(v)o(e.)0 333 y Fl(digest)p 213 333 V 29 w(size)p +371 333 V 30 w(thr)o(eshold)41 b Fo(Normally)-5 b(,)24 +b(digest)g(members)f(get)h(at)h(least)g(one)f(message)g(per)g(day)-5 +b(,)24 b(if)h(there)f(ha)n(v)o(e)f(been)h(an)o(y)f(messages)208 +432 y(posted)18 b(to)i(the)g(list.)25 b(Ho)n(we)n(v)o(er)m(,)18 +b(for)h(high)f(v)n(olume)h(lists,)i(you)d(may)h(w)o(ant)h(to)g(send)f +(out)g(digests)h(when)f(the)g(size)h(has)g(reached)e(a)208 +532 y(certain)h(threshold,)f(otherwise,)h(the)h(one)f(digest)g(the)o(y) +h(recei)n(v)o(e)e(could)h(be)h(huge.)j(This)d(v)n(ariable)f(controls)g +(the)h(size)g(threshold)208 632 y(by)e(specifying)e(the)j(maximum)d +(digest)j(size)g(in)f(kilobytes.)24 b(Note)18 b(that)h(this)f +(threshold)f(isn')o(t)h(e)o(xact.)24 b(Set)19 b(this)g(v)n(ariable)f +(to)g(zero)208 731 y(to)i(specify)f(that)i(there)e(is)j(no)d(size)i +(threshold,)e(in)h(which)g(case)g(no)g(more)f(than)h(one)g(digest)g +(will)h(be)f(sent)g(out)g(per)g(day)-5 b(.)0 882 y Fl(digest)p +213 882 V 29 w(send)p 403 882 V 31 w(periodic)41 b Fo(This)20 +b(v)n(ariable)f(actually)h(controls)f(whether)h(or)g(not)f(a)i(digest)f +(is)h(sent)g(daily)f(when)f(the)i(size)g(threshold)d(has)208 +981 y(not)27 b(yet)h(been)g(met.)48 b(If)28 b(set)h(to)f +Fj(No)p Fo(,)i(then)d(digests)i(will)f(only)f(be)h(sent)h(when)e(the)o +(y)g(are)h(bigger)f(than)g Ff(digest_size_-)208 1081 +y(threshold)p Fo(.)0 1231 y Fl(digest)p 213 1231 V 29 +w(header)41 b Fo(This)26 b(te)o(xt)g(box)f(lets)i(you)d(enter)i +(information)d(that)j(will)h(be)e(included)g(in)h(the)f(header)g(of)h +(e)n(v)o(ery)e(digest)i(message)208 1331 y(sent)20 b(through)e(the)h +(list.)26 b(The)20 b(same)g(information)e(can)h(go)h(in)g(this)g +(header)f(as)i(can)e(go)h(in)g(the)g Ff(msg_header)p +Fo(,)e(e)o(xcept)h(for)h(the)208 1430 y(personalization)e(v)n +(ariables.)0 1581 y Fl(digest)p 213 1581 V 29 w(f)n(ooter)40 +b Fo(Just)20 b(lik)o(e)g(with)g(the)g(header)m(,)e(you)g(can)i(add)f(a) +h(footer)e(to)i(e)n(v)o(ery)e(message.)25 b(The)19 b(same)h(rules)g +(apply)e(to)i(digest)f(footers)208 1680 y(as)h(apply)g(to)g(digest)g +(headers.)0 1830 y Fl(digest)p 213 1830 V 29 w(v)o(olume)p +500 1830 V 30 w(fr)o(equency)40 b Fo(Each)23 b(digest)h(is)i(numbered) +21 b(with)j(a)h(v)n(olume)e(and)h(an)g(issue.)37 b(This)24 +b(v)n(ariable)f(controls)g(ho)n(w)h(often)f(a)208 1930 +y(ne)n(w)d(digest)g(v)n(olume)f(is)i(sent.)k(When)20 +b(the)g(digest)g(v)n(olume)g(number)e(is)j(incremented,)d(the)i(issue)h +(number)d(is)k(reset)e(to)g(1.)p 5 2080 V 30 2080 a Fl(new)p +178 2080 V 30 w(v)o(olume)41 b Fo(This)21 b(is)h(an)g(action)e(v)n +(ariable,)g(which)h(forces)g(an)g(increment)f(of)h(the)g(v)n(olume)f +(number)g(as)i(soon)e(as)i(you)f(submit)g(the)208 2180 +y(form.)p 5 2330 V 30 2330 a Fl(send)p 196 2330 V 30 +w(digest)p 434 2330 V 30 w(no)o(w)41 b Fo(This)22 b(is)g(another)f +(action)g(v)n(ariable.)28 b(Select)22 b Fj(Y)-8 b(es)p +Fo(,)23 b(submit)f(the)f(form,)g(and)g(the)h(current)e(digest)i(is)g +(packaged)e(up)208 2430 y(and)f(sent)i(to)f(digest)g(members,)f(re)o +(gardless)g(of)h(size)g(\(well,)h(there)e(has)i(to)f(be)g(at)h(least)g +(one)e(message)h(in)h(the)f(digest\).)0 2708 y Fk(2.7)100 +b(The)28 b(Pr)q(iv)n(acy)h(Options)f(Categor)s(y)0 2910 +y Fo(The)21 b(Pri)n(v)n(ac)o(y)e(cate)o(gory)g(lets)j(you)e(control)g +(ho)n(w)g(much)g(of)h(the)f(list')-5 b(s)23 b(information)18 +b(is)k(public,)e(as)i(well)f(as)h(who)e(can)h(send)f(messages)0 +3010 y(to)e(your)f(list.)25 b(It)19 b(also)f(contains)f(some)h(spam)g +(detection)f(\002lters.)25 b(Note)18 b(that)g(this)h(section)f(is)h +(not)e(used)h(to)g(control)f(whether)g(your)g(list')-5 +b(s)0 3110 y(archi)n(v)o(es)19 b(are)h(public)f(or)h(pri)n(v)n(ate;)g +(for)f(that,)h(use)h(the)f Fl(??)g Fo(cate)o(gory)-5 +b(.)0 3257 y(There)19 b(are)h(four)g(sub-cate)o(gories:)125 +3438 y Fi(\017)41 b Fo(Subscription)18 b(rules)i(\226)g(i.e.)26 +b(the)20 b(rules)g(for)g(joining)f(and)g(lea)n(ving)h(your)f(mailing)g +(list)125 3588 y Fi(\017)41 b Fo(Sender)19 b(\002lters)i(\226)f(the)g +(rules)g(for)g(who)g(may)f(post)i(messages)f(to)g(your)f(list)125 +3739 y Fi(\017)41 b Fo(Recipient)20 b(\002lters)g(\226)h(moderation)d +(rules)i(based)g(on)f(the)i(recipient)e(of)h(the)g(message)125 +3889 y Fi(\017)41 b Fo(Spam)19 b(\002lters)i(\226)g(some)f(re)o(gular)e +(e)o(xpression)h(based)h(rules)g(for)f(header)g(matching)0 +4071 y(The)25 b(sender)m(,)h(recipient,)g(and)g(spam)f(\002ltering)g +(rules)h(are)g(part)f(of)h(the)g(general)e(list)j(moderation)d +(features)h(of)g(Mailman.)42 b(When)25 b(a)0 4170 y(message)c(is)h +(posted)e(to)h(the)g(list,)i(it)e(is)h(matched)e(against)h(a)g(number)e +(of)i(criteria,)g(the)g(outcome)e(of)i(which)g(determines)f(whether)g +(the)0 4270 y(message)g(is)h(re\003ected)f(to)g(the)g(membership)f(or)g +(not.)25 b(In)20 b(general,)f(the)h(outcome)f(is)i(one)e(of)h(four)f +(states:)125 4460 y Fi(\017)41 b Fo(Appro)o(v)o(ed)17 +b(or)j(Accepted)f(\226)h(the)g(message)g(may)g(be)g(sent)h(on)f(to)g +(the)g(members)f(of)h(the)g(mailing)g(list.)125 4610 +y Fi(\017)41 b Fo(Hold)28 b(\226)h(the)g(message)g(will)h(be)e(held)h +(for)f(moderator)f(appro)o(v)n(al.)49 b(The)28 b(list)i(o)n(wners)f +(and)f(moderators)f(will)j(then)e(ha)n(v)o(e)g(to)208 +4710 y(e)o(xplicitly)19 b(appro)o(v)o(e)e(the)k(message)f(before)e(the) +j(list)g(members)e(will)i(see)g(it.)125 4860 y Fi(\017)41 +b Fo(Reject)32 b(\226)f(the)g(message)g(is)i(bounced)c(back)h(to)i(the) +f(original)f(sender)m(,)j(often)d(with)i(a)g(notice)e(containing)g(the) +h(reason)g(the)208 4960 y(message)20 b(w)o(as)h(rejected.)j(The)c(list) +h(members)e(ne)n(v)o(er)g(see)i(rejected)e(messages.)125 +5110 y Fi(\017)41 b Fo(Discard)20 b(\226)g(the)g(message)g(is)h(simply) +f(thro)n(wn)f(a)o(w)o(ay)h(without)f(further)g(processing.)0 +5300 y(Man)o(y)i(of)g(the)h(\002elds)g(in)g(this)h(section)e(are)h(te)o +(xt)g(box)o(es)e(accepting)h(addresses,)g(one)h(per)f(line.)30 +b(Unless)22 b(otherwise)f(noted,)g(these)h(also)0 5400 +y(accept)e(re)o(gular)e(e)o(xpressions)h(which)h(will)h(be)f(matched)f +(against)h(an)g(address,)f(if)i(the)f(line)g(be)o(gins)f(with)i(a)3115 +5381 y(\210)3115 5400 y(\(caret\))f(character)-5 b(.)p +0 5549 3901 4 v 0 5649 a Fg(12)2612 b(2)84 b(The)23 b(List)g +(Con\002gur)o(ation)h(P)m(ages)p eop end +%%Page: 13 13 +TeXDict begin 13 12 bop 0 83 a Fg(Subscr)q(iption)24 +b(r)q(ules)0 286 y Fo(This)c(subcate)o(gory)d(controls)h(the)i(rules)g +(for)f(e)o(xposing)e(the)j(e)o(xistance)f(of)g(this)h(list,)h(and)e +(for)g(what)g(ne)n(w)h(members)e(must)i(do)f(in)h(order)0 +386 y(to)g(subscribe)g(to)g(the)g(list.)0 615 y Fl(adv)o(ertised)41 +b Fo(This)19 b(option)g(controls)f(whether)g(this)i(list)h(will)f(sho)n +(w)f(up)h(in)f(the)h(list)g(o)o(v)o(ervie)n(w)e(for)g(the)i(site.)25 +b(Normally)-5 b(,)18 b(an)i(o)o(v)o(ervie)n(w)208 715 +y(contains)j(the)h(name)f(and)g(short)h(description)e(of)i(e)n(v)o(ery) +f(mailing)g(list)i(in)f(the)g(virtual)f(domain.)35 b(By)24 +b(setting)g(this)h(v)n(ariable)d(to)208 815 y Fj(No)p +Fo(,)g(it)g(will)h(not)e(sho)n(w)g(up)h(in)g(this)g(o)o(v)o(ervie)n(w) +-5 b(,)19 b(nor)i(will)h(it)h(sho)n(w)e(up)h(in)f(the)h(administrati)n +(v)o(e)e(o)o(v)o(ervie)n(w)-5 b(.)27 b(The)21 b(only)g(w)o(ay)h(then) +208 914 y(to)e(\002nd)g(the)g(list)h(is)g(to)g(guess)f(\(or)g(kno)n +(w!\))j(its)e(name.)0 1080 y Fl(subscribe)p 341 1080 +25 4 v 31 w(policy)40 b Fo(This)24 b(option)f(controls)g(the)h(steps)h +(that)f(a)g(ne)n(w)g(member)e(must)i(tak)o(e)g(to)g(join)g(the)g(list.) +37 b(The)24 b(a)n(v)n(ailable)g(options)208 1180 y(may)19 +b(dif)n(fer)g(based)h(on)g(some)g(def)o(aults)g(that)g(the)g(site)h +(administrator)e(chooses.)24 b(The)o(y)19 b(are:)307 +1363 y Fi(\017)41 b Fo(None)23 b(\226)h(No)g(v)o(eri\002cation)e(is)i +(done)f(on)g(the)h(subscribing)e(member)-5 b(.)34 b(This)24 +b(is)h(also)e(called)h Fj(open)f(subscriptions)g Fo(and)g(is)390 +1462 y(generally)f(disabled)g(by)h(def)o(ault.)33 b(The)22 +b(site)i(administrator)e(must)h(allo)n(w)g(list)h(admins)e(to)i(choose) +e(this)h(option;)h(if)f(not,)390 1562 y(this)e(option)e(will)i(not)f +(be)g(presented)f(to)h(you.)307 1695 y Fi(\017)41 b Fo(Con\002rm)21 +b(\226)h(An)f(email)h(con\002rmation)d(step)j(is)g(required)e(before)g +(the)h(address)g(is)i(added)d(to)h(the)h(list.)30 b(When)21 +b(a)h(member)390 1794 y(requests)15 b(subscription,)g(either)g(via)g +(the)g(web)h(page)e(or)i(by)e(sending)h(a)g(message)h(to)f +Fj(yourlist)q Ff(-join@example.com)p Fo(,)390 1894 y(Mailman)h(will)g +(send)g(a)h(con\002rmation)d(message)i(to)g(the)g(requesting)e +(address.)23 b(This)17 b(mail-back)d(con\002rmation)g(contains)390 +1994 y(a)19 b(unique)e(identi\002er)m(,)h(which)g(the)h(requester)e +(can)h(present)g(to)h(Mailman)f(in)h(order)e(to)i(con\002rm)e(their)i +(subscription.)j(This)390 2093 y(can)i(be)f(done)g(either)g(by)g +(replying)f(to)h(the)h(mail-back,)f(or)g(by)g(visiting)g(the)h(url)f +(in)h(the)g(mail-back)e(message.)35 b(The)23 b(url)390 +2193 y(points)d(to)g(a)h(page)e(that)i(lets)g(the)f(user)g(either)g +(discard)f(or)h(con\002rm)f(their)h(request.)307 2326 +y Fi(\017)41 b Fo(Require)27 b(appro)o(v)n(al)f(\226)h(All)i +(subscription)d(requests)h(are)h(held)f(for)g(appro)o(v)n(al)e(of)i +(the)h(list)h(moderator)-5 b(.)45 b(No)28 b(mail-back)390 +2425 y(con\002rmation)18 b(is)j(sent,)g(b)n(ut)f(the)g(list)h(admins)f +(will)h(recie)n(v)o(e)e(a)i(message)f(indicating)e(that)j(appro)o(v)n +(al)d(is)j(pending.)307 2558 y Fi(\017)41 b Fo(Con\002rm)18 +b(and)g(appro)o(v)o(e)e(\226)i(Here,)g(a)h(mail-back)e(notice)h(must)g +(\002rst)i(be)e(con\002rmed)f(by)g(the)i(requester)-5 +b(.)23 b(Once)c(con\002rmed,)390 2658 y(the)26 b(list)h(moderator)c +(must)j(then)f(appro)o(v)o(e)e(the)j(request.)40 b(This)26 +b(is)h(the)f(most)f(secure)g(method)g(for)g(users)h(to)f(subscribe)390 +2757 y(since)c(it)f(both)g(v)o(eri\002es)g(the)g(requesting)f(address,) +g(and)h(forces)f(the)i(list)g(moderators)d(to)i(appro)o(v)o(e)e(the)i +(request.)0 2940 y Fl(unsubscribe)p 433 2940 V 31 w(policy)41 +b Fo(Speci\002es)29 b(whether)e(the)i(list)g(moderator')-5 +b(s)27 b(appro)o(v)n(al)f(is)k(required)c(for)i(unsubscription)e +(requests.)50 b Fj(No)29 b Fo(is)208 3040 y(highly)20 +b(recommended,)e(since)k(it)g(is)h(e)o(xceedingly)c(impolite)i(to)g +(not)g(allo)n(w)h(people)e(to)i(lea)n(v)o(e)f(a)h(mailing)f(list)i +(whene)n(v)o(er)c(the)o(y)208 3139 y(w)o(ant)25 b(\(i.e.)41 +b(opt-out\).)f Fj(Y)-8 b(es)27 b Fo(is)f(useful)f(in)h(some)f +(specialized)g(conte)o(xts;)j(e.g.)41 b(you)24 b(may)i(not)f(w)o(ant)h +(to)f(allo)n(w)h(emplo)o(yees)e(to)208 3239 y(unsubscribe)18 +b(from)h(the)h(compan)o(y)e(ne)n(wsletter)-5 b(.)0 3405 +y Fl(ban)p 139 3405 V 30 w(list)41 b Fo(This)16 b(contains)e(a)i(list)h +(of)e(addresses)g(\(or)f(re)o(gular)g(e)o(xpressiosn\),)h(one)f(per)h +(line,)i(that)e(are)g(banned)f(from)g(e)n(v)o(er)h(subscribing)e(to)208 +3505 y(your)21 b(mailing)g(list.)32 b(If)22 b(a)h(match)f(occurs)f +(during)g(the)h(subscription)f(process,)h(the)g(request)g(will)h(be)f +(automatically)e(rejected,)208 3604 y(and)28 b(the)h(requester)f(will)i +(get)g(a)f(rejection)g(notice.)51 b(Y)-9 b(ou)29 b(can)g(use)g(this)h +(to)f(permanently)e(ban)i(troublesome)e(posters)i(to)g(a)208 +3704 y(members-only)17 b(list.)0 3870 y Fl(pri)o(v)o(ate)p +258 3870 V 29 w(r)o(oster)40 b Fo(This)20 b(speci\002es)h(who)e(is)i +(allo)n(wed)e(to)h(vie)n(w)g(the)g(roster)g(of)g(member)e(addresses.)25 +b(If)20 b(you)f(choose)g Fj(Anyone)p Fo(,)f(then)i(the)208 +3970 y(list)25 b(membership)e(is)j(completely)d(public.)38 +b(Y)-9 b(ou)24 b(can)h(limit)g(e)o(xposure)e(of)i(the)f(roster)h(to)g +(just)g(list)h(members,)f(or)f(just)i(to)f(the)208 4069 +y(list)19 b(administrators.)k(In)c(the)g(former)e(case,)i(a)g(user)g +(must)g(enter)f(a)h(v)n(alid)f(member')-5 b(s)18 b(address)g(and)g +(passw)o(ord)g(before)g(the)o(y)g(can)208 4169 y(vie)n(w)k(the)g +(roster)-5 b(.)32 b(In)23 b(the)f(latter)h(case,)g(a)g(list)h +(administrator')-5 b(s)21 b(passw)o(ord)h(must)g(be)h(enter;)g(if)g(a)g +(matching)e(admin)g(passw)o(ord)208 4268 y(is)g(entered,)e(address)g +(\002eld)i(is)g(ignored.)0 4434 y Fl(obscur)o(e)p 281 +4434 V 29 w(addr)o(esses)41 b Fo(Controls)24 b(whether)f(some)g(simple) +h(obfuscation)e(of)i(addresses)f(is)i(used)f(when)f(member)f(addresses) +i(are)g(in-)208 4534 y(cluded)d(on)h(web)g(pages.)31 +b(This)23 b(should)e(reduce)h(the)g(opportunity)e(for)h(email)i +(address)f(harv)o(esting)e(by)i(spammers,)g(although)208 +4634 y(it)e(probably)e(doesn')o(t)h(eliminate)h(it.)0 +4902 y Fg(Sender)k(\002lters)0 5105 y Fo(When)i(a)h(message)f(is)h +(posted)e(to)h(the)h(list,)h(a)f(series)f(of)g(moderation)e(criteria)i +(are)g(applied)f(to)i(determine)d(the)i(disposition)g(of)g(the)0 +5205 y(message.)f(This)20 b(section)g(contains)g(the)g(modeation)e +(controls)h(for)h(postings)f(from)h(both)f(members)g(and)h +(non-members.)p 0 5549 3901 4 v 0 5649 a Fg(2.7)83 b(The)24 +b(Pr)q(iv)n(acy)e(Options)h(Categor)r(y)2501 b(13)p eop +end +%%Page: 14 14 +TeXDict begin 14 13 bop 0 83 a Fl(default)p 255 83 25 +4 v 29 w(member)p 579 83 V 30 w(moderation)40 b Fo(Member)22 +b(postings)h(are)h(held)f(for)g(moderation)e(if)j(their)f +Fj(moder)o(ation)f(\003a)o(g)h Fo(is)i(turned)d(on.)35 +b(Note)208 183 y(that)20 b(only)f(the)h(list)i(administrators)d(can)g +(change)g(the)i(v)n(alue)e(of)h(a)h(member')-5 b(s)19 +b(moderation)f(\003ag.)208 315 y(Y)-9 b(ou)17 b(can)h(control)f +(whether)g(ne)n(w)h(members)f(get)h(their)g(moderation)e(\003ag)i +(turned)f(on)h(or)g(of)n(f)f(by)h(def)o(ault)f(when)h(the)o(y)f +(subscribe)208 415 y(to)j(the)h(list.)26 b(By)21 b(turning)e(this)i +(\003ag)f(of)n(f)g(by)g(def)o(ault,)f(postings)h(by)g(members)f(will)i +(be)g(allo)n(wed)e(without)h(further)f(interv)o(ention)208 +515 y(\(barring)28 b(other)j(restrictions)f(such)h(as)g(size)h(or)e +(implicit)h(recipient)f(lists)i(\226)f(see)h(belo)n(w\).)56 +b(By)31 b(turning)f(the)h(\003ag)g(on,)h(you)208 614 +y(can)27 b(quarantine)e(ne)n(w)j(member)e(postings)h(to)h(mak)o(e)f +(sure)g(that)h(the)o(y)e(meet)i(your)e(criteria)h(for)g(netiquette,)h +(topicality)-5 b(,)28 b(etc.)208 714 y(Once)f(you)f(determine)g(that)h +(the)h(ne)n(w)f(member)f(understands)f(the)i(community')-5 +b(s)26 b(posting)g(rules,)j(you)d(can)i(turn)e(of)n(f)h(their)208 +814 y(moderation)17 b(\003ag)k(and)e(let)i(their)f(postings)g(go)f +(through)f(unstopped.)208 946 y(E-ne)n(wsletter)43 b(style)i(lists)h +(can)e(also)h(be)g(set)g(up)f(by)g(using)g(the)h(moderation)d(\003ag.) +98 b(By)45 b(setting)g(the)f Ff(member_-)208 1046 y(moderation_action) +23 b Fo(to)i Fj(Reject)p Fo(,)i(and)e(by)g(turning)g(of)n(f)f(the)i +(moderation)d(\003ag)j(for)f(just)h(the)g(fe)n(w)g(appro)o(v)o(ed)c +(senders,)208 1146 y(your)e(list)j(will)g(operate)d(in)i(essentially)g +(a)h(one-w)o(ay)d(direction.)29 b(Note)21 b(that)h(you')l(d)e(also)j +(need)e(to)h(reject)f(or)h(discard)f(postings)208 1245 +y(from)e(non-members.)0 1411 y Fl(member)p 300 1411 V +30 w(moderation)p 742 1411 V 28 w(action)41 b Fo(This)20 +b(is)h(the)g(action)f(to)g(tak)o(e)g(for)g(postings)g(from)f(a)i +(member)e(who')-5 b(s)20 b(moderation)e(\003ag)i(is)i(set.)k(F)o(or)208 +1511 y(typical)g(discussion)g(lists,)k(you')o(ll)c(lik)o(ely)h(set)g +(this)h(to)f Fj(Hold)f Fo(so)i(that)f(the)g(list)h(moderator)c(will)k +(get)f(a)g(chance)f(to)h(manually)208 1611 y(appro)o(v)o(e,)19 +b(reject,)j(or)g(discard)f(the)h(message.)30 b(F)o(or)22 +b(e-ne)n(wsletter)f(and)g(announcement)e(lists,)24 b(you)d(might)g(w)o +(ant)h(to)g(set)h(this)f(to)208 1710 y Fj(Reject)e Fo(or)g +Fj(Discar)m(d)p Fo(.)208 1843 y(Note)27 b(that)h(when)g(a)g(moderated)e +(member)g(posts)i(to)g(your)f(list,)k(and)c(the)h Ff +(member_moderation_action)c Fo(is)29 b(set)f(to)208 1943 +y Fj(Hold)p Fo(,)20 b(the)h(message)f(will)i(appear)d(on)h(the)h +(administrati)n(v)o(e)e(requests)i(page.)26 b(When)20 +b(you)g(dispose)g(of)h(the)g(message,)f(you)g(will)208 +2042 y(be)26 b(gi)n(v)o(en)f(an)h(opportunity)d(to)k(clear)f(the)g +(moderation)e(\003ag)i(at)h(the)f(same)h(time.)43 b(If)26 +b(you')l(re)f(quarantining)e(ne)n(w)j(posts,)i(this)208 +2142 y(mak)o(es)20 b(it)h(v)o(ery)e(con)m(v)o(enient)e(to)j(both)g +(appro)o(v)o(e)d(a)k(ne)n(w)f(member')-5 b(s)19 b(post)h(and)g +(de-moderate)e(them)i(at)g(the)g(same)h(time.)0 2308 +y Fl(member)p 300 2308 V 30 w(moderation)p 742 2308 V +28 w(notice)41 b Fo(When)16 b(a)g(member')-5 b(s)15 b(moderation)f +(\003ag)i(is)h(turned)e(on)h(and)f Ff(member_moderation_action)208 +2408 y Fo(is)21 b Fj(Reject)p Fo(,)f(this)g(v)n(ariable)f(contains)h +(the)g(te)o(xt)g(sent)h(in)f(the)g(rejection)f(notice.)0 +2638 y(The)f(ne)o(xt)h(batch)f(of)g(v)n(ariables)g(controls)g(what)h +(happens)e(when)i(non-members)d(post)i(messages)h(to)g(the)g(list.)26 +b(Each)18 b(of)h(these)g(accepts)0 2737 y(one)j(email)g(address)g(per)h +(line;)g(re)o(gular)e(e)o(xpressions)g(are)i(allo)n(wed)f(if)g(the)h +(line)g(starts)g(with)g(the)2837 2718 y(\210)2837 2737 +y(\(caret\))f(character)-5 b(.)31 b(These)22 b(address)0 +2837 y(lists)k(are)f(al)o(w)o(ays)h(consulted)e(in)h(the)g(order)e(in)j +(which)e(the)o(y')l(re)f(presented)h(on)h(this)g(page)f(\(i.e.)40 +b(accepts)24 b(\002rst,)j(follo)n(wed)d(by)g(holds,)0 +2936 y(rejections,)19 b(and)h(discards\).)0 3166 y Fl(accept)p +232 3166 V 29 w(these)p 441 3166 V 29 w(nonmembers)42 +b Fo(Postings)23 b(from)e(non-members)f(whose)i(addresses)g(match)g +(this)i(list)f(are)g(accepted,)f(barring)e(other)208 +3266 y(list)27 b(restrictions)f(due)g(to)h(size,)i(implicit)d +(recipients,)h(etc.)45 b(Y)-9 b(ou)26 b(might)f(w)o(ant)i(to)g(add)f +(alternati)n(v)o(e)f(addresses)h(of)h(appro)o(v)o(ed)208 +3366 y(posters)20 b(to)g(this)h(list.)0 3532 y Fl(hold)p +162 3532 V 30 w(these)p 372 3532 V 30 w(nonmembers)41 +b Fo(Postings)30 b(from)e(non-members)e(whose)j(addresses)g(match)g +(this)h(list)g(are)f(held)g(for)g(moderator)e(ap-)208 +3631 y(pro)o(v)n(al.)0 3797 y Fl(r)o(eject)p 208 3797 +V 28 w(these)p 416 3797 V 30 w(nonmembers)42 b Fo(Postings)27 +b(from)g(non-members)e(whose)j(addresses)f(match)h(this)g(list)h(are)f +(rejected,)h(i.e.)48 b(bounced)208 3897 y(back)19 b(to)h(the)h +(original)e(sender)-5 b(.)24 b(There)c(currently)e(is)j(no)f(w)o(ay)g +(to)h(add)e(additional)g(te)o(xt)h(to)g(the)h(rejection)e(message.)0 +4063 y Fl(discard)p 268 4063 V 30 w(these)p 478 4063 +V 30 w(nonmembers)41 b Fo(Postings)33 b(from)f(non-members)e(whose)i +(addresses)h(match)f(this)h(list)h(are)f(discarded,)h(with)f(no)208 +4163 y(bounce)18 b(back)i(message.)k(Y)-9 b(ou)20 b(might)f(w)o(ant)i +(to)f(add)g(the)g(addresses)g(of)g(kno)n(wn)e(spammers)i(to)g(this)h +(list.)0 4329 y Fl(generic)p 264 4329 V 29 w(nonmember)p +722 4329 V 30 w(action)40 b Fo(This)35 b(v)n(ariable)e(controls)h(what) +g(happens)f(to)i(non-member)c(posts)k(when)f(the)g(address)g(of)h(the) +208 4428 y(sender)27 b(doesn')o(t)f(match)i(an)o(y)f(of)h(the)g(abo)o +(v)o(e)e(four)h(lists.)49 b(If)28 b(you)f(set)i(this)g(to)f +Fj(Hold)p Fo(,)h(the)f(posting)f(will)i(appear)d(on)i(the)g(ad-)208 +4528 y(ministrati)n(v)o(e)16 b(requests)i(page,)f(and)h(you)f(will)h +(be)g(gi)n(v)o(en)f(an)h(opportunity)d(to)j(add)f(the)h(non-member)d +(to)j(one)f(of)h(the)f(abo)o(v)o(e)g(four)208 4627 y(lists)k(at)g(the)f +(same)g(time)h(you)e(dispose)h(of)g(the)g(held)g(message.)0 +4794 y Fl(f)n(orward)p 295 4794 V 28 w(auto)p 481 4794 +V 29 w(discards)42 b Fo(When)16 b(messages)h(from)e(non-members)f(are)i +(discarded,)g(either)g(because)g(the)g(sender)g(address)g(matched)208 +4893 y Ff(discard_these_nonmembers)p Fo(,)d(or)j(because)g +Ff(generic_nonmember_action)c Fo(is)18 b Fj(Discar)m(d)p +Fo(,)f(you)e(can)h(choose)208 4993 y(whether)j(such)h(messages)g(are)g +(forw)o(arded)e(to)j(the)f(lsit)h(administrators)e(or)h(not.)p +0 5549 3901 4 v 0 5649 a Fg(14)2612 b(2)84 b(The)23 b(List)g +(Con\002gur)o(ation)h(P)m(ages)p eop end +%%Page: 15 15 +TeXDict begin 15 14 bop 0 83 a Fg(Recipient)24 b(Filters)0 +286 y Fo(The)c(v)n(ariables)f(in)i(this)f(section)g(control)f(v)n +(arious)g(\002lters)i(based)f(on)g(the)g(recipient)f(of)h(the)g +(message.)0 510 y Fl(r)o(equir)o(e)p 266 510 25 4 v 29 +w(explicit)p 554 510 V 29 w(destination)41 b Fo(This)23 +b(controls)g(whether)g(the)h(mailing)f(list)i(posting)d(address)i(must) +g(be)f(e)o(xplicitly)g(named)g(in)h(the)208 610 y Fh(T)-9 +b(o:)42 b Fo(or)28 b Fh(Cc:)43 b Fo(recipient)28 b(lists.)53 +b(The)28 b(main)h(reason)f(why)g(it)h(w)o(ouldn')o(t)e(is)j(if)f(the)g +(message)g(w)o(as)g(blind-carbon-copied)24 b(\(i.e.)208 +709 y Fh(Bcc:)p Fo(')l(d\))g(to)h(the)f(list.)40 b(Spammers)24 +b(lik)o(e)h(to)g(do)f(this,)i(b)n(ut)f(sometimes)f(le)o(gitimate)g +(messages)h(are)g(forw)o(arded)e(to)h(the)h(list)h(this)208 +809 y(w)o(ay)-5 b(.)208 941 y(If)15 b(the)g(list)i(is)f(not)f(e)o +(xplicitly)g(addressed)f(and)h(this)h(setting)f(is)i(turned)d(on,)i +(the)f(message)g(will)i(be)e(held)g(for)g(moderator)e(appro)o(v)n(al.)0 +1104 y Fl(acceptable)p 380 1104 V 28 w(aliases)42 b Fo(This)f(is)h(the) +f(list)i(of)e(alternati)n(v)o(e)f(addresses)h(that)g(are)g(acceptable)f +(as)i(a)g(list)g(posting)e(address)h(when)208 1204 y +Ff(require_explicit_destination)16 b Fo(is)22 b(enabled.)j(This)c(is)h +(useful)e(for)h(when)f(there)g(aliases)i(for)e(the)h(main)g(posting)208 +1303 y(address)e(\(e.g.)25 b Ff(help@example.com)17 b +Fo(may)j(be)g(an)g(alias)h(for)f Ff(help-list@example.com)p +Fo(\).)0 1467 y Fl(max)p 158 1467 V 29 w(num)p 348 1467 +V 30 w(r)o(ecipients)41 b Fo(This)30 b(is)g(the)f(maximum)e(number)h +(of)h(e)o(xplicit)f(recipients)h(that)g(are)g(allo)n(wed)g(on)f(the)h +(posted)g(message.)208 1567 y(Spammers)g(sometimes)h(send)g(messages)h +(with)g(lots)g(of)f(e)o(xplicit)g(recipients,)i(so)f(setting)f(this)h +(number)e(to)h(a)h(reasonable)208 1666 y(v)n(alue)19 +b(may)h(cut)g(do)n(wn)f(on)h(spam.)0 1934 y Fg(Spam)k(Filters)0 +2137 y Fo(This)e(section)g(pro)o(vides)f(some)h(adjuncts)f(to)i(spam)f +(\002ghting)f(tools;)i(it)g(doesn')o(t)e(replace)g(dedicated)g +(anti-spam)h(tools)g(such)g(as)h(Spa-)0 2236 y(mAssassin)e(or)f +(Spambayes.)0 2460 y Fl(bounce)p 259 2460 V 30 w(matching)p +622 2460 V 29 w(headers)41 b Fo(This)19 b(v)n(ariable)g(contains)g +(header)f(re)o(gular)g(e)o(xpressions,)g(one)h(per)g(line,)h(and)f(if)g +(an)o(y)g(of)g(a)h(message')-5 b(s)208 2560 y(headers)23 +b(matches)i(one)f(of)g(these)h(patterns,)g(it)g(will)h(be)e(held)h(for) +f(moderation.)36 b(The)24 b(format)g(is)h(a)g(colon)f(separated)g +(header)208 2659 y(and)d(v)n(alue,)g(where)g(the)h(header)e(is)j(case)f +(insensiti)n(v)o(e)f(and)g(the)h(v)n(alue)f(is)h(an)o(y)f(v)n(alid)g +(Python)g(re)o(gular)f(e)o(xpression.)28 b(Lines)21 b(that)208 +2759 y(start)f(with)h(#)f(are)g(ignored.)208 2891 y(This)j(v)n(ariable) +f(can)h(be)g(used)f(to)i(catch)f(kno)n(wn)e(spammers)h(by)h(writing)g +(re)o(ge)o(xps)e(that)i(match)g(against)f Fh(T)-9 b(o:)31 +b Fo(or)22 b Fh(Cc:)32 b Fo(lines,)24 b(or)208 2990 y(kno)n(wn-bad)15 +b Fh(Message-ID:)p Fo(s.)24 b(Perhaps)17 b(more)h(useful)g(though)e +(are)j(patterns)e(that)i(match)f(headers)f(added)g(by)h(spam)h +(detection)208 3090 y(tools)25 b(higher)g(up)g(in)h(the)g(tool)g +(chain.)41 b(F)o(or)25 b(e)o(xample,)h(you)f(might)g(con\002gure)f +(SpamAssassin)i(to)g(add)g(an)f Fh(X-Spam-Score:)208 +3190 y Fo(header)17 b(with)h(between)f(zero)h(and)g(5)g(stars)h +(depending)d(on)h(the)i(spam)f(score.)24 b(Then)17 b(you)g(can)h(add)g +(a)h(line)f(to)g(this)h(v)n(ariable)e(lik)o(e:)623 3413 +y Fb(X-Spam-Score:)43 b([)1296 3426 y(*)1341 3413 y(]{3,5})208 +3775 y Fo(This)20 b(line)g(will)h(match)f(from)f(3)h(to)h(5)f(stars)h +(in)f(the)g(v)n(alue)g(of)g(this)g(\002eld.)0 4059 y +Fk(2.8)100 b(The)28 b(Bounce)i(Processing)f(Categor)s(y)0 +4262 y Fo(These)20 b(policies)g(control)f(the)h(automatic)f(bounce)g +(processing)g(system)h(in)g(Mailman.)25 b(Here')-5 b(s)20 +b(an)g(o)o(v)o(ervie)n(w)e(of)i(ho)n(w)g(it)h(w)o(orks:)0 +4409 y(When)i(a)g(bounce)f(is)i(recei)n(v)o(ed,)e(Mailman)g(tries)i(to) +f(e)o(xtract)g(tw)o(o)g(pieces)g(of)g(information)e(from)h(the)h +(message:)31 b(the)23 b(address)g(of)g(the)0 4509 y(member)c(the)h +(message)g(w)o(as)i(intended)c(for)m(,)h(and)h(the)h(se)n(v)o(erity)e +(of)h(the)g(problem)f(causing)g(the)i(bounce.)i(The)d(se)n(v)o(erity)g +(can)g(be)g(either)0 4608 y Fj(har)m(d)g Fo(for)f(f)o(atal)i(errors,)e +(or)h Fj(soft)g Fo(for)g(transient)g(errors.)k(When)c(in)g(doubt,)f(a)h +(hard)f(se)n(v)o(erity)h(is)h(used.)0 4755 y(If)d(no)h(member)e +(address)h(can)h(be)f(e)o(xtracted)f(from)h(the)h(bounce,)e(then)h(the) +h(bounce)e(message)h(is)i(usually)e(discarded.)23 b(Ev)o(ery)17 +b(member)0 4855 y(has)30 b(a)h Fj(bounce)d(scor)m(e)p +Fo(,)33 b(initialized)c(at)i(zero,)h(and)d(e)n(v)o(ery)g(time)h(we)g +(encounter)e(a)j(bounce)d(from)h(a)i(member)d(we)j(increment)d(that)0 +4954 y(member')-5 b(s)22 b(score.)35 b(Hard)23 b(bounces)f(increment)g +(by)h(1)h(while)f(soft)h(bounces)e(increment)g(by)h(0.5.)34 +b(W)-7 b(e)25 b(only)e(increment)f(the)h(bounce)0 5054 +y(score)d(once)g(per)g(day)-5 b(,)19 b(so)i(e)n(v)o(en)e(if)i(we)g +(recei)n(v)o(e)e(ten)i(hard)e(bounces)g(from)g(a)i(member)e(per)h(day) +-5 b(,)20 b(their)g(score)g(will)h(increase)f(by)g(only)f(1)0 +5154 y(for)h(that)g(day)-5 b(.)0 5300 y(When)22 b(a)h(member')-5 +b(s)22 b(bounce)e(score)j(is)g(greater)f(than)g(the)g +Fj(bounce)f(scor)m(e)i(thr)m(eshold)e Fo(\(see)i(belo)n(w\),)f(the)g +(member')-5 b(s)22 b(subscription)f(is)0 5400 y(disabled.)37 +b(Once)25 b(disabled,)f(the)h(member)e(will)i(not)g(recei)n(v)o(e)e(an) +o(y)h(postings)g(from)f(the)i(list)h(until)e(their)g(membership)f(is)j +(e)o(xplicitly)p 0 5549 3901 4 v 0 5649 a Fg(2.8)83 b(The)24 +b(Bounce)f(Processing)g(Categor)r(y)2366 b(15)p eop end +%%Page: 16 16 +TeXDict begin 16 15 bop 0 83 a Fo(re-enabled,)29 b(either)g(by)g(the)g +(list)h(administrator)e(or)g(the)i(user)-5 b(.)52 b(Ho)n(we)n(v)o(er)m +(,)29 b(the)o(y)g(will)h(recei)n(v)o(e)e(occasional)g(reminders)g(that) +h(their)0 183 y(membership)14 b(has)j(been)f(disabled,)g(and)g(these)g +(reminders)f(will)i(include)e(information)f(about)i(ho)n(w)f(to)i +(re-enable)e(their)h(membership.)0 282 y(Y)-9 b(ou)19 +b(can)h(control)f(both)g(the)g(number)g(of)g(reminders)g(the)g(member)g +(will)i(recei)n(v)o(e)d(and)i(the)f(frequenc)o(y)f(with)i(which)f +(these)h(reminders)0 382 y(are)g(sent.)0 529 y(There)f(is)h(one)f +(other)g(important)f(con\002guration)f(v)n(ariable;)i(after)g(a)h +(certain)f(period)g(of)g(time)h(\226)f(during)f(which)i(no)f(bounces)f +(from)h(the)0 628 y(member)e(are)i(recei)n(v)o(ed)e(\226)i(the)g +(bounce)e(information)g(is)i(considered)e(stale)j(and)e(discarded.)23 +b(Thus)c(by)f(adjusting)g(this)h(v)n(alue,)f(and)h(the)0 +728 y(score)24 b(threshold,)g(you)g(can)g(control)f(ho)n(w)h(quickly)g +(bouncing)e(members)h(are)i(disabled.)37 b(Y)-9 b(ou)24 +b(should)f(tune)h(both)g(of)g(these)h(to)g(the)0 828 +y(frequenc)o(y)17 b(and)j(traf)n(\002c)g(v)n(olume)f(of)h(your)f(list.) +0 1058 y Fl(bounce)p 259 1058 25 4 v 30 w(pr)o(ocessing)40 +b Fo(Speci\002es)21 b(whether)e(or)h(not)g(this)g(list)i(should)d(do)h +(automatic)f(bounce)f(processing.)0 1224 y Fl(bounce)p +259 1224 V 30 w(scor)o(e)p 473 1224 V 28 w(thr)o(eshold)41 +b Fo(This)27 b(is)h(the)e(bounce)f(score)i(abo)o(v)o(e)e(which)h(a)h +(member')-5 b(s)26 b(subscription)f(will)j(be)e(automatically)f(dis-) +208 1323 y(abled.)f(When)19 b(the)g(subscription)f(is)i(re-enabled,)e +(their)h(bounce)f(score)h(will)h(be)f(reset)h(to)f(zero.)25 +b(This)19 b(v)n(alue)g(can)g(be)g(a)h(\003oating)208 +1423 y(point)f(number)-5 b(.)0 1589 y Fl(bounce)p 259 +1589 V 30 w(inf)n(o)p 426 1589 V 29 w(stale)p 617 1589 +V 29 w(after)40 b Fo(Thenumber)24 b(of)i(days)g(after)f(which)h(a)h +(member')-5 b(s)25 b(bounce)g(information)e(is)28 b(considered)c +(stale.)44 b(If)26 b(no)208 1689 y(ne)n(w)18 b(bounces)g(ha)n(v)o(e)g +(been)g(recei)n(v)o(ed)g(in)h(the)g(interrim,)f(the)h(bounce)e(score)h +(is)i(reset)g(to)f(zero.)24 b(This)19 b(v)n(alue)f(must)h(be)g(an)g +(inte)o(ger)-5 b(.)0 1855 y Fl(bounce)p 259 1855 V 30 +w(y)n(ou)p 417 1855 V 29 w(ar)o(e)p 561 1855 V 28 w(disabled)p +884 1855 V 30 w(war)o(nings)41 b Fo(The)26 b(number)e(of)h(notices)h(a) +g(disabled)f(member)f(will)j(recei)n(v)o(e)d(before)h(their)g(address)h +(is)208 1954 y(remo)o(v)o(ed)21 b(from)h(the)h(mailing)g(list')-5 +b(s)25 b(roster)-5 b(.)34 b(Set)25 b(this)e(to)h(0)f(to)h(immediately)e +(remo)o(v)o(e)g(an)h(address)g(from)f(the)i(list)g(once)f(their)208 +2054 y(bounce)18 b(score)i(e)o(xceeds)f(the)h(threshold.)k(This)c(v)n +(alue)g(must)g(be)g(an)g(inte)o(ger)-5 b(.)0 2220 y Fl(bounce)p +259 2220 V 30 w(y)n(ou)p 417 2220 V 29 w(ar)o(e)p 561 +2220 V 28 w(disabled)p 884 2220 V 30 w(war)o(nings)p +1241 2220 V 30 w(inter)o(v)o(al)40 b Fo(The)20 b(number)e(of)i(days)g +(between)g(each)f(disabled)h(noti\002cation.)0 2386 y +Fl(bounce)p 259 2386 V 30 w(unr)o(ecognized)p 764 2386 +V 28 w(goes)p 945 2386 V 29 w(to)p 1044 2386 V 29 w(list)p +1179 2386 V 30 w(o)o(wner)41 b Fo(This)32 b(v)n(ariable)e(controls)g +(whether)g(unrecognized)e(bounces)i(are)h(discarded,)i(or)208 +2486 y(forw)o(arded)26 b(on)j(the)f(list)i(administrator)-5 +b(.)50 b(The)28 b(bounce)f(detector)h(isn')o(t)h(perfect,)g(although)e +(personalization)g(can)h(mak)o(e)h(it)208 2585 y(much)g(more)g +(accurate.)54 b(The)30 b(list)h(o)n(wner)e(may)h(w)o(ant)g(to)g(recei)n +(v)o(e)f(unrecognized)e(bounces)i(so)h(that)h(the)o(y)e(can)h(manually) +208 2685 y(disable)20 b(or)f(remo)o(v)o(e)g(such)h(members.)0 +2851 y Fl(bounce)p 259 2851 V 30 w(notify)p 498 2851 +V 28 w(o)o(wner)p 747 2851 V 29 w(on)p 864 2851 V 30 +w(disable)42 b Fo(This)29 b(option)f(controls)h(whether)f(or)h(not)g +(the)g(list)i(o)n(wner)d(is)i(noti\002ed)f(when)g(a)h(member')-5 +b(s)208 2950 y(subscription)18 b(is)j(automatically)e(disabled)h(due)f +(to)h(their)g(bounce)f(threshold)g(being)g(reached.)0 +3116 y Fl(bounce)p 259 3116 V 30 w(notify)p 498 3116 +V 28 w(o)o(wner)p 747 3116 V 29 w(on)p 864 3116 V 30 +w(r)o(emo)o(v)o(al)40 b Fo(This)24 b(option)g(controls)f(whether)h(or)g +(not)g(the)h(list)g(o)n(wner)f(is)h(noti\002ed)f(when)g(a)h(member)e +(is)208 3216 y(remo)o(v)o(ed)17 b(from)i(the)i(list)g(after)f(their)g +(disabled)f(noti\002cations)g(ha)n(v)o(e)h(been)g(e)o(xhausted.)0 +3501 y Fk(2.9)100 b(The)28 b(Archiving)i(Options)e(Categor)s(y)0 +3704 y Fo(Mailman)e(comes)h(with)f(a)i(b)n(uilt-in)e(web-based)f(archi) +n(v)o(er)g(called)i Fj(Pipermail)p Fo(,)g(although)e(it)j(can)e(be)h +(con\002gured)d(to)j(use)g(e)o(xternal,)0 3804 y(third)20 +b(party)f(archi)n(v)o(ers.)0 4033 y Fl(ar)o(chi)o(v)o(e)40 +b Fo(This)21 b(option)e(tells)j(Mailman)e(whether)g(to)h(archi)n(v)o(e) +e(messages)i(it)g(recei)n(v)o(es)f(or)g(not,)h(re)o(gardless)e(of)h +(whether)g(Pipermail)g(or)208 4133 y(a)g(third)g(party)f(archi)n(v)o +(er)g(is)i(used.)j(T)l(urn)c(this)g(of)n(f)g(if)g(you)g(don')o(t)e(w)o +(ant)j(to)f(archi)n(v)o(e)f(messages.)208 4266 y(Note)k(that)g(senders) +g(can)g(control)f(whether)h(their)g(o)n(wn)g(posts)g(are)g(archi)n(v)o +(ed,)f(on)h(an)h(indi)n(vidual)d(per)n(-message)h(basis.)35 +b(If)24 b(the)208 4366 y(posted)i(message)i(has)f(a)h +Fh(X-No-Archiv)n(e:)39 b Fo(header)26 b(\(re)o(gardless)g(of)h(v)n +(alue\),)h(or)f(a)h Fh(X-Archiv)n(e:)39 b Fo(header)27 +b(with)g(a)h(v)n(alue)f(of)g Ff(No)208 4465 y Fo(\(case)20 +b(insensiti)n(v)o(e\),)f(then)h(the)g(message)g(will)h(not)f(be)g +(archi)n(v)o(ed,)e(although)g(it)j(will)g(be)f(treated)g(as)h(normal)e +(in)h(all)h(other)e(w)o(ays.)0 4631 y Fl(ar)o(chi)o(v)o(e)p +266 4631 V 29 w(pri)o(v)o(ate)40 b Fo(Controls)23 b(whether)g +(Pipermail)h(archi)n(v)o(es)e(are)i(pri)n(v)n(ate)f(or)h(public.)35 +b(Pri)n(v)n(ate)23 b(archi)n(v)o(es)g(require)f(a)j(v)n(alid)e(member) +208 4731 y(address)e(and)f(passw)o(ord,)h(or)g(a)h(list)h +(administrator)c(passw)o(ord)i(in)h(order)e(to)i(access)g(them.)28 +b(This)21 b(option)g(has)g(no)g(ef)n(fect)g(when)208 +4830 y(a)f(third)g(party)f(archi)n(v)o(er)g(is)i(used.)0 +4996 y Fl(ar)o(chi)o(v)o(e)p 266 4996 V 29 w(v)o(olume)p +553 4996 V 29 w(fr)o(equency)40 b Fo(Controls)31 b(ho)n(w)g(Pipermail)g +(splits)h(messages)g(in)g(the)f(archi)n(v)o(e.)58 b(The)31 +b(most)h(common)d(option)i(is)208 5096 y Fj(Monthly)d +Fo(meaning)f(a)i(ne)n(w)g(archi)n(v)o(e)e(v)n(olume)h(is)h(started)g(e) +n(v)o(ery)f(month.)49 b(V)-9 b(ery)28 b(high)g(v)n(olume)g(lists)i(may) +e(w)o(ant)h(a)g(shorter)208 5196 y(frequenc)o(y)19 b(\(e.g.)32 +b Fj(W)-8 b(eekly)23 b Fo(or)g Fj(Daily)p Fo(\))f(where)g(as)i(lo)n +(wer)e(v)n(olume)g(lists)i(may)e(w)o(ant)h(a)g(longer)e(frequenc)o(y)f +(\(e.g.)32 b Fj(Y)-8 b(early)p Fo(\).)32 b(This)208 5295 +y(option)19 b(has)h(no)g(ef)n(fect)f(when)h(a)h(third)e(party)g(archi)n +(v)o(er)g(is)i(used.)p 0 5549 3901 4 v 0 5649 a Fg(16)2612 +b(2)84 b(The)23 b(List)g(Con\002gur)o(ation)h(P)m(ages)p +eop end +%%Page: 17 17 +TeXDict begin 17 16 bop 0 83 a Fk(2.10)100 b(The)29 b(Mail/Ne)n(ws)f +(Gate)n(w)o(a)m(y)f(Categor)s(y)0 286 y Fo(Mailman)18 +b(has)g(a)h(sophisticated)e(mail-to-ne)n(ws)g(gate)n(w)o(ay)h(feature.) +23 b(It)c(can)f(independently)d(gate)j(messages)g(from)g(ne)n(ws)g(to)h +(mail)f(and)0 386 y(vice)i(v)o(ersa,)g(and)f(can)h(e)n(v)o(en)f(be)h +(used)g(to)h(manage)e(moderated)f(ne)n(wsgroups.)0 670 +y Fk(2.11)100 b(The)29 b(A)m(uto-responder)i(Categor)s(y)0 +890 y(2.12)100 b(The)29 b(Content)f(Filter)q(ing)i(Categor)s(y)0 +1109 y(2.13)100 b(The)29 b(T)-12 b(opics)28 b(Categor)s(y)0 +1362 y Fp(3)120 b(Membership)34 b(Management)0 1645 y(4)120 +b(T)-14 b(ending)35 b(to)f(P)-6 b(ending)35 b(Moder)o(ator)f(Requests)0 +1927 y(5)120 b(Editing)34 b(the)g(Pub)n(lic)f(HTML)g(P)-5 +b(ages)0 2210 y(6)120 b(Deleting)35 b(the)f(Mailing)f(List)0 +2493 y(A)119 b(This)33 b(is)g(an)h(Appendix)0 2725 y +Fo(T)-7 b(o)20 b(create)g(an)g(appendix)f(in)h(a)g(Python)g(HO)m(WT)o +(O)g(document,)e(use)i(markup)f(lik)o(e)h(this:)236 2964 +y Fb(\\appendix)236 3146 y(\\section{This)43 b(is)h(an)h(Appendix})236 +3329 y(To)g(create)f(an)g(appendix)g(in)g(a)h(Python)f(HOWTO)f +(document,)h(....)236 3603 y(\\section{This)f(is)h(another})236 +3786 y(Just)g(add)h(another)e(\\section{},)g(but)i(don't)f(say)g +(\\appendix)f(again.)p 0 5549 3901 4 v 0 5649 a Fg(2.10)84 +b(The)23 b(Mail/Ne)n(ws)h(Gate)n(w)o(a)n(y)e(Categor)r(y)2309 +b(17)p eop end +%%Trailer + +userdict /end-hook known{end-hook}if +%%EOF diff --git a/doc/mailman-admin.tex b/doc/mailman-admin.tex deleted file mode 100644 index 6a9e3c77..00000000 --- a/doc/mailman-admin.tex +++ /dev/null @@ -1,1402 +0,0 @@ -\documentclass{howto} - -\title{GNU Mailman - List Administration Manual} - -% Increment the release number whenever significant changes are made. -% The author and/or editor can define 'significant' however they like. -\release{1.0} - -% At minimum, give your name and an email address. You can include a -% snail-mail address if you like. -\author{Barry A. Warsaw} -%\authoraddress{barry (at) list dot org} - -\date{\today} % XXX update before tagging release! -\release{2.1} % software release, not documentation -\setreleaseinfo{} % empty for final release -\setshortversion{2.1} % major.minor only for software - -\begin{document} -\maketitle - -% This makes the Abstract go on a separate page in the HTML version; -% if a copyright notice is used, it should go immediately after this. -% -\ifhtml -\chapter*{Front Matter\label{front}} -\fi - -% Copyright statement should go here, if needed. -% ... - -% The abstract should be a paragraph or two long, and describe the -% scope of the document. -\begin{abstract} -\noindent -This document describes the list administrator's interface for GNU -Mailman 2.1. It contains information a list owner would need to -configure their list, either through the web interface or through -email. It also covers the moderator's interface for approving held -messages and subscription notices, and the web interface for creating -new mailing lists. In general, it does not cover the command line -interface to Mailman, installing Mailman, or interacting with Mailman -from the point of view of the user. That information is covered in -other manuals. -\end{abstract} - -\tableofcontents - -\section{Introduction to 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 for controlling the privacy of your lists, distributing your -list as personalized postings or digests, gatewaying postings to and -from Usenet, and providing automatic bounce detection. Mailman -provides a built-in archiver, multiple natural languages, as well as -advanced content and topic filtering. - -Mailman provides several interfaces to its functionality. Most list -administrators will primarily use the web interface to customize their -lists. There is also a limited email command interface to the -administrative functions, as well as a command line interface if you -have shell access on the Mailman server. This document does not cover -the command line interface; see the GNU Mailman site administrator's -manual for more details. - -\subsection{A List's Email Addresses} - -Every mailing list has a set of email addresses that messages can be -sent to. There's always one address for posting messages to the list, -one address that bounces will be sent to, and addresses for processing -email commands. For example, for a mailing list called -\var{mylist@example.com}, you'd find these addresses: - -\begin{itemize} -\item mylist@example.com -- this is the email address people should - use for new postings to the list. - -\item mylist-join@example.com -- by sending a message to this address, - a new member can request subscription to the list. Both the - \mailheader{Subject} header and body of such a message are - ignored. Note that mylist-subscribe@example.com is an alias for - the -join address. - -\item mylist-leave@example.com -- by sending a message to this address, - a member can request unsubscription from the list. As with the - -join address, the \mailheader{Subject} header and body of the - message is ignored. Note that mylist-unsubscribe@example.com is - an alias for the -leave address. - -\item mylist-owner@example.com -- This address reaches the list owner - and list moderators directly. - -\item mylist-request@example.com -- This address reaches a mail robot - which processes email commands that can be used to set member - subscription options, as well as process other commands. - -\item mylist-bounces@example.com -- This address receives bounces from - members who's addresses have become either temporarily or - permanently inactive. The -bounces address is also a mail robot - that processes bounces and automatically disables or removes - members as configured in the bounce processing settings. Any - bounce messages that are either unrecognized, or do not seem to - contain member addresses, are forwarded to the list - administrators. - -\item mylist-confirm@example.com -- This address is another email - robot, which processes confirmation messages for subscription - and unsubscription requests. -\end{itemize} - -There's also an -admin address which also reaches the list -administrators, but this address only exists for compatibility with -older versions of Mailman. - -\subsection{Administrative Roles} - -There are two primary administrative roles for each mailing list, a -list owner and a list moderator. A list owner is allowed to change -various settings of the list, such as the privacy and archiving -policies, the content filtering settings, etc. The list owner is also -allowed to subscribe or invite members, unsubscribe members, and -change any member's subscription options. - -The list moderator on the other hand, is only allowed to approve or -reject postings and subscription requests. The list moderator can -also do things like clear a member's moderation flag, or add an -address to a list of approved non-member posters. - -Normally, the list owner and list moderator are the same person. In -fact, the list owner can always do all the tasks a list moderator can -do. Access to both the owner's configuration pages, and the -moderation pages are protected by the same password. However, if the -list owner wants to delegate posting and subscription approval -authority to other people, a separate list moderator password can be -set, giving moderators access to the approval pages, but not the -configuration pages. In this setup, list owners can still moderate -the list, of course. - -In the sections that follow, we'll often use the terms list owner and -list administrator interchangably, meaning both roles. When -necessary, we'll distinguish the list moderator explicitly. - -\subsection{A List's Web Pages} - -Every mailing list is also accessible by a number of web pages. Note -that the exact urls is configurable by the site administrator, so they -may be different than what's described below. We'll describe the most -common default configuration, but check with your site administrator -or hosting service for details. - -Mailman provides a set of web pages that list members use to get -information about the list, or manage their membership options. There -are also list archive pages, for browsing an online web-based archive -of the list traffic. These are described in more detail in the GNU -Mailman user's manual. - -Mailman also provides a set of pages for configuring an individual -list, as well as a set of pages for disposing of posting and -subscription requests. - -For a mailing list called \var{mylist} hosted at the domain -\var{lists.example.com}, you would typically access the administrative -pages by going to \code{http://lists.example.com/mailman/admin/mylist}. -The first time you visit this page, you will be presented with a login -page, asking for the list owner's password. When you enter the -password, Mailman will store a session cookie in your browser, so you -don't have to re-authenticate for every action you want to take. This -cookie is stored only until you exit your browser. - -To access the administrative requests page, you'd visit -\code{http://lists.example.com/mailman/admindb/mylist} (note the -\emph{admindb} url as opposed to the \emph{admin} url). Again, the -first time you visit this page, you'll be presented with a login page, -on which you can enter either the list moderator password or the list -owner password. Again, a session cookie is dropped in your browser. -Note also that if you've previously logged in as the list owner, you -do not need to re-login to access the administrative requests page. - -\subsection{Basic Architectural Overview} - -This section will outline the basic architecture of GNU Mailman, such -as how messages are processed by the sytem. Without going into lots -of detail, this information will help you understand how the -configuration options control Mailman's functionality. - -When mail enters the system from your mail server, it is dropped into -one of several Mailman \emph{queues} depending on the address the -message was sent to. For example, if your system has a mailing list -named \var{mylist} and your domain is \var{example.com}, people can -post messages to your list by sending them to -\var{mylist@example.com}. These messages will be dropped into the -\emph{incoming} queue, which is also colloquially called the -\emph{moderate-and-munge} queue. The incoming queue is where most of -the approval process occurs, and it's also where the message is -prepared for sending out to the list membership. - -There are separate queues for the built-in archiver, the bounce -processor, the email command processor, as well as the outgoing email -and news queues. There's also a queue for messages generated by the -Mailman system. Each of these queues typically has one \emph{queue -runner} (or ``qrunner'') that processes messages in the queue. The -qrunners are idle when there are no messages to process. - -Every message in the queues are represented by two files, a message -file and a metadata file. Both of these files share the same base -name, which is a combination of a unique hash and the Unix time that -the message was received. The metadata file has a suffix of -\file{.db} and the message file has a suffix of either \file{.msg} if -stored in plain text, or \file{.pck} if stored in a more efficient -internal representation\footnote{Specifically, a Python pickle}. - -As a message moves through the incoming queue, it performs various -checks on the message, such as whether it matches one of the -moderation criteria, or contains disallowed MIME types. Once a -message is approved for sending to the list membership, the message is -prepared for sending by deleting, adding, or changing message headers, -adding footers, etc. Messages in the incoming queue may also be -stored for appending to digests. - -\section{The List Configuration Pages} - -After logging into the list configuration pages, you'll see the -configuration options for the list, grouped in categories. All the -administrative pages have some common elements. In the upper section, -you'll see two columns labeled ``Configuration Categories''. Some -categories have sub-categories which are only visible when you click -on the category link. The first page you see after logging in will be -the ``General Options'' category. The specific option settings for -each category are described below. - -On the right side of the top section, you'll see a column labeled -``Other Administrative Activities''. Here you'll find some other -things you can do to your list, as well as convenient links to the -list information page and the list archives. Note the big ``Logout'' -link; use this if you're finished configuring your list and don't want -to leave the session cookie active in your browser. - -Below this common header, you'll find a list of this category's -configuration variables, arranged in two columns. In the left column -is a brief description of the option, which also contains a -``details'' link. For many of the variables, more details are -available describing the semantics of the various available settings, -or information on the interaction between this setting and other list -options. Clicking on the details link brings up a page which contains -only the information for that option, as well as a button for -submitting your setting, and a link back to the category page. - -On the right side of the two-column section, you'll see the variable's -current value. Some variables may present a limited set of values, -via radio button or check box arrays. Other variables may present -text entry boxes of one or multiple lines. Most variables control -settings for the operation of the list, but others perform immediate -actions (these are clearly labeled). - -At the bottom of the page, you'll find a ``Submit'' button and a -footer with some more useful links and a few logos. Hitting the -submit button commits your list settings, after they've been -validated. Any invalid values will be ignored and an error message -will be displayed at the top of the resulting page. The results page -will always be the category page that you submitted. - -\subsection{The General Options Category} - -The General Options category is where you can set a variety of -variables that affect basic behavior and public information. In the -descriptions that follow, the variable name is given first, along with -an overview and a description of what that variable controls. - -\subsubsection{General list personality} - -These variables, grouped under the general list personality section, -control some public information about the mailing list. - -\begin{description} -\item[real_name] - Every mailing list has both a \emph{posting name} and a \emph{real - name}. The posting name shows up in urls and in email addresses, - e.g. the \code{mylist} in \code{mylist@example.com}. The posting - name is always presented in lower case, with alphanumeric - characters and no spaces. The list's real name is used in some - public information and email responses, such as in the general - list overview. The real name can differ from the posting name by - case only. For example, if the posting name is \code{mylist}, the - real name can be \code{Posting}. - -\item[owner] - This variable contains a list of email addresses, one address per - line, of the list owners. These addresses are used whenever the - list owners need to be contacted, either by the system or by end - users. Often, these addresses are used in combination with the - \code{moderator} addresses (see below). - -\item[moderator] - This variable contains a list of email addresses, one address per - line, of the list moderators. These addresses are often used in - combination with the \code{owner} addresses. For example, when - you email \code{mylist-owner@example.com}, both the owner and - moderator addresses will receive a copy of the message. - -\item[description] - In the general list overview page, which shows you every available - mailing list, each list is displayed with a short description. - The contents of this variable is that description. Note that in - emails from the mailing list, this description is also used in the - comment section of the \mailheader{To} address. This text should - be relatively short and no longer than one line. - -\item[info] - This variable contains a longer description of the mailing list. - It is included at the top of the list's information page, and it - can contain HTML. However, blank lines will be automatically - converted into paragraph breaks. Preview your HTML though, - because unclosed or invalid HTML can prevent display of parts of - the list information page. - -\item[subject_prefix] - This is a string that will be prepended to the - \mailheader{Subject} header of any message posted to the list. - For example, if a message is posted to the list with a - \mailheader{Subject} like: - - \begin{verbatim} - Subject: This is a message - \end{verbatim} - - and the \code{subject_prefix} is \code{[My List] } (note the - trailing space!), then the message will be received like so: - - \begin{verbatim} - Subject: [My List] This is a message - \end{verbatim} - - If you leave \code{subject_prefix} empty, no prefix will be added - to the \mailheader{Subject}. Mailman is careful not to add a - prefix when the header already has one, as is the case in replies - for example. The prefix can also contain characters in the list's - preferred language. In this case, because of vagarities of the - email standards, you may or may not want to add a trailing space. - -\item[anonymous_list] - This variable allows you to turn on some simple anonymizing - features of Mailman. When you set this option to \emph{Yes}, - Mailman will remove or replace the \mailheader{From}, - \mailheader{Sender}, and \mailheader{Reply-To} fields of any - message posted to the list. - - Note that this option is simply an aid for anonymization, it - doesn't guarantee it. For example, a poster's identity could be - evident in their signature, or in other mail headers, or even in - the style of the content of the message. There's little Mailman - can do about this kind of identity leakage. -\end{description} - -\subsubsection{Reply-To header munging} - -This section controls what happens to the \mailheader{Reply-To} -headers of messages posted through your list. - -Beware! \mailheader{Reply-To} munging is considered a religious issue -and the policies you set here can ignite some of the most heated -off-topic flame wars on your mailing lists. We'll try to stay as -agnostic as possible, but our biases may still peak through. - -\mailheader{Reply-To} is a header that is commonly used to redirect -replies to messages. Exactly what happens when your uses reply to -such a message depends on the mail readers your users use, and what -functions they provide. Usually, there is both a ``reply to sender'' -button and a ``reply to all'' button. If people use these buttons -correctly, you will probably never need to munge -\mailheader{Reply-To}, so the default values should be fine. - -Since an informed decision is always best, here are links to two -articles that discuss the opposing viewpoints in great detail: - -\begin{itemize} - -\item \ulink{Reply-To Munging Considered - Harmful}{http://www.unicom.com/pw/reply-to-harmful.html} -\item \ulink{Reply-To Munging Considered - Useful}{http://www.metasystema.org/essays/reply-to-useful.mhtml} - -\end{itemize} - -The three options in this section work together to provide enough -flexibility to do whatever \mailheader{Reply-To} munging you might -(misguidingly :) feel you need to do. - -\begin{description} - -\item[first_strip_reply_to] - This variable controls whether any \mailheader{Reply-To} header - already present in the posted message should get removed before - any other munging occurs. Stripping this header will be done - regardless of whether or not Mailman will add its own - \mailheader{Reply-To} header to the message. - - If this option is set to \emph{No}, then any existing - \mailheader{Reply-To} header will be retained in the posted - message. If Mailman adds its own header, it will contain - addresses which are the union of the original header and the - Mailman added addresses. The mail standards specify that a - message may only have one \mailheader{Reply-To} header, but that - that header may contain multiple addresses. - -\item[reply_goes_to_list] - This variable controls whether Mailman will add its own - \mailheader{Reply-To} header, and if so, what the value of that - header will be (not counting original header stripping -- see - above). - - When you set this variable to \emph{Poster}, no additional - \mailheader{Reply-To} header will be added by Mailman. This - setting is strongly recommended. - - When you set this variable to \emph{This list}, a - \mailheader{Reply-To} header pointing back to your list's posting - address will be added. - - When you set this variable to \emph{Explicit address}, the value - of the variable \code{reply_to_address} (see below) will be - added. Note that this is one situation where - \mailheader{Reply-To} munging may have a legitimate purpose. Say - you have two lists at your site, an announce list and a discussion - list. The announce list might allow postings only from a small - number of approved users; the general list membership probably - can't post to this list. But you want to allow comments on - announcements to be posted to the general discussion list by any - list member. In this case, you can set the \mailheader{Reply-To} - header for the announce list to point to the discussion list's - posting address. - -\item[reply_to_address] - This is the address that will be added in the - \mailheader{Reply-To} header if \code{reply_goes_to_list} is set - to \emph{Explicit address}. - -\end{description} - -\subsubsection{Umbrella list settings} - -TBD. Note that umbrella lists are deprecated and will be replace with -a better mechanism for Mailman 3.0. - -\subsubsection{Notifications} - -Mailman sends notifications to the list administrators or list members -under a number of different circumstances. Most of these -notifications can be configured in this section, but see the Bounce -Processing and Auto-responder categories for other notifications that -Mailman can send. - -\begin{description} -\item[send_reminders] - By default Mailman sends all list members a monthly password - reminder. This notice serves two purposes. First, it reminds - people about all the lists they may be subscribed to on this - domain, including the lists where their subscription may be - disabled. Second, it reminds people about their passwords for - these lists, as well as the url for their personal options pages, - so that they can more easily configure their subscription options. - - Some people get annoyed with these monthly reminders, and they can - disable the reminders via their subscription options page. For - some lists, the monthly reminders aren't appropriate for any of - the members, so you can disable them list-wide by setting the - \code{send_reminders} variable to \emph{No}. - -\item[welcome_msg] - When new members are subscribed to the list, either by their own - action, or the action of a list administrator, a welcome message - can be sent to them. The welcome message contains some common - boilerplate information, such as the name of the list, - instructions for posting to the list, and the member's - subscription password. You can add additional information to the - welcome message by typing the text into the \code{welcome_msg} - text box. Note that because this text is sent as part of an - email, it should \strong{not} contain HTML. - -\item[send_welcome_msg] - This flag controls whether or not the welcome message is sent to - new subscribers. - -\item[goodbye_msg] - Like the \code{welcome_msg}, a ``goodbye'' message can be sent to - members when they unsubscribe from the list. Unlike the welcome - message, there's no boilerplate for the goodbye message. Enter - the entire goodbye message you'd like unsubscribing members to - receive into the \code{goodbye_msg} text box. - -\item[send_goodbye_msg] - This flag controls whether or not the goodbye message is sent to - unsubscribing members. - -\item[admin_immed_notify] - List moderators get notifications of pending administrative - actions, such as subscription or unsubscription requests that - require moderator approval, or posted messages that are being held - for moderator approval. List moderators will always get a daily - summary of such pending requests, but they can also get immediate - notifications when such a request is made. The - \code{admin_immed_notify} variable controls whether these - immediate notifications are sent or not. It's generally a good - idea to leave this set to \emph{Yes}. - -\item[admin_notify_mchanges] - This variable controls whether the list administrators should get - notifications when members join or leave the list. - -\item[respond_to_post_requests] - This variable controls whether the original sender of a posting - gets a notice when their message is held for moderator approval. - -\end{description} - -\subsubsection{Additional settings} - -This section contains some miscellaneous settings for your mailing -list. - -\begin{description} -\item[emergency] - When this option is enabled, all list traffic is emergency - moderated, i.e. held for moderation. Turn this option on when - your list is experiencing a flamewar and you want a cooling off - period. - -\item[new_member_options] - Each member has a set of subscription options which they can use - to control how they receive messages and otherwise interact with - the list. While the members can change these settings by logging - into their personal options page, you might want to set the - default for a number of the member options. You can do that with - this variable, but see also the other categories for other member - defaults you can set. - - This variable presents a set of checkboxes which control the - defaults for some of the member options. \emph{Conceal the - member's address} specifies whether or not the address is - displayed in the list roster. \emph{Acknowledge the member's - posting} controls whether or not Mailman sends an acknowledgement - to a member when they post a message to the list. \emph{Do not - send a copy of a member's own post} specifies whether a member - posting to the list will get a copy of their own posting. - \emph{Filter out duplicate messages to list members (if possible)} - specifies whether members who are explicitly listed as a recipient - of a message (e.g. via the \mailheader{Cc} header) will also get a - copy from Mailman. - - Of course, members can always override these defaults by making - changes on their membership options page. - -\item[administrivia] - This option specifies whether Mailman will search posted messages - for \emph{admimistrivia}, in other words, email commands which - usually should be posted to the \code{-request} address for the - list. Setting this to \emph{Yes} helps prevent such things as - unsubscribe messages getting erroneously posted to the list. - - If a message seems to contain administrivia, it is held for - moderator approval. - -\item[max_message_size] - This option specifies a maximum message size, in kilobytes, over - which the message will be held for moderator approval. - -\item[host_name] - This option specifies the host name part of email addresses used - by this list. For example, this is the \code{example.com} part of - the posting address \code{mylist@example.com}. - - It's generally not a good idea to change this value, since its - default value is specified when the mailing list is created. - Changing this to an incorrect value could make it difficult to - contact your mailing list. Also not that the url used to visit - the list's pages is not configurable through the web interface. - This is because if you messed it up, you'd have to have the site - administrator fix it. - -\item[include_rfc2369_headers] - \rfc{2369} is an internet standard that describes a bunch of - headers that mailing list managers should add to messages to make - it easier for people to interact with the list. Mail reading - programs which support this standard may provide buttons for easy - access to the list's archives, or for subscribing and - unsubscribing to the list. It's generally a good idea to enable - these headers as it provides for an improved user experience. - These headers are often called the \code{List-*} headers. - - However, not all mail readers are standards compliant yet, and if - you have a large number of members who are using non-compliant - mail readers, they may be annoyed at these headers. You should - first try to educate your members as to why these headers exist, - and how to hide them in their mail clients. As a last resort you - can disable these headers, but this is not recommended. - -\item[include_list_post_header] - The \mailheader{List-Post} header is one of the headers - recommended by \rfc{2369}. However for some announce-only mailing - lists, only a very select group of people are allowed to post to - the list; the general membership is usually not allowed to post to - such lists. For lists of this nature, the \mailheader{List-Post} - header is misleading. Select \emph{No} to disable the inclusion - of this header. (This does not affect the inclusion of the other - \code{List-*} headers.) -\end{description} - -\subsection{The Passwords Category} -As mentioned above, there are two primary administrative roles for -mailing lists. In this category you can specify the password for -these roles. - -The list owner has total control over the configuration of their -mailing list (within some bounds as specified by the site -administrator). Note that on this page, for historical reasons, the -list owner role is described here as the \emph{list administrator}. -You can set the list owner's password by entering it in the password -field on the left. You must type it twice for confirmation. Note -that if you forget this password, the only way for you to get back -into your list's administrative pages is to ask the site administrator -to reset it for you (there's no password reminders for list owners). - -If you want to delegate list moderation to someone else, you can enter -a different moderator password in the field on the right (typed twice -for confirmation). Note that if you aren't going to delegate -moderation, and the same people are going to both configure the list -and moderate postings to the list, don't enter anything into the -moderator password fields. If you do enter a separate moderator -password, be sure to fill in the \code{moderator} variable in the -\emph{General options} category page. - -\subsection{The Language Options Category} -Mailman is multilingual and internationalized, meaning you can set up -your list so that members can interact with it in any of a number of -natural languages. Of course, Mailman won't translate list -postings. :) - -However, if your site administrator has enabled its support, you can -set your list up to support any of about two dozen languages, such as -German, Italian, Japanese, or Spanish. Your list members can then -choose any of your supported languages as their \emph{preferred -language} for interacting with the list. Such things as their member -options page will be displayed in this language. Each mailing list -also has its own \emph{preferred language} which is the language the -list supports if no other language context is known. - -These variables control the language settings for your mailing list: - -\begin{description} -\item[preferred_language] - This is the list's preferred language, which is the language that - the list administrative pages will be displayed in. Also any - messages sent to the list owners by Mailman will be sent in this - language. This option is presented as a drop-down list containing - the language enabled in the \code{available_languages} variable. - -\item[available_languages] - This set of checkboxes contains all the natural languages that - your site administrator has made available to your mailing lists. - Select any language that you'd either like your members to be able - to view the list in, or that you'd like to be able to use in your - list's \code{preferred_language} variable. - -\item[encode_ascii_prefixes] - If your mailing list's preferred language uses a non-ASCII - character set and the \code{subject_prefix} contains non-ASCII - characters, the prefix will always be encoded according to the - relevant standards. However, if your subject prefix contains only - ASCII characters, you may want to set this option to \emph{Never} - to disable prefix encoding. This can make the subject headers - slightly more readable for users with mail readers that don't - properly handle non-ASCII encodings. - - Note however, that if your mailing list receives both encoded and - unencoded subject headers, you might want to choose \emph{As - needed}. Using this setting, Mailman will not encode ASCII - prefixes when the rest of the header contains only ASCII - characters, but if the original header contains non-ASCII - characters, it will encode the prefix. This avoids an ambiguity - in the standards which could cause some mail readers to display - extra, or missing spaces between the prefix and the original - header. -\end{description} - -\subsection{The Membership Management Category} - -The \emph{Membership Management} category is unlike the other -administrative categories. It doesn't contain configuration variables -or list settings. Instead, it presents a number of pages that allow -you to manage the membership of you list. This includes pages for -subscribing and unsubscribing members, and for searching for members, -and for changing various member-specific settings. - -More details on membership management are described in the Membership -Management section. - -\subsection{The Non-digest Options Category} - -Mailman delivers messages to users via two modes. List members can -elect to receive postings in bundles call \emph{digests} one or a few -times a day, or they can receive messages immediately whenever the -message is posted to the list. This latter delivery mode is also -called \emph{non-digest delivery}. There are two administrative -categories available for separately controlling digest and non-digest -delivery. You can even disable one or the other forms of delivery -(but not both). - -Both kinds of delivery can have list-specific headers and footers -added to them which can contain other useful information you want your -list members to see. For example, you can include instructions for -unsubscribing, or a url to the lists digest, or any other information. - -Non-digest deliveries can also be \emph{personalized} which means -certain parts of the message can contain information tailored to the -member receiving the message. For example, the \mailheader{To} header -will contain the address of the member when deliveries are -personalized. Footers and headers can contain personalized -information as well, such as a link to the individual user's options -page. - -In addition, personalized messages will contain extra information that -Mailman can use to unambiguously track bounces from members. -Ordinarily, Mailman does some pattern recognition on bounce messages -to determine list members whose addresses are no longer valid, but -because of the vagaries of mail systems, and the countless forwards -people can put in place, it's often the case that bounce messages -don't contain any useful information in them. Personalized messages -avoid this problem by encoding information in certain headers that -unambiguously identify the recipient of a message. If that message -bounces, Mailman will know exactly which member it was intended for. - -Note that because personalization requires extra system resources, it -must be enabled by the site administrator before you can choose it. - -Here are the variables which control non-digest delivery: - -\begin{description} -\item[nondigestable] - This option controls whether members can receive immediate - delivery or not. If not, they will be forced to receive messages - in digests. You can't disable non-digest delivery if digests are - already disabled. - -\item[personalize] - This option turns on message personalization. - -\item[msg_header] - This text box lets you enter information that will be included in - the header of every non-digest message sent through the - list. - - See below for more information on what can go in the headers and - footers. If you leave this text box empty, no header will be - added. - -\item[msg_footer] - Just like with the header, you can add a footer to every message. - The same rules apply to footers as apply to headers. -\end{description} - -Headers and footers can contain any text you want. For non-English -lists, the headers and footers can contain any character in the -character set of the list's preferred language. The headers and -footers can also contain \emph{substitution variables} which Mailman -will fill in with information taken from the mailing list. These -substitutions are in Python string interpolation format, where -something like \code{\%(list_name)s} is substituted with he name of -the mailing list. Note that the trailing \samp{s} is -required\footnote{The site administrator can configure lists to use a -simpler interpolation format, where \code{\$list_name} or -\code{\$\{list_name\}} would be substituted with the mailing list's -name. Ask your site administrator if the've configured your list this -way.}. - -For example, a footer containing the following text: - -\begin{verbatim} -This is the \%(list_name)s mailing list -Description: \%(description)s -\end{verbatim} - -might get attached to postings like so: - -\begin{verbatim} -This is the Example mailing list -Description: An example of Mailman mailing lists -\end{verbatim} - -Here is the list of substitution variables available for your headers -and footers: - -\begin{description} -\item[real_name] - This is the value of the \code{real_name} configuration variable - in the General options category. - -\item[list_name] - This is the canonical name of the mailing list. In other words - it's the posting address of the list\footnote{For backward - compatibility, the variable \code{_internal_name} is - equivalent.}. - -\item[host_name] - This is the domain name part of the email address for this list. - -\item[web_page_url] - This is the base url for contacting the list via the web. It can - be appended with \code{listinfo/\%(list_name)s} to yield the - general list information page for the mailing list. - -\item[description] - The brief description of the mailing list. - -\item[info] - This is the full description of the mailing list. - -\item[cgiext] - This is the extension added to CGI scripts. It might be the empty - string, \code{.cgi}, or something else depending on how your site - is configured. -\end{description} - -Note that \code{real_name}, \code{host_name}, \code{description}, and -\code{info} substitution variables take their values from the list -configuration variables of the same name. - -When personalization is enabled, the following substitution variables -are also available: - -\begin{description} -\item[user_address] - The address of the recipient of the message, coerced to lower case. - -\item[user_delivered_to] - The case-preserved address that the user subscribed to the mailing - list with\footnote{Usually it makes no difference which of - \code{user_address} and \code{user_delivered_to} is used, but it's - important to remember that they can be different. When they're - different, Mailman always uses the lower case address as the key - to the member's subscription information, but it always delivers - messages to the case-preserved version.}. - -\item[user_password] - The user's password, in clear text. - -\item[user_name] - The user's full name. - -\item[user_optionsurl] - The url to the user's personal options page. -\end{description} - -\subsection{The Digest Options Category} - -Digest delivery is a way to bundle many articles together into one -package, which can be delivered once per day (if there were any posted -articles), or whenever the package is bigger than a specified limit. -Some users may prefer this style of delivery for higher traffic lists -since they will receive fewer messages. - -Mailman supports two standard digest formats, and if digests are -enabled, users can select which of the two formats they receive. One -is MIME digests, where each message is an attachment inside a -\mimetype{multipart/digest}. This format also contains a summary -table of contents, and of course the an optional header and footer, -and it retains most of the headers of the original messages. - -The second type is called ``plaintext'' digests because they are -readable in mail readers that don't support MIME. Actually, they -adhere to the \rfc{1153} digest standard. The retain some, but not -all of the original messages, but can also include a summary and -headers and footers. - -Like non-digest delivery, you can enable or disable digest delivery, -but you cannot disable both types of delivery. You can specify -different headers and footers for digest and non-digest deliveries. -You cannot personalize digest deliveries. - -As list administrator, you may want to send an urgent message to all -list members, bypassing the normal digest bundling. To do this, send -the message with a \mailheader{Urgent} header, where the value of the -header is the list administrator's password. Non-digest members will -receive the message like normal, but digest members will receive the -message immediately\footnote{They'll also receive the message in the -digest.}. - -Here are the variables which control digest delivery: - -\begin{description} -\item[digestable] - The option controls whether members can receive digest deliveries - or not. If not, they will be forced to receive immediate - deliveries. You can't disable digests if non-digests are already - disabled. - -\item[digest_is_default] - Controls which style of delivery is the default for new members. - You can choose \emph{Regular} (non-digest) or \emph{Digest} - delivery. - -\item[mime_is_default_digest] - If a member is allowed to choose digests, this variable controls - which is the default digest style they will receive. \emph{Plain} - digests are \rfc{1153} format as described above. - -\item[digest_size_threshold] - Normally, digest members get at least one message per day, if - there have been any messages posted to the list. However, for - high volume lists, you may want to send out digests when the size - has reached a certain threshold, otherwise, the one digest they - receive could be huge. This variable controls the size threshold - by specifying the maximum digest size in kilobytes. Note that - this threshold isn't exact. Set this variable to zero to specify - that there is no size threshold, in which case no more than one - digest will be sent out per day. - -\item[digest_send_periodic] - This variable actually controls whether or not a digest is sent - daily when the size threshold has not yet been met. If set to - \emph{No}, then digests will only be sent when they are bigger - than \code{digest_size_threshold}. - -\item[digest_header] - This text box lets you enter information that will be included in - the header of every digest message sent through the list. The - same information can go in this header as can go in the - \code{msg_header}, except for the personalization variables. - -\item[digest_footer] - Just like with the header, you can add a footer to every message. - The same rules apply to digest footers as apply to digest headers. - -\item[digest_volume_frequency] - Each digest is numbered with a volume and an issue. This variable - controls how often a new digest volume is sent. When the digest - volume number is incremented, the issue number is reset to 1. - -\item[_new_volume] - This is an action variable, which forces an increment of the - volume number as soon as you submit the form. - -\item[_send_digest_now] - This is another action variable. Select \emph{Yes}, submit the - form, and the current digest is packaged up and sent to digest - members, regardless of size (well, there has to be at least one - message in the digest). -\end{description} - -\subsection{The Privacy Options Category} - -The Privacy category lets you control how much of the list's -information is public, as well as who can send messages to your list. -It also contains some spam detection filters. Note that this section -is not used to control whether your list's archives are public or -private; for that, use the \ref{Archiving options} category. - -There are four sub-categories: -\begin{itemize} -\item Subscription rules -- i.e. the rules for joining and leaving - your mailing list - -\item Sender filters -- the rules for who may post messages to your - list - -\item Recipient filters -- moderation rules based on the recipient of - the message - -\item Spam filters -- some regular expression based rules for header - matching -\end{itemize} - -The sender, recipient, and spam filtering rules are part of the -general list moderation features of Mailman. When a message is posted -to the list, it is matched against a number of criteria, the outcome -of which determines whether the message is reflected to the membership -or not. In general, the outcome is one of four states: - -\begin{itemize} -\item Approved or Accepted -- the message may be sent on to the - members of the mailing list. - -\item Hold -- the message will be held for moderator approval. The - list owners and moderators will then have to explicitly approve - the message before the list members will see it. - -\item Reject -- the message is bounced back to the original sender, - often with a notice containing the reason the message was - rejected. The list members never see rejected messages. - -\item Discard -- the message is simply thrown away without further - processing. -\end{itemize} - -Many of the fields in this section are text boxes accepting addresses, -one per line. Unless otherwise noted, these also accept regular -expressions which will be matched against an address, if the line -begins with a \^ (caret) character. - -\subsubsection{Subscription rules} - -This subcategory controls the rules for exposing the existance of this -list, and for what new members must do in order to subscribe to the -list. - -\begin{description} -\item[advertised] - This option controls whether this list will show up in the list - overview for the site. Normally, an overview contains the name - and short description of every mailing list in the virtual - domain. By setting this variable to \emph{No}, it will not show - up in this overview, nor will it show up in the administrative - overview. The only way then to find the list is to guess (or - know!) its name. - -\item[subscribe_policy] - This option controls the steps that a new member must take to join - the list. The available options may differ based on some defaults - that the site administrator chooses. They are: - - \begin{itemize} - \item None -- No verification is done on the subscribing - member. This is also called \emph{open subscriptions} and is - generally disabled by default. The site administrator must - allow list admins to choose this option; if not, this option - will not be presented to you. - - \item Confirm -- An email confirmation step is required before the - address is added to the list. When a member requests - subscription, either via the web page or by sending a - message to \var{yourlist}\code{-join@example.com}, Mailman - will send a confirmation message to the requesting address. - This mail-back confirmation contains a unique identifier, - which the requester can present to Mailman in order to - confirm their subscription. This can be done either by - replying to the mail-back, or by visiting the url in the - mail-back message. The url points to a page that lets the - user either discard or confirm their request. - - \item Require approval -- All subscription requests are held for - approval of the list moderator. No mail-back confirmation - is sent, but the list admins will recieve a message - indicating that approval is pending. - - \item Confirm and approve -- Here, a mail-back notice must first - be confirmed by the requester. Once confirmed, the list - moderator must then approve the request. This is the most - secure method for users to subscribe since it both verifies - the requesting address, and forces the list moderators to - approve the request. - - \end{itemize} - -\item[unsubscribe_policy] - Specifies whether the list moderator's approval is required for - unsubscription requests. \emph{No} is highly recommended, since - it is exceedingly impolite to not allow people to leave a mailing - list whenever they want (i.e. opt-out). \emph{Yes} is useful in - some specialized contexts; e.g. you may not want to allow - employees to unsubscribe from the company newsletter. - -\item[ban_list] - This contains a list of addresses (or regular expressiosn), one - per line, that are banned from ever subscribing to your mailing - list. If a match occurs during the subscription process, the - request will be automatically rejected, and the requester will get - a rejection notice. You can use this to permanently ban - troublesome posters to a members-only list. - -\item[private_roster] - This specifies who is allowed to view the roster of member - addresses. If you choose \emph{Anyone}, then the list membership - is completely public. You can limit exposure of the roster to - just list members, or just to the list administrators. In the - former case, a user must enter a valid member's address and - password before they can view the roster. In the latter case, a - list administrator's password must be enter; if a matching admin - password is entered, address field is ignored. - -\item[obscure_addresses] - Controls whether some simple obfuscation of addresses is used when - member addresses are included on web pages. This should reduce - the opportunity for email address harvesting by spammers, although - it probably doesn't eliminate it. -\end{description} - -\subsubsection{Sender filters} - -When a message is posted to the list, a series of moderation criteria are -applied to determine the disposition of the message. This section -contains the modeation controls for postings from both members and -non-members. - -\begin{description} -\item[default_member_moderation] - Member postings are held for moderation if their \emph{moderation - flag} is turned on. Note that only the list administrators can - change the value of a member's moderation flag. - - You can control whether new members get their moderation flag - turned on or off by default when they subscribe to the list. By - turning this flag off by default, postings by members will be - allowed without further intervention (barring other restrictions - such as size or implicit recipient lists -- see below). By - turning the flag on, you can quarantine new member postings to - make sure that they meet your criteria for netiquette, topicality, - etc. Once you determine that the new member understands the - community's posting rules, you can turn off their moderation flag - and let their postings go through unstopped. - - E-newsletter style lists can also be set up by using the - moderation flag. By setting the \code{member_moderation_action} - to \emph{Reject}, and by turning off the moderation flag for just - the few approved senders, your list will operate in essentially a - one-way direction. Note that you'd also need to reject or discard - postings from non-members. - -\item[member_moderation_action] - This is the action to take for postings from a member who's - moderation flag is set. For typical discussion lists, you'll - likely set this to \emph{Hold} so that the list moderator will get - a chance to manually approve, reject, or discard the message. For - e-newsletter and announcement lists, you might want to set this to - \emph{Reject} or \emph{Discard}. - - Note that when a moderated member posts to your list, and the - \code{member_moderation_action} is set to \emph{Hold}, the message - will appear on the administrative requests page. When you dispose - of the message, you will be given an opportunity to clear the - moderation flag at the same time. If you're quarantining new - posts, this makes it very convenient to both approve a new - member's post and de-moderate them at the same time. - -\item[member_moderation_notice] - When a member's moderation flag is turned on and - \code{member_moderation_action} is \emph{Reject}, this variable - contains the text sent in the rejection notice. -\end{description} - -The next batch of variables controls what happens when non-members -post messages to the list. Each of these accepts one email address -per line; regular expressions are allowed if the line starts with the -\^ (caret) character. These address lists are always consulted in the -order in which they're presented on this page (i.e. accepts first, -followed by holds, rejections, and discards). - -\begin{description} -\item[accept_these_nonmembers] - Postings from non-members whose addresses match this list are - accepted, barring other list restrictions due to size, implicit - recipients, etc. You might want to add alternative addresses of - approved posters to this list. - -\item[hold_these_nonmembers] - Postings from non-members whose addresses match this list are - held for moderator approval. - -\item[reject_these_nonmembers] - Postings from non-members whose addresses match this list are - rejected, i.e. bounced back to the original sender. There - currently is no way to add additional text to the rejection - message. - -\item[discard_these_nonmembers] - Postings from non-members whose addresses match this list are - discarded, with no bounce back message. You might want to add the - addresses of known spammers to this list. - -\item[generic_nonmember_action] - This variable controls what happens to non-member posts when the - address of the sender doesn't match any of the above four lists. - If you set this to \emph{Hold}, the posting will appear on the - administrative requests page, and you will be given an opportunity - to add the non-member to one of the above four lists at the same - time you dispose of the held message. - -\item[forward_auto_discards] - When messages from non-members are discarded, either because the - sender address matched \code{discard_these_nonmembers}, or because - \code{generic_nonmember_action} is \emph{Discard}, you can choose - whether such messages are forwarded to the lsit administrators or - not. -\end{description} - -\subsubsection{Recipient Filters} - -The variables in this section control various filters based on the -recipient of the message. - -\begin{description} -\item[require_explicit_destination] - This controls whether the mailing list posting address must be - explicitly named in the \mailheader{To} or \mailheader{Cc} - recipient lists. The main reason why it wouldn't is if the - message was blind-carbon-copied (i.e. \mailheader{Bcc}'d) to the - list. Spammers like to do this, but sometimes legitimate messages - are forwarded to the list this way. - - If the list is not explicitly addressed and this setting is turned - on, the message will be held for moderator approval. - -\item[acceptable_aliases] - This is the list of alternative addresses that are acceptable as a - list posting address when \code{require_explicit_destination} is - enabled. This is useful for when there aliases for the main - posting address (e.g. \code{help@example.com} may be an alias for - \code{help-list@example.com}). - -\item[max_num_recipients] - This is the maximum number of explicit recipients that are allowed - on the posted message. Spammers sometimes send messages with lots - of explicit recipients, so setting this number to a reasonable - value may cut down on spam. -\end{description} - -\subsubsection{Spam Filters} - -This section provides some adjuncts to spam fighting tools; it -doesn't replace dedicated anti-spam tools such as SpamAssassin or -Spambayes. - -\begin{description} -\item[bounce_matching_headers] - This variable contains header regular expressions, one per line, - and if any of a message's headers matches one of these patterns, - it will be held for moderation. The format is a colon separated - header and value, where the header is case insensitive and the - value is any valid Python regular expression. Lines that start - with \# are ignored. - - This variable can be used to catch known spammers by writing - regexps that match against \mailheader{To} or \mailheader{Cc} - lines, or known-bad \mailheader{Message-ID}s. Perhaps more useful - though are patterns that match headers added by spam detection - tools higher up in the tool chain. For example, you might - configure SpamAssassin to add an \mailheader{X-Spam-Score} header - with between zero and 5 stars depending on the spam score. Then - you can add a line to this variable like: - - \begin{verbatim} - X-Spam-Score: [*]{3,5} - \end{verbatim} - - This line will match from 3 to 5 stars in the value of this - field. -\end{description} - -\subsection{The Bounce Processing Category} - -These policies control the automatic bounce processing system in -Mailman. Here's an overview of how it works: - -When a bounce is received, Mailman tries to extract two pieces of -information from the message: the address of the member the message -was intended for, and the severity of the problem causing the bounce. -The severity can be either \emph{hard} for fatal errors, or -\emph{soft} for transient errors. When in doubt, a hard severity is -used. - -If no member address can be extracted from the bounce, then the bounce -message is usually discarded. Every member has a \emph{bounce score}, -initialized at zero, and every time we encounter a bounce from a -member we increment that member's score. Hard bounces increment by 1 -while soft bounces increment by 0.5. We only increment the bounce -score once per day, so even if we receive ten hard bounces from a -member per day, their score will increase by only 1 for that day. - -When a member's bounce score is greater than the \emph{bounce score -threshold} (see below), the member's subscription is disabled. Once -disabled, the member will not receive any postings from the list until -their membership is explicitly re-enabled, either by the list -administrator or the user. However, they will receive occasional -reminders that their membership has been disabled, and these reminders -will include information about how to re-enable their membership. You -can control both the number of reminders the member will receive and -the frequency with which these reminders are sent. - -There is one other important configuration variable; after a certain -period of time -- during which no bounces from the member are received --- the bounce information is considered stale and discarded. Thus by -adjusting this value, and the score threshold, you can control how -quickly bouncing members are disabled. You should tune both of these -to the frequency and traffic volume of your list. - -\begin{description} - -\item[bounce_processing] - Specifies whether or not this list should do automatic bounce - processing. - -\item[bounce_score_threshold] - This is the bounce score above which a member's subscription will - be automatically disabled. When the subscription is re-enabled, - their bounce score will be reset to zero. This value can be a - floating point number. - -\item[bounce_info_stale_after] - Thenumber of days after which a member's bounce information is - considered stale. If no new bounces have been received in the - interrim, the bounce score is reset to zero. This value must be - an integer. - -\item[bounce_you_are_disabled_warnings] - The number of notices a disabled member will receive before their - address is removed from the mailing list's roster. Set this to 0 - to immediately remove an address from the list once their bounce - score exceeds the threshold. This value must be an integer. - -\item[bounce_you_are_disabled_warnings_interval] - The number of days between each disabled notification. - -\item[bounce_unrecognized_goes_to_list_owner] - This variable controls whether unrecognized bounces are discarded, - or forwarded on the list administrator. The bounce detector isn't - perfect, although personalization can make it much more accurate. - The list owner may want to receive unrecognized bounces so that - they can manually disable or remove such members. - -\item[bounce_notify_owner_on_disable] - This option controls whether or not the list owner is notified - when a member's subscription is automatically disabled due to - their bounce threshold being reached. - -\item[bounce_notify_owner_on_removal] - This option controls whether or not the list owner is notified - when a member is removed from the list after their disabled - notifications have been exhausted. -\end{description} - -\subsection{The Archiving Options Category} - -Mailman comes with a built-in web-based archiver called -\emph{Pipermail}, although it can be configured to use external, -third party archivers. - -\begin{description} - -\item[archive] - This option tells Mailman whether to archive messages it receives - or not, regardless of whether Pipermail or a third party archiver - is used. Turn this off if you don't want to archive messages. - - Note that senders can control whether their own posts are - archived, on an individual per-message basis. If the posted - message has a \mailheader{X-No-Archive} header (regardless of - value), or a \mailheader{X-Archive} header with a value of - \code{No} (case insensitive), then the message will not be - archived, although it will be treated as normal in all other - ways. - -\item[archive_private] - Controls whether Pipermail archives are private or public. - Private archives require a valid member address and password, or a - list administrator password in order to access them. This - option has no effect when a third party archiver is used. - -\item[archive_volume_frequency] - Controls how Pipermail splits messages in the archive. The most - common option is \emph{Monthly} meaning a new archive volume is - started every month. Very high volume lists may want a shorter - frequency (e.g. \emph{Weekly} or \emph{Daily}) where as lower - volume lists may want a longer frequency (e.g. \emph{Yearly}). - This option has no effect when a third party archiver is used. -\end{description} - -\subsection{The Mail/News Gateway Category} - -Mailman has a sophisticated mail-to-news gateway feature. It can -independently gate messages from news to mail and vice versa, and can -even be used to manage moderated newsgroups. - -\subsection{The Auto-responder Category} -\subsection{The Content Filtering Category} -\subsection{The Topics Category} - -\section{Membership Management} -\section{Tending to Pending Moderator Requests} -\section{Editing the Public HTML Pages} -\section{Deleting the Mailing List} - -\appendix - -\section{This is an Appendix} - -To create an appendix in a Python HOWTO document, use markup like -this: - -\begin{verbatim} -\appendix - -\section{This is an Appendix} - -To create an appendix in a Python HOWTO document, .... - - -\section{This is another} - -Just add another \section{}, but don't say \appendix again. -\end{verbatim} - - -\end{document} diff --git a/doc/mailman-admin.txt b/doc/mailman-admin.txt new file mode 100644 index 00000000..210fbec8 --- /dev/null +++ b/doc/mailman-admin.txt @@ -0,0 +1,1352 @@ + #GNU mailman - list Administration Manual Contents About this + document... About this document... + + Previous Page Up one Level Next Page GNU Mailman - List Administration + Manual + __________________________________________________________________ + +GNU Mailman - List Administration Manual + + Barry A. Warsaw + + Release 2.1 + December 5, 2007 + + Front Matter + + Abstract: + + This document describes the list administrator's interface for GNU + Mailman 2.1. It contains information a list owner would need to + configure their list, either through the web interface or through + email. It also covers the moderator's interface for approving held + messages and subscription notices, and the web interface for creating + new mailing lists. In general, it does not cover the command line + interface to Mailman, installing Mailman, or interacting with Mailman + from the point of view of the user. That information is covered in + other manuals. + +Contents + + * + + 1 Introduction to GNU Mailman + o 1.1 A List's Email Addresses + o 1.2 Administrative Roles + o 1.3 A List's Web Pages + o 1.4 Basic Architectural Overview + + 2 The List Configuration Pages + o 2.1 The General Options Category + o 2.2 The Passwords Category + o 2.3 The Language Options Category + o 2.4 The Membership Management Category + o 2.5 The Non-digest Options Category + o 2.6 The Digest Options Category + o 2.7 The Privacy Options Category + o 2.8 The Bounce Processing Category + o 2.9 The Archiving Options Category + o 2.10 The Mail/News Gateway Category + o 2.11 The Auto-responder Category + o 2.12 The Content Filtering Category + o 2.13 The Topics Category + + 3 Membership Management + + 4 Tending to Pending Moderator Requests + + 5 Editing the Public HTML Pages + + 6 Deleting the Mailing List + + 1 This is an Appendix + + 1 Introduction to 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 for controlling the privacy of your lists, distributing your + list as personalized postings or digests, gatewaying postings to and + from Usenet, and providing automatic bounce detection. Mailman provides + a built-in archiver, multiple natural languages, as well as advanced + content and topic filtering. + + Mailman provides several interfaces to its functionality. Most list + administrators will primarily use the web interface to customize their + lists. There is also a limited email command interface to the + administrative functions, as well as a command line interface if you + have shell access on the Mailman server. This document does not cover + the command line interface; see the GNU Mailman site administrator's + manual for more details. + +1.1 A List's Email Addresses + + Every mailing list has a set of email addresses that messages can be + sent to. There's always one address for posting messages to the list, + one address that bounces will be sent to, and addresses for processing + email commands. For example, for a mailing list called + mylist@example.com, you'd find these addresses: + + * mylist@example.com - this is the email address people should use + for new postings to the list. + * mylist-join@example.com - by sending a message to this address, a + new member can request subscription to the list. Both the Subject: + header and body of such a message are ignored. Note that + mylist-subscribe@example.com is an alias for the -join address. + * mylist-leave@example.com - by sending a message to this address, a + member can request unsubscription from the list. As with the -join + address, the Subject: header and body of the message is ignored. + Note that mylist-unsubscribe@example.com is an alias for the -leave + address. + * mylist-owner@example.com - This address reaches the list owner and + list moderators directly. + * mylist-request@example.com - This address reaches a mail robot + which processes email commands that can be used to set member + subscription options, as well as process other commands. + * mylist-bounces@example.com - This address receives bounces from + members who's addresses have become either temporarily or + permanently inactive. The -bounces address is also a mail robot + that processes bounces and automatically disables or removes + members as configured in the bounce processing settings. Any bounce + messages that are either unrecognized, or do not seem to contain + member addresses, are forwarded to the list administrators. + * mylist-confirm@example.com - This address is another email robot, + which processes confirmation messages for subscription and + unsubscription requests. + + There's also an -admin address which also reaches the list + administrators, but this address only exists for compatibility with + older versions of Mailman. + +1.2 Administrative Roles + + There are two primary administrative roles for each mailing list, a + list owner and a list moderator. A list owner is allowed to change + various settings of the list, such as the privacy and archiving + policies, the content filtering settings, etc. The list owner is also + allowed to subscribe or invite members, unsubscribe members, and change + any member's subscription options. + + The list moderator on the other hand, is only allowed to approve or + reject postings and subscription requests. The list moderator can also + do things like clear a member's moderation flag, or add an address to a + list of approved non-member posters. + + Normally, the list owner and list moderator are the same person. In + fact, the list owner can always do all the tasks a list moderator can + do. Access to both the owner's configuration pages, and the moderation + pages are protected by the same password. However, if the list owner + wants to delegate posting and subscription approval authority to other + people, a separate list moderator password can be set, giving + moderators access to the approval pages, but not the configuration + pages. In this setup, list owners can still moderate the list, of + course. + + In the sections that follow, we'll often use the terms list owner and + list administrator interchangably, meaning both roles. When necessary, + we'll distinguish the list moderator explicitly. + +1.3 A List's Web Pages + + Every mailing list is also accessible by a number of web pages. Note + that the exact urls is configurable by the site administrator, so they + may be different than what's described below. We'll describe the most + common default configuration, but check with your site administrator or + hosting service for details. + + Mailman provides a set of web pages that list members use to get + information about the list, or manage their membership options. There + are also list archive pages, for browsing an online web-based archive + of the list traffic. These are described in more detail in the GNU + Mailman user's manual. + + Mailman also provides a set of pages for configuring an individual + list, as well as a set of pages for disposing of posting and + subscription requests. + + For a mailing list called mylist hosted at the domain + lists.example.com, you would typically access the administrative pages + by going to http://lists.example.com/mailman/admin/mylist. The first + time you visit this page, you will be presented with a login page, + asking for the list owner's password. When you enter the password, + Mailman will store a session cookie in your browser, so you don't have + to re-authenticate for every action you want to take. This cookie is + stored only until you exit your browser. + + To access the administrative requests page, you'd visit + http://lists.example.com/mailman/admindb/mylist (note the admindb url + as opposed to the admin url). Again, the first time you visit this + page, you'll be presented with a login page, on which you can enter + either the list moderator password or the list owner password. Again, a + session cookie is dropped in your browser. Note also that if you've + previously logged in as the list owner, you do not need to re-login to + access the administrative requests page. + +1.4 Basic Architectural Overview + + This section will outline the basic architecture of GNU Mailman, such + as how messages are processed by the sytem. Without going into lots of + detail, this information will help you understand how the configuration + options control Mailman's functionality. + + When mail enters the system from your mail server, it is dropped into + one of several Mailman queues depending on the address the message was + sent to. For example, if your system has a mailing list named mylist + and your domain is example.com, people can post messages to your list + by sending them to mylist@example.com. These messages will be dropped + into the incoming queue, which is also colloquially called the + moderate-and-munge queue. The incoming queue is where most of the + approval process occurs, and it's also where the message is prepared + for sending out to the list membership. + + There are separate queues for the built-in archiver, the bounce + processor, the email command processor, as well as the outgoing email + and news queues. There's also a queue for messages generated by the + Mailman system. Each of these queues typically has one queue runner (or + ``qrunner'') that processes messages in the queue. The qrunners are + idle when there are no messages to process. + + Every message in the queues are represented by two files, a message + file and a metadata file. Both of these files share the same base name, + which is a combination of a unique hash and the Unix time that the + message was received. The metadata file has a suffix of .db and the + message file has a suffix of either .msg if stored in plain text, or + .pck if stored in a more efficient internal representation^1. + + As a message moves through the incoming queue, it performs various + checks on the message, such as whether it matches one of the moderation + criteria, or contains disallowed MIME types. Once a message is approved + for sending to the list membership, the message is prepared for sending + by deleting, adding, or changing message headers, adding footers, etc. + Messages in the incoming queue may also be stored for appending to + digests. + + 2 The List Configuration Pages + + After logging into the list configuration pages, you'll see the + configuration options for the list, grouped in categories. All the + administrative pages have some common elements. In the upper section, + you'll see two columns labeled ``Configuration Categories''. Some + categories have sub-categories which are only visible when you click on + the category link. The first page you see after logging in will be the + ``General Options'' category. The specific option settings for each + category are described below. + + On the right side of the top section, you'll see a column labeled + ``Other Administrative Activities''. Here you'll find some other things + you can do to your list, as well as convenient links to the list + information page and the list archives. Note the big ``Logout'' link; + use this if you're finished configuring your list and don't want to + leave the session cookie active in your browser. + + Below this common header, you'll find a list of this category's + configuration variables, arranged in two columns. In the left column is + a brief description of the option, which also contains a ``details'' + link. For many of the variables, more details are available describing + the semantics of the various available settings, or information on the + interaction between this setting and other list options. Clicking on + the details link brings up a page which contains only the information + for that option, as well as a button for submitting your setting, and a + link back to the category page. + + On the right side of the two-column section, you'll see the variable's + current value. Some variables may present a limited set of values, via + radio button or check box arrays. Other variables may present text + entry boxes of one or multiple lines. Most variables control settings + for the operation of the list, but others perform immediate actions + (these are clearly labeled). + + At the bottom of the page, you'll find a ``Submit'' button and a footer + with some more useful links and a few logos. Hitting the submit button + commits your list settings, after they've been validated. Any invalid + values will be ignored and an error message will be displayed at the + top of the resulting page. The results page will always be the category + page that you submitted. + +2.1 The General Options Category + + The General Options category is where you can set a variety of + variables that affect basic behavior and public information. In the + descriptions that follow, the variable name is given first, along with + an overview and a description of what that variable controls. + + 2.1.1 General list personality + + These variables, grouped under the general list personality section, + control some public information about the mailing list. + + real_name + Every mailing list has both a posting name and a real name. The + posting name shows up in urls and in email addresses, e.g. the + mylist in mylist@example.com. The posting name is always + presented in lower case, with alphanumeric characters and no + spaces. The list's real name is used in some public information + and email responses, such as in the general list overview. The + real name can differ from the posting name by case only. For + example, if the posting name is mylist, the real name can be + Posting. + + owner + This variable contains a list of email addresses, one address + per line, of the list owners. These addresses are used whenever + the list owners need to be contacted, either by the system or by + end users. Often, these addresses are used in combination with + the moderator addresses (see below). + + moderator + This variable contains a list of email addresses, one address + per line, of the list moderators. These addresses are often used + in combination with the owner addresses. For example, when you + email mylist-owner@example.com, both the owner and moderator + addresses will receive a copy of the message. + + description + In the general list overview page, which shows you every + available mailing list, each list is displayed with a short + description. The contents of this variable is that description. + Note that in emails from the mailing list, this description is + also used in the comment section of the To: address. This text + should be relatively short and no longer than one line. + + info + This variable contains a longer description of the mailing list. + It is included at the top of the list's information page, and it + can contain HTML. However, blank lines will be automatically + converted into paragraph breaks. Preview your HTML though, + because unclosed or invalid HTML can prevent display of parts of + the list information page. + + subject_prefix + This is a string that will be prepended to the Subject: header + of any message posted to the list. For example, if a message is + posted to the list with a Subject: like: + + Subject: This is a message + + and the subject_prefix is [My List] (note the trailing space!), + then the message will be received like so: + + Subject: [My List] This is a message + + If you leave subject_prefix empty, no prefix will be added to + the Subject:. Mailman is careful not to add a prefix when the + header already has one, as is the case in replies for example. + The prefix can also contain characters in the list's preferred + language. In this case, because of vagarities of the email + standards, you may or may not want to add a trailing space. + + anonymous_list + This variable allows you to turn on some simple anonymizing + features of Mailman. When you set this option to Yes, Mailman + will remove or replace the From:, Sender:, and Reply-To: fields + of any message posted to the list. + + Note that this option is simply an aid for anonymization, it + doesn't guarantee it. For example, a poster's identity could be + evident in their signature, or in other mail headers, or even in + the style of the content of the message. There's little Mailman + can do about this kind of identity leakage. + + 2.1.2 Reply-To header munging + + This section controls what happens to the Reply-To: headers of messages + posted through your list. + + Beware! Reply-To: munging is considered a religious issue and the + policies you set here can ignite some of the most heated off-topic + flame wars on your mailing lists. We'll try to stay as agnostic as + possible, but our biases may still peak through. + + Reply-To: is a header that is commonly used to redirect replies to + messages. Exactly what happens when your uses reply to such a message + depends on the mail readers your users use, and what functions they + provide. Usually, there is both a ``reply to sender'' button and a + ``reply to all'' button. If people use these buttons correctly, you + will probably never need to munge Reply-To:, so the default values + should be fine. + + Since an informed decision is always best, here are links to two + articles that discuss the opposing viewpoints in great detail: + + * Reply-To Munging Considered Harmful + * Reply-To Munging Considered Useful + + The three options in this section work together to provide enough + flexibility to do whatever Reply-To: munging you might (misguidingly :) + feel you need to do. + + first_strip_reply_to + This variable controls whether any Reply-To: header already + present in the posted message should get removed before any + other munging occurs. Stripping this header will be done + regardless of whether or not Mailman will add its own Reply-To: + header to the message. + + If this option is set to No, then any existing Reply-To: header + will be retained in the posted message. If Mailman adds its own + header, it will contain addresses which are the union of the + original header and the Mailman added addresses. The mail + standards specify that a message may only have one Reply-To: + header, but that that header may contain multiple addresses. + + reply_goes_to_list + This variable controls whether Mailman will add its own + Reply-To: header, and if so, what the value of that header will + be (not counting original header stripping - see above). + + When you set this variable to Poster, no additional Reply-To: + header will be added by Mailman. This setting is strongly + recommended. + + When you set this variable to This list, a Reply-To: header + pointing back to your list's posting address will be added. + + When you set this variable to Explicit address, the value of the + variable reply_to_address (see below) will be added. Note that + this is one situation where Reply-To: munging may have a + legitimate purpose. Say you have two lists at your site, an + announce list and a discussion list. The announce list might + allow postings only from a small number of approved users; the + general list membership probably can't post to this list. But + you want to allow comments on announcements to be posted to the + general discussion list by any list member. In this case, you + can set the Reply-To: header for the announce list to point to + the discussion list's posting address. + + reply_to_address + This is the address that will be added in the Reply-To: header + if reply_goes_to_list is set to Explicit address. + + 2.1.3 Umbrella list settings + + TBD. Note that umbrella lists are deprecated and will be replace with a + better mechanism for Mailman 3.0. + + 2.1.4 Notifications + + Mailman sends notifications to the list administrators or list members + under a number of different circumstances. Most of these notifications + can be configured in this section, but see the Bounce Processing and + Auto-responder categories for other notifications that Mailman can + send. + + send_reminders + By default Mailman sends all list members a monthly password + reminder. This notice serves two purposes. First, it reminds + people about all the lists they may be subscribed to on this + domain, including the lists where their subscription may be + disabled. Second, it reminds people about their passwords for + these lists, as well as the url for their personal options + pages, so that they can more easily configure their subscription + options. + + Some people get annoyed with these monthly reminders, and they + can disable the reminders via their subscription options page. + For some lists, the monthly reminders aren't appropriate for any + of the members, so you can disable them list-wide by setting the + send_reminders variable to No. + + welcome_msg + When new members are subscribed to the list, either by their own + action, or the action of a list administrator, a welcome message + can be sent to them. The welcome message contains some common + boilerplate information, such as the name of the list, + instructions for posting to the list, and the member's + subscription password. You can add additional information to the + welcome message by typing the text into the welcome_msg text + box. Note that because this text is sent as part of an email, it + should not contain HTML. + + send_welcome_msg + This flag controls whether or not the welcome message is sent to + new subscribers. + + goodbye_msg + Like the welcome_msg, a ``goodbye'' message can be sent to + members when they unsubscribe from the list. Unlike the welcome + message, there's no boilerplate for the goodbye message. Enter + the entire goodbye message you'd like unsubscribing members to + receive into the goodbye_msg text box. + + send_goodbye_msg + This flag controls whether or not the goodbye message is sent to + unsubscribing members. + + admin_immed_notify + List moderators get notifications of pending administrative + actions, such as subscription or unsubscription requests that + require moderator approval, or posted messages that are being + held for moderator approval. List moderators will always get a + daily summary of such pending requests, but they can also get + immediate notifications when such a request is made. The + admin_immed_notify variable controls whether these immediate + notifications are sent or not. It's generally a good idea to + leave this set to Yes. + + admin_notify_mchanges + This variable controls whether the list administrators should + get notifications when members join or leave the list. + + respond_to_post_requests + This variable controls whether the original sender of a posting + gets a notice when their message is held for moderator approval. + + 2.1.5 Additional settings + + This section contains some miscellaneous settings for your mailing + list. + + emergency + When this option is enabled, all list traffic is emergency + moderated, i.e. held for moderation. Turn this option on when + your list is experiencing a flamewar and you want a cooling off + period. + + new_member_options + Each member has a set of subscription options which they can use + to control how they receive messages and otherwise interact with + the list. While the members can change these settings by logging + into their personal options page, you might want to set the + default for a number of the member options. You can do that with + this variable, but see also the other categories for other + member defaults you can set. + + This variable presents a set of checkboxes which control the + defaults for some of the member options. Conceal the member's + address specifies whether or not the address is displayed in the + list roster. Acknowledge the member's posting controls whether + or not Mailman sends an acknowledgement to a member when they + post a message to the list. Do not send a copy of a member's own + post specifies whether a member posting to the list will get a + copy of their own posting. Filter out duplicate messages to list + members (if possible) specifies whether members who are + explicitly listed as a recipient of a message (e.g. via the Cc: + header) will also get a copy from Mailman. + + Of course, members can always override these defaults by making + changes on their membership options page. + + administrivia + This option specifies whether Mailman will search posted + messages for admimistrivia, in other words, email commands which + usually should be posted to the -request address for the list. + Setting this to Yes helps prevent such things as unsubscribe + messages getting erroneously posted to the list. + + If a message seems to contain administrivia, it is held for + moderator approval. + + max_message_size + This option specifies a maximum message size, in kilobytes, over + which the message will be held for moderator approval. + + host_name + This option specifies the host name part of email addresses used + by this list. For example, this is the example.com part of the + posting address mylist@example.com. + + It's generally not a good idea to change this value, since its + default value is specified when the mailing list is created. + Changing this to an incorrect value could make it difficult to + contact your mailing list. Also not that the url used to visit + the list's pages is not configurable through the web interface. + This is because if you messed it up, you'd have to have the site + administrator fix it. + + include_rfc2369_headers + RFC 2369 is an internet standard that describes a bunch of + headers that mailing list managers should add to messages to + make it easier for people to interact with the list. Mail + reading programs which support this standard may provide buttons + for easy access to the list's archives, or for subscribing and + unsubscribing to the list. It's generally a good idea to enable + these headers as it provides for an improved user experience. + These headers are often called the List-* headers. + + However, not all mail readers are standards compliant yet, and + if you have a large number of members who are using + non-compliant mail readers, they may be annoyed at these + headers. You should first try to educate your members as to why + these headers exist, and how to hide them in their mail clients. + As a last resort you can disable these headers, but this is not + recommended. + + include_list_post_header + The List-Post: header is one of the headers recommended by RFC + 2369. However for some announce-only mailing lists, only a very + select group of people are allowed to post to the list; the + general membership is usually not allowed to post to such lists. + For lists of this nature, the List-Post: header is misleading. + Select No to disable the inclusion of this header. (This does + not affect the inclusion of the other List-* headers.) + +2.2 The Passwords Category + + As mentioned above, there are two primary administrative roles for + mailing lists. In this category you can specify the password for these + roles. + + The list owner has total control over the configuration of their + mailing list (within some bounds as specified by the site + administrator). Note that on this page, for historical reasons, the + list owner role is described here as the list administrator. You can + set the list owner's password by entering it in the password field on + the left. You must type it twice for confirmation. Note that if you + forget this password, the only way for you to get back into your list's + administrative pages is to ask the site administrator to reset it for + you (there's no password reminders for list owners). + + If you want to delegate list moderation to someone else, you can enter + a different moderator password in the field on the right (typed twice + for confirmation). Note that if you aren't going to delegate + moderation, and the same people are going to both configure the list + and moderate postings to the list, don't enter anything into the + moderator password fields. If you do enter a separate moderator + password, be sure to fill in the moderator variable in the General + options category page. + +2.3 The Language Options Category + + Mailman is multilingual and internationalized, meaning you can set up + your list so that members can interact with it in any of a number of + natural languages. Of course, Mailman won't translate list postings. :) + + However, if your site administrator has enabled its support, you can + set your list up to support any of about two dozen languages, such as + German, Italian, Japanese, or Spanish. Your list members can then + choose any of your supported languages as their preferred language for + interacting with the list. Such things as their member options page + will be displayed in this language. Each mailing list also has its own + preferred language which is the language the list supports if no other + language context is known. + + These variables control the language settings for your mailing list: + + preferred_language + This is the list's preferred language, which is the language + that the list administrative pages will be displayed in. Also + any messages sent to the list owners by Mailman will be sent in + this language. This option is presented as a drop-down list + containing the language enabled in the available_languages + variable. + + available_languages + This set of checkboxes contains all the natural languages that + your site administrator has made available to your mailing + lists. Select any language that you'd either like your members + to be able to view the list in, or that you'd like to be able to + use in your list's preferred_language variable. + + encode_ascii_prefixes + If your mailing list's preferred language uses a non-ASCII + character set and the subject_prefix contains non-ASCII + characters, the prefix will always be encoded according to the + relevant standards. However, if your subject prefix contains + only ASCII characters, you may want to set this option to Never + to disable prefix encoding. This can make the subject headers + slightly more readable for users with mail readers that don't + properly handle non-ASCII encodings. + + Note however, that if your mailing list receives both encoded + and unencoded subject headers, you might want to choose As + needed. Using this setting, Mailman will not encode ASCII + prefixes when the rest of the header contains only ASCII + characters, but if the original header contains non-ASCII + characters, it will encode the prefix. This avoids an ambiguity + in the standards which could cause some mail readers to display + extra, or missing spaces between the prefix and the original + header. + +2.4 The Membership Management Category + + The Membership Management category is unlike the other administrative + categories. It doesn't contain configuration variables or list + settings. Instead, it presents a number of pages that allow you to + manage the membership of you list. This includes pages for subscribing + and unsubscribing members, and for searching for members, and for + changing various member-specific settings. + + More details on membership management are described in the Membership + Management section. + +2.5 The Non-digest Options Category + + Mailman delivers messages to users via two modes. List members can + elect to receive postings in bundles call digests one or a few times a + day, or they can receive messages immediately whenever the message is + posted to the list. This latter delivery mode is also called non-digest + delivery. There are two administrative categories available for + separately controlling digest and non-digest delivery. You can even + disable one or the other forms of delivery (but not both). + + Both kinds of delivery can have list-specific headers and footers added + to them which can contain other useful information you want your list + members to see. For example, you can include instructions for + unsubscribing, or a url to the lists digest, or any other information. + + Non-digest deliveries can also be personalized which means certain + parts of the message can contain information tailored to the member + receiving the message. For example, the To: header will contain the + address of the member when deliveries are personalized. Footers and + headers can contain personalized information as well, such as a link to + the individual user's options page. + + In addition, personalized messages will contain extra information that + Mailman can use to unambiguously track bounces from members. + Ordinarily, Mailman does some pattern recognition on bounce messages to + determine list members whose addresses are no longer valid, but because + of the vagaries of mail systems, and the countless forwards people can + put in place, it's often the case that bounce messages don't contain + any useful information in them. Personalized messages avoid this + problem by encoding information in certain headers that unambiguously + identify the recipient of a message. If that message bounces, Mailman + will know exactly which member it was intended for. + + Note that because personalization requires extra system resources, it + must be enabled by the site administrator before you can choose it. + + Here are the variables which control non-digest delivery: + + nondigestable + This option controls whether members can receive immediate + delivery or not. If not, they will be forced to receive messages + in digests. You can't disable non-digest delivery if digests are + already disabled. + + personalize + This option turns on message personalization. + + msg_header + This text box lets you enter information that will be included + in the header of every non-digest message sent through the list. + + See below for more information on what can go in the headers and + footers. If you leave this text box empty, no header will be + added. + + msg_footer + Just like with the header, you can add a footer to every + message. The same rules apply to footers as apply to headers. + + Headers and footers can contain any text you want. For non-English + lists, the headers and footers can contain any character in the + character set of the list's preferred language. The headers and footers + can also contain substitution variables which Mailman will fill in with + information taken from the mailing list. These substitutions are in + Python string interpolation format, where something like %(list_name)s + is substituted with he name of the mailing list. Note that the trailing + "s" is required^2. + + For example, a footer containing the following text: + +This is the \%(list_name)s mailing list +Description: \%(description)s + + might get attached to postings like so: + +This is the Example mailing list +Description: An example of Mailman mailing lists + + Here is the list of substitution variables available for your headers + and footers: + + real_name + This is the value of the real_name configuration variable in the + General options category. + + list_name + This is the canonical name of the mailing list. In other words + it's the posting address of the list^3. + + host_name + This is the domain name part of the email address for this list. + + web_page_url + This is the base url for contacting the list via the web. It can + be appended with listinfo/%(list_name)s to yield the general + list information page for the mailing list. + + description + The brief description of the mailing list. + + info + This is the full description of the mailing list. + + cgiext + This is the extension added to CGI scripts. It might be the + empty string, .cgi, or something else depending on how your site + is configured. + + Note that real_name, host_name, description, and info substitution + variables take their values from the list configuration variables of + the same name. + + When personalization is enabled, the following substitution variables + are also available: + + user_address + The address of the recipient of the message, coerced to lower + case. + + user_delivered_to + The case-preserved address that the user subscribed to the + mailing list with^4. + + user_password + The user's password, in clear text. + + user_name + The user's full name. + + user_optionsurl + The url to the user's personal options page. + +2.6 The Digest Options Category + + Digest delivery is a way to bundle many articles together into one + package, which can be delivered once per day (if there were any posted + articles), or whenever the package is bigger than a specified limit. + Some users may prefer this style of delivery for higher traffic lists + since they will receive fewer messages. + + Mailman supports two standard digest formats, and if digests are + enabled, users can select which of the two formats they receive. One is + MIME digests, where each message is an attachment inside a + multipart/digest. This format also contains a summary table of + contents, and of course the an optional header and footer, and it + retains most of the headers of the original messages. + + The second type is called ``plaintext'' digests because they are + readable in mail readers that don't support MIME. Actually, they adhere + to the RFC 1153 digest standard. The retain some, but not all of the + original messages, but can also include a summary and headers and + footers. + + Like non-digest delivery, you can enable or disable digest delivery, + but you cannot disable both types of delivery. You can specify + different headers and footers for digest and non-digest deliveries. You + cannot personalize digest deliveries. + + As list administrator, you may want to send an urgent message to all + list members, bypassing the normal digest bundling. To do this, send + the message with a Urgent: header, where the value of the header is the + list administrator's password. Non-digest members will receive the + message like normal, but digest members will receive the message + immediately^5. + + Here are the variables which control digest delivery: + + digestable + The option controls whether members can receive digest + deliveries or not. If not, they will be forced to receive + immediate deliveries. You can't disable digests if non-digests + are already disabled. + + digest_is_default + Controls which style of delivery is the default for new members. + You can choose Regular (non-digest) or Digest delivery. + + mime_is_default_digest + If a member is allowed to choose digests, this variable controls + which is the default digest style they will receive. Plain + digests are RFC 1153 format as described above. + + digest_size_threshold + Normally, digest members get at least one message per day, if + there have been any messages posted to the list. However, for + high volume lists, you may want to send out digests when the + size has reached a certain threshold, otherwise, the one digest + they receive could be huge. This variable controls the size + threshold by specifying the maximum digest size in kilobytes. + Note that this threshold isn't exact. Set this variable to zero + to specify that there is no size threshold, in which case no + more than one digest will be sent out per day. + + digest_send_periodic + This variable actually controls whether or not a digest is sent + daily when the size threshold has not yet been met. If set to + No, then digests will only be sent when they are bigger than + digest_size_threshold. + + digest_header + This text box lets you enter information that will be included + in the header of every digest message sent through the list. The + same information can go in this header as can go in the + msg_header, except for the personalization variables. + + digest_footer + Just like with the header, you can add a footer to every + message. The same rules apply to digest footers as apply to + digest headers. + + digest_volume_frequency + Each digest is numbered with a volume and an issue. This + variable controls how often a new digest volume is sent. When + the digest volume number is incremented, the issue number is + reset to 1. + + _new_volume + This is an action variable, which forces an increment of the + volume number as soon as you submit the form. + + _send_digest_now + This is another action variable. Select Yes, submit the form, + and the current digest is packaged up and sent to digest + members, regardless of size (well, there has to be at least one + message in the digest). + +2.7 The Privacy Options Category + + The Privacy category lets you control how much of the list's + information is public, as well as who can send messages to your list. + It also contains some spam detection filters. Note that this section is + not used to control whether your list's archives are public or private; + for that, use the category. + + There are four sub-categories: + * Subscription rules - i.e. the rules for joining and leaving your + mailing list + * Sender filters - the rules for who may post messages to your list + * Recipient filters - moderation rules based on the recipient of the + message + * Spam filters - some regular expression based rules for header + matching + + The sender, recipient, and spam filtering rules are part of the general + list moderation features of Mailman. When a message is posted to the + list, it is matched against a number of criteria, the outcome of which + determines whether the message is reflected to the membership or not. + In general, the outcome is one of four states: + + * Approved or Accepted - the message may be sent on to the members of + the mailing list. + * Hold - the message will be held for moderator approval. The list + owners and moderators will then have to explicitly approve the + message before the list members will see it. + * Reject - the message is bounced back to the original sender, often + with a notice containing the reason the message was rejected. The + list members never see rejected messages. + * Discard - the message is simply thrown away without further + processing. + + Many of the fields in this section are text boxes accepting addresses, + one per line. Unless otherwise noted, these also accept regular + expressions which will be matched against an address, if the line + begins with a (caret) character. + + 2.7.1 Subscription rules + + This subcategory controls the rules for exposing the existance of this + list, and for what new members must do in order to subscribe to the + list. + + advertised + This option controls whether this list will show up in the list + overview for the site. Normally, an overview contains the name + and short description of every mailing list in the virtual + domain. By setting this variable to No, it will not show up in + this overview, nor will it show up in the administrative + overview. The only way then to find the list is to guess (or + know!) its name. + + subscribe_policy + This option controls the steps that a new member must take to + join the list. The available options may differ based on some + defaults that the site administrator chooses. They are: + + + None - No verification is done on the subscribing member. This + is also called open subscriptions and is generally disabled by + default. The site administrator must allow list admins to + choose this option; if not, this option will not be presented + to you. + + Confirm - An email confirmation step is required before the + address is added to the list. When a member requests + subscription, either via the web page or by sending a message + to yourlist-join@example.com, Mailman will send a confirmation + message to the requesting address. This mail-back confirmation + contains a unique identifier, which the requester can present + to Mailman in order to confirm their subscription. This can be + done either by replying to the mail-back, or by visiting the + url in the mail-back message. The url points to a page that + lets the user either discard or confirm their request. + + Require approval - All subscription requests are held for + approval of the list moderator. No mail-back confirmation is + sent, but the list admins will recieve a message indicating + that approval is pending. + + Confirm and approve - Here, a mail-back notice must first be + confirmed by the requester. Once confirmed, the list moderator + must then approve the request. This is the most secure method + for users to subscribe since it both verifies the requesting + address, and forces the list moderators to approve the + request. + + unsubscribe_policy + Specifies whether the list moderator's approval is required for + unsubscription requests. No is highly recommended, since it is + exceedingly impolite to not allow people to leave a mailing list + whenever they want (i.e. opt-out). Yes is useful in some + specialized contexts; e.g. you may not want to allow employees + to unsubscribe from the company newsletter. + + ban_list + This contains a list of addresses (or regular expressiosn), one + per line, that are banned from ever subscribing to your mailing + list. If a match occurs during the subscription process, the + request will be automatically rejected, and the requester will + get a rejection notice. You can use this to permanently ban + troublesome posters to a members-only list. + + private_roster + This specifies who is allowed to view the roster of member + addresses. If you choose Anyone, then the list membership is + completely public. You can limit exposure of the roster to just + list members, or just to the list administrators. In the former + case, a user must enter a valid member's address and password + before they can view the roster. In the latter case, a list + administrator's password must be enter; if a matching admin + password is entered, address field is ignored. + + obscure_addresses + Controls whether some simple obfuscation of addresses is used + when member addresses are included on web pages. This should + reduce the opportunity for email address harvesting by spammers, + although it probably doesn't eliminate it. + + 2.7.2 Sender filters + + When a message is posted to the list, a series of moderation criteria + are applied to determine the disposition of the message. This section + contains the modeation controls for postings from both members and + non-members. + + default_member_moderation + Member postings are held for moderation if their moderation flag + is turned on. Note that only the list administrators can change + the value of a member's moderation flag. + + You can control whether new members get their moderation flag + turned on or off by default when they subscribe to the list. By + turning this flag off by default, postings by members will be + allowed without further intervention (barring other restrictions + such as size or implicit recipient lists - see below). By + turning the flag on, you can quarantine new member postings to + make sure that they meet your criteria for netiquette, + topicality, etc. Once you determine that the new member + understands the community's posting rules, you can turn off + their moderation flag and let their postings go through + unstopped. + + E-newsletter style lists can also be set up by using the + moderation flag. By setting the member_moderation_action to + Reject, and by turning off the moderation flag for just the few + approved senders, your list will operate in essentially a + one-way direction. Note that you'd also need to reject or + discard postings from non-members. + + member_moderation_action + This is the action to take for postings from a member who's + moderation flag is set. For typical discussion lists, you'll + likely set this to Hold so that the list moderator will get a + chance to manually approve, reject, or discard the message. For + e-newsletter and announcement lists, you might want to set this + to Reject or Discard. + + Note that when a moderated member posts to your list, and the + member_moderation_action is set to Hold, the message will appear + on the administrative requests page. When you dispose of the + message, you will be given an opportunity to clear the + moderation flag at the same time. If you're quarantining new + posts, this makes it very convenient to both approve a new + member's post and de-moderate them at the same time. + + member_moderation_notice + When a member's moderation flag is turned on and + member_moderation_action is Reject, this variable contains the + text sent in the rejection notice. + + The next batch of variables controls what happens when non-members post + messages to the list. Each of these accepts one email address per line; + regular expressions are allowed if the line starts with the (caret) + character. These address lists are always consulted in the order in + which they're presented on this page (i.e. accepts first, followed by + holds, rejections, and discards). + + accept_these_nonmembers + Postings from non-members whose addresses match this list are + accepted, barring other list restrictions due to size, implicit + recipients, etc. You might want to add alternative addresses of + approved posters to this list. + + hold_these_nonmembers + Postings from non-members whose addresses match this list are + held for moderator approval. + + reject_these_nonmembers + Postings from non-members whose addresses match this list are + rejected, i.e. bounced back to the original sender. There + currently is no way to add additional text to the rejection + message. + + discard_these_nonmembers + Postings from non-members whose addresses match this list are + discarded, with no bounce back message. You might want to add + the addresses of known spammers to this list. + + generic_nonmember_action + This variable controls what happens to non-member posts when the + address of the sender doesn't match any of the above four lists. + If you set this to Hold, the posting will appear on the + administrative requests page, and you will be given an + opportunity to add the non-member to one of the above four lists + at the same time you dispose of the held message. + + forward_auto_discards + When messages from non-members are discarded, either because the + sender address matched discard_these_nonmembers, or because + generic_nonmember_action is Discard, you can choose whether such + messages are forwarded to the lsit administrators or not. + + 2.7.3 Recipient Filters + + The variables in this section control various filters based on the + recipient of the message. + + require_explicit_destination + This controls whether the mailing list posting address must be + explicitly named in the To: or Cc: recipient lists. The main + reason why it wouldn't is if the message was blind-carbon-copied + (i.e. Bcc:'d) to the list. Spammers like to do this, but + sometimes legitimate messages are forwarded to the list this + way. + + If the list is not explicitly addressed and this setting is + turned on, the message will be held for moderator approval. + + acceptable_aliases + This is the list of alternative addresses that are acceptable as + a list posting address when require_explicit_destination is + enabled. This is useful for when there aliases for the main + posting address (e.g. help@example.com may be an alias for + help-list@example.com). + + max_num_recipients + This is the maximum number of explicit recipients that are + allowed on the posted message. Spammers sometimes send messages + with lots of explicit recipients, so setting this number to a + reasonable value may cut down on spam. + + 2.7.4 Spam Filters + + This section provides some adjuncts to spam fighting tools; it doesn't + replace dedicated anti-spam tools such as SpamAssassin or Spambayes. + + bounce_matching_headers + This variable contains header regular expressions, one per line, + and if any of a message's headers matches one of these patterns, + it will be held for moderation. The format is a colon separated + header and value, where the header is case insensitive and the + value is any valid Python regular expression. Lines that start + with # are ignored. + + This variable can be used to catch known spammers by writing + regexps that match against To: or Cc: lines, or known-bad + Message-ID:s. Perhaps more useful though are patterns that match + headers added by spam detection tools higher up in the tool + chain. For example, you might configure SpamAssassin to add an + X-Spam-Score: header with between zero and 5 stars depending on + the spam score. Then you can add a line to this variable like: + + X-Spam-Score: [*]{3,5} + + This line will match from 3 to 5 stars in the value of this + field. + +2.8 The Bounce Processing Category + + These policies control the automatic bounce processing system in + Mailman. Here's an overview of how it works: + + When a bounce is received, Mailman tries to extract two pieces of + information from the message: the address of the member the message was + intended for, and the severity of the problem causing the bounce. The + severity can be either hard for fatal errors, or soft for transient + errors. When in doubt, a hard severity is used. + + If no member address can be extracted from the bounce, then the bounce + message is usually discarded. Every member has a bounce score, + initialized at zero, and every time we encounter a bounce from a member + we increment that member's score. Hard bounces increment by 1 while + soft bounces increment by 0.5. We only increment the bounce score once + per day, so even if we receive ten hard bounces from a member per day, + their score will increase by only 1 for that day. + + When a member's bounce score is greater than the bounce score threshold + (see below), the member's subscription is disabled. Once disabled, the + member will not receive any postings from the list until their + membership is explicitly re-enabled, either by the list administrator + or the user. However, they will receive occasional reminders that their + membership has been disabled, and these reminders will include + information about how to re-enable their membership. You can control + both the number of reminders the member will receive and the frequency + with which these reminders are sent. + + There is one other important configuration variable; after a certain + period of time - during which no bounces from the member are received - + the bounce information is considered stale and discarded. Thus by + adjusting this value, and the score threshold, you can control how + quickly bouncing members are disabled. You should tune both of these to + the frequency and traffic volume of your list. + + bounce_processing + Specifies whether or not this list should do automatic bounce + processing. + + bounce_score_threshold + This is the bounce score above which a member's subscription + will be automatically disabled. When the subscription is + re-enabled, their bounce score will be reset to zero. This value + can be a floating point number. + + bounce_info_stale_after + Thenumber of days after which a member's bounce information is + considered stale. If no new bounces have been received in the + interrim, the bounce score is reset to zero. This value must be + an integer. + + bounce_you_are_disabled_warnings + The number of notices a disabled member will receive before + their address is removed from the mailing list's roster. Set + this to 0 to immediately remove an address from the list once + their bounce score exceeds the threshold. This value must be an + integer. + + bounce_you_are_disabled_warnings_interval + The number of days between each disabled notification. + + bounce_unrecognized_goes_to_list_owner + This variable controls whether unrecognized bounces are + discarded, or forwarded on the list administrator. The bounce + detector isn't perfect, although personalization can make it + much more accurate. The list owner may want to receive + unrecognized bounces so that they can manually disable or remove + such members. + + bounce_notify_owner_on_disable + This option controls whether or not the list owner is notified + when a member's subscription is automatically disabled due to + their bounce threshold being reached. + + bounce_notify_owner_on_removal + This option controls whether or not the list owner is notified + when a member is removed from the list after their disabled + notifications have been exhausted. + +2.9 The Archiving Options Category + + Mailman comes with a built-in web-based archiver called Pipermail, + although it can be configured to use external, third party archivers. + + archive + This option tells Mailman whether to archive messages it + receives or not, regardless of whether Pipermail or a third + party archiver is used. Turn this off if you don't want to + archive messages. + + Note that senders can control whether their own posts are + archived, on an individual per-message basis. If the posted + message has a X-No-Archive: header (regardless of value), or a + X-Archive: header with a value of No (case insensitive), then + the message will not be archived, although it will be treated as + normal in all other ways. + + archive_private + Controls whether Pipermail archives are private or public. + Private archives require a valid member address and password, or + a list administrator password in order to access them. This + option has no effect when a third party archiver is used. + + archive_volume_frequency + Controls how Pipermail splits messages in the archive. The most + common option is Monthly meaning a new archive volume is started + every month. Very high volume lists may want a shorter frequency + (e.g. Weekly or Daily) where as lower volume lists may want a + longer frequency (e.g. Yearly). This option has no effect when a + third party archiver is used. + +2.10 The Mail/News Gateway Category + + Mailman has a sophisticated mail-to-news gateway feature. It can + independently gate messages from news to mail and vice versa, and can + even be used to manage moderated newsgroups. + +2.11 The Auto-responder Category + +2.12 The Content Filtering Category + +2.13 The Topics Category + + 3 Membership Management + + 4 Tending to Pending Moderator Requests + + 5 Editing the Public HTML Pages + + 6 Deleting the Mailing List + + 1 This is an Appendix + + To create an appendix in a Python HOWTO document, use markup like this: + +\appendix + +\section{This is an Appendix} + +To create an appendix in a Python HOWTO document, .... + + +\section{This is another} + +Just add another \section{}, but don't say \appendix again. + + About this document ... + + GNU Mailman - List Administration 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. + __________________________________________________________________ + + Footnotes + + ... representation^1 + Specifically, a Python pickle + + ... required^2 + The site administrator can configure lists to use a simpler + interpolation format, where $list_name or ${list_name} would be + substituted with the mailing list's name. Ask your site + administrator if the've configured your list this way. + + ... list^3 + For backward compatibility, the variable _internal_name is + equivalent. + + ... with^4 + Usually it makes no difference which of user_address and + user_delivered_to is used, but it's important to remember that + they can be different. When they're different, Mailman always + uses the lower case address as the key to the member's + subscription information, but it always delivers messages to the + case-preserved version. + + ... immediately^5 + They'll also receive the message in the digest. + __________________________________________________________________ + + Previous Page Up one Level Next Page GNU Mailman - List Administration + Manual + __________________________________________________________________ + + Release 2.1, documentation updated on December 5, 2007. diff --git a/doc/mailman-admin/WARNINGS b/doc/mailman-admin/WARNINGS new file mode 100644 index 00000000..355383a0 --- /dev/null +++ b/doc/mailman-admin/WARNINGS @@ -0,0 +1,3 @@ +couldn't convert character (circ into available encodings + + ...set $ACCENT_IMAGES to get an image diff --git a/doc/mailman-admin/about.html b/doc/mailman-admin/about.html new file mode 100644 index 00000000..153099b2 --- /dev/null +++ b/doc/mailman-admin/about.html @@ -0,0 +1,112 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> +<html> +<head> +<link rel="STYLESHEET" href="mailman-admin.css" type='text/css' /> +<link rel="first" href="mailman-admin.html" title='GNU mailman - list Administration Manual' /> +<link rel='contents' href='contents.html' title="Contents" /> +<link rel='last' href='about.html' title='About this document...' /> +<link rel='help' href='about.html' title='About this document...' /> +<link rel="prev" href="contents.html" /> +<link rel="parent" href="mailman-admin.html" /> +<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> +<meta name='aesop' content='information' /> +<title>About this document ...</title> +</head> +<body> +<div class="navigation"> +<div id='top-navigation-panel' xml:id='top-navigation-panel'> +<table align="center" width="100%" cellpadding="0" cellspacing="2"> +<tr> +<td class='online-navigation'><a rel="prev" title="1 this is an" + href="node35.html"><img src='previous.png' + border='0' height='32' alt='Previous Page' width='32' /></a></td> +<td class='online-navigation'><a rel="parent" title="GNU mailman - List" + href="mailman-admin.html"><img src='up.png' + border='0' height='32' alt='Up one Level' width='32' /></a></td> +<td class='online-navigation'><img src='next.png' + border='0' height='32' alt='Next Page' width='32' /></td> +<td align="center" width="100%">GNU Mailman - List Administration Manual</td> +<td class='online-navigation'><a rel="contents" title="Table of Contents" + href="contents.html"><img src='contents.png' + border='0' height='32' alt='Contents' width='32' /></a></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +</tr></table> +<div class='online-navigation'> +<b class="navlabel">Previous:</b> +<a class="sectref" rel="prev" href="node35.html">1 This is an</a> +<b class="navlabel">Up:</b> +<a class="sectref" rel="parent" href="mailman-admin.html">GNU Mailman - List</a> +</div> +<hr /></div> +</div> +<!--End of Navigation Panel--> + +<h1><a name="SECTION003000000000000000000"> +About this document ...</a> +</h1> + <strong>GNU Mailman - List Administration Manual</strong>, +December 5, 2007, Release 2.1 +<p> This document was generated using the <a + href="http://saftsack.fs.uni-bayreuth.de/~latex2ht/"> + <strong>LaTeX</strong>2<tt>HTML</tt></a> translator. +</p> + +<p> <a + href="http://saftsack.fs.uni-bayreuth.de/~latex2ht/"> + <strong>LaTeX</strong>2<tt>HTML</tt></a> is Copyright © + 1993, 1994, 1995, 1996, 1997, <a + href="http://cbl.leeds.ac.uk/nikos/personal.html">Nikos + Drakos</a>, Computer Based Learning Unit, University of + Leeds, and Copyright © 1997, 1998, <a + href="http://www.maths.mq.edu.au/~ross/">Ross + Moore</a>, Mathematics Department, Macquarie University, + Sydney. +</p> + +<p> The application of <a + href="http://saftsack.fs.uni-bayreuth.de/~latex2ht/"> + <strong>LaTeX</strong>2<tt>HTML</tt></a> to the Python + documentation has been heavily tailored by Fred L. Drake, + Jr. Original navigation icons were contributed by Christopher + Petrilli. +</p> + +<div class="navigation"> +<div class='online-navigation'> +<p></p><hr /> +<table align="center" width="100%" cellpadding="0" cellspacing="2"> +<tr> +<td class='online-navigation'><a rel="prev" title="1 this is an" + href="node35.html"><img src='previous.png' + border='0' height='32' alt='Previous Page' width='32' /></a></td> +<td class='online-navigation'><a rel="parent" title="GNU mailman - List" + href="mailman-admin.html"><img src='up.png' + border='0' height='32' alt='Up one Level' width='32' /></a></td> +<td class='online-navigation'><img src='next.png' + border='0' height='32' alt='Next Page' width='32' /></td> +<td align="center" width="100%">GNU Mailman - List Administration Manual</td> +<td class='online-navigation'><a rel="contents" title="Table of Contents" + href="contents.html"><img src='contents.png' + border='0' height='32' alt='Contents' width='32' /></a></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +</tr></table> +<div class='online-navigation'> +<b class="navlabel">Previous:</b> +<a class="sectref" rel="prev" href="node35.html">1 This is an</a> +<b class="navlabel">Up:</b> +<a class="sectref" rel="parent" href="mailman-admin.html">GNU Mailman - List</a> +</div> +</div> +<hr /> +<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +</div> +<!--End of Navigation Panel--> + +</body> +</html> diff --git a/doc/mailman-admin/blank.png b/doc/mailman-admin/blank.png Binary files differnew file mode 100644 index 00000000..2af5639b --- /dev/null +++ b/doc/mailman-admin/blank.png diff --git a/doc/mailman-admin/contents.html b/doc/mailman-admin/contents.html new file mode 100644 index 00000000..24113e68 --- /dev/null +++ b/doc/mailman-admin/contents.html @@ -0,0 +1,126 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> +<html> +<head> +<link rel="STYLESHEET" href="mailman-admin.css" type='text/css' /> +<link rel="first" href="mailman-admin.html" title='GNU mailman - list Administration Manual' /> +<link rel='contents' href='contents.html' title="Contents" /> +<link rel='last' href='about.html' title='About this document...' /> +<link rel='help' href='about.html' title='About this document...' /> +<link rel="next" href="about.html" /> +<link rel="prev" href="front.html" /> +<link rel="parent" href="mailman-admin.html" /> +<link rel="next" href="node3.html" /> +<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> +<meta name='aesop' content='information' /> +<title>Contents</title> +</head> +<body> +<div class="navigation"> +<div id='top-navigation-panel' xml:id='top-navigation-panel'> +<table align="center" width="100%" cellpadding="0" cellspacing="2"> +<tr> +<td class='online-navigation'><a rel="prev" title="Front Matter" + href="front.html"><img src='previous.png' + border='0' height='32' alt='Previous Page' width='32' /></a></td> +<td class='online-navigation'><a rel="parent" title="GNU mailman - List" + href="mailman-admin.html"><img src='up.png' + border='0' height='32' alt='Up one Level' width='32' /></a></td> +<td class='online-navigation'><a rel="next" title="1 introduction to GNU" + href="node3.html"><img src='next.png' + border='0' height='32' alt='Next Page' width='32' /></a></td> +<td align="center" width="100%">GNU Mailman - List Administration Manual</td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +</tr></table> +<div class='online-navigation'> +<b class="navlabel">Previous:</b> +<a class="sectref" rel="prev" href="front.html">Front Matter</a> +<b class="navlabel">Up:</b> +<a class="sectref" rel="parent" href="mailman-admin.html">GNU Mailman - List</a> +<b class="navlabel">Next:</b> +<a class="sectref" rel="next" href="node3.html">1 Introduction to GNU</a> +</div> +<hr /></div> +</div> +<!--End of Navigation Panel--> +<br><h2><a name="SECTION002000000000000000000"> +Contents</a> +</h2> +<!--Table of Contents--> + +<ul class="TofC"> +<li><ul> +<li><a href="node3.html">1 Introduction to GNU Mailman</a> +<ul> +<li><a href="node4.html">1.1 A List's Email Addresses</a> +<li><a href="node5.html">1.2 Administrative Roles</a> +<li><a href="node6.html">1.3 A List's Web Pages</a> +<li><a href="node7.html">1.4 Basic Architectural Overview</a> +</ul> +<li><a href="node8.html">2 The List Configuration Pages</a> +<ul> +<li><a href="node9.html">2.1 The General Options Category</a> +<li><a href="node15.html">2.2 The Passwords Category</a> +<li><a href="node16.html">2.3 The Language Options Category</a> +<li><a href="node17.html">2.4 The Membership Management Category</a> +<li><a href="node18.html">2.5 The Non-digest Options Category</a> +<li><a href="node19.html">2.6 The Digest Options Category</a> +<li><a href="node20.html">2.7 The Privacy Options Category</a> +<li><a href="node25.html">2.8 The Bounce Processing Category</a> +<li><a href="node26.html">2.9 The Archiving Options Category</a> +<li><a href="node27.html">2.10 The Mail/News Gateway Category</a> +<li><a href="node28.html">2.11 The Auto-responder Category</a> +<li><a href="node29.html">2.12 The Content Filtering Category</a> +<li><a href="node30.html">2.13 The Topics Category</a> +</ul> +<li><a href="node31.html">3 Membership Management</a> +<li><a href="node32.html">4 Tending to Pending Moderator Requests</a> +<li><a href="node33.html">5 Editing the Public HTML Pages</a> +<li><a href="node34.html">6 Deleting the Mailing List</a> +<li><a href="node35.html">1 This is an Appendix</a> +</ul></ul> +<!--End of Table of Contents--> +<p> + +<div class="navigation"> +<div class='online-navigation'> +<p></p><hr /> +<table align="center" width="100%" cellpadding="0" cellspacing="2"> +<tr> +<td class='online-navigation'><a rel="prev" title="Front Matter" + href="front.html"><img src='previous.png' + border='0' height='32' alt='Previous Page' width='32' /></a></td> +<td class='online-navigation'><a rel="parent" title="GNU mailman - List" + href="mailman-admin.html"><img src='up.png' + border='0' height='32' alt='Up one Level' width='32' /></a></td> +<td class='online-navigation'><a rel="next" title="1 introduction to GNU" + href="node3.html"><img src='next.png' + border='0' height='32' alt='Next Page' width='32' /></a></td> +<td align="center" width="100%">GNU Mailman - List Administration Manual</td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +</tr></table> +<div class='online-navigation'> +<b class="navlabel">Previous:</b> +<a class="sectref" rel="prev" href="front.html">Front Matter</a> +<b class="navlabel">Up:</b> +<a class="sectref" rel="parent" href="mailman-admin.html">GNU Mailman - List</a> +<b class="navlabel">Next:</b> +<a class="sectref" rel="next" href="node3.html">1 Introduction to GNU</a> +</div> +</div> +<hr /> +<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +</div> +<!--End of Navigation Panel--> + +</body> +</html> diff --git a/doc/mailman-admin/contents.png b/doc/mailman-admin/contents.png Binary files differnew file mode 100644 index 00000000..3429be0c --- /dev/null +++ b/doc/mailman-admin/contents.png diff --git a/doc/mailman-admin/front.html b/doc/mailman-admin/front.html new file mode 100644 index 00000000..b0977103 --- /dev/null +++ b/doc/mailman-admin/front.html @@ -0,0 +1,114 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> +<html> +<head> +<link rel="STYLESHEET" href="mailman-admin.css" type='text/css' /> +<link rel="first" href="mailman-admin.html" title='GNU mailman - list Administration Manual' /> +<link rel='contents' href='contents.html' title="Contents" /> +<link rel='last' href='about.html' title='About this document...' /> +<link rel='help' href='about.html' title='About this document...' /> +<link rel="next" href="contents.html" /> +<link rel="prev" href="mailman-admin.html" /> +<link rel="parent" href="mailman-admin.html" /> +<link rel="next" href="contents.html" /> +<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> +<meta name='aesop' content='information' /> +<title>Front Matter</title> +</head> +<body> +<div class="navigation"> +<div id='top-navigation-panel' xml:id='top-navigation-panel'> +<table align="center" width="100%" cellpadding="0" cellspacing="2"> +<tr> +<td class='online-navigation'><a rel="prev" title="GNU mailman - List" + href="mailman-admin.html"><img src='previous.png' + border='0' height='32' alt='Previous Page' width='32' /></a></td> +<td class='online-navigation'><a rel="parent" title="GNU mailman - List" + href="mailman-admin.html"><img src='up.png' + border='0' height='32' alt='Up one Level' width='32' /></a></td> +<td class='online-navigation'><a rel="next" title="Contents" + href="contents.html"><img src='next.png' + border='0' height='32' alt='Next Page' width='32' /></a></td> +<td align="center" width="100%">GNU Mailman - List Administration Manual</td> +<td class='online-navigation'><a rel="contents" title="Table of Contents" + href="contents.html"><img src='contents.png' + border='0' height='32' alt='Contents' width='32' /></a></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +</tr></table> +<div class='online-navigation'> +<b class="navlabel">Previous:</b> +<a class="sectref" rel="prev" href="mailman-admin.html">GNU Mailman - List</a> +<b class="navlabel">Up:</b> +<a class="sectref" rel="parent" href="mailman-admin.html">GNU Mailman - List</a> +<b class="navlabel">Next:</b> +<a class="sectref" rel="next" href="contents.html">Contents</a> +</div> +<hr /></div> +</div> +<!--End of Navigation Panel--> + +<h1><a name="SECTION001000000000000000000"></a><a name="front"></a> +<br> +Front Matter +</h1> + +<p> + +<h3>Abstract:</h3> +<div class="ABSTRACT"> + +This document describes the list administrator's interface for GNU +Mailman 2.1. It contains information a list owner would need to +configure their list, either through the web interface or through +email. It also covers the moderator's interface for approving held +messages and subscription notices, and the web interface for creating +new mailing lists. In general, it does not cover the command line +interface to Mailman, installing Mailman, or interacting with Mailman +from the point of view of the user. That information is covered in +other manuals. +</div> +<p> + +<p> + +<div class="navigation"> +<div class='online-navigation'> +<p></p><hr /> +<table align="center" width="100%" cellpadding="0" cellspacing="2"> +<tr> +<td class='online-navigation'><a rel="prev" title="GNU mailman - List" + href="mailman-admin.html"><img src='previous.png' + border='0' height='32' alt='Previous Page' width='32' /></a></td> +<td class='online-navigation'><a rel="parent" title="GNU mailman - List" + href="mailman-admin.html"><img src='up.png' + border='0' height='32' alt='Up one Level' width='32' /></a></td> +<td class='online-navigation'><a rel="next" title="Contents" + href="contents.html"><img src='next.png' + border='0' height='32' alt='Next Page' width='32' /></a></td> +<td align="center" width="100%">GNU Mailman - List Administration Manual</td> +<td class='online-navigation'><a rel="contents" title="Table of Contents" + href="contents.html"><img src='contents.png' + border='0' height='32' alt='Contents' width='32' /></a></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +</tr></table> +<div class='online-navigation'> +<b class="navlabel">Previous:</b> +<a class="sectref" rel="prev" href="mailman-admin.html">GNU Mailman - List</a> +<b class="navlabel">Up:</b> +<a class="sectref" rel="parent" href="mailman-admin.html">GNU Mailman - List</a> +<b class="navlabel">Next:</b> +<a class="sectref" rel="next" href="contents.html">Contents</a> +</div> +</div> +<hr /> +<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +</div> +<!--End of Navigation Panel--> + +</body> +</html> diff --git a/doc/mailman-admin/index.dat b/doc/mailman-admin/index.dat new file mode 100644 index 00000000..e69de29b --- /dev/null +++ b/doc/mailman-admin/index.dat diff --git a/doc/mailman-admin/index.html b/doc/mailman-admin/index.html new file mode 100644 index 00000000..d79769ad --- /dev/null +++ b/doc/mailman-admin/index.html @@ -0,0 +1,130 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> +<html> +<head> +<link rel="STYLESHEET" href="mailman-admin.css" type='text/css' /> +<link rel="first" href="mailman-admin.html" title='GNU mailman - list Administration Manual' /> +<link rel='contents' href='contents.html' title="Contents" /> +<link rel='last' href='about.html' title='About this document...' /> +<link rel='help' href='about.html' title='About this document...' /> +<link rel="next" href="front.html" /> +<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> +<meta name='aesop' content='information' /> +<title>GNU Mailman - List Administration Manual</title> +</head> +<body> +<div class="navigation"> +<div id='top-navigation-panel' xml:id='top-navigation-panel'> +<table align="center" width="100%" cellpadding="0" cellspacing="2"> +<tr> +<td class='online-navigation'><img src='previous.png' + border='0' height='32' alt='Previous Page' width='32' /></td> +<td class='online-navigation'><img src='up.png' + border='0' height='32' alt='Up one Level' width='32' /></td> +<td class='online-navigation'><a rel="next" title="Front Matter" + href="front.html"><img src='next.png' + border='0' height='32' alt='Next Page' width='32' /></a></td> +<td align="center" width="100%">GNU Mailman - List Administration Manual</td> +<td class='online-navigation'><a rel="contents" title="Table of Contents" + href="contents.html"><img src='contents.png' + border='0' height='32' alt='Contents' width='32' /></a></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +</tr></table> +<div class='online-navigation'> +<b class="navlabel">Next:</b> +<a class="sectref" rel="next" href="front.html">Front Matter</a> +</div> +<hr /></div> +</div> +<!--End of Navigation Panel--> + +<div class="titlepage"> +<div class='center'> +<h1>GNU Mailman - List Administration Manual</h1> +<p><b><font size="+2">Barry A. Warsaw</font></b></p> +<p><strong>Release 2.1</strong><br /> +<strong>December 5, 2007</strong></p> +<p></p> +</div> +</div> + +<p> + +<p><br /></p><hr class='online-navigation' /> +<div class='online-navigation'> +<!--Table of Child-Links--> +<a name="CHILD_LINKS"></a> + +<ul class="ChildLinks"> +<li><a href="front.html">Front Matter</a> +<li><a href="contents.html">Contents</a> +<ul> +<li><a href="node3.html">1 Introduction to GNU Mailman</a> +<ul> +<li><a href="node4.html">1.1 A List's Email Addresses</a> +<li><a href="node5.html">1.2 Administrative Roles</a> +<li><a href="node6.html">1.3 A List's Web Pages</a> +<li><a href="node7.html">1.4 Basic Architectural Overview</a> +</ul> +<li><a href="node8.html">2 The List Configuration Pages</a> +<ul> +<li><a href="node9.html">2.1 The General Options Category</a> +<li><a href="node15.html">2.2 The Passwords Category</a> +<li><a href="node16.html">2.3 The Language Options Category</a> +<li><a href="node17.html">2.4 The Membership Management Category</a> +<li><a href="node18.html">2.5 The Non-digest Options Category</a> +<li><a href="node19.html">2.6 The Digest Options Category</a> +<li><a href="node20.html">2.7 The Privacy Options Category</a> +<li><a href="node25.html">2.8 The Bounce Processing Category</a> +<li><a href="node26.html">2.9 The Archiving Options Category</a> +<li><a href="node27.html">2.10 The Mail/News Gateway Category</a> +<li><a href="node28.html">2.11 The Auto-responder Category</a> +<li><a href="node29.html">2.12 The Content Filtering Category</a> +<li><a href="node30.html">2.13 The Topics Category</a> +</ul> +<li><a href="node31.html">3 Membership Management</a> +<li><a href="node32.html">4 Tending to Pending Moderator Requests</a> +<li><a href="node33.html">5 Editing the Public HTML Pages</a> +<li><a href="node34.html">6 Deleting the Mailing List</a> +<li><a href="node35.html">1 This is an Appendix</a> +</ul> +<li><a href="about.html">About this document ...</a> +</ul> +<!--End of Table of Child-Links--> +</div> + +<div class="navigation"> +<div class='online-navigation'> +<p></p><hr /> +<table align="center" width="100%" cellpadding="0" cellspacing="2"> +<tr> +<td class='online-navigation'><img src='previous.png' + border='0' height='32' alt='Previous Page' width='32' /></td> +<td class='online-navigation'><img src='up.png' + border='0' height='32' alt='Up one Level' width='32' /></td> +<td class='online-navigation'><a rel="next" title="Front Matter" + href="front.html"><img src='next.png' + border='0' height='32' alt='Next Page' width='32' /></a></td> +<td align="center" width="100%">GNU Mailman - List Administration Manual</td> +<td class='online-navigation'><a rel="contents" title="Table of Contents" + href="contents.html"><img src='contents.png' + border='0' height='32' alt='Contents' width='32' /></a></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +</tr></table> +<div class='online-navigation'> +<b class="navlabel">Next:</b> +<a class="sectref" rel="next" href="front.html">Front Matter</a> +</div> +</div> +<hr /> +<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +</div> +<!--End of Navigation Panel--> + +</body> +</html> diff --git a/doc/mailman-admin/index.png b/doc/mailman-admin/index.png Binary files differnew file mode 100644 index 00000000..cd918afe --- /dev/null +++ b/doc/mailman-admin/index.png diff --git a/doc/mailman-admin/internals.pl b/doc/mailman-admin/internals.pl new file mode 100644 index 00000000..8ef71735 --- /dev/null +++ b/doc/mailman-admin/internals.pl @@ -0,0 +1,18 @@ +# LaTeX2HTML 2002-2-1 (1.71) +# Associate internals original text with physical files. + + +$key = q/front/; +$ref_files{$key} = "$dir".q|node1.html|; +$noresave{$key} = "$nosave"; + +$key = q/contents/; +$ref_files{$key} = "$dir".q|node2.html|; +$noresave{$key} = "$nosave"; + +$key = q/about/; +$ref_files{$key} = "$dir".q|node36.html|; +$noresave{$key} = "$nosave"; + +1; + diff --git a/doc/mailman-admin/intlabels.pl b/doc/mailman-admin/intlabels.pl new file mode 100644 index 00000000..44814752 --- /dev/null +++ b/doc/mailman-admin/intlabels.pl @@ -0,0 +1,3 @@ +%internal_labels = (); +1; # hack in case there are no entries + diff --git a/doc/mailman-admin/labels.pl b/doc/mailman-admin/labels.pl new file mode 100644 index 00000000..70f0223d --- /dev/null +++ b/doc/mailman-admin/labels.pl @@ -0,0 +1,25 @@ +# LaTeX2HTML 2002-2-1 (1.71) +# Associate labels original text with physical files. + + +$key = q/front/; +$external_labels{$key} = "$URL/" . q|node1.html|; +$noresave{$key} = "$nosave"; + +$key = q/contents/; +$external_labels{$key} = "$URL/" . q|node2.html|; +$noresave{$key} = "$nosave"; + +$key = q/about/; +$external_labels{$key} = "$URL/" . q|node36.html|; +$noresave{$key} = "$nosave"; + +1; + + +# LaTeX2HTML 2002-2-1 (1.71) +# labels from external_latex_labels array. + + +1; + diff --git a/doc/mailman-admin/mailman-admin.css b/doc/mailman-admin/mailman-admin.css new file mode 100644 index 00000000..06a613c2 --- /dev/null +++ b/doc/mailman-admin/mailman-admin.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 <br> 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-admin/mailman-admin.html b/doc/mailman-admin/mailman-admin.html new file mode 100644 index 00000000..d79769ad --- /dev/null +++ b/doc/mailman-admin/mailman-admin.html @@ -0,0 +1,130 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> +<html> +<head> +<link rel="STYLESHEET" href="mailman-admin.css" type='text/css' /> +<link rel="first" href="mailman-admin.html" title='GNU mailman - list Administration Manual' /> +<link rel='contents' href='contents.html' title="Contents" /> +<link rel='last' href='about.html' title='About this document...' /> +<link rel='help' href='about.html' title='About this document...' /> +<link rel="next" href="front.html" /> +<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> +<meta name='aesop' content='information' /> +<title>GNU Mailman - List Administration Manual</title> +</head> +<body> +<div class="navigation"> +<div id='top-navigation-panel' xml:id='top-navigation-panel'> +<table align="center" width="100%" cellpadding="0" cellspacing="2"> +<tr> +<td class='online-navigation'><img src='previous.png' + border='0' height='32' alt='Previous Page' width='32' /></td> +<td class='online-navigation'><img src='up.png' + border='0' height='32' alt='Up one Level' width='32' /></td> +<td class='online-navigation'><a rel="next" title="Front Matter" + href="front.html"><img src='next.png' + border='0' height='32' alt='Next Page' width='32' /></a></td> +<td align="center" width="100%">GNU Mailman - List Administration Manual</td> +<td class='online-navigation'><a rel="contents" title="Table of Contents" + href="contents.html"><img src='contents.png' + border='0' height='32' alt='Contents' width='32' /></a></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +</tr></table> +<div class='online-navigation'> +<b class="navlabel">Next:</b> +<a class="sectref" rel="next" href="front.html">Front Matter</a> +</div> +<hr /></div> +</div> +<!--End of Navigation Panel--> + +<div class="titlepage"> +<div class='center'> +<h1>GNU Mailman - List Administration Manual</h1> +<p><b><font size="+2">Barry A. Warsaw</font></b></p> +<p><strong>Release 2.1</strong><br /> +<strong>December 5, 2007</strong></p> +<p></p> +</div> +</div> + +<p> + +<p><br /></p><hr class='online-navigation' /> +<div class='online-navigation'> +<!--Table of Child-Links--> +<a name="CHILD_LINKS"></a> + +<ul class="ChildLinks"> +<li><a href="front.html">Front Matter</a> +<li><a href="contents.html">Contents</a> +<ul> +<li><a href="node3.html">1 Introduction to GNU Mailman</a> +<ul> +<li><a href="node4.html">1.1 A List's Email Addresses</a> +<li><a href="node5.html">1.2 Administrative Roles</a> +<li><a href="node6.html">1.3 A List's Web Pages</a> +<li><a href="node7.html">1.4 Basic Architectural Overview</a> +</ul> +<li><a href="node8.html">2 The List Configuration Pages</a> +<ul> +<li><a href="node9.html">2.1 The General Options Category</a> +<li><a href="node15.html">2.2 The Passwords Category</a> +<li><a href="node16.html">2.3 The Language Options Category</a> +<li><a href="node17.html">2.4 The Membership Management Category</a> +<li><a href="node18.html">2.5 The Non-digest Options Category</a> +<li><a href="node19.html">2.6 The Digest Options Category</a> +<li><a href="node20.html">2.7 The Privacy Options Category</a> +<li><a href="node25.html">2.8 The Bounce Processing Category</a> +<li><a href="node26.html">2.9 The Archiving Options Category</a> +<li><a href="node27.html">2.10 The Mail/News Gateway Category</a> +<li><a href="node28.html">2.11 The Auto-responder Category</a> +<li><a href="node29.html">2.12 The Content Filtering Category</a> +<li><a href="node30.html">2.13 The Topics Category</a> +</ul> +<li><a href="node31.html">3 Membership Management</a> +<li><a href="node32.html">4 Tending to Pending Moderator Requests</a> +<li><a href="node33.html">5 Editing the Public HTML Pages</a> +<li><a href="node34.html">6 Deleting the Mailing List</a> +<li><a href="node35.html">1 This is an Appendix</a> +</ul> +<li><a href="about.html">About this document ...</a> +</ul> +<!--End of Table of Child-Links--> +</div> + +<div class="navigation"> +<div class='online-navigation'> +<p></p><hr /> +<table align="center" width="100%" cellpadding="0" cellspacing="2"> +<tr> +<td class='online-navigation'><img src='previous.png' + border='0' height='32' alt='Previous Page' width='32' /></td> +<td class='online-navigation'><img src='up.png' + border='0' height='32' alt='Up one Level' width='32' /></td> +<td class='online-navigation'><a rel="next" title="Front Matter" + href="front.html"><img src='next.png' + border='0' height='32' alt='Next Page' width='32' /></a></td> +<td align="center" width="100%">GNU Mailman - List Administration Manual</td> +<td class='online-navigation'><a rel="contents" title="Table of Contents" + href="contents.html"><img src='contents.png' + border='0' height='32' alt='Contents' width='32' /></a></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +</tr></table> +<div class='online-navigation'> +<b class="navlabel">Next:</b> +<a class="sectref" rel="next" href="front.html">Front Matter</a> +</div> +</div> +<hr /> +<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +</div> +<!--End of Navigation Panel--> + +</body> +</html> diff --git a/doc/mailman-admin/modules.png b/doc/mailman-admin/modules.png Binary files differnew file mode 100644 index 00000000..8fa8b755 --- /dev/null +++ b/doc/mailman-admin/modules.png diff --git a/doc/mailman-admin/next.png b/doc/mailman-admin/next.png Binary files differnew file mode 100644 index 00000000..cfe5e51c --- /dev/null +++ b/doc/mailman-admin/next.png diff --git a/doc/mailman-admin/node10.html b/doc/mailman-admin/node10.html new file mode 100644 index 00000000..29a6bb8d --- /dev/null +++ b/doc/mailman-admin/node10.html @@ -0,0 +1,199 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> +<html> +<head> +<link rel="STYLESHEET" href="mailman-admin.css" type='text/css' /> +<link rel="first" href="mailman-admin.html" title='GNU mailman - list Administration Manual' /> +<link rel='contents' href='contents.html' title="Contents" /> +<link rel='last' href='about.html' title='About this document...' /> +<link rel='help' href='about.html' title='About this document...' /> +<link rel="next" href="node11.html" /> +<link rel="prev" href="node9.html" /> +<link rel="parent" href="node9.html" /> +<link rel="next" href="node11.html" /> +<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> +<meta name='aesop' content='information' /> +<title>2.1.1 General list personality</title> +</head> +<body> +<div class="navigation"> +<div id='top-navigation-panel' xml:id='top-navigation-panel'> +<table align="center" width="100%" cellpadding="0" cellspacing="2"> +<tr> +<td class='online-navigation'><a rel="prev" title="2.1 the General Options" + href="node9.html"><img src='previous.png' + border='0' height='32' alt='Previous Page' width='32' /></a></td> +<td class='online-navigation'><a rel="parent" title="2.1 the General Options" + href="node9.html"><img src='up.png' + border='0' height='32' alt='Up one Level' width='32' /></a></td> +<td class='online-navigation'><a rel="next" title="2.1.2 reply-to header munging" + href="node11.html"><img src='next.png' + border='0' height='32' alt='Next Page' width='32' /></a></td> +<td align="center" width="100%">GNU Mailman - List Administration Manual</td> +<td class='online-navigation'><a rel="contents" title="Table of Contents" + href="contents.html"><img src='contents.png' + border='0' height='32' alt='Contents' width='32' /></a></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +</tr></table> +<div class='online-navigation'> +<b class="navlabel">Previous:</b> +<a class="sectref" rel="prev" href="node9.html">2.1 The General Options</a> +<b class="navlabel">Up:</b> +<a class="sectref" rel="parent" href="node9.html">2.1 The General Options</a> +<b class="navlabel">Next:</b> +<a class="sectref" rel="next" href="node11.html">2.1.2 Reply-To header munging</a> +</div> +<hr /></div> +</div> +<!--End of Navigation Panel--> + +<h3><a name="SECTION002211000000000000000"> +2.1.1 General list personality</a> +</h3> + +<p> +These variables, grouped under the general list personality section, +control some public information about the mailing list. + +<p> +<dl> +<dt><strong>real_name</strong></dt> +<dd>Every mailing list has both a <em>posting name</em> and a <em>real + name</em>. The posting name shows up in urls and in email addresses, + e.g. the <code>mylist</code> in <code>mylist@example.com</code>. The posting + name is always presented in lower case, with alphanumeric + characters and no spaces. The list's real name is used in some + public information and email responses, such as in the general + list overview. The real name can differ from the posting name by + case only. For example, if the posting name is <code>mylist</code>, the + real name can be <code>Posting</code>. + +<p> +</dd> +<dt><strong>owner</strong></dt> +<dd>This variable contains a list of email addresses, one address per + line, of the list owners. These addresses are used whenever the + list owners need to be contacted, either by the system or by end + users. Often, these addresses are used in combination with the + <code>moderator</code> addresses (see below). + +<p> +</dd> +<dt><strong>moderator</strong></dt> +<dd>This variable contains a list of email addresses, one address per + line, of the list moderators. These addresses are often used in + combination with the <code>owner</code> addresses. For example, when + you email <code>mylist-owner@example.com</code>, both the owner and + moderator addresses will receive a copy of the message. + +<p> +</dd> +<dt><strong>description</strong></dt> +<dd>In the general list overview page, which shows you every available + mailing list, each list is displayed with a short description. + The contents of this variable is that description. Note that in + emails from the mailing list, this description is also used in the + comment section of the <span class="mailheader">To:</span> address. This text should + be relatively short and no longer than one line. + +<p> +</dd> +<dt><strong>info</strong></dt> +<dd>This variable contains a longer description of the mailing list. + It is included at the top of the list's information page, and it + can contain HTML. However, blank lines will be automatically + converted into paragraph breaks. Preview your HTML though, + because unclosed or invalid HTML can prevent display of parts of + the list information page. + +<p> +</dd> +<dt><strong>subject_prefix</strong></dt> +<dd>This is a string that will be prepended to the + <span class="mailheader">Subject:</span> header of any message posted to the list. + For example, if a message is posted to the list with a + <span class="mailheader">Subject:</span> like: + +<p> +<div class="verbatim"><pre> + Subject: This is a message +</pre></div> + +<p> +and the <code>subject_prefix</code> is <code>[My List] </code> (note the + trailing space!), then the message will be received like so: + +<p> +<div class="verbatim"><pre> + Subject: [My List] This is a message +</pre></div> + +<p> +If you leave <code>subject_prefix</code> empty, no prefix will be added + to the <span class="mailheader">Subject:</span>. Mailman is careful not to add a + prefix when the header already has one, as is the case in replies + for example. The prefix can also contain characters in the list's + preferred language. In this case, because of vagarities of the + email standards, you may or may not want to add a trailing space. + +<p> +</dd> +<dt><strong>anonymous_list</strong></dt> +<dd>This variable allows you to turn on some simple anonymizing + features of Mailman. When you set this option to <em>Yes</em>, + Mailman will remove or replace the <span class="mailheader">From:</span>, + <span class="mailheader">Sender:</span>, and <span class="mailheader">Reply-To:</span> fields of any + message posted to the list. + +<p> +Note that this option is simply an aid for anonymization, it + doesn't guarantee it. For example, a poster's identity could be + evident in their signature, or in other mail headers, or even in + the style of the content of the message. There's little Mailman + can do about this kind of identity leakage. +</dd> +</dl> + +<p> + +<div class="navigation"> +<div class='online-navigation'> +<p></p><hr /> +<table align="center" width="100%" cellpadding="0" cellspacing="2"> +<tr> +<td class='online-navigation'><a rel="prev" title="2.1 the General Options" + href="node9.html"><img src='previous.png' + border='0' height='32' alt='Previous Page' width='32' /></a></td> +<td class='online-navigation'><a rel="parent" title="2.1 the General Options" + href="node9.html"><img src='up.png' + border='0' height='32' alt='Up one Level' width='32' /></a></td> +<td class='online-navigation'><a rel="next" title="2.1.2 reply-to header munging" + href="node11.html"><img src='next.png' + border='0' height='32' alt='Next Page' width='32' /></a></td> +<td align="center" width="100%">GNU Mailman - List Administration Manual</td> +<td class='online-navigation'><a rel="contents" title="Table of Contents" + href="contents.html"><img src='contents.png' + border='0' height='32' alt='Contents' width='32' /></a></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +</tr></table> +<div class='online-navigation'> +<b class="navlabel">Previous:</b> +<a class="sectref" rel="prev" href="node9.html">2.1 The General Options</a> +<b class="navlabel">Up:</b> +<a class="sectref" rel="parent" href="node9.html">2.1 The General Options</a> +<b class="navlabel">Next:</b> +<a class="sectref" rel="next" href="node11.html">2.1.2 Reply-To header munging</a> +</div> +</div> +<hr /> +<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +</div> +<!--End of Navigation Panel--> + +</body> +</html> diff --git a/doc/mailman-admin/node11.html b/doc/mailman-admin/node11.html new file mode 100644 index 00000000..665d5bfd --- /dev/null +++ b/doc/mailman-admin/node11.html @@ -0,0 +1,200 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> +<html> +<head> +<link rel="STYLESHEET" href="mailman-admin.css" type='text/css' /> +<link rel="first" href="mailman-admin.html" title='GNU mailman - list Administration Manual' /> +<link rel='contents' href='contents.html' title="Contents" /> +<link rel='last' href='about.html' title='About this document...' /> +<link rel='help' href='about.html' title='About this document...' /> +<link rel="next" href="node12.html" /> +<link rel="prev" href="node10.html" /> +<link rel="parent" href="node9.html" /> +<link rel="next" href="node12.html" /> +<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> +<meta name='aesop' content='information' /> +<title>2.1.2 Reply-To header munging</title> +</head> +<body> +<div class="navigation"> +<div id='top-navigation-panel' xml:id='top-navigation-panel'> +<table align="center" width="100%" cellpadding="0" cellspacing="2"> +<tr> +<td class='online-navigation'><a rel="prev" title="2.1.1 general list personality" + href="node10.html"><img src='previous.png' + border='0' height='32' alt='Previous Page' width='32' /></a></td> +<td class='online-navigation'><a rel="parent" title="2.1 the General Options" + href="node9.html"><img src='up.png' + border='0' height='32' alt='Up one Level' width='32' /></a></td> +<td class='online-navigation'><a rel="next" title="2.1.3 umbrella list settings" + href="node12.html"><img src='next.png' + border='0' height='32' alt='Next Page' width='32' /></a></td> +<td align="center" width="100%">GNU Mailman - List Administration Manual</td> +<td class='online-navigation'><a rel="contents" title="Table of Contents" + href="contents.html"><img src='contents.png' + border='0' height='32' alt='Contents' width='32' /></a></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +</tr></table> +<div class='online-navigation'> +<b class="navlabel">Previous:</b> +<a class="sectref" rel="prev" href="node10.html">2.1.1 General list personality</a> +<b class="navlabel">Up:</b> +<a class="sectref" rel="parent" href="node9.html">2.1 The General Options</a> +<b class="navlabel">Next:</b> +<a class="sectref" rel="next" href="node12.html">2.1.3 Umbrella list settings</a> +</div> +<hr /></div> +</div> +<!--End of Navigation Panel--> + +<h3><a name="SECTION002212000000000000000"> +2.1.2 Reply-To header munging</a> +</h3> + +<p> +This section controls what happens to the <span class="mailheader">Reply-To:</span> +headers of messages posted through your list. + +<p> +Beware! <span class="mailheader">Reply-To:</span> munging is considered a religious issue +and the policies you set here can ignite some of the most heated +off-topic flame wars on your mailing lists. We'll try to stay as +agnostic as possible, but our biases may still peak through. + +<p> +<span class="mailheader">Reply-To:</span> is a header that is commonly used to redirect +replies to messages. Exactly what happens when your uses reply to +such a message depends on the mail readers your users use, and what +functions they provide. Usually, there is both a ``reply to sender'' +button and a ``reply to all'' button. If people use these buttons +correctly, you will probably never need to munge +<span class="mailheader">Reply-To:</span>, so the default values should be fine. + +<p> +Since an informed decision is always best, here are links to two +articles that discuss the opposing viewpoints in great detail: + +<p> + +<ul> +<li><a class="ulink" href="http://www.unicom.com/pw/reply-to-harmful.html" + >Reply-To Munging Considered + Harmful</a> +</li> +<li><a class="ulink" href="http://www.metasystema.org/essays/reply-to-useful.mhtml" + >Reply-To Munging Considered + Useful</a> + +<p> +</li> +</ul> + +<p> +The three options in this section work together to provide enough +flexibility to do whatever <span class="mailheader">Reply-To:</span> munging you might +(misguidingly :) feel you need to do. + +<p> +<dl> +<dt><strong>first_strip_reply_to</strong></dt> +<dd>This variable controls whether any <span class="mailheader">Reply-To:</span> header + already present in the posted message should get removed before + any other munging occurs. Stripping this header will be done + regardless of whether or not Mailman will add its own + <span class="mailheader">Reply-To:</span> header to the message. + +<p> +If this option is set to <em>No</em>, then any existing + <span class="mailheader">Reply-To:</span> header will be retained in the posted + message. If Mailman adds its own header, it will contain + addresses which are the union of the original header and the + Mailman added addresses. The mail standards specify that a + message may only have one <span class="mailheader">Reply-To:</span> header, but that + that header may contain multiple addresses. + +<p> +</dd> +<dt><strong>reply_goes_to_list</strong></dt> +<dd>This variable controls whether Mailman will add its own + <span class="mailheader">Reply-To:</span> header, and if so, what the value of that + header will be (not counting original header stripping - see + above). + +<p> +When you set this variable to <em>Poster</em>, no additional + <span class="mailheader">Reply-To:</span> header will be added by Mailman. This + setting is strongly recommended. + +<p> +When you set this variable to <em>This list</em>, a + <span class="mailheader">Reply-To:</span> header pointing back to your list's posting + address will be added. + +<p> +When you set this variable to <em>Explicit address</em>, the value + of the variable <code>reply_to_address</code> (see below) will be + added. Note that this is one situation where + <span class="mailheader">Reply-To:</span> munging may have a legitimate purpose. Say + you have two lists at your site, an announce list and a discussion + list. The announce list might allow postings only from a small + number of approved users; the general list membership probably + can't post to this list. But you want to allow comments on + announcements to be posted to the general discussion list by any + list member. In this case, you can set the <span class="mailheader">Reply-To:</span> + header for the announce list to point to the discussion list's + posting address. + +<p> +</dd> +<dt><strong>reply_to_address</strong></dt> +<dd>This is the address that will be added in the + <span class="mailheader">Reply-To:</span> header if <code>reply_goes_to_list</code> is set + to <em>Explicit address</em>. + +<p> +</dd> +</dl> + +<p> + +<div class="navigation"> +<div class='online-navigation'> +<p></p><hr /> +<table align="center" width="100%" cellpadding="0" cellspacing="2"> +<tr> +<td class='online-navigation'><a rel="prev" title="2.1.1 general list personality" + href="node10.html"><img src='previous.png' + border='0' height='32' alt='Previous Page' width='32' /></a></td> +<td class='online-navigation'><a rel="parent" title="2.1 the General Options" + href="node9.html"><img src='up.png' + border='0' height='32' alt='Up one Level' width='32' /></a></td> +<td class='online-navigation'><a rel="next" title="2.1.3 umbrella list settings" + href="node12.html"><img src='next.png' + border='0' height='32' alt='Next Page' width='32' /></a></td> +<td align="center" width="100%">GNU Mailman - List Administration Manual</td> +<td class='online-navigation'><a rel="contents" title="Table of Contents" + href="contents.html"><img src='contents.png' + border='0' height='32' alt='Contents' width='32' /></a></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +</tr></table> +<div class='online-navigation'> +<b class="navlabel">Previous:</b> +<a class="sectref" rel="prev" href="node10.html">2.1.1 General list personality</a> +<b class="navlabel">Up:</b> +<a class="sectref" rel="parent" href="node9.html">2.1 The General Options</a> +<b class="navlabel">Next:</b> +<a class="sectref" rel="next" href="node12.html">2.1.3 Umbrella list settings</a> +</div> +</div> +<hr /> +<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +</div> +<!--End of Navigation Panel--> + +</body> +</html> diff --git a/doc/mailman-admin/node12.html b/doc/mailman-admin/node12.html new file mode 100644 index 00000000..1f4a69cc --- /dev/null +++ b/doc/mailman-admin/node12.html @@ -0,0 +1,100 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> +<html> +<head> +<link rel="STYLESHEET" href="mailman-admin.css" type='text/css' /> +<link rel="first" href="mailman-admin.html" title='GNU mailman - list Administration Manual' /> +<link rel='contents' href='contents.html' title="Contents" /> +<link rel='last' href='about.html' title='About this document...' /> +<link rel='help' href='about.html' title='About this document...' /> +<link rel="next" href="node13.html" /> +<link rel="prev" href="node11.html" /> +<link rel="parent" href="node9.html" /> +<link rel="next" href="node13.html" /> +<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> +<meta name='aesop' content='information' /> +<title>2.1.3 Umbrella list settings</title> +</head> +<body> +<div class="navigation"> +<div id='top-navigation-panel' xml:id='top-navigation-panel'> +<table align="center" width="100%" cellpadding="0" cellspacing="2"> +<tr> +<td class='online-navigation'><a rel="prev" title="2.1.2 reply-to header munging" + href="node11.html"><img src='previous.png' + border='0' height='32' alt='Previous Page' width='32' /></a></td> +<td class='online-navigation'><a rel="parent" title="2.1 the General Options" + href="node9.html"><img src='up.png' + border='0' height='32' alt='Up one Level' width='32' /></a></td> +<td class='online-navigation'><a rel="next" title="2.1.4 Notifications" + href="node13.html"><img src='next.png' + border='0' height='32' alt='Next Page' width='32' /></a></td> +<td align="center" width="100%">GNU Mailman - List Administration Manual</td> +<td class='online-navigation'><a rel="contents" title="Table of Contents" + href="contents.html"><img src='contents.png' + border='0' height='32' alt='Contents' width='32' /></a></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +</tr></table> +<div class='online-navigation'> +<b class="navlabel">Previous:</b> +<a class="sectref" rel="prev" href="node11.html">2.1.2 Reply-To header munging</a> +<b class="navlabel">Up:</b> +<a class="sectref" rel="parent" href="node9.html">2.1 The General Options</a> +<b class="navlabel">Next:</b> +<a class="sectref" rel="next" href="node13.html">2.1.4 Notifications</a> +</div> +<hr /></div> +</div> +<!--End of Navigation Panel--> + +<h3><a name="SECTION002213000000000000000"> +2.1.3 Umbrella list settings</a> +</h3> + +<p> +TBD. Note that umbrella lists are deprecated and will be replace with +a better mechanism for Mailman 3.0. + +<p> + +<div class="navigation"> +<div class='online-navigation'> +<p></p><hr /> +<table align="center" width="100%" cellpadding="0" cellspacing="2"> +<tr> +<td class='online-navigation'><a rel="prev" title="2.1.2 reply-to header munging" + href="node11.html"><img src='previous.png' + border='0' height='32' alt='Previous Page' width='32' /></a></td> +<td class='online-navigation'><a rel="parent" title="2.1 the General Options" + href="node9.html"><img src='up.png' + border='0' height='32' alt='Up one Level' width='32' /></a></td> +<td class='online-navigation'><a rel="next" title="2.1.4 Notifications" + href="node13.html"><img src='next.png' + border='0' height='32' alt='Next Page' width='32' /></a></td> +<td align="center" width="100%">GNU Mailman - List Administration Manual</td> +<td class='online-navigation'><a rel="contents" title="Table of Contents" + href="contents.html"><img src='contents.png' + border='0' height='32' alt='Contents' width='32' /></a></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +</tr></table> +<div class='online-navigation'> +<b class="navlabel">Previous:</b> +<a class="sectref" rel="prev" href="node11.html">2.1.2 Reply-To header munging</a> +<b class="navlabel">Up:</b> +<a class="sectref" rel="parent" href="node9.html">2.1 The General Options</a> +<b class="navlabel">Next:</b> +<a class="sectref" rel="next" href="node13.html">2.1.4 Notifications</a> +</div> +</div> +<hr /> +<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +</div> +<!--End of Navigation Panel--> + +</body> +</html> diff --git a/doc/mailman-admin/node13.html b/doc/mailman-admin/node13.html new file mode 100644 index 00000000..bbf848ce --- /dev/null +++ b/doc/mailman-admin/node13.html @@ -0,0 +1,184 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> +<html> +<head> +<link rel="STYLESHEET" href="mailman-admin.css" type='text/css' /> +<link rel="first" href="mailman-admin.html" title='GNU mailman - list Administration Manual' /> +<link rel='contents' href='contents.html' title="Contents" /> +<link rel='last' href='about.html' title='About this document...' /> +<link rel='help' href='about.html' title='About this document...' /> +<link rel="next" href="node14.html" /> +<link rel="prev" href="node12.html" /> +<link rel="parent" href="node9.html" /> +<link rel="next" href="node14.html" /> +<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> +<meta name='aesop' content='information' /> +<title>2.1.4 Notifications</title> +</head> +<body> +<div class="navigation"> +<div id='top-navigation-panel' xml:id='top-navigation-panel'> +<table align="center" width="100%" cellpadding="0" cellspacing="2"> +<tr> +<td class='online-navigation'><a rel="prev" title="2.1.3 umbrella list settings" + href="node12.html"><img src='previous.png' + border='0' height='32' alt='Previous Page' width='32' /></a></td> +<td class='online-navigation'><a rel="parent" title="2.1 the General Options" + href="node9.html"><img src='up.png' + border='0' height='32' alt='Up one Level' width='32' /></a></td> +<td class='online-navigation'><a rel="next" title="2.1.5 additional settings" + href="node14.html"><img src='next.png' + border='0' height='32' alt='Next Page' width='32' /></a></td> +<td align="center" width="100%">GNU Mailman - List Administration Manual</td> +<td class='online-navigation'><a rel="contents" title="Table of Contents" + href="contents.html"><img src='contents.png' + border='0' height='32' alt='Contents' width='32' /></a></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +</tr></table> +<div class='online-navigation'> +<b class="navlabel">Previous:</b> +<a class="sectref" rel="prev" href="node12.html">2.1.3 Umbrella list settings</a> +<b class="navlabel">Up:</b> +<a class="sectref" rel="parent" href="node9.html">2.1 The General Options</a> +<b class="navlabel">Next:</b> +<a class="sectref" rel="next" href="node14.html">2.1.5 Additional settings</a> +</div> +<hr /></div> +</div> +<!--End of Navigation Panel--> + +<h3><a name="SECTION002214000000000000000"> +2.1.4 Notifications</a> +</h3> + +<p> +Mailman sends notifications to the list administrators or list members +under a number of different circumstances. Most of these +notifications can be configured in this section, but see the Bounce +Processing and Auto-responder categories for other notifications that +Mailman can send. + +<p> +<dl> +<dt><strong>send_reminders</strong></dt> +<dd>By default Mailman sends all list members a monthly password + reminder. This notice serves two purposes. First, it reminds + people about all the lists they may be subscribed to on this + domain, including the lists where their subscription may be + disabled. Second, it reminds people about their passwords for + these lists, as well as the url for their personal options pages, + so that they can more easily configure their subscription options. + +<p> +Some people get annoyed with these monthly reminders, and they can + disable the reminders via their subscription options page. For + some lists, the monthly reminders aren't appropriate for any of + the members, so you can disable them list-wide by setting the + <code>send_reminders</code> variable to <em>No</em>. + +<p> +</dd> +<dt><strong>welcome_msg</strong></dt> +<dd>When new members are subscribed to the list, either by their own + action, or the action of a list administrator, a welcome message + can be sent to them. The welcome message contains some common + boilerplate information, such as the name of the list, + instructions for posting to the list, and the member's + subscription password. You can add additional information to the + welcome message by typing the text into the <code>welcome_msg</code> + text box. Note that because this text is sent as part of an + email, it should <strong>not</strong> contain HTML. + +<p> +</dd> +<dt><strong>send_welcome_msg</strong></dt> +<dd>This flag controls whether or not the welcome message is sent to + new subscribers. + +<p> +</dd> +<dt><strong>goodbye_msg</strong></dt> +<dd>Like the <code>welcome_msg</code>, a ``goodbye'' message can be sent to + members when they unsubscribe from the list. Unlike the welcome + message, there's no boilerplate for the goodbye message. Enter + the entire goodbye message you'd like unsubscribing members to + receive into the <code>goodbye_msg</code> text box. + +<p> +</dd> +<dt><strong>send_goodbye_msg</strong></dt> +<dd>This flag controls whether or not the goodbye message is sent to + unsubscribing members. + +<p> +</dd> +<dt><strong>admin_immed_notify</strong></dt> +<dd>List moderators get notifications of pending administrative + actions, such as subscription or unsubscription requests that + require moderator approval, or posted messages that are being held + for moderator approval. List moderators will always get a daily + summary of such pending requests, but they can also get immediate + notifications when such a request is made. The + <code>admin_immed_notify</code> variable controls whether these + immediate notifications are sent or not. It's generally a good + idea to leave this set to <em>Yes</em>. + +<p> +</dd> +<dt><strong>admin_notify_mchanges</strong></dt> +<dd>This variable controls whether the list administrators should get + notifications when members join or leave the list. + +<p> +</dd> +<dt><strong>respond_to_post_requests</strong></dt> +<dd>This variable controls whether the original sender of a posting + gets a notice when their message is held for moderator approval. + +<p> +</dd> +</dl> + +<p> + +<div class="navigation"> +<div class='online-navigation'> +<p></p><hr /> +<table align="center" width="100%" cellpadding="0" cellspacing="2"> +<tr> +<td class='online-navigation'><a rel="prev" title="2.1.3 umbrella list settings" + href="node12.html"><img src='previous.png' + border='0' height='32' alt='Previous Page' width='32' /></a></td> +<td class='online-navigation'><a rel="parent" title="2.1 the General Options" + href="node9.html"><img src='up.png' + border='0' height='32' alt='Up one Level' width='32' /></a></td> +<td class='online-navigation'><a rel="next" title="2.1.5 additional settings" + href="node14.html"><img src='next.png' + border='0' height='32' alt='Next Page' width='32' /></a></td> +<td align="center" width="100%">GNU Mailman - List Administration Manual</td> +<td class='online-navigation'><a rel="contents" title="Table of Contents" + href="contents.html"><img src='contents.png' + border='0' height='32' alt='Contents' width='32' /></a></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +</tr></table> +<div class='online-navigation'> +<b class="navlabel">Previous:</b> +<a class="sectref" rel="prev" href="node12.html">2.1.3 Umbrella list settings</a> +<b class="navlabel">Up:</b> +<a class="sectref" rel="parent" href="node9.html">2.1 The General Options</a> +<b class="navlabel">Next:</b> +<a class="sectref" rel="next" href="node14.html">2.1.5 Additional settings</a> +</div> +</div> +<hr /> +<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +</div> +<!--End of Navigation Panel--> + +</body> +</html> diff --git a/doc/mailman-admin/node14.html b/doc/mailman-admin/node14.html new file mode 100644 index 00000000..99e91f28 --- /dev/null +++ b/doc/mailman-admin/node14.html @@ -0,0 +1,207 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> +<html> +<head> +<link rel="STYLESHEET" href="mailman-admin.css" type='text/css' /> +<link rel="first" href="mailman-admin.html" title='GNU mailman - list Administration Manual' /> +<link rel='contents' href='contents.html' title="Contents" /> +<link rel='last' href='about.html' title='About this document...' /> +<link rel='help' href='about.html' title='About this document...' /> +<link rel="prev" href="node13.html" /> +<link rel="parent" href="node9.html" /> +<link rel="next" href="node15.html" /> +<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> +<meta name='aesop' content='information' /> +<title>2.1.5 Additional settings</title> +</head> +<body> +<div class="navigation"> +<div id='top-navigation-panel' xml:id='top-navigation-panel'> +<table align="center" width="100%" cellpadding="0" cellspacing="2"> +<tr> +<td class='online-navigation'><a rel="prev" title="2.1.4 Notifications" + href="node13.html"><img src='previous.png' + border='0' height='32' alt='Previous Page' width='32' /></a></td> +<td class='online-navigation'><a rel="parent" title="2.1 the General Options" + href="node9.html"><img src='up.png' + border='0' height='32' alt='Up one Level' width='32' /></a></td> +<td class='online-navigation'><a rel="next" title="2.2 the Passwords Category" + href="node15.html"><img src='next.png' + border='0' height='32' alt='Next Page' width='32' /></a></td> +<td align="center" width="100%">GNU Mailman - List Administration Manual</td> +<td class='online-navigation'><a rel="contents" title="Table of Contents" + href="contents.html"><img src='contents.png' + border='0' height='32' alt='Contents' width='32' /></a></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +</tr></table> +<div class='online-navigation'> +<b class="navlabel">Previous:</b> +<a class="sectref" rel="prev" href="node13.html">2.1.4 Notifications</a> +<b class="navlabel">Up:</b> +<a class="sectref" rel="parent" href="node9.html">2.1 The General Options</a> +<b class="navlabel">Next:</b> +<a class="sectref" rel="next" href="node15.html">2.2 The Passwords Category</a> +</div> +<hr /></div> +</div> +<!--End of Navigation Panel--> + +<h3><a name="SECTION002215000000000000000"> +2.1.5 Additional settings</a> +</h3> + +<p> +This section contains some miscellaneous settings for your mailing +list. + +<p> +<dl> +<dt><strong>emergency</strong></dt> +<dd>When this option is enabled, all list traffic is emergency + moderated, i.e. held for moderation. Turn this option on when + your list is experiencing a flamewar and you want a cooling off + period. + +<p> +</dd> +<dt><strong>new_member_options</strong></dt> +<dd>Each member has a set of subscription options which they can use + to control how they receive messages and otherwise interact with + the list. While the members can change these settings by logging + into their personal options page, you might want to set the + default for a number of the member options. You can do that with + this variable, but see also the other categories for other member + defaults you can set. + +<p> +This variable presents a set of checkboxes which control the + defaults for some of the member options. <em>Conceal the + member's address</em> specifies whether or not the address is + displayed in the list roster. <em>Acknowledge the member's + posting</em> controls whether or not Mailman sends an acknowledgement + to a member when they post a message to the list. <em>Do not + send a copy of a member's own post</em> specifies whether a member + posting to the list will get a copy of their own posting. + <em>Filter out duplicate messages to list members (if possible)</em> + specifies whether members who are explicitly listed as a recipient + of a message (e.g. via the <span class="mailheader">Cc:</span> header) will also get a + copy from Mailman. + +<p> +Of course, members can always override these defaults by making + changes on their membership options page. + +<p> +</dd> +<dt><strong>administrivia</strong></dt> +<dd>This option specifies whether Mailman will search posted messages + for <em>admimistrivia</em>, in other words, email commands which + usually should be posted to the <code>-request</code> address for the + list. Setting this to <em>Yes</em> helps prevent such things as + unsubscribe messages getting erroneously posted to the list. + +<p> +If a message seems to contain administrivia, it is held for + moderator approval. + +<p> +</dd> +<dt><strong>max_message_size</strong></dt> +<dd>This option specifies a maximum message size, in kilobytes, over + which the message will be held for moderator approval. + +<p> +</dd> +<dt><strong>host_name</strong></dt> +<dd>This option specifies the host name part of email addresses used + by this list. For example, this is the <code>example.com</code> part of + the posting address <code>mylist@example.com</code>. + +<p> +It's generally not a good idea to change this value, since its + default value is specified when the mailing list is created. + Changing this to an incorrect value could make it difficult to + contact your mailing list. Also not that the url used to visit + the list's pages is not configurable through the web interface. + This is because if you messed it up, you'd have to have the site + administrator fix it. + +<p> +</dd> +<dt><strong>include_rfc2369_headers</strong></dt> +<dd><a class="rfc" id='rfcref-1033' xml:id='rfcref-1033' +href="http://www.faqs.org/rfcs/rfc2369.html">RFC 2369</a> is an internet standard that describes a bunch of + headers that mailing list managers should add to messages to make + it easier for people to interact with the list. Mail reading + programs which support this standard may provide buttons for easy + access to the list's archives, or for subscribing and + unsubscribing to the list. It's generally a good idea to enable + these headers as it provides for an improved user experience. + These headers are often called the <code>List-*</code> headers. + +<p> +However, not all mail readers are standards compliant yet, and if + you have a large number of members who are using non-compliant + mail readers, they may be annoyed at these headers. You should + first try to educate your members as to why these headers exist, + and how to hide them in their mail clients. As a last resort you + can disable these headers, but this is not recommended. + +<p> +</dd> +<dt><strong>include_list_post_header</strong></dt> +<dd>The <span class="mailheader">List-Post:</span> header is one of the headers + recommended by <a class="rfc" id='rfcref-1035' xml:id='rfcref-1035' +href="http://www.faqs.org/rfcs/rfc2369.html">RFC 2369</a>. However for some announce-only mailing + lists, only a very select group of people are allowed to post to + the list; the general membership is usually not allowed to post to + such lists. For lists of this nature, the <span class="mailheader">List-Post:</span> + header is misleading. Select <em>No</em> to disable the inclusion + of this header. (This does not affect the inclusion of the other + <code>List-*</code> headers.) +</dd> +</dl> + +<p> + +<div class="navigation"> +<div class='online-navigation'> +<p></p><hr /> +<table align="center" width="100%" cellpadding="0" cellspacing="2"> +<tr> +<td class='online-navigation'><a rel="prev" title="2.1.4 Notifications" + href="node13.html"><img src='previous.png' + border='0' height='32' alt='Previous Page' width='32' /></a></td> +<td class='online-navigation'><a rel="parent" title="2.1 the General Options" + href="node9.html"><img src='up.png' + border='0' height='32' alt='Up one Level' width='32' /></a></td> +<td class='online-navigation'><a rel="next" title="2.2 the Passwords Category" + href="node15.html"><img src='next.png' + border='0' height='32' alt='Next Page' width='32' /></a></td> +<td align="center" width="100%">GNU Mailman - List Administration Manual</td> +<td class='online-navigation'><a rel="contents" title="Table of Contents" + href="contents.html"><img src='contents.png' + border='0' height='32' alt='Contents' width='32' /></a></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +</tr></table> +<div class='online-navigation'> +<b class="navlabel">Previous:</b> +<a class="sectref" rel="prev" href="node13.html">2.1.4 Notifications</a> +<b class="navlabel">Up:</b> +<a class="sectref" rel="parent" href="node9.html">2.1 The General Options</a> +<b class="navlabel">Next:</b> +<a class="sectref" rel="next" href="node15.html">2.2 The Passwords Category</a> +</div> +</div> +<hr /> +<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +</div> +<!--End of Navigation Panel--> + +</body> +</html> diff --git a/doc/mailman-admin/node15.html b/doc/mailman-admin/node15.html new file mode 100644 index 00000000..db700d93 --- /dev/null +++ b/doc/mailman-admin/node15.html @@ -0,0 +1,120 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> +<html> +<head> +<link rel="STYLESHEET" href="mailman-admin.css" type='text/css' /> +<link rel="first" href="mailman-admin.html" title='GNU mailman - list Administration Manual' /> +<link rel='contents' href='contents.html' title="Contents" /> +<link rel='last' href='about.html' title='About this document...' /> +<link rel='help' href='about.html' title='About this document...' /> +<link rel="next" href="node16.html" /> +<link rel="prev" href="node9.html" /> +<link rel="parent" href="node8.html" /> +<link rel="next" href="node16.html" /> +<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> +<meta name='aesop' content='information' /> +<title>2.2 The Passwords Category</title> +</head> +<body> +<div class="navigation"> +<div id='top-navigation-panel' xml:id='top-navigation-panel'> +<table align="center" width="100%" cellpadding="0" cellspacing="2"> +<tr> +<td class='online-navigation'><a rel="prev" title="2.1.5 additional settings" + href="node14.html"><img src='previous.png' + border='0' height='32' alt='Previous Page' width='32' /></a></td> +<td class='online-navigation'><a rel="parent" title="2 the List Configuration" + href="node8.html"><img src='up.png' + border='0' height='32' alt='Up one Level' width='32' /></a></td> +<td class='online-navigation'><a rel="next" title="2.3 the Language Options" + href="node16.html"><img src='next.png' + border='0' height='32' alt='Next Page' width='32' /></a></td> +<td align="center" width="100%">GNU Mailman - List Administration Manual</td> +<td class='online-navigation'><a rel="contents" title="Table of Contents" + href="contents.html"><img src='contents.png' + border='0' height='32' alt='Contents' width='32' /></a></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +</tr></table> +<div class='online-navigation'> +<b class="navlabel">Previous:</b> +<a class="sectref" rel="prev" href="node14.html">2.1.5 Additional settings</a> +<b class="navlabel">Up:</b> +<a class="sectref" rel="parent" href="node8.html">2 The List Configuration</a> +<b class="navlabel">Next:</b> +<a class="sectref" rel="next" href="node16.html">2.3 The Language Options</a> +</div> +<hr /></div> +</div> +<!--End of Navigation Panel--> + +<h2><a name="SECTION002220000000000000000"> +2.2 The Passwords Category</a> +</h2> +As mentioned above, there are two primary administrative roles for +mailing lists. In this category you can specify the password for +these roles. + +<p> +The list owner has total control over the configuration of their +mailing list (within some bounds as specified by the site +administrator). Note that on this page, for historical reasons, the +list owner role is described here as the <em>list administrator</em>. +You can set the list owner's password by entering it in the password +field on the left. You must type it twice for confirmation. Note +that if you forget this password, the only way for you to get back +into your list's administrative pages is to ask the site administrator +to reset it for you (there's no password reminders for list owners). + +<p> +If you want to delegate list moderation to someone else, you can enter +a different moderator password in the field on the right (typed twice +for confirmation). Note that if you aren't going to delegate +moderation, and the same people are going to both configure the list +and moderate postings to the list, don't enter anything into the +moderator password fields. If you do enter a separate moderator +password, be sure to fill in the <code>moderator</code> variable in the +<em>General options</em> category page. + +<p> + +<div class="navigation"> +<div class='online-navigation'> +<p></p><hr /> +<table align="center" width="100%" cellpadding="0" cellspacing="2"> +<tr> +<td class='online-navigation'><a rel="prev" title="2.1.5 additional settings" + href="node14.html"><img src='previous.png' + border='0' height='32' alt='Previous Page' width='32' /></a></td> +<td class='online-navigation'><a rel="parent" title="2 the List Configuration" + href="node8.html"><img src='up.png' + border='0' height='32' alt='Up one Level' width='32' /></a></td> +<td class='online-navigation'><a rel="next" title="2.3 the Language Options" + href="node16.html"><img src='next.png' + border='0' height='32' alt='Next Page' width='32' /></a></td> +<td align="center" width="100%">GNU Mailman - List Administration Manual</td> +<td class='online-navigation'><a rel="contents" title="Table of Contents" + href="contents.html"><img src='contents.png' + border='0' height='32' alt='Contents' width='32' /></a></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +</tr></table> +<div class='online-navigation'> +<b class="navlabel">Previous:</b> +<a class="sectref" rel="prev" href="node14.html">2.1.5 Additional settings</a> +<b class="navlabel">Up:</b> +<a class="sectref" rel="parent" href="node8.html">2 The List Configuration</a> +<b class="navlabel">Next:</b> +<a class="sectref" rel="next" href="node16.html">2.3 The Language Options</a> +</div> +</div> +<hr /> +<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +</div> +<!--End of Navigation Panel--> + +</body> +</html> diff --git a/doc/mailman-admin/node16.html b/doc/mailman-admin/node16.html new file mode 100644 index 00000000..fe00410f --- /dev/null +++ b/doc/mailman-admin/node16.html @@ -0,0 +1,156 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> +<html> +<head> +<link rel="STYLESHEET" href="mailman-admin.css" type='text/css' /> +<link rel="first" href="mailman-admin.html" title='GNU mailman - list Administration Manual' /> +<link rel='contents' href='contents.html' title="Contents" /> +<link rel='last' href='about.html' title='About this document...' /> +<link rel='help' href='about.html' title='About this document...' /> +<link rel="next" href="node17.html" /> +<link rel="prev" href="node15.html" /> +<link rel="parent" href="node8.html" /> +<link rel="next" href="node17.html" /> +<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> +<meta name='aesop' content='information' /> +<title>2.3 The Language Options Category</title> +</head> +<body> +<div class="navigation"> +<div id='top-navigation-panel' xml:id='top-navigation-panel'> +<table align="center" width="100%" cellpadding="0" cellspacing="2"> +<tr> +<td class='online-navigation'><a rel="prev" title="2.2 the Passwords Category" + href="node15.html"><img src='previous.png' + border='0' height='32' alt='Previous Page' width='32' /></a></td> +<td class='online-navigation'><a rel="parent" title="2 the List Configuration" + href="node8.html"><img src='up.png' + border='0' height='32' alt='Up one Level' width='32' /></a></td> +<td class='online-navigation'><a rel="next" title="2.4 the Membership Management" + href="node17.html"><img src='next.png' + border='0' height='32' alt='Next Page' width='32' /></a></td> +<td align="center" width="100%">GNU Mailman - List Administration Manual</td> +<td class='online-navigation'><a rel="contents" title="Table of Contents" + href="contents.html"><img src='contents.png' + border='0' height='32' alt='Contents' width='32' /></a></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +</tr></table> +<div class='online-navigation'> +<b class="navlabel">Previous:</b> +<a class="sectref" rel="prev" href="node15.html">2.2 The Passwords Category</a> +<b class="navlabel">Up:</b> +<a class="sectref" rel="parent" href="node8.html">2 The List Configuration</a> +<b class="navlabel">Next:</b> +<a class="sectref" rel="next" href="node17.html">2.4 The Membership Management</a> +</div> +<hr /></div> +</div> +<!--End of Navigation Panel--> + +<h2><a name="SECTION002230000000000000000"> +2.3 The Language Options Category</a> +</h2> +Mailman is multilingual and internationalized, meaning you can set up +your list so that members can interact with it in any of a number of +natural languages. Of course, Mailman won't translate list +postings. :) + +<p> +However, if your site administrator has enabled its support, you can +set your list up to support any of about two dozen languages, such as +German, Italian, Japanese, or Spanish. Your list members can then +choose any of your supported languages as their <em>preferred +language</em> for interacting with the list. Such things as their member +options page will be displayed in this language. Each mailing list +also has its own <em>preferred language</em> which is the language the +list supports if no other language context is known. + +<p> +These variables control the language settings for your mailing list: + +<p> +<dl> +<dt><strong>preferred_language</strong></dt> +<dd>This is the list's preferred language, which is the language that + the list administrative pages will be displayed in. Also any + messages sent to the list owners by Mailman will be sent in this + language. This option is presented as a drop-down list containing + the language enabled in the <code>available_languages</code> variable. + +<p> +</dd> +<dt><strong>available_languages</strong></dt> +<dd>This set of checkboxes contains all the natural languages that + your site administrator has made available to your mailing lists. + Select any language that you'd either like your members to be able + to view the list in, or that you'd like to be able to use in your + list's <code>preferred_language</code> variable. + +<p> +</dd> +<dt><strong>encode_ascii_prefixes</strong></dt> +<dd>If your mailing list's preferred language uses a non-ASCII + character set and the <code>subject_prefix</code> contains non-ASCII + characters, the prefix will always be encoded according to the + relevant standards. However, if your subject prefix contains only + ASCII characters, you may want to set this option to <em>Never</em> + to disable prefix encoding. This can make the subject headers + slightly more readable for users with mail readers that don't + properly handle non-ASCII encodings. + +<p> +Note however, that if your mailing list receives both encoded and + unencoded subject headers, you might want to choose <em>As + needed</em>. Using this setting, Mailman will not encode ASCII + prefixes when the rest of the header contains only ASCII + characters, but if the original header contains non-ASCII + characters, it will encode the prefix. This avoids an ambiguity + in the standards which could cause some mail readers to display + extra, or missing spaces between the prefix and the original + header. +</dd> +</dl> + +<p> + +<div class="navigation"> +<div class='online-navigation'> +<p></p><hr /> +<table align="center" width="100%" cellpadding="0" cellspacing="2"> +<tr> +<td class='online-navigation'><a rel="prev" title="2.2 the Passwords Category" + href="node15.html"><img src='previous.png' + border='0' height='32' alt='Previous Page' width='32' /></a></td> +<td class='online-navigation'><a rel="parent" title="2 the List Configuration" + href="node8.html"><img src='up.png' + border='0' height='32' alt='Up one Level' width='32' /></a></td> +<td class='online-navigation'><a rel="next" title="2.4 the Membership Management" + href="node17.html"><img src='next.png' + border='0' height='32' alt='Next Page' width='32' /></a></td> +<td align="center" width="100%">GNU Mailman - List Administration Manual</td> +<td class='online-navigation'><a rel="contents" title="Table of Contents" + href="contents.html"><img src='contents.png' + border='0' height='32' alt='Contents' width='32' /></a></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +</tr></table> +<div class='online-navigation'> +<b class="navlabel">Previous:</b> +<a class="sectref" rel="prev" href="node15.html">2.2 The Passwords Category</a> +<b class="navlabel">Up:</b> +<a class="sectref" rel="parent" href="node8.html">2 The List Configuration</a> +<b class="navlabel">Next:</b> +<a class="sectref" rel="next" href="node17.html">2.4 The Membership Management</a> +</div> +</div> +<hr /> +<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +</div> +<!--End of Navigation Panel--> + +</body> +</html> diff --git a/doc/mailman-admin/node17.html b/doc/mailman-admin/node17.html new file mode 100644 index 00000000..df0e7232 --- /dev/null +++ b/doc/mailman-admin/node17.html @@ -0,0 +1,108 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> +<html> +<head> +<link rel="STYLESHEET" href="mailman-admin.css" type='text/css' /> +<link rel="first" href="mailman-admin.html" title='GNU mailman - list Administration Manual' /> +<link rel='contents' href='contents.html' title="Contents" /> +<link rel='last' href='about.html' title='About this document...' /> +<link rel='help' href='about.html' title='About this document...' /> +<link rel="next" href="node18.html" /> +<link rel="prev" href="node16.html" /> +<link rel="parent" href="node8.html" /> +<link rel="next" href="node18.html" /> +<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> +<meta name='aesop' content='information' /> +<title>2.4 The Membership Management Category</title> +</head> +<body> +<div class="navigation"> +<div id='top-navigation-panel' xml:id='top-navigation-panel'> +<table align="center" width="100%" cellpadding="0" cellspacing="2"> +<tr> +<td class='online-navigation'><a rel="prev" title="2.3 the Language Options" + href="node16.html"><img src='previous.png' + border='0' height='32' alt='Previous Page' width='32' /></a></td> +<td class='online-navigation'><a rel="parent" title="2 the List Configuration" + href="node8.html"><img src='up.png' + border='0' height='32' alt='Up one Level' width='32' /></a></td> +<td class='online-navigation'><a rel="next" title="2.5 the Non-digest Options" + href="node18.html"><img src='next.png' + border='0' height='32' alt='Next Page' width='32' /></a></td> +<td align="center" width="100%">GNU Mailman - List Administration Manual</td> +<td class='online-navigation'><a rel="contents" title="Table of Contents" + href="contents.html"><img src='contents.png' + border='0' height='32' alt='Contents' width='32' /></a></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +</tr></table> +<div class='online-navigation'> +<b class="navlabel">Previous:</b> +<a class="sectref" rel="prev" href="node16.html">2.3 The Language Options</a> +<b class="navlabel">Up:</b> +<a class="sectref" rel="parent" href="node8.html">2 The List Configuration</a> +<b class="navlabel">Next:</b> +<a class="sectref" rel="next" href="node18.html">2.5 The Non-digest Options</a> +</div> +<hr /></div> +</div> +<!--End of Navigation Panel--> + +<h2><a name="SECTION002240000000000000000"> +2.4 The Membership Management Category</a> +</h2> + +<p> +The <em>Membership Management</em> category is unlike the other +administrative categories. It doesn't contain configuration variables +or list settings. Instead, it presents a number of pages that allow +you to manage the membership of you list. This includes pages for +subscribing and unsubscribing members, and for searching for members, +and for changing various member-specific settings. + +<p> +More details on membership management are described in the Membership +Management section. + +<p> + +<div class="navigation"> +<div class='online-navigation'> +<p></p><hr /> +<table align="center" width="100%" cellpadding="0" cellspacing="2"> +<tr> +<td class='online-navigation'><a rel="prev" title="2.3 the Language Options" + href="node16.html"><img src='previous.png' + border='0' height='32' alt='Previous Page' width='32' /></a></td> +<td class='online-navigation'><a rel="parent" title="2 the List Configuration" + href="node8.html"><img src='up.png' + border='0' height='32' alt='Up one Level' width='32' /></a></td> +<td class='online-navigation'><a rel="next" title="2.5 the Non-digest Options" + href="node18.html"><img src='next.png' + border='0' height='32' alt='Next Page' width='32' /></a></td> +<td align="center" width="100%">GNU Mailman - List Administration Manual</td> +<td class='online-navigation'><a rel="contents" title="Table of Contents" + href="contents.html"><img src='contents.png' + border='0' height='32' alt='Contents' width='32' /></a></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +</tr></table> +<div class='online-navigation'> +<b class="navlabel">Previous:</b> +<a class="sectref" rel="prev" href="node16.html">2.3 The Language Options</a> +<b class="navlabel">Up:</b> +<a class="sectref" rel="parent" href="node8.html">2 The List Configuration</a> +<b class="navlabel">Next:</b> +<a class="sectref" rel="next" href="node18.html">2.5 The Non-digest Options</a> +</div> +</div> +<hr /> +<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +</div> +<!--End of Navigation Panel--> + +</body> +</html> diff --git a/doc/mailman-admin/node18.html b/doc/mailman-admin/node18.html new file mode 100644 index 00000000..69795786 --- /dev/null +++ b/doc/mailman-admin/node18.html @@ -0,0 +1,318 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> +<html> +<head> +<link rel="STYLESHEET" href="mailman-admin.css" type='text/css' /> +<link rel="first" href="mailman-admin.html" title='GNU mailman - list Administration Manual' /> +<link rel='contents' href='contents.html' title="Contents" /> +<link rel='last' href='about.html' title='About this document...' /> +<link rel='help' href='about.html' title='About this document...' /> +<link rel="next" href="node19.html" /> +<link rel="prev" href="node17.html" /> +<link rel="parent" href="node8.html" /> +<link rel="next" href="node19.html" /> +<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> +<meta name='aesop' content='information' /> +<title>2.5 The Non-digest Options Category</title> +</head> +<body> +<div class="navigation"> +<div id='top-navigation-panel' xml:id='top-navigation-panel'> +<table align="center" width="100%" cellpadding="0" cellspacing="2"> +<tr> +<td class='online-navigation'><a rel="prev" title="2.4 the Membership Management" + href="node17.html"><img src='previous.png' + border='0' height='32' alt='Previous Page' width='32' /></a></td> +<td class='online-navigation'><a rel="parent" title="2 the List Configuration" + href="node8.html"><img src='up.png' + border='0' height='32' alt='Up one Level' width='32' /></a></td> +<td class='online-navigation'><a rel="next" title="2.6 the Digest Options" + href="node19.html"><img src='next.png' + border='0' height='32' alt='Next Page' width='32' /></a></td> +<td align="center" width="100%">GNU Mailman - List Administration Manual</td> +<td class='online-navigation'><a rel="contents" title="Table of Contents" + href="contents.html"><img src='contents.png' + border='0' height='32' alt='Contents' width='32' /></a></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +</tr></table> +<div class='online-navigation'> +<b class="navlabel">Previous:</b> +<a class="sectref" rel="prev" href="node17.html">2.4 The Membership Management</a> +<b class="navlabel">Up:</b> +<a class="sectref" rel="parent" href="node8.html">2 The List Configuration</a> +<b class="navlabel">Next:</b> +<a class="sectref" rel="next" href="node19.html">2.6 The Digest Options</a> +</div> +<hr /></div> +</div> +<!--End of Navigation Panel--> + +<h2><a name="SECTION002250000000000000000"> +2.5 The Non-digest Options Category</a> +</h2> + +<p> +Mailman delivers messages to users via two modes. List members can +elect to receive postings in bundles call <em>digests</em> one or a few +times a day, or they can receive messages immediately whenever the +message is posted to the list. This latter delivery mode is also +called <em>non-digest delivery</em>. There are two administrative +categories available for separately controlling digest and non-digest +delivery. You can even disable one or the other forms of delivery +(but not both). + +<p> +Both kinds of delivery can have list-specific headers and footers +added to them which can contain other useful information you want your +list members to see. For example, you can include instructions for +unsubscribing, or a url to the lists digest, or any other information. + +<p> +Non-digest deliveries can also be <em>personalized</em> which means +certain parts of the message can contain information tailored to the +member receiving the message. For example, the <span class="mailheader">To:</span> header +will contain the address of the member when deliveries are +personalized. Footers and headers can contain personalized +information as well, such as a link to the individual user's options +page. + +<p> +In addition, personalized messages will contain extra information that +Mailman can use to unambiguously track bounces from members. +Ordinarily, Mailman does some pattern recognition on bounce messages +to determine list members whose addresses are no longer valid, but +because of the vagaries of mail systems, and the countless forwards +people can put in place, it's often the case that bounce messages +don't contain any useful information in them. Personalized messages +avoid this problem by encoding information in certain headers that +unambiguously identify the recipient of a message. If that message +bounces, Mailman will know exactly which member it was intended for. + +<p> +Note that because personalization requires extra system resources, it +must be enabled by the site administrator before you can choose it. + +<p> +Here are the variables which control non-digest delivery: + +<p> +<dl> +<dt><strong>nondigestable</strong></dt> +<dd>This option controls whether members can receive immediate + delivery or not. If not, they will be forced to receive messages + in digests. You can't disable non-digest delivery if digests are + already disabled. + +<p> +</dd> +<dt><strong>personalize</strong></dt> +<dd>This option turns on message personalization. + +<p> +</dd> +<dt><strong>msg_header</strong></dt> +<dd>This text box lets you enter information that will be included in + the header of every non-digest message sent through the + list. + +<p> +See below for more information on what can go in the headers and + footers. If you leave this text box empty, no header will be + added. + +<p> +</dd> +<dt><strong>msg_footer</strong></dt> +<dd>Just like with the header, you can add a footer to every message. + The same rules apply to footers as apply to headers. +</dd> +</dl> + +<p> +Headers and footers can contain any text you want. For non-English +lists, the headers and footers can contain any character in the +character set of the list's preferred language. The headers and +footers can also contain <em>substitution variables</em> which Mailman +will fill in with information taken from the mailing list. These +substitutions are in Python string interpolation format, where +something like <code>%(list_name)s</code> is substituted with he name of +the mailing list. Note that the trailing "<tt class="samp">s</tt>" is +required<a name="tex2html4" + href="#foot279"><sup>2</sup></a>. + +<p> +For example, a footer containing the following text: + +<p> +<div class="verbatim"><pre> +This is the \%(list_name)s mailing list +Description: \%(description)s +</pre></div> + +<p> +might get attached to postings like so: + +<p> +<div class="verbatim"><pre> +This is the Example mailing list +Description: An example of Mailman mailing lists +</pre></div> + +<p> +Here is the list of substitution variables available for your headers +and footers: + +<p> +<dl> +<dt><strong>real_name</strong></dt> +<dd>This is the value of the <code>real_name</code> configuration variable + in the General options category. + +<p> +</dd> +<dt><strong>list_name</strong></dt> +<dd>This is the canonical name of the mailing list. In other words + it's the posting address of the list<a name="tex2html5" + href="#foot280"><sup>3</sup></a>. + +<p> +</dd> +<dt><strong>host_name</strong></dt> +<dd>This is the domain name part of the email address for this list. + +<p> +</dd> +<dt><strong>web_page_url</strong></dt> +<dd>This is the base url for contacting the list via the web. It can + be appended with <code>listinfo/%(list_name)s</code> to yield the + general list information page for the mailing list. + +<p> +</dd> +<dt><strong>description</strong></dt> +<dd>The brief description of the mailing list. + +<p> +</dd> +<dt><strong>info</strong></dt> +<dd>This is the full description of the mailing list. + +<p> +</dd> +<dt><strong>cgiext</strong></dt> +<dd>This is the extension added to CGI scripts. It might be the empty + string, <code>.cgi</code>, or something else depending on how your site + is configured. +</dd> +</dl> + +<p> +Note that <code>real_name</code>, <code>host_name</code>, <code>description</code>, and +<code>info</code> substitution variables take their values from the list +configuration variables of the same name. + +<p> +When personalization is enabled, the following substitution variables +are also available: + +<p> +<dl> +<dt><strong>user_address</strong></dt> +<dd>The address of the recipient of the message, coerced to lower case. + +<p> +</dd> +<dt><strong>user_delivered_to</strong></dt> +<dd>The case-preserved address that the user subscribed to the mailing + list with<a name="tex2html6" + href="#foot281"><sup>4</sup></a>. + +<p> +</dd> +<dt><strong>user_password</strong></dt> +<dd>The user's password, in clear text. + +<p> +</dd> +<dt><strong>user_name</strong></dt> +<dd>The user's full name. + +<p> +</dd> +<dt><strong>user_optionsurl</strong></dt> +<dd>The url to the user's personal options page. +</dd> +</dl> + +<p> +<br><hr><h4>Footnotes</h4> +<dl> +<dt><a name="foot279">... +required</a><A + HREF="node18.html#tex2html4"><sup>2</sup></a></dt> +<dd>The site administrator can configure lists to use a +simpler interpolation format, where <code>$list_name</code> or +<code>${list_name}</code> would be substituted with the mailing list's +name. Ask your site administrator if the've configured your list this +way. + +</dd> +<dt><a name="foot280">... list</a><A + HREF="node18.html#tex2html5"><sup>3</sup></a></dt> +<dd>For backward + compatibility, the variable <code>_internal_name</code> is + equivalent. + +</dd> +<dt><a name="foot281">... with</a><A + HREF="node18.html#tex2html6"><sup>4</sup></a></dt> +<dd>Usually it makes no difference which of + <code>user_address</code> and <code>user_delivered_to</code> is used, but it's + important to remember that they can be different. When they're + different, Mailman always uses the lower case address as the key + to the member's subscription information, but it always delivers + messages to the case-preserved version. + +</dd> +</dl> +<div class="navigation"> +<div class='online-navigation'> +<p></p><hr /> +<table align="center" width="100%" cellpadding="0" cellspacing="2"> +<tr> +<td class='online-navigation'><a rel="prev" title="2.4 the Membership Management" + href="node17.html"><img src='previous.png' + border='0' height='32' alt='Previous Page' width='32' /></a></td> +<td class='online-navigation'><a rel="parent" title="2 the List Configuration" + href="node8.html"><img src='up.png' + border='0' height='32' alt='Up one Level' width='32' /></a></td> +<td class='online-navigation'><a rel="next" title="2.6 the Digest Options" + href="node19.html"><img src='next.png' + border='0' height='32' alt='Next Page' width='32' /></a></td> +<td align="center" width="100%">GNU Mailman - List Administration Manual</td> +<td class='online-navigation'><a rel="contents" title="Table of Contents" + href="contents.html"><img src='contents.png' + border='0' height='32' alt='Contents' width='32' /></a></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +</tr></table> +<div class='online-navigation'> +<b class="navlabel">Previous:</b> +<a class="sectref" rel="prev" href="node17.html">2.4 The Membership Management</a> +<b class="navlabel">Up:</b> +<a class="sectref" rel="parent" href="node8.html">2 The List Configuration</a> +<b class="navlabel">Next:</b> +<a class="sectref" rel="next" href="node19.html">2.6 The Digest Options</a> +</div> +</div> +<hr /> +<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +</div> +<!--End of Navigation Panel--> + +</body> +</html> diff --git a/doc/mailman-admin/node19.html b/doc/mailman-admin/node19.html new file mode 100644 index 00000000..75a5f53e --- /dev/null +++ b/doc/mailman-admin/node19.html @@ -0,0 +1,226 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> +<html> +<head> +<link rel="STYLESHEET" href="mailman-admin.css" type='text/css' /> +<link rel="first" href="mailman-admin.html" title='GNU mailman - list Administration Manual' /> +<link rel='contents' href='contents.html' title="Contents" /> +<link rel='last' href='about.html' title='About this document...' /> +<link rel='help' href='about.html' title='About this document...' /> +<link rel="next" href="node20.html" /> +<link rel="prev" href="node18.html" /> +<link rel="parent" href="node8.html" /> +<link rel="next" href="node20.html" /> +<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> +<meta name='aesop' content='information' /> +<title>2.6 The Digest Options Category</title> +</head> +<body> +<div class="navigation"> +<div id='top-navigation-panel' xml:id='top-navigation-panel'> +<table align="center" width="100%" cellpadding="0" cellspacing="2"> +<tr> +<td class='online-navigation'><a rel="prev" title="2.5 the Non-digest Options" + href="node18.html"><img src='previous.png' + border='0' height='32' alt='Previous Page' width='32' /></a></td> +<td class='online-navigation'><a rel="parent" title="2 the List Configuration" + href="node8.html"><img src='up.png' + border='0' height='32' alt='Up one Level' width='32' /></a></td> +<td class='online-navigation'><a rel="next" title="2.7 the Privacy Options" + href="node20.html"><img src='next.png' + border='0' height='32' alt='Next Page' width='32' /></a></td> +<td align="center" width="100%">GNU Mailman - List Administration Manual</td> +<td class='online-navigation'><a rel="contents" title="Table of Contents" + href="contents.html"><img src='contents.png' + border='0' height='32' alt='Contents' width='32' /></a></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +</tr></table> +<div class='online-navigation'> +<b class="navlabel">Previous:</b> +<a class="sectref" rel="prev" href="node18.html">2.5 The Non-digest Options</a> +<b class="navlabel">Up:</b> +<a class="sectref" rel="parent" href="node8.html">2 The List Configuration</a> +<b class="navlabel">Next:</b> +<a class="sectref" rel="next" href="node20.html">2.7 The Privacy Options</a> +</div> +<hr /></div> +</div> +<!--End of Navigation Panel--> + +<h2><a name="SECTION002260000000000000000"> +2.6 The Digest Options Category</a> +</h2> + +<p> +Digest delivery is a way to bundle many articles together into one +package, which can be delivered once per day (if there were any posted +articles), or whenever the package is bigger than a specified limit. +Some users may prefer this style of delivery for higher traffic lists +since they will receive fewer messages. + +<p> +Mailman supports two standard digest formats, and if digests are +enabled, users can select which of the two formats they receive. One +is MIME digests, where each message is an attachment inside a +<span class="mimetype">multipart/digest</span>. This format also contains a summary +table of contents, and of course the an optional header and footer, +and it retains most of the headers of the original messages. + +<p> +The second type is called ``plaintext'' digests because they are +readable in mail readers that don't support MIME. Actually, they +adhere to the <a class="rfc" id='rfcref-1080' xml:id='rfcref-1080' +href="http://www.faqs.org/rfcs/rfc1153.html">RFC 1153</a> digest standard. The retain some, but not +all of the original messages, but can also include a summary and +headers and footers. + +<p> +Like non-digest delivery, you can enable or disable digest delivery, +but you cannot disable both types of delivery. You can specify +different headers and footers for digest and non-digest deliveries. +You cannot personalize digest deliveries. + +<p> +As list administrator, you may want to send an urgent message to all +list members, bypassing the normal digest bundling. To do this, send +the message with a <span class="mailheader">Urgent:</span> header, where the value of the +header is the list administrator's password. Non-digest members will +receive the message like normal, but digest members will receive the +message immediately<a name="tex2html7" + href="#foot182"><sup>5</sup></a>. + +<p> +Here are the variables which control digest delivery: + +<p> +<dl> +<dt><strong>digestable</strong></dt> +<dd>The option controls whether members can receive digest deliveries + or not. If not, they will be forced to receive immediate + deliveries. You can't disable digests if non-digests are already + disabled. + +<p> +</dd> +<dt><strong>digest_is_default</strong></dt> +<dd>Controls which style of delivery is the default for new members. + You can choose <em>Regular</em> (non-digest) or <em>Digest</em> + delivery. + +<p> +</dd> +<dt><strong>mime_is_default_digest</strong></dt> +<dd>If a member is allowed to choose digests, this variable controls + which is the default digest style they will receive. <em>Plain</em> + digests are <a class="rfc" id='rfcref-1082' xml:id='rfcref-1082' +href="http://www.faqs.org/rfcs/rfc1153.html">RFC 1153</a> format as described above. + +<p> +</dd> +<dt><strong>digest_size_threshold</strong></dt> +<dd>Normally, digest members get at least one message per day, if + there have been any messages posted to the list. However, for + high volume lists, you may want to send out digests when the size + has reached a certain threshold, otherwise, the one digest they + receive could be huge. This variable controls the size threshold + by specifying the maximum digest size in kilobytes. Note that + this threshold isn't exact. Set this variable to zero to specify + that there is no size threshold, in which case no more than one + digest will be sent out per day. + +<p> +</dd> +<dt><strong>digest_send_periodic</strong></dt> +<dd>This variable actually controls whether or not a digest is sent + daily when the size threshold has not yet been met. If set to + <em>No</em>, then digests will only be sent when they are bigger + than <code>digest_size_threshold</code>. + +<p> +</dd> +<dt><strong>digest_header</strong></dt> +<dd>This text box lets you enter information that will be included in + the header of every digest message sent through the list. The + same information can go in this header as can go in the + <code>msg_header</code>, except for the personalization variables. + +<p> +</dd> +<dt><strong>digest_footer</strong></dt> +<dd>Just like with the header, you can add a footer to every message. + The same rules apply to digest footers as apply to digest headers. + +<p> +</dd> +<dt><strong>digest_volume_frequency</strong></dt> +<dd>Each digest is numbered with a volume and an issue. This variable + controls how often a new digest volume is sent. When the digest + volume number is incremented, the issue number is reset to 1. + +<p> +</dd> +<dt><strong>_new_volume</strong></dt> +<dd>This is an action variable, which forces an increment of the + volume number as soon as you submit the form. + +<p> +</dd> +<dt><strong>_send_digest_now</strong></dt> +<dd>This is another action variable. Select <em>Yes</em>, submit the + form, and the current digest is packaged up and sent to digest + members, regardless of size (well, there has to be at least one + message in the digest). +</dd> +</dl> + +<p> +<br><hr><h4>Footnotes</h4> +<dl> +<dt><a name="foot182">... immediately</a><A + HREF="node19.html#tex2html7"><sup>5</sup></a></dt> +<dd>They'll also receive the message in the +digest. + +</dd> +</dl> +<div class="navigation"> +<div class='online-navigation'> +<p></p><hr /> +<table align="center" width="100%" cellpadding="0" cellspacing="2"> +<tr> +<td class='online-navigation'><a rel="prev" title="2.5 the Non-digest Options" + href="node18.html"><img src='previous.png' + border='0' height='32' alt='Previous Page' width='32' /></a></td> +<td class='online-navigation'><a rel="parent" title="2 the List Configuration" + href="node8.html"><img src='up.png' + border='0' height='32' alt='Up one Level' width='32' /></a></td> +<td class='online-navigation'><a rel="next" title="2.7 the Privacy Options" + href="node20.html"><img src='next.png' + border='0' height='32' alt='Next Page' width='32' /></a></td> +<td align="center" width="100%">GNU Mailman - List Administration Manual</td> +<td class='online-navigation'><a rel="contents" title="Table of Contents" + href="contents.html"><img src='contents.png' + border='0' height='32' alt='Contents' width='32' /></a></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +</tr></table> +<div class='online-navigation'> +<b class="navlabel">Previous:</b> +<a class="sectref" rel="prev" href="node18.html">2.5 The Non-digest Options</a> +<b class="navlabel">Up:</b> +<a class="sectref" rel="parent" href="node8.html">2 The List Configuration</a> +<b class="navlabel">Next:</b> +<a class="sectref" rel="next" href="node20.html">2.7 The Privacy Options</a> +</div> +</div> +<hr /> +<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +</div> +<!--End of Navigation Panel--> + +</body> +</html> diff --git a/doc/mailman-admin/node20.html b/doc/mailman-admin/node20.html new file mode 100644 index 00000000..5205808d --- /dev/null +++ b/doc/mailman-admin/node20.html @@ -0,0 +1,179 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> +<html> +<head> +<link rel="STYLESHEET" href="mailman-admin.css" type='text/css' /> +<link rel="first" href="mailman-admin.html" title='GNU mailman - list Administration Manual' /> +<link rel='contents' href='contents.html' title="Contents" /> +<link rel='last' href='about.html' title='About this document...' /> +<link rel='help' href='about.html' title='About this document...' /> +<link rel="next" href="node25.html" /> +<link rel="prev" href="node19.html" /> +<link rel="parent" href="node8.html" /> +<link rel="next" href="node21.html" /> +<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> +<meta name='aesop' content='information' /> +<title>2.7 The Privacy Options Category</title> +</head> +<body> +<div class="navigation"> +<div id='top-navigation-panel' xml:id='top-navigation-panel'> +<table align="center" width="100%" cellpadding="0" cellspacing="2"> +<tr> +<td class='online-navigation'><a rel="prev" title="2.6 the Digest Options" + href="node19.html"><img src='previous.png' + border='0' height='32' alt='Previous Page' width='32' /></a></td> +<td class='online-navigation'><a rel="parent" title="2 the List Configuration" + href="node8.html"><img src='up.png' + border='0' height='32' alt='Up one Level' width='32' /></a></td> +<td class='online-navigation'><a rel="next" title="2.7.1 subscription rules" + href="node21.html"><img src='next.png' + border='0' height='32' alt='Next Page' width='32' /></a></td> +<td align="center" width="100%">GNU Mailman - List Administration Manual</td> +<td class='online-navigation'><a rel="contents" title="Table of Contents" + href="contents.html"><img src='contents.png' + border='0' height='32' alt='Contents' width='32' /></a></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +</tr></table> +<div class='online-navigation'> +<b class="navlabel">Previous:</b> +<a class="sectref" rel="prev" href="node19.html">2.6 The Digest Options</a> +<b class="navlabel">Up:</b> +<a class="sectref" rel="parent" href="node8.html">2 The List Configuration</a> +<b class="navlabel">Next:</b> +<a class="sectref" rel="next" href="node21.html">2.7.1 Subscription rules</a> +</div> +<hr /></div> +</div> +<!--End of Navigation Panel--> + +<h2><a name="SECTION002270000000000000000"> +2.7 The Privacy Options Category</a> +</h2> + +<p> +The Privacy category lets you control how much of the list's +information is public, as well as who can send messages to your list. +It also contains some spam detection filters. Note that this section +is not used to control whether your list's archives are public or +private; for that, use the <a href="#Archiving_options"><tex2html_cross_ref_visible_mark></a> category. + +<p> +There are four sub-categories: + +<ul> +<li>Subscription rules - i.e. the rules for joining and leaving + your mailing list + +<p> +</li> +<li>Sender filters - the rules for who may post messages to your + list + +<p> +</li> +<li>Recipient filters - moderation rules based on the recipient of + the message + +<p> +</li> +<li>Spam filters - some regular expression based rules for header + matching +</li> +</ul> + +<p> +The sender, recipient, and spam filtering rules are part of the +general list moderation features of Mailman. When a message is posted +to the list, it is matched against a number of criteria, the outcome +of which determines whether the message is reflected to the membership +or not. In general, the outcome is one of four states: + +<p> + +<ul> +<li>Approved or Accepted - the message may be sent on to the + members of the mailing list. + +<p> +</li> +<li>Hold - the message will be held for moderator approval. The + list owners and moderators will then have to explicitly approve + the message before the list members will see it. + +<p> +</li> +<li>Reject - the message is bounced back to the original sender, + often with a notice containing the reason the message was + rejected. The list members never see rejected messages. + +<p> +</li> +<li>Discard - the message is simply thrown away without further + processing. +</li> +</ul> + +<p> +Many of the fields in this section are text boxes accepting addresses, +one per line. Unless otherwise noted, these also accept regular +expressions which will be matched against an address, if the line +begins with a (caret) character. + +<p> + +<p><br /></p><hr class='online-navigation' /> +<div class='online-navigation'> +<!--Table of Child-Links--> +<a name="CHILD_LINKS"><strong>Subsections</strong></a> + +<ul class="ChildLinks"> +<li><a href="node21.html">2.7.1 Subscription rules</a> +<li><a href="node22.html">2.7.2 Sender filters</a> +<li><a href="node23.html">2.7.3 Recipient Filters</a> +<li><a href="node24.html">2.7.4 Spam Filters</a> +</ul> +<!--End of Table of Child-Links--> +</div> + +<div class="navigation"> +<div class='online-navigation'> +<p></p><hr /> +<table align="center" width="100%" cellpadding="0" cellspacing="2"> +<tr> +<td class='online-navigation'><a rel="prev" title="2.6 the Digest Options" + href="node19.html"><img src='previous.png' + border='0' height='32' alt='Previous Page' width='32' /></a></td> +<td class='online-navigation'><a rel="parent" title="2 the List Configuration" + href="node8.html"><img src='up.png' + border='0' height='32' alt='Up one Level' width='32' /></a></td> +<td class='online-navigation'><a rel="next" title="2.7.1 subscription rules" + href="node21.html"><img src='next.png' + border='0' height='32' alt='Next Page' width='32' /></a></td> +<td align="center" width="100%">GNU Mailman - List Administration Manual</td> +<td class='online-navigation'><a rel="contents" title="Table of Contents" + href="contents.html"><img src='contents.png' + border='0' height='32' alt='Contents' width='32' /></a></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +</tr></table> +<div class='online-navigation'> +<b class="navlabel">Previous:</b> +<a class="sectref" rel="prev" href="node19.html">2.6 The Digest Options</a> +<b class="navlabel">Up:</b> +<a class="sectref" rel="parent" href="node8.html">2 The List Configuration</a> +<b class="navlabel">Next:</b> +<a class="sectref" rel="next" href="node21.html">2.7.1 Subscription rules</a> +</div> +</div> +<hr /> +<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +</div> +<!--End of Navigation Panel--> + +</body> +</html> diff --git a/doc/mailman-admin/node21.html b/doc/mailman-admin/node21.html new file mode 100644 index 00000000..0db2153a --- /dev/null +++ b/doc/mailman-admin/node21.html @@ -0,0 +1,204 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> +<html> +<head> +<link rel="STYLESHEET" href="mailman-admin.css" type='text/css' /> +<link rel="first" href="mailman-admin.html" title='GNU mailman - list Administration Manual' /> +<link rel='contents' href='contents.html' title="Contents" /> +<link rel='last' href='about.html' title='About this document...' /> +<link rel='help' href='about.html' title='About this document...' /> +<link rel="next" href="node22.html" /> +<link rel="prev" href="node20.html" /> +<link rel="parent" href="node20.html" /> +<link rel="next" href="node22.html" /> +<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> +<meta name='aesop' content='information' /> +<title>2.7.1 Subscription rules</title> +</head> +<body> +<div class="navigation"> +<div id='top-navigation-panel' xml:id='top-navigation-panel'> +<table align="center" width="100%" cellpadding="0" cellspacing="2"> +<tr> +<td class='online-navigation'><a rel="prev" title="2.7 the Privacy Options" + href="node20.html"><img src='previous.png' + border='0' height='32' alt='Previous Page' width='32' /></a></td> +<td class='online-navigation'><a rel="parent" title="2.7 the Privacy Options" + href="node20.html"><img src='up.png' + border='0' height='32' alt='Up one Level' width='32' /></a></td> +<td class='online-navigation'><a rel="next" title="2.7.2 sender filters" + href="node22.html"><img src='next.png' + border='0' height='32' alt='Next Page' width='32' /></a></td> +<td align="center" width="100%">GNU Mailman - List Administration Manual</td> +<td class='online-navigation'><a rel="contents" title="Table of Contents" + href="contents.html"><img src='contents.png' + border='0' height='32' alt='Contents' width='32' /></a></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +</tr></table> +<div class='online-navigation'> +<b class="navlabel">Previous:</b> +<a class="sectref" rel="prev" href="node20.html">2.7 The Privacy Options</a> +<b class="navlabel">Up:</b> +<a class="sectref" rel="parent" href="node20.html">2.7 The Privacy Options</a> +<b class="navlabel">Next:</b> +<a class="sectref" rel="next" href="node22.html">2.7.2 Sender filters</a> +</div> +<hr /></div> +</div> +<!--End of Navigation Panel--> + +<h3><a name="SECTION002271000000000000000"> +2.7.1 Subscription rules</a> +</h3> + +<p> +This subcategory controls the rules for exposing the existance of this +list, and for what new members must do in order to subscribe to the +list. + +<p> +<dl> +<dt><strong>advertised</strong></dt> +<dd>This option controls whether this list will show up in the list + overview for the site. Normally, an overview contains the name + and short description of every mailing list in the virtual + domain. By setting this variable to <em>No</em>, it will not show + up in this overview, nor will it show up in the administrative + overview. The only way then to find the list is to guess (or + know!) its name. + +<p> +</dd> +<dt><strong>subscribe_policy</strong></dt> +<dd>This option controls the steps that a new member must take to join + the list. The available options may differ based on some defaults + that the site administrator chooses. They are: + +<p> + +<ul> +<li>None - No verification is done on the subscribing + member. This is also called <em>open subscriptions</em> and is + generally disabled by default. The site administrator must + allow list admins to choose this option; if not, this option + will not be presented to you. + +<p> +</li> +<li>Confirm - An email confirmation step is required before the + address is added to the list. When a member requests + subscription, either via the web page or by sending a + message to <var>yourlist</var><code>-join@example.com</code>, Mailman + will send a confirmation message to the requesting address. + This mail-back confirmation contains a unique identifier, + which the requester can present to Mailman in order to + confirm their subscription. This can be done either by + replying to the mail-back, or by visiting the url in the + mail-back message. The url points to a page that lets the + user either discard or confirm their request. + +<p> +</li> +<li>Require approval - All subscription requests are held for + approval of the list moderator. No mail-back confirmation + is sent, but the list admins will recieve a message + indicating that approval is pending. + +<p> +</li> +<li>Confirm and approve - Here, a mail-back notice must first + be confirmed by the requester. Once confirmed, the list + moderator must then approve the request. This is the most + secure method for users to subscribe since it both verifies + the requesting address, and forces the list moderators to + approve the request. + +<p> +</li> +</ul> + +<p> +</dd> +<dt><strong>unsubscribe_policy</strong></dt> +<dd>Specifies whether the list moderator's approval is required for + unsubscription requests. <em>No</em> is highly recommended, since + it is exceedingly impolite to not allow people to leave a mailing + list whenever they want (i.e. opt-out). <em>Yes</em> is useful in + some specialized contexts; e.g. you may not want to allow + employees to unsubscribe from the company newsletter. + +<p> +</dd> +<dt><strong>ban_list</strong></dt> +<dd>This contains a list of addresses (or regular expressiosn), one + per line, that are banned from ever subscribing to your mailing + list. If a match occurs during the subscription process, the + request will be automatically rejected, and the requester will get + a rejection notice. You can use this to permanently ban + troublesome posters to a members-only list. + +<p> +</dd> +<dt><strong>private_roster</strong></dt> +<dd>This specifies who is allowed to view the roster of member + addresses. If you choose <em>Anyone</em>, then the list membership + is completely public. You can limit exposure of the roster to + just list members, or just to the list administrators. In the + former case, a user must enter a valid member's address and + password before they can view the roster. In the latter case, a + list administrator's password must be enter; if a matching admin + password is entered, address field is ignored. + +<p> +</dd> +<dt><strong>obscure_addresses</strong></dt> +<dd>Controls whether some simple obfuscation of addresses is used when + member addresses are included on web pages. This should reduce + the opportunity for email address harvesting by spammers, although + it probably doesn't eliminate it. +</dd> +</dl> + +<p> + +<div class="navigation"> +<div class='online-navigation'> +<p></p><hr /> +<table align="center" width="100%" cellpadding="0" cellspacing="2"> +<tr> +<td class='online-navigation'><a rel="prev" title="2.7 the Privacy Options" + href="node20.html"><img src='previous.png' + border='0' height='32' alt='Previous Page' width='32' /></a></td> +<td class='online-navigation'><a rel="parent" title="2.7 the Privacy Options" + href="node20.html"><img src='up.png' + border='0' height='32' alt='Up one Level' width='32' /></a></td> +<td class='online-navigation'><a rel="next" title="2.7.2 sender filters" + href="node22.html"><img src='next.png' + border='0' height='32' alt='Next Page' width='32' /></a></td> +<td align="center" width="100%">GNU Mailman - List Administration Manual</td> +<td class='online-navigation'><a rel="contents" title="Table of Contents" + href="contents.html"><img src='contents.png' + border='0' height='32' alt='Contents' width='32' /></a></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +</tr></table> +<div class='online-navigation'> +<b class="navlabel">Previous:</b> +<a class="sectref" rel="prev" href="node20.html">2.7 The Privacy Options</a> +<b class="navlabel">Up:</b> +<a class="sectref" rel="parent" href="node20.html">2.7 The Privacy Options</a> +<b class="navlabel">Next:</b> +<a class="sectref" rel="next" href="node22.html">2.7.2 Sender filters</a> +</div> +</div> +<hr /> +<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +</div> +<!--End of Navigation Panel--> + +</body> +</html> diff --git a/doc/mailman-admin/node22.html b/doc/mailman-admin/node22.html new file mode 100644 index 00000000..62bbe43f --- /dev/null +++ b/doc/mailman-admin/node22.html @@ -0,0 +1,215 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> +<html> +<head> +<link rel="STYLESHEET" href="mailman-admin.css" type='text/css' /> +<link rel="first" href="mailman-admin.html" title='GNU mailman - list Administration Manual' /> +<link rel='contents' href='contents.html' title="Contents" /> +<link rel='last' href='about.html' title='About this document...' /> +<link rel='help' href='about.html' title='About this document...' /> +<link rel="next" href="node23.html" /> +<link rel="prev" href="node21.html" /> +<link rel="parent" href="node20.html" /> +<link rel="next" href="node23.html" /> +<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> +<meta name='aesop' content='information' /> +<title>2.7.2 Sender filters</title> +</head> +<body> +<div class="navigation"> +<div id='top-navigation-panel' xml:id='top-navigation-panel'> +<table align="center" width="100%" cellpadding="0" cellspacing="2"> +<tr> +<td class='online-navigation'><a rel="prev" title="2.7.1 subscription rules" + href="node21.html"><img src='previous.png' + border='0' height='32' alt='Previous Page' width='32' /></a></td> +<td class='online-navigation'><a rel="parent" title="2.7 the Privacy Options" + href="node20.html"><img src='up.png' + border='0' height='32' alt='Up one Level' width='32' /></a></td> +<td class='online-navigation'><a rel="next" title="2.7.3 recipient Filters" + href="node23.html"><img src='next.png' + border='0' height='32' alt='Next Page' width='32' /></a></td> +<td align="center" width="100%">GNU Mailman - List Administration Manual</td> +<td class='online-navigation'><a rel="contents" title="Table of Contents" + href="contents.html"><img src='contents.png' + border='0' height='32' alt='Contents' width='32' /></a></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +</tr></table> +<div class='online-navigation'> +<b class="navlabel">Previous:</b> +<a class="sectref" rel="prev" href="node21.html">2.7.1 Subscription rules</a> +<b class="navlabel">Up:</b> +<a class="sectref" rel="parent" href="node20.html">2.7 The Privacy Options</a> +<b class="navlabel">Next:</b> +<a class="sectref" rel="next" href="node23.html">2.7.3 Recipient Filters</a> +</div> +<hr /></div> +</div> +<!--End of Navigation Panel--> + +<h3><a name="SECTION002272000000000000000"> +2.7.2 Sender filters</a> +</h3> + +<p> +When a message is posted to the list, a series of moderation criteria are +applied to determine the disposition of the message. This section +contains the modeation controls for postings from both members and +non-members. + +<p> +<dl> +<dt><strong>default_member_moderation</strong></dt> +<dd>Member postings are held for moderation if their <em>moderation + flag</em> is turned on. Note that only the list administrators can + change the value of a member's moderation flag. + +<p> +You can control whether new members get their moderation flag + turned on or off by default when they subscribe to the list. By + turning this flag off by default, postings by members will be + allowed without further intervention (barring other restrictions + such as size or implicit recipient lists - see below). By + turning the flag on, you can quarantine new member postings to + make sure that they meet your criteria for netiquette, topicality, + etc. Once you determine that the new member understands the + community's posting rules, you can turn off their moderation flag + and let their postings go through unstopped. + +<p> +E-newsletter style lists can also be set up by using the + moderation flag. By setting the <code>member_moderation_action</code> + to <em>Reject</em>, and by turning off the moderation flag for just + the few approved senders, your list will operate in essentially a + one-way direction. Note that you'd also need to reject or discard + postings from non-members. + +<p> +</dd> +<dt><strong>member_moderation_action</strong></dt> +<dd>This is the action to take for postings from a member who's + moderation flag is set. For typical discussion lists, you'll + likely set this to <em>Hold</em> so that the list moderator will get + a chance to manually approve, reject, or discard the message. For + e-newsletter and announcement lists, you might want to set this to + <em>Reject</em> or <em>Discard</em>. + +<p> +Note that when a moderated member posts to your list, and the + <code>member_moderation_action</code> is set to <em>Hold</em>, the message + will appear on the administrative requests page. When you dispose + of the message, you will be given an opportunity to clear the + moderation flag at the same time. If you're quarantining new + posts, this makes it very convenient to both approve a new + member's post and de-moderate them at the same time. + +<p> +</dd> +<dt><strong>member_moderation_notice</strong></dt> +<dd>When a member's moderation flag is turned on and + <code>member_moderation_action</code> is <em>Reject</em>, this variable + contains the text sent in the rejection notice. +</dd> +</dl> + +<p> +The next batch of variables controls what happens when non-members +post messages to the list. Each of these accepts one email address +per line; regular expressions are allowed if the line starts with the +(caret) character. These address lists are always consulted in the +order in which they're presented on this page (i.e. accepts first, +followed by holds, rejections, and discards). + +<p> +<dl> +<dt><strong>accept_these_nonmembers</strong></dt> +<dd>Postings from non-members whose addresses match this list are + accepted, barring other list restrictions due to size, implicit + recipients, etc. You might want to add alternative addresses of + approved posters to this list. + +<p> +</dd> +<dt><strong>hold_these_nonmembers</strong></dt> +<dd>Postings from non-members whose addresses match this list are + held for moderator approval. + +<p> +</dd> +<dt><strong>reject_these_nonmembers</strong></dt> +<dd>Postings from non-members whose addresses match this list are + rejected, i.e. bounced back to the original sender. There + currently is no way to add additional text to the rejection + message. + +<p> +</dd> +<dt><strong>discard_these_nonmembers</strong></dt> +<dd>Postings from non-members whose addresses match this list are + discarded, with no bounce back message. You might want to add the + addresses of known spammers to this list. + +<p> +</dd> +<dt><strong>generic_nonmember_action</strong></dt> +<dd>This variable controls what happens to non-member posts when the + address of the sender doesn't match any of the above four lists. + If you set this to <em>Hold</em>, the posting will appear on the + administrative requests page, and you will be given an opportunity + to add the non-member to one of the above four lists at the same + time you dispose of the held message. + +<p> +</dd> +<dt><strong>forward_auto_discards</strong></dt> +<dd>When messages from non-members are discarded, either because the + sender address matched <code>discard_these_nonmembers</code>, or because + <code>generic_nonmember_action</code> is <em>Discard</em>, you can choose + whether such messages are forwarded to the lsit administrators or + not. +</dd> +</dl> + +<p> + +<div class="navigation"> +<div class='online-navigation'> +<p></p><hr /> +<table align="center" width="100%" cellpadding="0" cellspacing="2"> +<tr> +<td class='online-navigation'><a rel="prev" title="2.7.1 subscription rules" + href="node21.html"><img src='previous.png' + border='0' height='32' alt='Previous Page' width='32' /></a></td> +<td class='online-navigation'><a rel="parent" title="2.7 the Privacy Options" + href="node20.html"><img src='up.png' + border='0' height='32' alt='Up one Level' width='32' /></a></td> +<td class='online-navigation'><a rel="next" title="2.7.3 recipient Filters" + href="node23.html"><img src='next.png' + border='0' height='32' alt='Next Page' width='32' /></a></td> +<td align="center" width="100%">GNU Mailman - List Administration Manual</td> +<td class='online-navigation'><a rel="contents" title="Table of Contents" + href="contents.html"><img src='contents.png' + border='0' height='32' alt='Contents' width='32' /></a></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +</tr></table> +<div class='online-navigation'> +<b class="navlabel">Previous:</b> +<a class="sectref" rel="prev" href="node21.html">2.7.1 Subscription rules</a> +<b class="navlabel">Up:</b> +<a class="sectref" rel="parent" href="node20.html">2.7 The Privacy Options</a> +<b class="navlabel">Next:</b> +<a class="sectref" rel="next" href="node23.html">2.7.3 Recipient Filters</a> +</div> +</div> +<hr /> +<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +</div> +<!--End of Navigation Panel--> + +</body> +</html> diff --git a/doc/mailman-admin/node23.html b/doc/mailman-admin/node23.html new file mode 100644 index 00000000..eb6ab6c1 --- /dev/null +++ b/doc/mailman-admin/node23.html @@ -0,0 +1,133 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> +<html> +<head> +<link rel="STYLESHEET" href="mailman-admin.css" type='text/css' /> +<link rel="first" href="mailman-admin.html" title='GNU mailman - list Administration Manual' /> +<link rel='contents' href='contents.html' title="Contents" /> +<link rel='last' href='about.html' title='About this document...' /> +<link rel='help' href='about.html' title='About this document...' /> +<link rel="next" href="node24.html" /> +<link rel="prev" href="node22.html" /> +<link rel="parent" href="node20.html" /> +<link rel="next" href="node24.html" /> +<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> +<meta name='aesop' content='information' /> +<title>2.7.3 Recipient Filters</title> +</head> +<body> +<div class="navigation"> +<div id='top-navigation-panel' xml:id='top-navigation-panel'> +<table align="center" width="100%" cellpadding="0" cellspacing="2"> +<tr> +<td class='online-navigation'><a rel="prev" title="2.7.2 sender filters" + href="node22.html"><img src='previous.png' + border='0' height='32' alt='Previous Page' width='32' /></a></td> +<td class='online-navigation'><a rel="parent" title="2.7 the Privacy Options" + href="node20.html"><img src='up.png' + border='0' height='32' alt='Up one Level' width='32' /></a></td> +<td class='online-navigation'><a rel="next" title="2.7.4 spam Filters" + href="node24.html"><img src='next.png' + border='0' height='32' alt='Next Page' width='32' /></a></td> +<td align="center" width="100%">GNU Mailman - List Administration Manual</td> +<td class='online-navigation'><a rel="contents" title="Table of Contents" + href="contents.html"><img src='contents.png' + border='0' height='32' alt='Contents' width='32' /></a></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +</tr></table> +<div class='online-navigation'> +<b class="navlabel">Previous:</b> +<a class="sectref" rel="prev" href="node22.html">2.7.2 Sender filters</a> +<b class="navlabel">Up:</b> +<a class="sectref" rel="parent" href="node20.html">2.7 The Privacy Options</a> +<b class="navlabel">Next:</b> +<a class="sectref" rel="next" href="node24.html">2.7.4 Spam Filters</a> +</div> +<hr /></div> +</div> +<!--End of Navigation Panel--> + +<h3><a name="SECTION002273000000000000000"> +2.7.3 Recipient Filters</a> +</h3> + +<p> +The variables in this section control various filters based on the +recipient of the message. + +<p> +<dl> +<dt><strong>require_explicit_destination</strong></dt> +<dd>This controls whether the mailing list posting address must be + explicitly named in the <span class="mailheader">To:</span> or <span class="mailheader">Cc:</span> + recipient lists. The main reason why it wouldn't is if the + message was blind-carbon-copied (i.e. <span class="mailheader">Bcc:</span>'d) to the + list. Spammers like to do this, but sometimes legitimate messages + are forwarded to the list this way. + +<p> +If the list is not explicitly addressed and this setting is turned + on, the message will be held for moderator approval. + +<p> +</dd> +<dt><strong>acceptable_aliases</strong></dt> +<dd>This is the list of alternative addresses that are acceptable as a + list posting address when <code>require_explicit_destination</code> is + enabled. This is useful for when there aliases for the main + posting address (e.g. <code>help@example.com</code> may be an alias for + <code>help-list@example.com</code>). + +<p> +</dd> +<dt><strong>max_num_recipients</strong></dt> +<dd>This is the maximum number of explicit recipients that are allowed + on the posted message. Spammers sometimes send messages with lots + of explicit recipients, so setting this number to a reasonable + value may cut down on spam. +</dd> +</dl> + +<p> + +<div class="navigation"> +<div class='online-navigation'> +<p></p><hr /> +<table align="center" width="100%" cellpadding="0" cellspacing="2"> +<tr> +<td class='online-navigation'><a rel="prev" title="2.7.2 sender filters" + href="node22.html"><img src='previous.png' + border='0' height='32' alt='Previous Page' width='32' /></a></td> +<td class='online-navigation'><a rel="parent" title="2.7 the Privacy Options" + href="node20.html"><img src='up.png' + border='0' height='32' alt='Up one Level' width='32' /></a></td> +<td class='online-navigation'><a rel="next" title="2.7.4 spam Filters" + href="node24.html"><img src='next.png' + border='0' height='32' alt='Next Page' width='32' /></a></td> +<td align="center" width="100%">GNU Mailman - List Administration Manual</td> +<td class='online-navigation'><a rel="contents" title="Table of Contents" + href="contents.html"><img src='contents.png' + border='0' height='32' alt='Contents' width='32' /></a></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +</tr></table> +<div class='online-navigation'> +<b class="navlabel">Previous:</b> +<a class="sectref" rel="prev" href="node22.html">2.7.2 Sender filters</a> +<b class="navlabel">Up:</b> +<a class="sectref" rel="parent" href="node20.html">2.7 The Privacy Options</a> +<b class="navlabel">Next:</b> +<a class="sectref" rel="next" href="node24.html">2.7.4 Spam Filters</a> +</div> +</div> +<hr /> +<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +</div> +<!--End of Navigation Panel--> + +</body> +</html> diff --git a/doc/mailman-admin/node24.html b/doc/mailman-admin/node24.html new file mode 100644 index 00000000..49951ddf --- /dev/null +++ b/doc/mailman-admin/node24.html @@ -0,0 +1,131 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> +<html> +<head> +<link rel="STYLESHEET" href="mailman-admin.css" type='text/css' /> +<link rel="first" href="mailman-admin.html" title='GNU mailman - list Administration Manual' /> +<link rel='contents' href='contents.html' title="Contents" /> +<link rel='last' href='about.html' title='About this document...' /> +<link rel='help' href='about.html' title='About this document...' /> +<link rel="prev" href="node23.html" /> +<link rel="parent" href="node20.html" /> +<link rel="next" href="node25.html" /> +<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> +<meta name='aesop' content='information' /> +<title>2.7.4 Spam Filters</title> +</head> +<body> +<div class="navigation"> +<div id='top-navigation-panel' xml:id='top-navigation-panel'> +<table align="center" width="100%" cellpadding="0" cellspacing="2"> +<tr> +<td class='online-navigation'><a rel="prev" title="2.7.3 recipient Filters" + href="node23.html"><img src='previous.png' + border='0' height='32' alt='Previous Page' width='32' /></a></td> +<td class='online-navigation'><a rel="parent" title="2.7 the Privacy Options" + href="node20.html"><img src='up.png' + border='0' height='32' alt='Up one Level' width='32' /></a></td> +<td class='online-navigation'><a rel="next" title="2.8 the Bounce Processing" + href="node25.html"><img src='next.png' + border='0' height='32' alt='Next Page' width='32' /></a></td> +<td align="center" width="100%">GNU Mailman - List Administration Manual</td> +<td class='online-navigation'><a rel="contents" title="Table of Contents" + href="contents.html"><img src='contents.png' + border='0' height='32' alt='Contents' width='32' /></a></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +</tr></table> +<div class='online-navigation'> +<b class="navlabel">Previous:</b> +<a class="sectref" rel="prev" href="node23.html">2.7.3 Recipient Filters</a> +<b class="navlabel">Up:</b> +<a class="sectref" rel="parent" href="node20.html">2.7 The Privacy Options</a> +<b class="navlabel">Next:</b> +<a class="sectref" rel="next" href="node25.html">2.8 The Bounce Processing</a> +</div> +<hr /></div> +</div> +<!--End of Navigation Panel--> + +<h3><a name="SECTION002274000000000000000"> +2.7.4 Spam Filters</a> +</h3> + +<p> +This section provides some adjuncts to spam fighting tools; it +doesn't replace dedicated anti-spam tools such as SpamAssassin or +Spambayes. + +<p> +<dl> +<dt><strong>bounce_matching_headers</strong></dt> +<dd>This variable contains header regular expressions, one per line, + and if any of a message's headers matches one of these patterns, + it will be held for moderation. The format is a colon separated + header and value, where the header is case insensitive and the + value is any valid Python regular expression. Lines that start + with # are ignored. + +<p> +This variable can be used to catch known spammers by writing + regexps that match against <span class="mailheader">To:</span> or <span class="mailheader">Cc:</span> + lines, or known-bad <span class="mailheader">Message-ID:</span>s. Perhaps more useful + though are patterns that match headers added by spam detection + tools higher up in the tool chain. For example, you might + configure SpamAssassin to add an <span class="mailheader">X-Spam-Score:</span> header + with between zero and 5 stars depending on the spam score. Then + you can add a line to this variable like: + +<p> +<div class="verbatim"><pre> + X-Spam-Score: [*]{3,5} +</pre></div> + +<p> +This line will match from 3 to 5 stars in the value of this + field. +</dd> +</dl> + +<p> + +<div class="navigation"> +<div class='online-navigation'> +<p></p><hr /> +<table align="center" width="100%" cellpadding="0" cellspacing="2"> +<tr> +<td class='online-navigation'><a rel="prev" title="2.7.3 recipient Filters" + href="node23.html"><img src='previous.png' + border='0' height='32' alt='Previous Page' width='32' /></a></td> +<td class='online-navigation'><a rel="parent" title="2.7 the Privacy Options" + href="node20.html"><img src='up.png' + border='0' height='32' alt='Up one Level' width='32' /></a></td> +<td class='online-navigation'><a rel="next" title="2.8 the Bounce Processing" + href="node25.html"><img src='next.png' + border='0' height='32' alt='Next Page' width='32' /></a></td> +<td align="center" width="100%">GNU Mailman - List Administration Manual</td> +<td class='online-navigation'><a rel="contents" title="Table of Contents" + href="contents.html"><img src='contents.png' + border='0' height='32' alt='Contents' width='32' /></a></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +</tr></table> +<div class='online-navigation'> +<b class="navlabel">Previous:</b> +<a class="sectref" rel="prev" href="node23.html">2.7.3 Recipient Filters</a> +<b class="navlabel">Up:</b> +<a class="sectref" rel="parent" href="node20.html">2.7 The Privacy Options</a> +<b class="navlabel">Next:</b> +<a class="sectref" rel="next" href="node25.html">2.8 The Bounce Processing</a> +</div> +</div> +<hr /> +<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +</div> +<!--End of Navigation Panel--> + +</body> +</html> diff --git a/doc/mailman-admin/node25.html b/doc/mailman-admin/node25.html new file mode 100644 index 00000000..48a42e3a --- /dev/null +++ b/doc/mailman-admin/node25.html @@ -0,0 +1,196 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> +<html> +<head> +<link rel="STYLESHEET" href="mailman-admin.css" type='text/css' /> +<link rel="first" href="mailman-admin.html" title='GNU mailman - list Administration Manual' /> +<link rel='contents' href='contents.html' title="Contents" /> +<link rel='last' href='about.html' title='About this document...' /> +<link rel='help' href='about.html' title='About this document...' /> +<link rel="next" href="node26.html" /> +<link rel="prev" href="node20.html" /> +<link rel="parent" href="node8.html" /> +<link rel="next" href="node26.html" /> +<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> +<meta name='aesop' content='information' /> +<title>2.8 The Bounce Processing Category</title> +</head> +<body> +<div class="navigation"> +<div id='top-navigation-panel' xml:id='top-navigation-panel'> +<table align="center" width="100%" cellpadding="0" cellspacing="2"> +<tr> +<td class='online-navigation'><a rel="prev" title="2.7.4 spam Filters" + href="node24.html"><img src='previous.png' + border='0' height='32' alt='Previous Page' width='32' /></a></td> +<td class='online-navigation'><a rel="parent" title="2 the List Configuration" + href="node8.html"><img src='up.png' + border='0' height='32' alt='Up one Level' width='32' /></a></td> +<td class='online-navigation'><a rel="next" title="2.9 the Archiving Options" + href="node26.html"><img src='next.png' + border='0' height='32' alt='Next Page' width='32' /></a></td> +<td align="center" width="100%">GNU Mailman - List Administration Manual</td> +<td class='online-navigation'><a rel="contents" title="Table of Contents" + href="contents.html"><img src='contents.png' + border='0' height='32' alt='Contents' width='32' /></a></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +</tr></table> +<div class='online-navigation'> +<b class="navlabel">Previous:</b> +<a class="sectref" rel="prev" href="node24.html">2.7.4 Spam Filters</a> +<b class="navlabel">Up:</b> +<a class="sectref" rel="parent" href="node8.html">2 The List Configuration</a> +<b class="navlabel">Next:</b> +<a class="sectref" rel="next" href="node26.html">2.9 The Archiving Options</a> +</div> +<hr /></div> +</div> +<!--End of Navigation Panel--> + +<h2><a name="SECTION002280000000000000000"> +2.8 The Bounce Processing Category</a> +</h2> + +<p> +These policies control the automatic bounce processing system in +Mailman. Here's an overview of how it works: + +<p> +When a bounce is received, Mailman tries to extract two pieces of +information from the message: the address of the member the message +was intended for, and the severity of the problem causing the bounce. +The severity can be either <em>hard</em> for fatal errors, or +<em>soft</em> for transient errors. When in doubt, a hard severity is +used. + +<p> +If no member address can be extracted from the bounce, then the bounce +message is usually discarded. Every member has a <em>bounce score</em>, +initialized at zero, and every time we encounter a bounce from a +member we increment that member's score. Hard bounces increment by 1 +while soft bounces increment by 0.5. We only increment the bounce +score once per day, so even if we receive ten hard bounces from a +member per day, their score will increase by only 1 for that day. + +<p> +When a member's bounce score is greater than the <em>bounce score +threshold</em> (see below), the member's subscription is disabled. Once +disabled, the member will not receive any postings from the list until +their membership is explicitly re-enabled, either by the list +administrator or the user. However, they will receive occasional +reminders that their membership has been disabled, and these reminders +will include information about how to re-enable their membership. You +can control both the number of reminders the member will receive and +the frequency with which these reminders are sent. + +<p> +There is one other important configuration variable; after a certain +period of time - during which no bounces from the member are received +- the bounce information is considered stale and discarded. Thus by +adjusting this value, and the score threshold, you can control how +quickly bouncing members are disabled. You should tune both of these +to the frequency and traffic volume of your list. + +<p> +<dl> +<dt><strong>bounce_processing</strong></dt> +<dd>Specifies whether or not this list should do automatic bounce + processing. + +<p> +</dd> +<dt><strong>bounce_score_threshold</strong></dt> +<dd>This is the bounce score above which a member's subscription will + be automatically disabled. When the subscription is re-enabled, + their bounce score will be reset to zero. This value can be a + floating point number. + +<p> +</dd> +<dt><strong>bounce_info_stale_after</strong></dt> +<dd>Thenumber of days after which a member's bounce information is + considered stale. If no new bounces have been received in the + interrim, the bounce score is reset to zero. This value must be + an integer. + +<p> +</dd> +<dt><strong>bounce_you_are_disabled_warnings</strong></dt> +<dd>The number of notices a disabled member will receive before their + address is removed from the mailing list's roster. Set this to 0 + to immediately remove an address from the list once their bounce + score exceeds the threshold. This value must be an integer. + +<p> +</dd> +<dt><strong>bounce_you_are_disabled_warnings_interval</strong></dt> +<dd>The number of days between each disabled notification. + +<p> +</dd> +<dt><strong>bounce_unrecognized_goes_to_list_owner</strong></dt> +<dd>This variable controls whether unrecognized bounces are discarded, + or forwarded on the list administrator. The bounce detector isn't + perfect, although personalization can make it much more accurate. + The list owner may want to receive unrecognized bounces so that + they can manually disable or remove such members. + +<p> +</dd> +<dt><strong>bounce_notify_owner_on_disable</strong></dt> +<dd>This option controls whether or not the list owner is notified + when a member's subscription is automatically disabled due to + their bounce threshold being reached. + +<p> +</dd> +<dt><strong>bounce_notify_owner_on_removal</strong></dt> +<dd>This option controls whether or not the list owner is notified + when a member is removed from the list after their disabled + notifications have been exhausted. +</dd> +</dl> + +<p> + +<div class="navigation"> +<div class='online-navigation'> +<p></p><hr /> +<table align="center" width="100%" cellpadding="0" cellspacing="2"> +<tr> +<td class='online-navigation'><a rel="prev" title="2.7.4 spam Filters" + href="node24.html"><img src='previous.png' + border='0' height='32' alt='Previous Page' width='32' /></a></td> +<td class='online-navigation'><a rel="parent" title="2 the List Configuration" + href="node8.html"><img src='up.png' + border='0' height='32' alt='Up one Level' width='32' /></a></td> +<td class='online-navigation'><a rel="next" title="2.9 the Archiving Options" + href="node26.html"><img src='next.png' + border='0' height='32' alt='Next Page' width='32' /></a></td> +<td align="center" width="100%">GNU Mailman - List Administration Manual</td> +<td class='online-navigation'><a rel="contents" title="Table of Contents" + href="contents.html"><img src='contents.png' + border='0' height='32' alt='Contents' width='32' /></a></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +</tr></table> +<div class='online-navigation'> +<b class="navlabel">Previous:</b> +<a class="sectref" rel="prev" href="node24.html">2.7.4 Spam Filters</a> +<b class="navlabel">Up:</b> +<a class="sectref" rel="parent" href="node8.html">2 The List Configuration</a> +<b class="navlabel">Next:</b> +<a class="sectref" rel="next" href="node26.html">2.9 The Archiving Options</a> +</div> +</div> +<hr /> +<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +</div> +<!--End of Navigation Panel--> + +</body> +</html> diff --git a/doc/mailman-admin/node26.html b/doc/mailman-admin/node26.html new file mode 100644 index 00000000..1cb22484 --- /dev/null +++ b/doc/mailman-admin/node26.html @@ -0,0 +1,137 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> +<html> +<head> +<link rel="STYLESHEET" href="mailman-admin.css" type='text/css' /> +<link rel="first" href="mailman-admin.html" title='GNU mailman - list Administration Manual' /> +<link rel='contents' href='contents.html' title="Contents" /> +<link rel='last' href='about.html' title='About this document...' /> +<link rel='help' href='about.html' title='About this document...' /> +<link rel="next" href="node27.html" /> +<link rel="prev" href="node25.html" /> +<link rel="parent" href="node8.html" /> +<link rel="next" href="node27.html" /> +<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> +<meta name='aesop' content='information' /> +<title>2.9 The Archiving Options Category</title> +</head> +<body> +<div class="navigation"> +<div id='top-navigation-panel' xml:id='top-navigation-panel'> +<table align="center" width="100%" cellpadding="0" cellspacing="2"> +<tr> +<td class='online-navigation'><a rel="prev" title="2.8 the Bounce Processing" + href="node25.html"><img src='previous.png' + border='0' height='32' alt='Previous Page' width='32' /></a></td> +<td class='online-navigation'><a rel="parent" title="2 the List Configuration" + href="node8.html"><img src='up.png' + border='0' height='32' alt='Up one Level' width='32' /></a></td> +<td class='online-navigation'><a rel="next" title="2.10 the Mail/News Gateway" + href="node27.html"><img src='next.png' + border='0' height='32' alt='Next Page' width='32' /></a></td> +<td align="center" width="100%">GNU Mailman - List Administration Manual</td> +<td class='online-navigation'><a rel="contents" title="Table of Contents" + href="contents.html"><img src='contents.png' + border='0' height='32' alt='Contents' width='32' /></a></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +</tr></table> +<div class='online-navigation'> +<b class="navlabel">Previous:</b> +<a class="sectref" rel="prev" href="node25.html">2.8 The Bounce Processing</a> +<b class="navlabel">Up:</b> +<a class="sectref" rel="parent" href="node8.html">2 The List Configuration</a> +<b class="navlabel">Next:</b> +<a class="sectref" rel="next" href="node27.html">2.10 The Mail/News Gateway</a> +</div> +<hr /></div> +</div> +<!--End of Navigation Panel--> + +<h2><a name="SECTION002290000000000000000"> +2.9 The Archiving Options Category</a> +</h2> + +<p> +Mailman comes with a built-in web-based archiver called +<em>Pipermail</em>, although it can be configured to use external, +third party archivers. + +<p> +<dl> +<dt><strong>archive</strong></dt> +<dd>This option tells Mailman whether to archive messages it receives + or not, regardless of whether Pipermail or a third party archiver + is used. Turn this off if you don't want to archive messages. + +<p> +Note that senders can control whether their own posts are + archived, on an individual per-message basis. If the posted + message has a <span class="mailheader">X-No-Archive:</span> header (regardless of + value), or a <span class="mailheader">X-Archive:</span> header with a value of + <code>No</code> (case insensitive), then the message will not be + archived, although it will be treated as normal in all other + ways. + +<p> +</dd> +<dt><strong>archive_private</strong></dt> +<dd>Controls whether Pipermail archives are private or public. + Private archives require a valid member address and password, or a + list administrator password in order to access them. This + option has no effect when a third party archiver is used. + +<p> +</dd> +<dt><strong>archive_volume_frequency</strong></dt> +<dd>Controls how Pipermail splits messages in the archive. The most + common option is <em>Monthly</em> meaning a new archive volume is + started every month. Very high volume lists may want a shorter + frequency (e.g. <em>Weekly</em> or <em>Daily</em>) where as lower + volume lists may want a longer frequency (e.g. <em>Yearly</em>). + This option has no effect when a third party archiver is used. +</dd> +</dl> + +<p> + +<div class="navigation"> +<div class='online-navigation'> +<p></p><hr /> +<table align="center" width="100%" cellpadding="0" cellspacing="2"> +<tr> +<td class='online-navigation'><a rel="prev" title="2.8 the Bounce Processing" + href="node25.html"><img src='previous.png' + border='0' height='32' alt='Previous Page' width='32' /></a></td> +<td class='online-navigation'><a rel="parent" title="2 the List Configuration" + href="node8.html"><img src='up.png' + border='0' height='32' alt='Up one Level' width='32' /></a></td> +<td class='online-navigation'><a rel="next" title="2.10 the Mail/News Gateway" + href="node27.html"><img src='next.png' + border='0' height='32' alt='Next Page' width='32' /></a></td> +<td align="center" width="100%">GNU Mailman - List Administration Manual</td> +<td class='online-navigation'><a rel="contents" title="Table of Contents" + href="contents.html"><img src='contents.png' + border='0' height='32' alt='Contents' width='32' /></a></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +</tr></table> +<div class='online-navigation'> +<b class="navlabel">Previous:</b> +<a class="sectref" rel="prev" href="node25.html">2.8 The Bounce Processing</a> +<b class="navlabel">Up:</b> +<a class="sectref" rel="parent" href="node8.html">2 The List Configuration</a> +<b class="navlabel">Next:</b> +<a class="sectref" rel="next" href="node27.html">2.10 The Mail/News Gateway</a> +</div> +</div> +<hr /> +<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +</div> +<!--End of Navigation Panel--> + +</body> +</html> diff --git a/doc/mailman-admin/node27.html b/doc/mailman-admin/node27.html new file mode 100644 index 00000000..6388de8e --- /dev/null +++ b/doc/mailman-admin/node27.html @@ -0,0 +1,101 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> +<html> +<head> +<link rel="STYLESHEET" href="mailman-admin.css" type='text/css' /> +<link rel="first" href="mailman-admin.html" title='GNU mailman - list Administration Manual' /> +<link rel='contents' href='contents.html' title="Contents" /> +<link rel='last' href='about.html' title='About this document...' /> +<link rel='help' href='about.html' title='About this document...' /> +<link rel="next" href="node28.html" /> +<link rel="prev" href="node26.html" /> +<link rel="parent" href="node8.html" /> +<link rel="next" href="node28.html" /> +<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> +<meta name='aesop' content='information' /> +<title>2.10 The Mail/News Gateway Category</title> +</head> +<body> +<div class="navigation"> +<div id='top-navigation-panel' xml:id='top-navigation-panel'> +<table align="center" width="100%" cellpadding="0" cellspacing="2"> +<tr> +<td class='online-navigation'><a rel="prev" title="2.9 the Archiving Options" + href="node26.html"><img src='previous.png' + border='0' height='32' alt='Previous Page' width='32' /></a></td> +<td class='online-navigation'><a rel="parent" title="2 the List Configuration" + href="node8.html"><img src='up.png' + border='0' height='32' alt='Up one Level' width='32' /></a></td> +<td class='online-navigation'><a rel="next" title="2.11 the Auto-responder Category" + href="node28.html"><img src='next.png' + border='0' height='32' alt='Next Page' width='32' /></a></td> +<td align="center" width="100%">GNU Mailman - List Administration Manual</td> +<td class='online-navigation'><a rel="contents" title="Table of Contents" + href="contents.html"><img src='contents.png' + border='0' height='32' alt='Contents' width='32' /></a></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +</tr></table> +<div class='online-navigation'> +<b class="navlabel">Previous:</b> +<a class="sectref" rel="prev" href="node26.html">2.9 The Archiving Options</a> +<b class="navlabel">Up:</b> +<a class="sectref" rel="parent" href="node8.html">2 The List Configuration</a> +<b class="navlabel">Next:</b> +<a class="sectref" rel="next" href="node28.html">2.11 The Auto-responder Category</a> +</div> +<hr /></div> +</div> +<!--End of Navigation Panel--> + +<h2><a name="SECTION0022100000000000000000"> +2.10 The Mail/News Gateway Category</a> +</h2> + +<p> +Mailman has a sophisticated mail-to-news gateway feature. It can +independently gate messages from news to mail and vice versa, and can +even be used to manage moderated newsgroups. + +<p> + +<div class="navigation"> +<div class='online-navigation'> +<p></p><hr /> +<table align="center" width="100%" cellpadding="0" cellspacing="2"> +<tr> +<td class='online-navigation'><a rel="prev" title="2.9 the Archiving Options" + href="node26.html"><img src='previous.png' + border='0' height='32' alt='Previous Page' width='32' /></a></td> +<td class='online-navigation'><a rel="parent" title="2 the List Configuration" + href="node8.html"><img src='up.png' + border='0' height='32' alt='Up one Level' width='32' /></a></td> +<td class='online-navigation'><a rel="next" title="2.11 the Auto-responder Category" + href="node28.html"><img src='next.png' + border='0' height='32' alt='Next Page' width='32' /></a></td> +<td align="center" width="100%">GNU Mailman - List Administration Manual</td> +<td class='online-navigation'><a rel="contents" title="Table of Contents" + href="contents.html"><img src='contents.png' + border='0' height='32' alt='Contents' width='32' /></a></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +</tr></table> +<div class='online-navigation'> +<b class="navlabel">Previous:</b> +<a class="sectref" rel="prev" href="node26.html">2.9 The Archiving Options</a> +<b class="navlabel">Up:</b> +<a class="sectref" rel="parent" href="node8.html">2 The List Configuration</a> +<b class="navlabel">Next:</b> +<a class="sectref" rel="next" href="node28.html">2.11 The Auto-responder Category</a> +</div> +</div> +<hr /> +<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +</div> +<!--End of Navigation Panel--> + +</body> +</html> diff --git a/doc/mailman-admin/node28.html b/doc/mailman-admin/node28.html new file mode 100644 index 00000000..1b6bce1e --- /dev/null +++ b/doc/mailman-admin/node28.html @@ -0,0 +1,94 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> +<html> +<head> +<link rel="STYLESHEET" href="mailman-admin.css" type='text/css' /> +<link rel="first" href="mailman-admin.html" title='GNU mailman - list Administration Manual' /> +<link rel='contents' href='contents.html' title="Contents" /> +<link rel='last' href='about.html' title='About this document...' /> +<link rel='help' href='about.html' title='About this document...' /> +<link rel="next" href="node29.html" /> +<link rel="prev" href="node27.html" /> +<link rel="parent" href="node8.html" /> +<link rel="next" href="node29.html" /> +<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> +<meta name='aesop' content='information' /> +<title>2.11 The Auto-responder Category</title> +</head> +<body> +<div class="navigation"> +<div id='top-navigation-panel' xml:id='top-navigation-panel'> +<table align="center" width="100%" cellpadding="0" cellspacing="2"> +<tr> +<td class='online-navigation'><a rel="prev" title="2.10 the Mail/News Gateway" + href="node27.html"><img src='previous.png' + border='0' height='32' alt='Previous Page' width='32' /></a></td> +<td class='online-navigation'><a rel="parent" title="2 the List Configuration" + href="node8.html"><img src='up.png' + border='0' height='32' alt='Up one Level' width='32' /></a></td> +<td class='online-navigation'><a rel="next" title="2.12 the Content Filtering" + href="node29.html"><img src='next.png' + border='0' height='32' alt='Next Page' width='32' /></a></td> +<td align="center" width="100%">GNU Mailman - List Administration Manual</td> +<td class='online-navigation'><a rel="contents" title="Table of Contents" + href="contents.html"><img src='contents.png' + border='0' height='32' alt='Contents' width='32' /></a></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +</tr></table> +<div class='online-navigation'> +<b class="navlabel">Previous:</b> +<a class="sectref" rel="prev" href="node27.html">2.10 The Mail/News Gateway</a> +<b class="navlabel">Up:</b> +<a class="sectref" rel="parent" href="node8.html">2 The List Configuration</a> +<b class="navlabel">Next:</b> +<a class="sectref" rel="next" href="node29.html">2.12 The Content Filtering</a> +</div> +<hr /></div> +</div> +<!--End of Navigation Panel--> + +<h2><a name="SECTION0022110000000000000000"> +2.11 The Auto-responder Category</a> +</h2> + +<div class="navigation"> +<div class='online-navigation'> +<p></p><hr /> +<table align="center" width="100%" cellpadding="0" cellspacing="2"> +<tr> +<td class='online-navigation'><a rel="prev" title="2.10 the Mail/News Gateway" + href="node27.html"><img src='previous.png' + border='0' height='32' alt='Previous Page' width='32' /></a></td> +<td class='online-navigation'><a rel="parent" title="2 the List Configuration" + href="node8.html"><img src='up.png' + border='0' height='32' alt='Up one Level' width='32' /></a></td> +<td class='online-navigation'><a rel="next" title="2.12 the Content Filtering" + href="node29.html"><img src='next.png' + border='0' height='32' alt='Next Page' width='32' /></a></td> +<td align="center" width="100%">GNU Mailman - List Administration Manual</td> +<td class='online-navigation'><a rel="contents" title="Table of Contents" + href="contents.html"><img src='contents.png' + border='0' height='32' alt='Contents' width='32' /></a></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +</tr></table> +<div class='online-navigation'> +<b class="navlabel">Previous:</b> +<a class="sectref" rel="prev" href="node27.html">2.10 The Mail/News Gateway</a> +<b class="navlabel">Up:</b> +<a class="sectref" rel="parent" href="node8.html">2 The List Configuration</a> +<b class="navlabel">Next:</b> +<a class="sectref" rel="next" href="node29.html">2.12 The Content Filtering</a> +</div> +</div> +<hr /> +<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +</div> +<!--End of Navigation Panel--> + +</body> +</html> diff --git a/doc/mailman-admin/node29.html b/doc/mailman-admin/node29.html new file mode 100644 index 00000000..7fecbdf0 --- /dev/null +++ b/doc/mailman-admin/node29.html @@ -0,0 +1,94 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> +<html> +<head> +<link rel="STYLESHEET" href="mailman-admin.css" type='text/css' /> +<link rel="first" href="mailman-admin.html" title='GNU mailman - list Administration Manual' /> +<link rel='contents' href='contents.html' title="Contents" /> +<link rel='last' href='about.html' title='About this document...' /> +<link rel='help' href='about.html' title='About this document...' /> +<link rel="next" href="node30.html" /> +<link rel="prev" href="node28.html" /> +<link rel="parent" href="node8.html" /> +<link rel="next" href="node30.html" /> +<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> +<meta name='aesop' content='information' /> +<title>2.12 The Content Filtering Category</title> +</head> +<body> +<div class="navigation"> +<div id='top-navigation-panel' xml:id='top-navigation-panel'> +<table align="center" width="100%" cellpadding="0" cellspacing="2"> +<tr> +<td class='online-navigation'><a rel="prev" title="2.11 the Auto-responder Category" + href="node28.html"><img src='previous.png' + border='0' height='32' alt='Previous Page' width='32' /></a></td> +<td class='online-navigation'><a rel="parent" title="2 the List Configuration" + href="node8.html"><img src='up.png' + border='0' height='32' alt='Up one Level' width='32' /></a></td> +<td class='online-navigation'><a rel="next" title="2.13 the Topics Category" + href="node30.html"><img src='next.png' + border='0' height='32' alt='Next Page' width='32' /></a></td> +<td align="center" width="100%">GNU Mailman - List Administration Manual</td> +<td class='online-navigation'><a rel="contents" title="Table of Contents" + href="contents.html"><img src='contents.png' + border='0' height='32' alt='Contents' width='32' /></a></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +</tr></table> +<div class='online-navigation'> +<b class="navlabel">Previous:</b> +<a class="sectref" rel="prev" href="node28.html">2.11 The Auto-responder Category</a> +<b class="navlabel">Up:</b> +<a class="sectref" rel="parent" href="node8.html">2 The List Configuration</a> +<b class="navlabel">Next:</b> +<a class="sectref" rel="next" href="node30.html">2.13 The Topics Category</a> +</div> +<hr /></div> +</div> +<!--End of Navigation Panel--> + +<h2><a name="SECTION0022120000000000000000"> +2.12 The Content Filtering Category</a> +</h2> + +<div class="navigation"> +<div class='online-navigation'> +<p></p><hr /> +<table align="center" width="100%" cellpadding="0" cellspacing="2"> +<tr> +<td class='online-navigation'><a rel="prev" title="2.11 the Auto-responder Category" + href="node28.html"><img src='previous.png' + border='0' height='32' alt='Previous Page' width='32' /></a></td> +<td class='online-navigation'><a rel="parent" title="2 the List Configuration" + href="node8.html"><img src='up.png' + border='0' height='32' alt='Up one Level' width='32' /></a></td> +<td class='online-navigation'><a rel="next" title="2.13 the Topics Category" + href="node30.html"><img src='next.png' + border='0' height='32' alt='Next Page' width='32' /></a></td> +<td align="center" width="100%">GNU Mailman - List Administration Manual</td> +<td class='online-navigation'><a rel="contents" title="Table of Contents" + href="contents.html"><img src='contents.png' + border='0' height='32' alt='Contents' width='32' /></a></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +</tr></table> +<div class='online-navigation'> +<b class="navlabel">Previous:</b> +<a class="sectref" rel="prev" href="node28.html">2.11 The Auto-responder Category</a> +<b class="navlabel">Up:</b> +<a class="sectref" rel="parent" href="node8.html">2 The List Configuration</a> +<b class="navlabel">Next:</b> +<a class="sectref" rel="next" href="node30.html">2.13 The Topics Category</a> +</div> +</div> +<hr /> +<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +</div> +<!--End of Navigation Panel--> + +</body> +</html> diff --git a/doc/mailman-admin/node3.html b/doc/mailman-admin/node3.html new file mode 100644 index 00000000..e813a33f --- /dev/null +++ b/doc/mailman-admin/node3.html @@ -0,0 +1,129 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> +<html> +<head> +<link rel="STYLESHEET" href="mailman-admin.css" type='text/css' /> +<link rel="first" href="mailman-admin.html" title='GNU mailman - list Administration Manual' /> +<link rel='contents' href='contents.html' title="Contents" /> +<link rel='last' href='about.html' title='About this document...' /> +<link rel='help' href='about.html' title='About this document...' /> +<link rel="next" href="node8.html" /> +<link rel="prev" href="contents.html" /> +<link rel="parent" href="contents.html" /> +<link rel="next" href="node4.html" /> +<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> +<meta name='aesop' content='information' /> +<title>1 Introduction to GNU Mailman</title> +</head> +<body> +<div class="navigation"> +<div id='top-navigation-panel' xml:id='top-navigation-panel'> +<table align="center" width="100%" cellpadding="0" cellspacing="2"> +<tr> +<td class='online-navigation'><a rel="prev" title="Contents" + href="contents.html"><img src='previous.png' + border='0' height='32' alt='Previous Page' width='32' /></a></td> +<td class='online-navigation'><a rel="parent" title="Contents" + href="contents.html"><img src='up.png' + border='0' height='32' alt='Up one Level' width='32' /></a></td> +<td class='online-navigation'><a rel="next" title="1.1 a List's Email" + href="node4.html"><img src='next.png' + border='0' height='32' alt='Next Page' width='32' /></a></td> +<td align="center" width="100%">GNU Mailman - List Administration Manual</td> +<td class='online-navigation'><a rel="contents" title="Table of Contents" + href="contents.html"><img src='contents.png' + border='0' height='32' alt='Contents' width='32' /></a></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +</tr></table> +<div class='online-navigation'> +<b class="navlabel">Previous:</b> +<a class="sectref" rel="prev" href="contents.html">Contents</a> +<b class="navlabel">Up:</b> +<a class="sectref" rel="parent" href="contents.html">Contents</a> +<b class="navlabel">Next:</b> +<a class="sectref" rel="next" href="node4.html">1.1 A List's Email</a> +</div> +<hr /></div> +</div> +<!--End of Navigation Panel--> + +<h1><a name="SECTION002100000000000000000"> +1 Introduction to GNU Mailman</a> +</h1> + +<p> +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 for controlling the privacy of your lists, distributing your +list as personalized postings or digests, gatewaying postings to and +from Usenet, and providing automatic bounce detection. Mailman +provides a built-in archiver, multiple natural languages, as well as +advanced content and topic filtering. + +<p> +Mailman provides several interfaces to its functionality. Most list +administrators will primarily use the web interface to customize their +lists. There is also a limited email command interface to the +administrative functions, as well as a command line interface if you +have shell access on the Mailman server. This document does not cover +the command line interface; see the GNU Mailman site administrator's +manual for more details. + +<p> + +<p><br /></p><hr class='online-navigation' /> +<div class='online-navigation'> +<!--Table of Child-Links--> +<a name="CHILD_LINKS"><strong>Subsections</strong></a> + +<ul class="ChildLinks"> +<li><a href="node4.html">1.1 A List's Email Addresses</a> +<li><a href="node5.html">1.2 Administrative Roles</a> +<li><a href="node6.html">1.3 A List's Web Pages</a> +<li><a href="node7.html">1.4 Basic Architectural Overview</a> +</ul> +<!--End of Table of Child-Links--> +</div> + +<div class="navigation"> +<div class='online-navigation'> +<p></p><hr /> +<table align="center" width="100%" cellpadding="0" cellspacing="2"> +<tr> +<td class='online-navigation'><a rel="prev" title="Contents" + href="contents.html"><img src='previous.png' + border='0' height='32' alt='Previous Page' width='32' /></a></td> +<td class='online-navigation'><a rel="parent" title="Contents" + href="contents.html"><img src='up.png' + border='0' height='32' alt='Up one Level' width='32' /></a></td> +<td class='online-navigation'><a rel="next" title="1.1 a List's Email" + href="node4.html"><img src='next.png' + border='0' height='32' alt='Next Page' width='32' /></a></td> +<td align="center" width="100%">GNU Mailman - List Administration Manual</td> +<td class='online-navigation'><a rel="contents" title="Table of Contents" + href="contents.html"><img src='contents.png' + border='0' height='32' alt='Contents' width='32' /></a></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +</tr></table> +<div class='online-navigation'> +<b class="navlabel">Previous:</b> +<a class="sectref" rel="prev" href="contents.html">Contents</a> +<b class="navlabel">Up:</b> +<a class="sectref" rel="parent" href="contents.html">Contents</a> +<b class="navlabel">Next:</b> +<a class="sectref" rel="next" href="node4.html">1.1 A List's Email</a> +</div> +</div> +<hr /> +<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +</div> +<!--End of Navigation Panel--> + +</body> +</html> diff --git a/doc/mailman-admin/node30.html b/doc/mailman-admin/node30.html new file mode 100644 index 00000000..07c65bb5 --- /dev/null +++ b/doc/mailman-admin/node30.html @@ -0,0 +1,95 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> +<html> +<head> +<link rel="STYLESHEET" href="mailman-admin.css" type='text/css' /> +<link rel="first" href="mailman-admin.html" title='GNU mailman - list Administration Manual' /> +<link rel='contents' href='contents.html' title="Contents" /> +<link rel='last' href='about.html' title='About this document...' /> +<link rel='help' href='about.html' title='About this document...' /> +<link rel="prev" href="node29.html" /> +<link rel="parent" href="node8.html" /> +<link rel="next" href="node31.html" /> +<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> +<meta name='aesop' content='information' /> +<title>2.13 The Topics Category</title> +</head> +<body> +<div class="navigation"> +<div id='top-navigation-panel' xml:id='top-navigation-panel'> +<table align="center" width="100%" cellpadding="0" cellspacing="2"> +<tr> +<td class='online-navigation'><a rel="prev" title="2.12 the Content Filtering" + href="node29.html"><img src='previous.png' + border='0' height='32' alt='Previous Page' width='32' /></a></td> +<td class='online-navigation'><a rel="parent" title="2 the List Configuration" + href="node8.html"><img src='up.png' + border='0' height='32' alt='Up one Level' width='32' /></a></td> +<td class='online-navigation'><a rel="next" title="3 membership Management" + href="node31.html"><img src='next.png' + border='0' height='32' alt='Next Page' width='32' /></a></td> +<td align="center" width="100%">GNU Mailman - List Administration Manual</td> +<td class='online-navigation'><a rel="contents" title="Table of Contents" + href="contents.html"><img src='contents.png' + border='0' height='32' alt='Contents' width='32' /></a></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +</tr></table> +<div class='online-navigation'> +<b class="navlabel">Previous:</b> +<a class="sectref" rel="prev" href="node29.html">2.12 The Content Filtering</a> +<b class="navlabel">Up:</b> +<a class="sectref" rel="parent" href="node8.html">2 The List Configuration</a> +<b class="navlabel">Next:</b> +<a class="sectref" rel="next" href="node31.html">3 Membership Management</a> +</div> +<hr /></div> +</div> +<!--End of Navigation Panel--> + +<h2><a name="SECTION0022130000000000000000"> +2.13 The Topics Category</a> +</h2> + +<p> + +<div class="navigation"> +<div class='online-navigation'> +<p></p><hr /> +<table align="center" width="100%" cellpadding="0" cellspacing="2"> +<tr> +<td class='online-navigation'><a rel="prev" title="2.12 the Content Filtering" + href="node29.html"><img src='previous.png' + border='0' height='32' alt='Previous Page' width='32' /></a></td> +<td class='online-navigation'><a rel="parent" title="2 the List Configuration" + href="node8.html"><img src='up.png' + border='0' height='32' alt='Up one Level' width='32' /></a></td> +<td class='online-navigation'><a rel="next" title="3 membership Management" + href="node31.html"><img src='next.png' + border='0' height='32' alt='Next Page' width='32' /></a></td> +<td align="center" width="100%">GNU Mailman - List Administration Manual</td> +<td class='online-navigation'><a rel="contents" title="Table of Contents" + href="contents.html"><img src='contents.png' + border='0' height='32' alt='Contents' width='32' /></a></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +</tr></table> +<div class='online-navigation'> +<b class="navlabel">Previous:</b> +<a class="sectref" rel="prev" href="node29.html">2.12 The Content Filtering</a> +<b class="navlabel">Up:</b> +<a class="sectref" rel="parent" href="node8.html">2 The List Configuration</a> +<b class="navlabel">Next:</b> +<a class="sectref" rel="next" href="node31.html">3 Membership Management</a> +</div> +</div> +<hr /> +<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +</div> +<!--End of Navigation Panel--> + +</body> +</html> diff --git a/doc/mailman-admin/node31.html b/doc/mailman-admin/node31.html new file mode 100644 index 00000000..52d177a2 --- /dev/null +++ b/doc/mailman-admin/node31.html @@ -0,0 +1,94 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> +<html> +<head> +<link rel="STYLESHEET" href="mailman-admin.css" type='text/css' /> +<link rel="first" href="mailman-admin.html" title='GNU mailman - list Administration Manual' /> +<link rel='contents' href='contents.html' title="Contents" /> +<link rel='last' href='about.html' title='About this document...' /> +<link rel='help' href='about.html' title='About this document...' /> +<link rel="next" href="node32.html" /> +<link rel="prev" href="node8.html" /> +<link rel="parent" href="contents.html" /> +<link rel="next" href="node32.html" /> +<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> +<meta name='aesop' content='information' /> +<title>3 Membership Management</title> +</head> +<body> +<div class="navigation"> +<div id='top-navigation-panel' xml:id='top-navigation-panel'> +<table align="center" width="100%" cellpadding="0" cellspacing="2"> +<tr> +<td class='online-navigation'><a rel="prev" title="2.13 the Topics Category" + href="node30.html"><img src='previous.png' + border='0' height='32' alt='Previous Page' width='32' /></a></td> +<td class='online-navigation'><a rel="parent" title="Contents" + href="contents.html"><img src='up.png' + border='0' height='32' alt='Up one Level' width='32' /></a></td> +<td class='online-navigation'><a rel="next" title="4 tending to Pending" + href="node32.html"><img src='next.png' + border='0' height='32' alt='Next Page' width='32' /></a></td> +<td align="center" width="100%">GNU Mailman - List Administration Manual</td> +<td class='online-navigation'><a rel="contents" title="Table of Contents" + href="contents.html"><img src='contents.png' + border='0' height='32' alt='Contents' width='32' /></a></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +</tr></table> +<div class='online-navigation'> +<b class="navlabel">Previous:</b> +<a class="sectref" rel="prev" href="node30.html">2.13 The Topics Category</a> +<b class="navlabel">Up:</b> +<a class="sectref" rel="parent" href="contents.html">Contents</a> +<b class="navlabel">Next:</b> +<a class="sectref" rel="next" href="node32.html">4 Tending to Pending</a> +</div> +<hr /></div> +</div> +<!--End of Navigation Panel--> + +<h1><a name="SECTION002300000000000000000"> +3 Membership Management</a> +</h1> + +<div class="navigation"> +<div class='online-navigation'> +<p></p><hr /> +<table align="center" width="100%" cellpadding="0" cellspacing="2"> +<tr> +<td class='online-navigation'><a rel="prev" title="2.13 the Topics Category" + href="node30.html"><img src='previous.png' + border='0' height='32' alt='Previous Page' width='32' /></a></td> +<td class='online-navigation'><a rel="parent" title="Contents" + href="contents.html"><img src='up.png' + border='0' height='32' alt='Up one Level' width='32' /></a></td> +<td class='online-navigation'><a rel="next" title="4 tending to Pending" + href="node32.html"><img src='next.png' + border='0' height='32' alt='Next Page' width='32' /></a></td> +<td align="center" width="100%">GNU Mailman - List Administration Manual</td> +<td class='online-navigation'><a rel="contents" title="Table of Contents" + href="contents.html"><img src='contents.png' + border='0' height='32' alt='Contents' width='32' /></a></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +</tr></table> +<div class='online-navigation'> +<b class="navlabel">Previous:</b> +<a class="sectref" rel="prev" href="node30.html">2.13 The Topics Category</a> +<b class="navlabel">Up:</b> +<a class="sectref" rel="parent" href="contents.html">Contents</a> +<b class="navlabel">Next:</b> +<a class="sectref" rel="next" href="node32.html">4 Tending to Pending</a> +</div> +</div> +<hr /> +<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +</div> +<!--End of Navigation Panel--> + +</body> +</html> diff --git a/doc/mailman-admin/node32.html b/doc/mailman-admin/node32.html new file mode 100644 index 00000000..27f20051 --- /dev/null +++ b/doc/mailman-admin/node32.html @@ -0,0 +1,94 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> +<html> +<head> +<link rel="STYLESHEET" href="mailman-admin.css" type='text/css' /> +<link rel="first" href="mailman-admin.html" title='GNU mailman - list Administration Manual' /> +<link rel='contents' href='contents.html' title="Contents" /> +<link rel='last' href='about.html' title='About this document...' /> +<link rel='help' href='about.html' title='About this document...' /> +<link rel="next" href="node33.html" /> +<link rel="prev" href="node31.html" /> +<link rel="parent" href="contents.html" /> +<link rel="next" href="node33.html" /> +<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> +<meta name='aesop' content='information' /> +<title>4 Tending to Pending Moderator Requests</title> +</head> +<body> +<div class="navigation"> +<div id='top-navigation-panel' xml:id='top-navigation-panel'> +<table align="center" width="100%" cellpadding="0" cellspacing="2"> +<tr> +<td class='online-navigation'><a rel="prev" title="3 membership Management" + href="node31.html"><img src='previous.png' + border='0' height='32' alt='Previous Page' width='32' /></a></td> +<td class='online-navigation'><a rel="parent" title="Contents" + href="contents.html"><img src='up.png' + border='0' height='32' alt='Up one Level' width='32' /></a></td> +<td class='online-navigation'><a rel="next" title="5 editing the Public" + href="node33.html"><img src='next.png' + border='0' height='32' alt='Next Page' width='32' /></a></td> +<td align="center" width="100%">GNU Mailman - List Administration Manual</td> +<td class='online-navigation'><a rel="contents" title="Table of Contents" + href="contents.html"><img src='contents.png' + border='0' height='32' alt='Contents' width='32' /></a></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +</tr></table> +<div class='online-navigation'> +<b class="navlabel">Previous:</b> +<a class="sectref" rel="prev" href="node31.html">3 Membership Management</a> +<b class="navlabel">Up:</b> +<a class="sectref" rel="parent" href="contents.html">Contents</a> +<b class="navlabel">Next:</b> +<a class="sectref" rel="next" href="node33.html">5 Editing the Public</a> +</div> +<hr /></div> +</div> +<!--End of Navigation Panel--> + +<h1><a name="SECTION002400000000000000000"> +4 Tending to Pending Moderator Requests</a> +</h1> + +<div class="navigation"> +<div class='online-navigation'> +<p></p><hr /> +<table align="center" width="100%" cellpadding="0" cellspacing="2"> +<tr> +<td class='online-navigation'><a rel="prev" title="3 membership Management" + href="node31.html"><img src='previous.png' + border='0' height='32' alt='Previous Page' width='32' /></a></td> +<td class='online-navigation'><a rel="parent" title="Contents" + href="contents.html"><img src='up.png' + border='0' height='32' alt='Up one Level' width='32' /></a></td> +<td class='online-navigation'><a rel="next" title="5 editing the Public" + href="node33.html"><img src='next.png' + border='0' height='32' alt='Next Page' width='32' /></a></td> +<td align="center" width="100%">GNU Mailman - List Administration Manual</td> +<td class='online-navigation'><a rel="contents" title="Table of Contents" + href="contents.html"><img src='contents.png' + border='0' height='32' alt='Contents' width='32' /></a></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +</tr></table> +<div class='online-navigation'> +<b class="navlabel">Previous:</b> +<a class="sectref" rel="prev" href="node31.html">3 Membership Management</a> +<b class="navlabel">Up:</b> +<a class="sectref" rel="parent" href="contents.html">Contents</a> +<b class="navlabel">Next:</b> +<a class="sectref" rel="next" href="node33.html">5 Editing the Public</a> +</div> +</div> +<hr /> +<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +</div> +<!--End of Navigation Panel--> + +</body> +</html> diff --git a/doc/mailman-admin/node33.html b/doc/mailman-admin/node33.html new file mode 100644 index 00000000..335cb405 --- /dev/null +++ b/doc/mailman-admin/node33.html @@ -0,0 +1,94 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> +<html> +<head> +<link rel="STYLESHEET" href="mailman-admin.css" type='text/css' /> +<link rel="first" href="mailman-admin.html" title='GNU mailman - list Administration Manual' /> +<link rel='contents' href='contents.html' title="Contents" /> +<link rel='last' href='about.html' title='About this document...' /> +<link rel='help' href='about.html' title='About this document...' /> +<link rel="next" href="node34.html" /> +<link rel="prev" href="node32.html" /> +<link rel="parent" href="contents.html" /> +<link rel="next" href="node34.html" /> +<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> +<meta name='aesop' content='information' /> +<title>5 Editing the Public HTML Pages</title> +</head> +<body> +<div class="navigation"> +<div id='top-navigation-panel' xml:id='top-navigation-panel'> +<table align="center" width="100%" cellpadding="0" cellspacing="2"> +<tr> +<td class='online-navigation'><a rel="prev" title="4 tending to Pending" + href="node32.html"><img src='previous.png' + border='0' height='32' alt='Previous Page' width='32' /></a></td> +<td class='online-navigation'><a rel="parent" title="Contents" + href="contents.html"><img src='up.png' + border='0' height='32' alt='Up one Level' width='32' /></a></td> +<td class='online-navigation'><a rel="next" title="6 deleting the Mailing" + href="node34.html"><img src='next.png' + border='0' height='32' alt='Next Page' width='32' /></a></td> +<td align="center" width="100%">GNU Mailman - List Administration Manual</td> +<td class='online-navigation'><a rel="contents" title="Table of Contents" + href="contents.html"><img src='contents.png' + border='0' height='32' alt='Contents' width='32' /></a></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +</tr></table> +<div class='online-navigation'> +<b class="navlabel">Previous:</b> +<a class="sectref" rel="prev" href="node32.html">4 Tending to Pending</a> +<b class="navlabel">Up:</b> +<a class="sectref" rel="parent" href="contents.html">Contents</a> +<b class="navlabel">Next:</b> +<a class="sectref" rel="next" href="node34.html">6 Deleting the Mailing</a> +</div> +<hr /></div> +</div> +<!--End of Navigation Panel--> + +<h1><a name="SECTION002500000000000000000"> +5 Editing the Public HTML Pages</a> +</h1> + +<div class="navigation"> +<div class='online-navigation'> +<p></p><hr /> +<table align="center" width="100%" cellpadding="0" cellspacing="2"> +<tr> +<td class='online-navigation'><a rel="prev" title="4 tending to Pending" + href="node32.html"><img src='previous.png' + border='0' height='32' alt='Previous Page' width='32' /></a></td> +<td class='online-navigation'><a rel="parent" title="Contents" + href="contents.html"><img src='up.png' + border='0' height='32' alt='Up one Level' width='32' /></a></td> +<td class='online-navigation'><a rel="next" title="6 deleting the Mailing" + href="node34.html"><img src='next.png' + border='0' height='32' alt='Next Page' width='32' /></a></td> +<td align="center" width="100%">GNU Mailman - List Administration Manual</td> +<td class='online-navigation'><a rel="contents" title="Table of Contents" + href="contents.html"><img src='contents.png' + border='0' height='32' alt='Contents' width='32' /></a></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +</tr></table> +<div class='online-navigation'> +<b class="navlabel">Previous:</b> +<a class="sectref" rel="prev" href="node32.html">4 Tending to Pending</a> +<b class="navlabel">Up:</b> +<a class="sectref" rel="parent" href="contents.html">Contents</a> +<b class="navlabel">Next:</b> +<a class="sectref" rel="next" href="node34.html">6 Deleting the Mailing</a> +</div> +</div> +<hr /> +<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +</div> +<!--End of Navigation Panel--> + +</body> +</html> diff --git a/doc/mailman-admin/node34.html b/doc/mailman-admin/node34.html new file mode 100644 index 00000000..fe7aec18 --- /dev/null +++ b/doc/mailman-admin/node34.html @@ -0,0 +1,98 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> +<html> +<head> +<link rel="STYLESHEET" href="mailman-admin.css" type='text/css' /> +<link rel="first" href="mailman-admin.html" title='GNU mailman - list Administration Manual' /> +<link rel='contents' href='contents.html' title="Contents" /> +<link rel='last' href='about.html' title='About this document...' /> +<link rel='help' href='about.html' title='About this document...' /> +<link rel="next" href="node35.html" /> +<link rel="prev" href="node33.html" /> +<link rel="parent" href="contents.html" /> +<link rel="next" href="node35.html" /> +<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> +<meta name='aesop' content='information' /> +<title>6 Deleting the Mailing List</title> +</head> +<body> +<div class="navigation"> +<div id='top-navigation-panel' xml:id='top-navigation-panel'> +<table align="center" width="100%" cellpadding="0" cellspacing="2"> +<tr> +<td class='online-navigation'><a rel="prev" title="5 editing the Public" + href="node33.html"><img src='previous.png' + border='0' height='32' alt='Previous Page' width='32' /></a></td> +<td class='online-navigation'><a rel="parent" title="Contents" + href="contents.html"><img src='up.png' + border='0' height='32' alt='Up one Level' width='32' /></a></td> +<td class='online-navigation'><a rel="next" title="1 this is an" + href="node35.html"><img src='next.png' + border='0' height='32' alt='Next Page' width='32' /></a></td> +<td align="center" width="100%">GNU Mailman - List Administration Manual</td> +<td class='online-navigation'><a rel="contents" title="Table of Contents" + href="contents.html"><img src='contents.png' + border='0' height='32' alt='Contents' width='32' /></a></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +</tr></table> +<div class='online-navigation'> +<b class="navlabel">Previous:</b> +<a class="sectref" rel="prev" href="node33.html">5 Editing the Public</a> +<b class="navlabel">Up:</b> +<a class="sectref" rel="parent" href="contents.html">Contents</a> +<b class="navlabel">Next:</b> +<a class="sectref" rel="next" href="node35.html">1 This is an</a> +</div> +<hr /></div> +</div> +<!--End of Navigation Panel--> + +<h1><a name="SECTION002600000000000000000"> +6 Deleting the Mailing List</a> +</h1> + +<p> + +<p> + +<div class="navigation"> +<div class='online-navigation'> +<p></p><hr /> +<table align="center" width="100%" cellpadding="0" cellspacing="2"> +<tr> +<td class='online-navigation'><a rel="prev" title="5 editing the Public" + href="node33.html"><img src='previous.png' + border='0' height='32' alt='Previous Page' width='32' /></a></td> +<td class='online-navigation'><a rel="parent" title="Contents" + href="contents.html"><img src='up.png' + border='0' height='32' alt='Up one Level' width='32' /></a></td> +<td class='online-navigation'><a rel="next" title="1 this is an" + href="node35.html"><img src='next.png' + border='0' height='32' alt='Next Page' width='32' /></a></td> +<td align="center" width="100%">GNU Mailman - List Administration Manual</td> +<td class='online-navigation'><a rel="contents" title="Table of Contents" + href="contents.html"><img src='contents.png' + border='0' height='32' alt='Contents' width='32' /></a></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +</tr></table> +<div class='online-navigation'> +<b class="navlabel">Previous:</b> +<a class="sectref" rel="prev" href="node33.html">5 Editing the Public</a> +<b class="navlabel">Up:</b> +<a class="sectref" rel="parent" href="contents.html">Contents</a> +<b class="navlabel">Next:</b> +<a class="sectref" rel="next" href="node35.html">1 This is an</a> +</div> +</div> +<hr /> +<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +</div> +<!--End of Navigation Panel--> + +</body> +</html> diff --git a/doc/mailman-admin/node35.html b/doc/mailman-admin/node35.html new file mode 100644 index 00000000..0d64431c --- /dev/null +++ b/doc/mailman-admin/node35.html @@ -0,0 +1,113 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> +<html> +<head> +<link rel="STYLESHEET" href="mailman-admin.css" type='text/css' /> +<link rel="first" href="mailman-admin.html" title='GNU mailman - list Administration Manual' /> +<link rel='contents' href='contents.html' title="Contents" /> +<link rel='last' href='about.html' title='About this document...' /> +<link rel='help' href='about.html' title='About this document...' /> +<link rel="prev" href="node34.html" /> +<link rel="parent" href="contents.html" /> +<link rel="next" href="about.html" /> +<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> +<meta name='aesop' content='information' /> +<title>1 This is an Appendix</title> +</head> +<body> +<div class="navigation"> +<div id='top-navigation-panel' xml:id='top-navigation-panel'> +<table align="center" width="100%" cellpadding="0" cellspacing="2"> +<tr> +<td class='online-navigation'><a rel="prev" title="6 deleting the Mailing" + href="node34.html"><img src='previous.png' + border='0' height='32' alt='Previous Page' width='32' /></a></td> +<td class='online-navigation'><a rel="parent" title="Contents" + href="contents.html"><img src='up.png' + border='0' height='32' alt='Up one Level' width='32' /></a></td> +<td class='online-navigation'><a rel="next" title="About this document ..." + href="about.html"><img src='next.png' + border='0' height='32' alt='Next Page' width='32' /></a></td> +<td align="center" width="100%">GNU Mailman - List Administration Manual</td> +<td class='online-navigation'><a rel="contents" title="Table of Contents" + href="contents.html"><img src='contents.png' + border='0' height='32' alt='Contents' width='32' /></a></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +</tr></table> +<div class='online-navigation'> +<b class="navlabel">Previous:</b> +<a class="sectref" rel="prev" href="node34.html">6 Deleting the Mailing</a> +<b class="navlabel">Up:</b> +<a class="sectref" rel="parent" href="contents.html">Contents</a> +<b class="navlabel">Next:</b> +<a class="sectref" rel="next" href="about.html">About this document ...</a> +</div> +<hr /></div> +</div> +<!--End of Navigation Panel--> + +<h1><a name="SECTION002700000000000000000"> +1 This is an Appendix</a> +</h1> + +<p> +To create an appendix in a Python HOWTO document, use markup like +this: + +<p> +<div class="verbatim"><pre> +\appendix + +\section{This is an Appendix} + +To create an appendix in a Python HOWTO document, .... + + +\section{This is another} + +Just add another \section{}, but don't say \appendix again. +</pre></div> + +<p> + +<div class="navigation"> +<div class='online-navigation'> +<p></p><hr /> +<table align="center" width="100%" cellpadding="0" cellspacing="2"> +<tr> +<td class='online-navigation'><a rel="prev" title="6 deleting the Mailing" + href="node34.html"><img src='previous.png' + border='0' height='32' alt='Previous Page' width='32' /></a></td> +<td class='online-navigation'><a rel="parent" title="Contents" + href="contents.html"><img src='up.png' + border='0' height='32' alt='Up one Level' width='32' /></a></td> +<td class='online-navigation'><a rel="next" title="About this document ..." + href="about.html"><img src='next.png' + border='0' height='32' alt='Next Page' width='32' /></a></td> +<td align="center" width="100%">GNU Mailman - List Administration Manual</td> +<td class='online-navigation'><a rel="contents" title="Table of Contents" + href="contents.html"><img src='contents.png' + border='0' height='32' alt='Contents' width='32' /></a></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +</tr></table> +<div class='online-navigation'> +<b class="navlabel">Previous:</b> +<a class="sectref" rel="prev" href="node34.html">6 Deleting the Mailing</a> +<b class="navlabel">Up:</b> +<a class="sectref" rel="parent" href="contents.html">Contents</a> +<b class="navlabel">Next:</b> +<a class="sectref" rel="next" href="about.html">About this document ...</a> +</div> +</div> +<hr /> +<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +</div> +<!--End of Navigation Panel--> + +</body> +</html> diff --git a/doc/mailman-admin/node4.html b/doc/mailman-admin/node4.html new file mode 100644 index 00000000..538cd6b8 --- /dev/null +++ b/doc/mailman-admin/node4.html @@ -0,0 +1,160 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> +<html> +<head> +<link rel="STYLESHEET" href="mailman-admin.css" type='text/css' /> +<link rel="first" href="mailman-admin.html" title='GNU mailman - list Administration Manual' /> +<link rel='contents' href='contents.html' title="Contents" /> +<link rel='last' href='about.html' title='About this document...' /> +<link rel='help' href='about.html' title='About this document...' /> +<link rel="next" href="node5.html" /> +<link rel="prev" href="node3.html" /> +<link rel="parent" href="node3.html" /> +<link rel="next" href="node5.html" /> +<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> +<meta name='aesop' content='information' /> +<title>1.1 A List's Email Addresses</title> +</head> +<body> +<div class="navigation"> +<div id='top-navigation-panel' xml:id='top-navigation-panel'> +<table align="center" width="100%" cellpadding="0" cellspacing="2"> +<tr> +<td class='online-navigation'><a rel="prev" title="1 introduction to GNU" + href="node3.html"><img src='previous.png' + border='0' height='32' alt='Previous Page' width='32' /></a></td> +<td class='online-navigation'><a rel="parent" title="1 introduction to GNU" + href="node3.html"><img src='up.png' + border='0' height='32' alt='Up one Level' width='32' /></a></td> +<td class='online-navigation'><a rel="next" title="1.2 administrative Roles" + href="node5.html"><img src='next.png' + border='0' height='32' alt='Next Page' width='32' /></a></td> +<td align="center" width="100%">GNU Mailman - List Administration Manual</td> +<td class='online-navigation'><a rel="contents" title="Table of Contents" + href="contents.html"><img src='contents.png' + border='0' height='32' alt='Contents' width='32' /></a></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +</tr></table> +<div class='online-navigation'> +<b class="navlabel">Previous:</b> +<a class="sectref" rel="prev" href="node3.html">1 Introduction to GNU</a> +<b class="navlabel">Up:</b> +<a class="sectref" rel="parent" href="node3.html">1 Introduction to GNU</a> +<b class="navlabel">Next:</b> +<a class="sectref" rel="next" href="node5.html">1.2 Administrative Roles</a> +</div> +<hr /></div> +</div> +<!--End of Navigation Panel--> + +<h2><a name="SECTION002110000000000000000"> +1.1 A List's Email Addresses</a> +</h2> + +<p> +Every mailing list has a set of email addresses that messages can be +sent to. There's always one address for posting messages to the list, +one address that bounces will be sent to, and addresses for processing +email commands. For example, for a mailing list called +<var>mylist@example.com</var>, you'd find these addresses: + +<p> + +<ul> +<li>mylist@example.com - this is the email address people should + use for new postings to the list. + +<p> +</li> +<li>mylist-join@example.com - by sending a message to this address, + a new member can request subscription to the list. Both the + <span class="mailheader">Subject:</span> header and body of such a message are + ignored. Note that mylist-subscribe@example.com is an alias for + the -join address. + +<p> +</li> +<li>mylist-leave@example.com - by sending a message to this address, + a member can request unsubscription from the list. As with the + -join address, the <span class="mailheader">Subject:</span> header and body of the + message is ignored. Note that mylist-unsubscribe@example.com is + an alias for the -leave address. + +<p> +</li> +<li>mylist-owner@example.com - This address reaches the list owner + and list moderators directly. + +<p> +</li> +<li>mylist-request@example.com - This address reaches a mail robot + which processes email commands that can be used to set member + subscription options, as well as process other commands. + +<p> +</li> +<li>mylist-bounces@example.com - This address receives bounces from + members who's addresses have become either temporarily or + permanently inactive. The -bounces address is also a mail robot + that processes bounces and automatically disables or removes + members as configured in the bounce processing settings. Any + bounce messages that are either unrecognized, or do not seem to + contain member addresses, are forwarded to the list + administrators. + +<p> +</li> +<li>mylist-confirm@example.com - This address is another email + robot, which processes confirmation messages for subscription + and unsubscription requests. +</li> +</ul> + +<p> +There's also an -admin address which also reaches the list +administrators, but this address only exists for compatibility with +older versions of Mailman. + +<p> + +<div class="navigation"> +<div class='online-navigation'> +<p></p><hr /> +<table align="center" width="100%" cellpadding="0" cellspacing="2"> +<tr> +<td class='online-navigation'><a rel="prev" title="1 introduction to GNU" + href="node3.html"><img src='previous.png' + border='0' height='32' alt='Previous Page' width='32' /></a></td> +<td class='online-navigation'><a rel="parent" title="1 introduction to GNU" + href="node3.html"><img src='up.png' + border='0' height='32' alt='Up one Level' width='32' /></a></td> +<td class='online-navigation'><a rel="next" title="1.2 administrative Roles" + href="node5.html"><img src='next.png' + border='0' height='32' alt='Next Page' width='32' /></a></td> +<td align="center" width="100%">GNU Mailman - List Administration Manual</td> +<td class='online-navigation'><a rel="contents" title="Table of Contents" + href="contents.html"><img src='contents.png' + border='0' height='32' alt='Contents' width='32' /></a></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +</tr></table> +<div class='online-navigation'> +<b class="navlabel">Previous:</b> +<a class="sectref" rel="prev" href="node3.html">1 Introduction to GNU</a> +<b class="navlabel">Up:</b> +<a class="sectref" rel="parent" href="node3.html">1 Introduction to GNU</a> +<b class="navlabel">Next:</b> +<a class="sectref" rel="next" href="node5.html">1.2 Administrative Roles</a> +</div> +</div> +<hr /> +<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +</div> +<!--End of Navigation Panel--> + +</body> +</html> diff --git a/doc/mailman-admin/node5.html b/doc/mailman-admin/node5.html new file mode 100644 index 00000000..489d4a23 --- /dev/null +++ b/doc/mailman-admin/node5.html @@ -0,0 +1,126 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> +<html> +<head> +<link rel="STYLESHEET" href="mailman-admin.css" type='text/css' /> +<link rel="first" href="mailman-admin.html" title='GNU mailman - list Administration Manual' /> +<link rel='contents' href='contents.html' title="Contents" /> +<link rel='last' href='about.html' title='About this document...' /> +<link rel='help' href='about.html' title='About this document...' /> +<link rel="next" href="node6.html" /> +<link rel="prev" href="node4.html" /> +<link rel="parent" href="node3.html" /> +<link rel="next" href="node6.html" /> +<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> +<meta name='aesop' content='information' /> +<title>1.2 Administrative Roles</title> +</head> +<body> +<div class="navigation"> +<div id='top-navigation-panel' xml:id='top-navigation-panel'> +<table align="center" width="100%" cellpadding="0" cellspacing="2"> +<tr> +<td class='online-navigation'><a rel="prev" title="1.1 a List's Email" + href="node4.html"><img src='previous.png' + border='0' height='32' alt='Previous Page' width='32' /></a></td> +<td class='online-navigation'><a rel="parent" title="1 introduction to GNU" + href="node3.html"><img src='up.png' + border='0' height='32' alt='Up one Level' width='32' /></a></td> +<td class='online-navigation'><a rel="next" title="1.3 a List's Web" + href="node6.html"><img src='next.png' + border='0' height='32' alt='Next Page' width='32' /></a></td> +<td align="center" width="100%">GNU Mailman - List Administration Manual</td> +<td class='online-navigation'><a rel="contents" title="Table of Contents" + href="contents.html"><img src='contents.png' + border='0' height='32' alt='Contents' width='32' /></a></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +</tr></table> +<div class='online-navigation'> +<b class="navlabel">Previous:</b> +<a class="sectref" rel="prev" href="node4.html">1.1 A List's Email</a> +<b class="navlabel">Up:</b> +<a class="sectref" rel="parent" href="node3.html">1 Introduction to GNU</a> +<b class="navlabel">Next:</b> +<a class="sectref" rel="next" href="node6.html">1.3 A List's Web</a> +</div> +<hr /></div> +</div> +<!--End of Navigation Panel--> + +<h2><a name="SECTION002120000000000000000"> +1.2 Administrative Roles</a> +</h2> + +<p> +There are two primary administrative roles for each mailing list, a +list owner and a list moderator. A list owner is allowed to change +various settings of the list, such as the privacy and archiving +policies, the content filtering settings, etc. The list owner is also +allowed to subscribe or invite members, unsubscribe members, and +change any member's subscription options. + +<p> +The list moderator on the other hand, is only allowed to approve or +reject postings and subscription requests. The list moderator can +also do things like clear a member's moderation flag, or add an +address to a list of approved non-member posters. + +<p> +Normally, the list owner and list moderator are the same person. In +fact, the list owner can always do all the tasks a list moderator can +do. Access to both the owner's configuration pages, and the +moderation pages are protected by the same password. However, if the +list owner wants to delegate posting and subscription approval +authority to other people, a separate list moderator password can be +set, giving moderators access to the approval pages, but not the +configuration pages. In this setup, list owners can still moderate +the list, of course. + +<p> +In the sections that follow, we'll often use the terms list owner and +list administrator interchangably, meaning both roles. When +necessary, we'll distinguish the list moderator explicitly. + +<p> + +<div class="navigation"> +<div class='online-navigation'> +<p></p><hr /> +<table align="center" width="100%" cellpadding="0" cellspacing="2"> +<tr> +<td class='online-navigation'><a rel="prev" title="1.1 a List's Email" + href="node4.html"><img src='previous.png' + border='0' height='32' alt='Previous Page' width='32' /></a></td> +<td class='online-navigation'><a rel="parent" title="1 introduction to GNU" + href="node3.html"><img src='up.png' + border='0' height='32' alt='Up one Level' width='32' /></a></td> +<td class='online-navigation'><a rel="next" title="1.3 a List's Web" + href="node6.html"><img src='next.png' + border='0' height='32' alt='Next Page' width='32' /></a></td> +<td align="center" width="100%">GNU Mailman - List Administration Manual</td> +<td class='online-navigation'><a rel="contents" title="Table of Contents" + href="contents.html"><img src='contents.png' + border='0' height='32' alt='Contents' width='32' /></a></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +</tr></table> +<div class='online-navigation'> +<b class="navlabel">Previous:</b> +<a class="sectref" rel="prev" href="node4.html">1.1 A List's Email</a> +<b class="navlabel">Up:</b> +<a class="sectref" rel="parent" href="node3.html">1 Introduction to GNU</a> +<b class="navlabel">Next:</b> +<a class="sectref" rel="next" href="node6.html">1.3 A List's Web</a> +</div> +</div> +<hr /> +<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +</div> +<!--End of Navigation Panel--> + +</body> +</html> diff --git a/doc/mailman-admin/node6.html b/doc/mailman-admin/node6.html new file mode 100644 index 00000000..eca800af --- /dev/null +++ b/doc/mailman-admin/node6.html @@ -0,0 +1,135 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> +<html> +<head> +<link rel="STYLESHEET" href="mailman-admin.css" type='text/css' /> +<link rel="first" href="mailman-admin.html" title='GNU mailman - list Administration Manual' /> +<link rel='contents' href='contents.html' title="Contents" /> +<link rel='last' href='about.html' title='About this document...' /> +<link rel='help' href='about.html' title='About this document...' /> +<link rel="next" href="node7.html" /> +<link rel="prev" href="node5.html" /> +<link rel="parent" href="node3.html" /> +<link rel="next" href="node7.html" /> +<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> +<meta name='aesop' content='information' /> +<title>1.3 A List's Web Pages</title> +</head> +<body> +<div class="navigation"> +<div id='top-navigation-panel' xml:id='top-navigation-panel'> +<table align="center" width="100%" cellpadding="0" cellspacing="2"> +<tr> +<td class='online-navigation'><a rel="prev" title="1.2 administrative Roles" + href="node5.html"><img src='previous.png' + border='0' height='32' alt='Previous Page' width='32' /></a></td> +<td class='online-navigation'><a rel="parent" title="1 introduction to GNU" + href="node3.html"><img src='up.png' + border='0' height='32' alt='Up one Level' width='32' /></a></td> +<td class='online-navigation'><a rel="next" title="1.4 basic Architectural Overview" + href="node7.html"><img src='next.png' + border='0' height='32' alt='Next Page' width='32' /></a></td> +<td align="center" width="100%">GNU Mailman - List Administration Manual</td> +<td class='online-navigation'><a rel="contents" title="Table of Contents" + href="contents.html"><img src='contents.png' + border='0' height='32' alt='Contents' width='32' /></a></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +</tr></table> +<div class='online-navigation'> +<b class="navlabel">Previous:</b> +<a class="sectref" rel="prev" href="node5.html">1.2 Administrative Roles</a> +<b class="navlabel">Up:</b> +<a class="sectref" rel="parent" href="node3.html">1 Introduction to GNU</a> +<b class="navlabel">Next:</b> +<a class="sectref" rel="next" href="node7.html">1.4 Basic Architectural Overview</a> +</div> +<hr /></div> +</div> +<!--End of Navigation Panel--> + +<h2><a name="SECTION002130000000000000000"> +1.3 A List's Web Pages</a> +</h2> + +<p> +Every mailing list is also accessible by a number of web pages. Note +that the exact urls is configurable by the site administrator, so they +may be different than what's described below. We'll describe the most +common default configuration, but check with your site administrator +or hosting service for details. + +<p> +Mailman provides a set of web pages that list members use to get +information about the list, or manage their membership options. There +are also list archive pages, for browsing an online web-based archive +of the list traffic. These are described in more detail in the GNU +Mailman user's manual. + +<p> +Mailman also provides a set of pages for configuring an individual +list, as well as a set of pages for disposing of posting and +subscription requests. + +<p> +For a mailing list called <var>mylist</var> hosted at the domain +<var>lists.example.com</var>, you would typically access the administrative +pages by going to <code>http://lists.example.com/mailman/admin/mylist</code>. +The first time you visit this page, you will be presented with a login +page, asking for the list owner's password. When you enter the +password, Mailman will store a session cookie in your browser, so you +don't have to re-authenticate for every action you want to take. This +cookie is stored only until you exit your browser. + +<p> +To access the administrative requests page, you'd visit +<code>http://lists.example.com/mailman/admindb/mylist</code> (note the +<em>admindb</em> url as opposed to the <em>admin</em> url). Again, the +first time you visit this page, you'll be presented with a login page, +on which you can enter either the list moderator password or the list +owner password. Again, a session cookie is dropped in your browser. +Note also that if you've previously logged in as the list owner, you +do not need to re-login to access the administrative requests page. + +<p> + +<div class="navigation"> +<div class='online-navigation'> +<p></p><hr /> +<table align="center" width="100%" cellpadding="0" cellspacing="2"> +<tr> +<td class='online-navigation'><a rel="prev" title="1.2 administrative Roles" + href="node5.html"><img src='previous.png' + border='0' height='32' alt='Previous Page' width='32' /></a></td> +<td class='online-navigation'><a rel="parent" title="1 introduction to GNU" + href="node3.html"><img src='up.png' + border='0' height='32' alt='Up one Level' width='32' /></a></td> +<td class='online-navigation'><a rel="next" title="1.4 basic Architectural Overview" + href="node7.html"><img src='next.png' + border='0' height='32' alt='Next Page' width='32' /></a></td> +<td align="center" width="100%">GNU Mailman - List Administration Manual</td> +<td class='online-navigation'><a rel="contents" title="Table of Contents" + href="contents.html"><img src='contents.png' + border='0' height='32' alt='Contents' width='32' /></a></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +</tr></table> +<div class='online-navigation'> +<b class="navlabel">Previous:</b> +<a class="sectref" rel="prev" href="node5.html">1.2 Administrative Roles</a> +<b class="navlabel">Up:</b> +<a class="sectref" rel="parent" href="node3.html">1 Introduction to GNU</a> +<b class="navlabel">Next:</b> +<a class="sectref" rel="next" href="node7.html">1.4 Basic Architectural Overview</a> +</div> +</div> +<hr /> +<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +</div> +<!--End of Navigation Panel--> + +</body> +</html> diff --git a/doc/mailman-admin/node7.html b/doc/mailman-admin/node7.html new file mode 100644 index 00000000..8f41bc68 --- /dev/null +++ b/doc/mailman-admin/node7.html @@ -0,0 +1,147 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> +<html> +<head> +<link rel="STYLESHEET" href="mailman-admin.css" type='text/css' /> +<link rel="first" href="mailman-admin.html" title='GNU mailman - list Administration Manual' /> +<link rel='contents' href='contents.html' title="Contents" /> +<link rel='last' href='about.html' title='About this document...' /> +<link rel='help' href='about.html' title='About this document...' /> +<link rel="prev" href="node6.html" /> +<link rel="parent" href="node3.html" /> +<link rel="next" href="node8.html" /> +<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> +<meta name='aesop' content='information' /> +<title>1.4 Basic Architectural Overview</title> +</head> +<body> +<div class="navigation"> +<div id='top-navigation-panel' xml:id='top-navigation-panel'> +<table align="center" width="100%" cellpadding="0" cellspacing="2"> +<tr> +<td class='online-navigation'><a rel="prev" title="1.3 a List's Web" + href="node6.html"><img src='previous.png' + border='0' height='32' alt='Previous Page' width='32' /></a></td> +<td class='online-navigation'><a rel="parent" title="1 introduction to GNU" + href="node3.html"><img src='up.png' + border='0' height='32' alt='Up one Level' width='32' /></a></td> +<td class='online-navigation'><a rel="next" title="2 the List Configuration" + href="node8.html"><img src='next.png' + border='0' height='32' alt='Next Page' width='32' /></a></td> +<td align="center" width="100%">GNU Mailman - List Administration Manual</td> +<td class='online-navigation'><a rel="contents" title="Table of Contents" + href="contents.html"><img src='contents.png' + border='0' height='32' alt='Contents' width='32' /></a></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +</tr></table> +<div class='online-navigation'> +<b class="navlabel">Previous:</b> +<a class="sectref" rel="prev" href="node6.html">1.3 A List's Web</a> +<b class="navlabel">Up:</b> +<a class="sectref" rel="parent" href="node3.html">1 Introduction to GNU</a> +<b class="navlabel">Next:</b> +<a class="sectref" rel="next" href="node8.html">2 The List Configuration</a> +</div> +<hr /></div> +</div> +<!--End of Navigation Panel--> + +<h2><a name="SECTION002140000000000000000"> +1.4 Basic Architectural Overview</a> +</h2> + +<p> +This section will outline the basic architecture of GNU Mailman, such +as how messages are processed by the sytem. Without going into lots +of detail, this information will help you understand how the +configuration options control Mailman's functionality. + +<p> +When mail enters the system from your mail server, it is dropped into +one of several Mailman <em>queues</em> depending on the address the +message was sent to. For example, if your system has a mailing list +named <var>mylist</var> and your domain is <var>example.com</var>, people can +post messages to your list by sending them to +<var>mylist@example.com</var>. These messages will be dropped into the +<em>incoming</em> queue, which is also colloquially called the +<em>moderate-and-munge</em> queue. The incoming queue is where most of +the approval process occurs, and it's also where the message is +prepared for sending out to the list membership. + +<p> +There are separate queues for the built-in archiver, the bounce +processor, the email command processor, as well as the outgoing email +and news queues. There's also a queue for messages generated by the +Mailman system. Each of these queues typically has one <em>queue +runner</em> (or ``qrunner'') that processes messages in the queue. The +qrunners are idle when there are no messages to process. + +<p> +Every message in the queues are represented by two files, a message +file and a metadata file. Both of these files share the same base +name, which is a combination of a unique hash and the Unix time that +the message was received. The metadata file has a suffix of +<span class="file">.db</span> and the message file has a suffix of either <span class="file">.msg</span> if +stored in plain text, or <span class="file">.pck</span> if stored in a more efficient +internal representation<a name="tex2html1" + href="#foot39"><sup>1</sup></a>. + +<p> +As a message moves through the incoming queue, it performs various +checks on the message, such as whether it matches one of the +moderation criteria, or contains disallowed MIME types. Once a +message is approved for sending to the list membership, the message is +prepared for sending by deleting, adding, or changing message headers, +adding footers, etc. Messages in the incoming queue may also be +stored for appending to digests. + +<p> +<br><hr><h4>Footnotes</h4> +<dl> +<dt><a name="foot39">... representation</a><A + HREF="node7.html#tex2html1"><sup>1</sup></a></dt> +<dd>Specifically, a Python pickle + +</dd> +</dl> +<div class="navigation"> +<div class='online-navigation'> +<p></p><hr /> +<table align="center" width="100%" cellpadding="0" cellspacing="2"> +<tr> +<td class='online-navigation'><a rel="prev" title="1.3 a List's Web" + href="node6.html"><img src='previous.png' + border='0' height='32' alt='Previous Page' width='32' /></a></td> +<td class='online-navigation'><a rel="parent" title="1 introduction to GNU" + href="node3.html"><img src='up.png' + border='0' height='32' alt='Up one Level' width='32' /></a></td> +<td class='online-navigation'><a rel="next" title="2 the List Configuration" + href="node8.html"><img src='next.png' + border='0' height='32' alt='Next Page' width='32' /></a></td> +<td align="center" width="100%">GNU Mailman - List Administration Manual</td> +<td class='online-navigation'><a rel="contents" title="Table of Contents" + href="contents.html"><img src='contents.png' + border='0' height='32' alt='Contents' width='32' /></a></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +</tr></table> +<div class='online-navigation'> +<b class="navlabel">Previous:</b> +<a class="sectref" rel="prev" href="node6.html">1.3 A List's Web</a> +<b class="navlabel">Up:</b> +<a class="sectref" rel="parent" href="node3.html">1 Introduction to GNU</a> +<b class="navlabel">Next:</b> +<a class="sectref" rel="next" href="node8.html">2 The List Configuration</a> +</div> +</div> +<hr /> +<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +</div> +<!--End of Navigation Panel--> + +</body> +</html> diff --git a/doc/mailman-admin/node8.html b/doc/mailman-admin/node8.html new file mode 100644 index 00000000..3a7fc7c8 --- /dev/null +++ b/doc/mailman-admin/node8.html @@ -0,0 +1,177 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> +<html> +<head> +<link rel="STYLESHEET" href="mailman-admin.css" type='text/css' /> +<link rel="first" href="mailman-admin.html" title='GNU mailman - list Administration Manual' /> +<link rel='contents' href='contents.html' title="Contents" /> +<link rel='last' href='about.html' title='About this document...' /> +<link rel='help' href='about.html' title='About this document...' /> +<link rel="next" href="node31.html" /> +<link rel="prev" href="node3.html" /> +<link rel="parent" href="contents.html" /> +<link rel="next" href="node9.html" /> +<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> +<meta name='aesop' content='information' /> +<title>2 The List Configuration Pages</title> +</head> +<body> +<div class="navigation"> +<div id='top-navigation-panel' xml:id='top-navigation-panel'> +<table align="center" width="100%" cellpadding="0" cellspacing="2"> +<tr> +<td class='online-navigation'><a rel="prev" title="1.4 basic Architectural Overview" + href="node7.html"><img src='previous.png' + border='0' height='32' alt='Previous Page' width='32' /></a></td> +<td class='online-navigation'><a rel="parent" title="Contents" + href="contents.html"><img src='up.png' + border='0' height='32' alt='Up one Level' width='32' /></a></td> +<td class='online-navigation'><a rel="next" title="2.1 the General Options" + href="node9.html"><img src='next.png' + border='0' height='32' alt='Next Page' width='32' /></a></td> +<td align="center" width="100%">GNU Mailman - List Administration Manual</td> +<td class='online-navigation'><a rel="contents" title="Table of Contents" + href="contents.html"><img src='contents.png' + border='0' height='32' alt='Contents' width='32' /></a></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +</tr></table> +<div class='online-navigation'> +<b class="navlabel">Previous:</b> +<a class="sectref" rel="prev" href="node7.html">1.4 Basic Architectural Overview</a> +<b class="navlabel">Up:</b> +<a class="sectref" rel="parent" href="contents.html">Contents</a> +<b class="navlabel">Next:</b> +<a class="sectref" rel="next" href="node9.html">2.1 The General Options</a> +</div> +<hr /></div> +</div> +<!--End of Navigation Panel--> + +<h1><a name="SECTION002200000000000000000"> +2 The List Configuration Pages</a> +</h1> + +<p> +After logging into the list configuration pages, you'll see the +configuration options for the list, grouped in categories. All the +administrative pages have some common elements. In the upper section, +you'll see two columns labeled ``Configuration Categories''. Some +categories have sub-categories which are only visible when you click +on the category link. The first page you see after logging in will be +the ``General Options'' category. The specific option settings for +each category are described below. + +<p> +On the right side of the top section, you'll see a column labeled +``Other Administrative Activities''. Here you'll find some other +things you can do to your list, as well as convenient links to the +list information page and the list archives. Note the big ``Logout'' +link; use this if you're finished configuring your list and don't want +to leave the session cookie active in your browser. + +<p> +Below this common header, you'll find a list of this category's +configuration variables, arranged in two columns. In the left column +is a brief description of the option, which also contains a +``details'' link. For many of the variables, more details are +available describing the semantics of the various available settings, +or information on the interaction between this setting and other list +options. Clicking on the details link brings up a page which contains +only the information for that option, as well as a button for +submitting your setting, and a link back to the category page. + +<p> +On the right side of the two-column section, you'll see the variable's +current value. Some variables may present a limited set of values, +via radio button or check box arrays. Other variables may present +text entry boxes of one or multiple lines. Most variables control +settings for the operation of the list, but others perform immediate +actions (these are clearly labeled). + +<p> +At the bottom of the page, you'll find a ``Submit'' button and a +footer with some more useful links and a few logos. Hitting the +submit button commits your list settings, after they've been +validated. Any invalid values will be ignored and an error message +will be displayed at the top of the resulting page. The results page +will always be the category page that you submitted. + +<p> + +<p><br /></p><hr class='online-navigation' /> +<div class='online-navigation'> +<!--Table of Child-Links--> +<a name="CHILD_LINKS"><strong>Subsections</strong></a> + +<ul class="ChildLinks"> +<li><a href="node9.html">2.1 The General Options Category</a> +<ul> +<li><a href="node10.html">2.1.1 General list personality</a> +<li><a href="node11.html">2.1.2 Reply-To header munging</a> +<li><a href="node12.html">2.1.3 Umbrella list settings</a> +<li><a href="node13.html">2.1.4 Notifications</a> +<li><a href="node14.html">2.1.5 Additional settings</a> +</ul> +<li><a href="node15.html">2.2 The Passwords Category</a> +<li><a href="node16.html">2.3 The Language Options Category</a> +<li><a href="node17.html">2.4 The Membership Management Category</a> +<li><a href="node18.html">2.5 The Non-digest Options Category</a> +<li><a href="node19.html">2.6 The Digest Options Category</a> +<li><a href="node20.html">2.7 The Privacy Options Category</a> +<ul> +<li><a href="node21.html">2.7.1 Subscription rules</a> +<li><a href="node22.html">2.7.2 Sender filters</a> +<li><a href="node23.html">2.7.3 Recipient Filters</a> +<li><a href="node24.html">2.7.4 Spam Filters</a> +</ul> +<li><a href="node25.html">2.8 The Bounce Processing Category</a> +<li><a href="node26.html">2.9 The Archiving Options Category</a> +<li><a href="node27.html">2.10 The Mail/News Gateway Category</a> +<li><a href="node28.html">2.11 The Auto-responder Category</a> +<li><a href="node29.html">2.12 The Content Filtering Category</a> +<li><a href="node30.html">2.13 The Topics Category</a> +</ul> +<!--End of Table of Child-Links--> +</div> + +<div class="navigation"> +<div class='online-navigation'> +<p></p><hr /> +<table align="center" width="100%" cellpadding="0" cellspacing="2"> +<tr> +<td class='online-navigation'><a rel="prev" title="1.4 basic Architectural Overview" + href="node7.html"><img src='previous.png' + border='0' height='32' alt='Previous Page' width='32' /></a></td> +<td class='online-navigation'><a rel="parent" title="Contents" + href="contents.html"><img src='up.png' + border='0' height='32' alt='Up one Level' width='32' /></a></td> +<td class='online-navigation'><a rel="next" title="2.1 the General Options" + href="node9.html"><img src='next.png' + border='0' height='32' alt='Next Page' width='32' /></a></td> +<td align="center" width="100%">GNU Mailman - List Administration Manual</td> +<td class='online-navigation'><a rel="contents" title="Table of Contents" + href="contents.html"><img src='contents.png' + border='0' height='32' alt='Contents' width='32' /></a></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +</tr></table> +<div class='online-navigation'> +<b class="navlabel">Previous:</b> +<a class="sectref" rel="prev" href="node7.html">1.4 Basic Architectural Overview</a> +<b class="navlabel">Up:</b> +<a class="sectref" rel="parent" href="contents.html">Contents</a> +<b class="navlabel">Next:</b> +<a class="sectref" rel="next" href="node9.html">2.1 The General Options</a> +</div> +</div> +<hr /> +<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +</div> +<!--End of Navigation Panel--> + +</body> +</html> diff --git a/doc/mailman-admin/node9.html b/doc/mailman-admin/node9.html new file mode 100644 index 00000000..6203bde9 --- /dev/null +++ b/doc/mailman-admin/node9.html @@ -0,0 +1,117 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> +<html> +<head> +<link rel="STYLESHEET" href="mailman-admin.css" type='text/css' /> +<link rel="first" href="mailman-admin.html" title='GNU mailman - list Administration Manual' /> +<link rel='contents' href='contents.html' title="Contents" /> +<link rel='last' href='about.html' title='About this document...' /> +<link rel='help' href='about.html' title='About this document...' /> +<link rel="next" href="node15.html" /> +<link rel="prev" href="node8.html" /> +<link rel="parent" href="node8.html" /> +<link rel="next" href="node10.html" /> +<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> +<meta name='aesop' content='information' /> +<title>2.1 The General Options Category</title> +</head> +<body> +<div class="navigation"> +<div id='top-navigation-panel' xml:id='top-navigation-panel'> +<table align="center" width="100%" cellpadding="0" cellspacing="2"> +<tr> +<td class='online-navigation'><a rel="prev" title="2 the List Configuration" + href="node8.html"><img src='previous.png' + border='0' height='32' alt='Previous Page' width='32' /></a></td> +<td class='online-navigation'><a rel="parent" title="2 the List Configuration" + href="node8.html"><img src='up.png' + border='0' height='32' alt='Up one Level' width='32' /></a></td> +<td class='online-navigation'><a rel="next" title="2.1.1 general list personality" + href="node10.html"><img src='next.png' + border='0' height='32' alt='Next Page' width='32' /></a></td> +<td align="center" width="100%">GNU Mailman - List Administration Manual</td> +<td class='online-navigation'><a rel="contents" title="Table of Contents" + href="contents.html"><img src='contents.png' + border='0' height='32' alt='Contents' width='32' /></a></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +</tr></table> +<div class='online-navigation'> +<b class="navlabel">Previous:</b> +<a class="sectref" rel="prev" href="node8.html">2 The List Configuration</a> +<b class="navlabel">Up:</b> +<a class="sectref" rel="parent" href="node8.html">2 The List Configuration</a> +<b class="navlabel">Next:</b> +<a class="sectref" rel="next" href="node10.html">2.1.1 General list personality</a> +</div> +<hr /></div> +</div> +<!--End of Navigation Panel--> + +<h2><a name="SECTION002210000000000000000"> +2.1 The General Options Category</a> +</h2> + +<p> +The General Options category is where you can set a variety of +variables that affect basic behavior and public information. In the +descriptions that follow, the variable name is given first, along with +an overview and a description of what that variable controls. + +<p> + +<p><br /></p><hr class='online-navigation' /> +<div class='online-navigation'> +<!--Table of Child-Links--> +<a name="CHILD_LINKS"><strong>Subsections</strong></a> + +<ul class="ChildLinks"> +<li><a href="node10.html">2.1.1 General list personality</a> +<li><a href="node11.html">2.1.2 Reply-To header munging</a> +<li><a href="node12.html">2.1.3 Umbrella list settings</a> +<li><a href="node13.html">2.1.4 Notifications</a> +<li><a href="node14.html">2.1.5 Additional settings</a> +</ul> +<!--End of Table of Child-Links--> +</div> + +<div class="navigation"> +<div class='online-navigation'> +<p></p><hr /> +<table align="center" width="100%" cellpadding="0" cellspacing="2"> +<tr> +<td class='online-navigation'><a rel="prev" title="2 the List Configuration" + href="node8.html"><img src='previous.png' + border='0' height='32' alt='Previous Page' width='32' /></a></td> +<td class='online-navigation'><a rel="parent" title="2 the List Configuration" + href="node8.html"><img src='up.png' + border='0' height='32' alt='Up one Level' width='32' /></a></td> +<td class='online-navigation'><a rel="next" title="2.1.1 general list personality" + href="node10.html"><img src='next.png' + border='0' height='32' alt='Next Page' width='32' /></a></td> +<td align="center" width="100%">GNU Mailman - List Administration Manual</td> +<td class='online-navigation'><a rel="contents" title="Table of Contents" + href="contents.html"><img src='contents.png' + border='0' height='32' alt='Contents' width='32' /></a></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +<td class='online-navigation'><img src='blank.png' + border='0' height='32' alt='' width='32' /></td> +</tr></table> +<div class='online-navigation'> +<b class="navlabel">Previous:</b> +<a class="sectref" rel="prev" href="node8.html">2 The List Configuration</a> +<b class="navlabel">Up:</b> +<a class="sectref" rel="parent" href="node8.html">2 The List Configuration</a> +<b class="navlabel">Next:</b> +<a class="sectref" rel="next" href="node10.html">2.1.1 General list personality</a> +</div> +</div> +<hr /> +<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +</div> +<!--End of Navigation Panel--> + +</body> +</html> diff --git a/doc/mailman-admin/previous.png b/doc/mailman-admin/previous.png Binary files differnew file mode 100644 index 00000000..497def42 --- /dev/null +++ b/doc/mailman-admin/previous.png diff --git a/doc/mailman-admin/pyfav.png b/doc/mailman-admin/pyfav.png Binary files differnew file mode 100644 index 00000000..d2d8669d --- /dev/null +++ b/doc/mailman-admin/pyfav.png diff --git a/doc/mailman-admin/up.png b/doc/mailman-admin/up.png Binary files differnew file mode 100644 index 00000000..a90e0284 --- /dev/null +++ b/doc/mailman-admin/up.png |
