diff options
Diffstat (limited to '')
197 files changed, 1542 insertions, 1512 deletions
diff --git a/doc/mailman-admin.dvi b/doc/mailman-admin.dvi Binary files differindex 6bf73dae..6b33597f 100644 --- a/doc/mailman-admin.dvi +++ b/doc/mailman-admin.dvi diff --git a/doc/mailman-admin.pdf b/doc/mailman-admin.pdf Binary files differindex 7ead51d6..2b86ba6f 100644 --- a/doc/mailman-admin.pdf +++ b/doc/mailman-admin.pdf diff --git a/doc/mailman-admin.ps b/doc/mailman-admin.ps index 863ea552..7dcf8084 100644 --- a/doc/mailman-admin.ps +++ b/doc/mailman-admin.ps @@ -1,7 +1,6 @@ %!PS-Adobe-2.0 -%%Creator: dvips(k) 5.96.1 Copyright 2007 Radical Eye Software +%%Creator: dvips(k) 5.95a Copyright 2005 Radical Eye Software %%Title: mailman-admin.dvi -%%CreationDate: Wed Dec 5 17:20:42 2007 %%Pages: 17 %%PageOrder: Ascend %%BoundingBox: 0 0 595 842 @@ -12,7 +11,7 @@ %DVIPSWebPage: (www.radicaleye.com) %DVIPSCommandLine: dvips -N0 -o mailman-admin.ps mailman-admin %DVIPSParameters: dpi=600 -%DVIPSSource: TeX output 2007.12.05:1720 +%DVIPSSource: TeX output 2008.04.21:1057 %%BeginProcSet: tex.pro 0 0 %! /TeXDict 300 dict def TeXDict begin/N{def}def/B{bind def}N/S{exch}N/X{S @@ -66,7 +65,7 @@ rmoveto}B/y{3 2 roll p a}B/bos{/SS save N}B/eos{SS restore}B end % author = "S. Rahtz, P. MacKay, Alan Jeffrey, B. Horn, K. Berry, % W. Schmidt, P. Lehman", % version = "2.0", -% date = "27nov06", +% date = "30 October 2002", % filename = "8r.enc", % email = "tex-fonts@@tug.org", % docstring = "This is the encoding vector for Type1 and TrueType @@ -176,7 +175,7 @@ rmoveto}B/y{3 2 roll p a}B/bos{/SS save N}B/eos{SS restore}B end /currency /yen /brokenbar /section /dieresis /copyright /ordfeminine /guillemotleft /logicalnot /hyphen /registered /macron -% 0xB0 +% 0xD0 /degree /plusminus /twosuperior /threesuperior /acute /mu /paragraph /periodcentered /cedilla /onesuperior /ordmasculine /guillemotright @@ -347,7 +346,7 @@ TeXDict begin 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 +b(arsa)n(w)3413 1213 y Fo(April)20 b(21,)g(2008)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 diff --git a/doc/mailman-admin.txt b/doc/mailman-admin.txt index 210fbec8..8f8a74c2 100644 --- a/doc/mailman-admin.txt +++ b/doc/mailman-admin.txt @@ -1,18 +1,19 @@ + #GNU mailman - list Administration Manual Contents About this document... About this document... Previous Page Up one Level Next Page GNU Mailman - List Administration - Manual - __________________________________________________________________ + Manual + _________________________________________________________________ GNU Mailman - List Administration Manual Barry A. Warsaw Release 2.1 - December 5, 2007 + April 21, 2008 - Front Matter + Front Matter Abstract: @@ -61,9 +62,9 @@ Contents 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. + 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 @@ -90,8 +91,8 @@ Contents * 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. + 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 @@ -101,9 +102,10 @@ Contents 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. + 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. @@ -118,13 +120,13 @@ Contents 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. + 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. + 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 @@ -145,8 +147,8 @@ Contents 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. + 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 @@ -171,8 +173,8 @@ Contents 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 + 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. @@ -180,8 +182,8 @@ Contents 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. + 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 @@ -196,52 +198,52 @@ Contents 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. + 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. + 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. + 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 + 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. + 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. + ``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. + 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 @@ -250,12 +252,12 @@ Contents 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. + 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 @@ -283,16 +285,16 @@ Contents 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). + 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. + 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 @@ -303,12 +305,12 @@ Contents 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. + 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 @@ -337,14 +339,14 @@ Contents 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. + 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. + 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 @@ -366,8 +368,8 @@ Contents * 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. + 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 @@ -395,9 +397,9 @@ Contents 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 + 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 @@ -413,8 +415,8 @@ Contents 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. + TBD. Note that umbrella lists are deprecated and will be replace with + a better mechanism for Mailman 3.0. 2.1.4 Notifications @@ -431,29 +433,29 @@ Contents 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. + 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. + 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, + 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. + 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. + 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 @@ -463,8 +465,8 @@ Contents receive into the goodbye_msg text box. send_goodbye_msg - This flag controls whether or not the goodbye message is sent to - unsubscribing members. + This flag controls whether or not the goodbye message is sent + to unsubscribing members. admin_immed_notify List moderators get notifications of pending administrative @@ -483,7 +485,8 @@ Contents 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. + gets a notice when their message is held for moderator + approval. 2.1.5 Additional settings @@ -497,82 +500,84 @@ Contents 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 + 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. + 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. + 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. + 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. + 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. + 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. + 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. + 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.) + 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 @@ -586,9 +591,9 @@ Contents 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). + 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 @@ -603,7 +608,8 @@ Contents 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. :) + 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 @@ -628,8 +634,8 @@ Contents 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. + 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 @@ -668,33 +674,33 @@ Contents 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 + 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. + 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. + 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. @@ -703,20 +709,21 @@ Contents 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. + 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. + 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. + 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 @@ -724,12 +731,12 @@ Contents 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. + 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: @@ -745,20 +752,21 @@ Description: An example of Mailman mailing lists and footers: real_name - This is the value of the real_name configuration variable in the - General options category. + 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. + 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. + 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. @@ -768,8 +776,8 @@ Description: An example of Mailman mailing lists 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. + 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 @@ -804,27 +812,27 @@ Description: An example of Mailman mailing 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 + 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. + 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. + 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 + 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. @@ -837,13 +845,14 @@ Description: An example of Mailman mailing lists 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. + 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. + 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 @@ -864,8 +873,8 @@ Description: An example of Mailman mailing lists 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 + 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 @@ -893,9 +902,9 @@ Description: An example of Mailman mailing lists 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. + 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 @@ -906,14 +915,14 @@ Description: An example of Mailman mailing lists * 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: + 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. + * 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. @@ -948,37 +957,38 @@ Description: An example of Mailman mailing lists 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. + + 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. + 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. + 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 + 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. @@ -1003,8 +1013,8 @@ Description: An example of Mailman mailing lists 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. + reduce the opportunity for email address harvesting by + spammers, although it probably doesn't eliminate it. 2.7.2 Sender filters @@ -1014,20 +1024,20 @@ Description: An example of Mailman mailing lists 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. + 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 + 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 @@ -1046,9 +1056,9 @@ Description: An example of Mailman mailing lists 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 + 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. @@ -1058,12 +1068,12 @@ Description: An example of Mailman mailing lists 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). + 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 @@ -1087,18 +1097,18 @@ Description: An example of Mailman mailing lists 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 + 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. + 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. + 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 @@ -1108,17 +1118,17 @@ Description: An example of Mailman mailing lists 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. + 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 + 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). @@ -1135,20 +1145,21 @@ Description: An example of Mailman mailing lists 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 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: + 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} @@ -1161,35 +1172,35 @@ Description: An example of Mailman mailing lists 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. + 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. + 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 + 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. + 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 @@ -1198,8 +1209,8 @@ Description: An example of Mailman mailing lists 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. + 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 @@ -1222,8 +1233,8 @@ Description: An example of Mailman mailing lists 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. + 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 @@ -1250,22 +1261,22 @@ Description: An example of Mailman mailing lists 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. + 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 + 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. + 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 @@ -1289,7 +1300,8 @@ Description: An example of Mailman mailing lists 1 This is an Appendix - To create an appendix in a Python HOWTO document, use markup like this: + To create an appendix in a Python HOWTO document, use markup like + this: \appendix @@ -1304,7 +1316,7 @@ Just add another \section{}, but don't say \appendix again. About this document ... - GNU Mailman - List Administration Manual, December 5, 2007, Release 2.1 + GNU Mailman - List Administration Manual, April 21, 2008, Release 2.1 This document was generated using the LaTeX2HTML translator. @@ -1316,7 +1328,7 @@ Just add another \section{}, but don't say \appendix again. 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 @@ -1338,15 +1350,15 @@ Just add another \section{}, but don't say \appendix again. 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. + 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 - __________________________________________________________________ + Manual + _________________________________________________________________ - Release 2.1, documentation updated on December 5, 2007. + Release 2.1, documentation updated on April 21, 2008. diff --git a/doc/mailman-admin/about.html b/doc/mailman-admin/about.html index 153099b2..42dbdf5e 100644 --- a/doc/mailman-admin/about.html +++ b/doc/mailman-admin/about.html @@ -48,7 +48,7 @@ About this document ...</a> </h1> <strong>GNU Mailman - List Administration Manual</strong>, -December 5, 2007, Release 2.1 +April 21, 2008, 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. @@ -104,7 +104,7 @@ December 5, 2007, Release 2.1 </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-admin/contents.html b/doc/mailman-admin/contents.html index 24113e68..c1154850 100644 --- a/doc/mailman-admin/contents.html +++ b/doc/mailman-admin/contents.html @@ -118,7 +118,7 @@ Contents</a> </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-admin/front.html b/doc/mailman-admin/front.html index b0977103..ec54bbf2 100644 --- a/doc/mailman-admin/front.html +++ b/doc/mailman-admin/front.html @@ -106,7 +106,7 @@ other manuals. </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-admin/index.html b/doc/mailman-admin/index.html index d79769ad..5b1cee5e 100644 --- a/doc/mailman-admin/index.html +++ b/doc/mailman-admin/index.html @@ -45,7 +45,7 @@ <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> +<strong>April 21, 2008</strong></p> <p></p> </div> </div> @@ -122,7 +122,7 @@ </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-admin/mailman-admin.html b/doc/mailman-admin/mailman-admin.html index d79769ad..5b1cee5e 100644 --- a/doc/mailman-admin/mailman-admin.html +++ b/doc/mailman-admin/mailman-admin.html @@ -45,7 +45,7 @@ <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> +<strong>April 21, 2008</strong></p> <p></p> </div> </div> @@ -122,7 +122,7 @@ </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-admin/node10.html b/doc/mailman-admin/node10.html index 29a6bb8d..dcdd4b05 100644 --- a/doc/mailman-admin/node10.html +++ b/doc/mailman-admin/node10.html @@ -191,7 +191,7 @@ Note that this option is simply an aid for anonymization, it </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-admin/node11.html b/doc/mailman-admin/node11.html index 665d5bfd..ea9b21f1 100644 --- a/doc/mailman-admin/node11.html +++ b/doc/mailman-admin/node11.html @@ -192,7 +192,7 @@ When you set this variable to <em>Explicit address</em>, the value </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-admin/node12.html b/doc/mailman-admin/node12.html index 1f4a69cc..de5724ae 100644 --- a/doc/mailman-admin/node12.html +++ b/doc/mailman-admin/node12.html @@ -92,7 +92,7 @@ a better mechanism for Mailman 3.0. </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-admin/node13.html b/doc/mailman-admin/node13.html index bbf848ce..f3aec581 100644 --- a/doc/mailman-admin/node13.html +++ b/doc/mailman-admin/node13.html @@ -176,7 +176,7 @@ Some people get annoyed with these monthly reminders, and they can </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-admin/node14.html b/doc/mailman-admin/node14.html index 99e91f28..9c40f16c 100644 --- a/doc/mailman-admin/node14.html +++ b/doc/mailman-admin/node14.html @@ -199,7 +199,7 @@ href="http://www.faqs.org/rfcs/rfc2369.html">RFC 2369</a>. However for some ann </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-admin/node15.html b/doc/mailman-admin/node15.html index db700d93..8661f058 100644 --- a/doc/mailman-admin/node15.html +++ b/doc/mailman-admin/node15.html @@ -112,7 +112,7 @@ password, be sure to fill in the <code>moderator</code> variable in the </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-admin/node16.html b/doc/mailman-admin/node16.html index fe00410f..88ba51a2 100644 --- a/doc/mailman-admin/node16.html +++ b/doc/mailman-admin/node16.html @@ -148,7 +148,7 @@ Note however, that if your mailing list receives both encoded and </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-admin/node17.html b/doc/mailman-admin/node17.html index df0e7232..48e5fb59 100644 --- a/doc/mailman-admin/node17.html +++ b/doc/mailman-admin/node17.html @@ -100,7 +100,7 @@ Management section. </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-admin/node18.html b/doc/mailman-admin/node18.html index 69795786..c6341bf1 100644 --- a/doc/mailman-admin/node18.html +++ b/doc/mailman-admin/node18.html @@ -310,7 +310,7 @@ way. </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-admin/node19.html b/doc/mailman-admin/node19.html index 75a5f53e..df40930f 100644 --- a/doc/mailman-admin/node19.html +++ b/doc/mailman-admin/node19.html @@ -218,7 +218,7 @@ digest. </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-admin/node20.html b/doc/mailman-admin/node20.html index 5205808d..fe9bbcc5 100644 --- a/doc/mailman-admin/node20.html +++ b/doc/mailman-admin/node20.html @@ -171,7 +171,7 @@ begins with a (caret) character. </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-admin/node21.html b/doc/mailman-admin/node21.html index 0db2153a..122d382b 100644 --- a/doc/mailman-admin/node21.html +++ b/doc/mailman-admin/node21.html @@ -196,7 +196,7 @@ list. </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-admin/node22.html b/doc/mailman-admin/node22.html index 62bbe43f..a31a728a 100644 --- a/doc/mailman-admin/node22.html +++ b/doc/mailman-admin/node22.html @@ -207,7 +207,7 @@ followed by holds, rejections, and discards). </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-admin/node23.html b/doc/mailman-admin/node23.html index eb6ab6c1..e6ecc381 100644 --- a/doc/mailman-admin/node23.html +++ b/doc/mailman-admin/node23.html @@ -125,7 +125,7 @@ If the list is not explicitly addressed and this setting is turned </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-admin/node24.html b/doc/mailman-admin/node24.html index 49951ddf..fcd5d0af 100644 --- a/doc/mailman-admin/node24.html +++ b/doc/mailman-admin/node24.html @@ -123,7 +123,7 @@ This line will match from 3 to 5 stars in the value of this </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-admin/node25.html b/doc/mailman-admin/node25.html index 48a42e3a..d0db1778 100644 --- a/doc/mailman-admin/node25.html +++ b/doc/mailman-admin/node25.html @@ -188,7 +188,7 @@ to the frequency and traffic volume of your list. </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-admin/node26.html b/doc/mailman-admin/node26.html index 1cb22484..cc5201b6 100644 --- a/doc/mailman-admin/node26.html +++ b/doc/mailman-admin/node26.html @@ -129,7 +129,7 @@ Note that senders can control whether their own posts are </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-admin/node27.html b/doc/mailman-admin/node27.html index 6388de8e..63ac39da 100644 --- a/doc/mailman-admin/node27.html +++ b/doc/mailman-admin/node27.html @@ -93,7 +93,7 @@ even be used to manage moderated newsgroups. </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-admin/node28.html b/doc/mailman-admin/node28.html index 1b6bce1e..c1a9b9d8 100644 --- a/doc/mailman-admin/node28.html +++ b/doc/mailman-admin/node28.html @@ -86,7 +86,7 @@ </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-admin/node29.html b/doc/mailman-admin/node29.html index 7fecbdf0..90062bdb 100644 --- a/doc/mailman-admin/node29.html +++ b/doc/mailman-admin/node29.html @@ -86,7 +86,7 @@ </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-admin/node3.html b/doc/mailman-admin/node3.html index e813a33f..0d640890 100644 --- a/doc/mailman-admin/node3.html +++ b/doc/mailman-admin/node3.html @@ -121,7 +121,7 @@ manual for more details. </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-admin/node30.html b/doc/mailman-admin/node30.html index 07c65bb5..be3c952e 100644 --- a/doc/mailman-admin/node30.html +++ b/doc/mailman-admin/node30.html @@ -87,7 +87,7 @@ </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-admin/node31.html b/doc/mailman-admin/node31.html index 52d177a2..b016e880 100644 --- a/doc/mailman-admin/node31.html +++ b/doc/mailman-admin/node31.html @@ -86,7 +86,7 @@ </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-admin/node32.html b/doc/mailman-admin/node32.html index 27f20051..28bc7364 100644 --- a/doc/mailman-admin/node32.html +++ b/doc/mailman-admin/node32.html @@ -86,7 +86,7 @@ </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-admin/node33.html b/doc/mailman-admin/node33.html index 335cb405..c30590e5 100644 --- a/doc/mailman-admin/node33.html +++ b/doc/mailman-admin/node33.html @@ -86,7 +86,7 @@ </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-admin/node34.html b/doc/mailman-admin/node34.html index fe7aec18..9628acba 100644 --- a/doc/mailman-admin/node34.html +++ b/doc/mailman-admin/node34.html @@ -90,7 +90,7 @@ </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-admin/node35.html b/doc/mailman-admin/node35.html index 0d64431c..3f6b6fae 100644 --- a/doc/mailman-admin/node35.html +++ b/doc/mailman-admin/node35.html @@ -105,7 +105,7 @@ Just add another \section{}, but don't say \appendix again. </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-admin/node4.html b/doc/mailman-admin/node4.html index 538cd6b8..af969bc4 100644 --- a/doc/mailman-admin/node4.html +++ b/doc/mailman-admin/node4.html @@ -152,7 +152,7 @@ older versions of Mailman. </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-admin/node5.html b/doc/mailman-admin/node5.html index 489d4a23..7e52eba4 100644 --- a/doc/mailman-admin/node5.html +++ b/doc/mailman-admin/node5.html @@ -118,7 +118,7 @@ necessary, we'll distinguish the list moderator explicitly. </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-admin/node6.html b/doc/mailman-admin/node6.html index eca800af..d217095c 100644 --- a/doc/mailman-admin/node6.html +++ b/doc/mailman-admin/node6.html @@ -127,7 +127,7 @@ do not need to re-login to access the administrative requests page. </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-admin/node7.html b/doc/mailman-admin/node7.html index 8f41bc68..0727d0b8 100644 --- a/doc/mailman-admin/node7.html +++ b/doc/mailman-admin/node7.html @@ -139,7 +139,7 @@ stored for appending to digests. </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-admin/node8.html b/doc/mailman-admin/node8.html index 3a7fc7c8..29781a69 100644 --- a/doc/mailman-admin/node8.html +++ b/doc/mailman-admin/node8.html @@ -169,7 +169,7 @@ will always be the category page that you submitted. </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-admin/node9.html b/doc/mailman-admin/node9.html index 6203bde9..dd68450e 100644 --- a/doc/mailman-admin/node9.html +++ b/doc/mailman-admin/node9.html @@ -109,7 +109,7 @@ an overview and a description of what that variable controls. </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-install.dvi b/doc/mailman-install.dvi Binary files differindex 80c5c1be..d3667653 100644 --- a/doc/mailman-install.dvi +++ b/doc/mailman-install.dvi diff --git a/doc/mailman-install.pdf b/doc/mailman-install.pdf Binary files differindex 6df47825..566dd984 100644 --- a/doc/mailman-install.pdf +++ b/doc/mailman-install.pdf diff --git a/doc/mailman-install.ps b/doc/mailman-install.ps index b2802765..2bcc25ca 100644 --- a/doc/mailman-install.ps +++ b/doc/mailman-install.ps @@ -1,7 +1,6 @@ %!PS-Adobe-2.0 -%%Creator: dvips(k) 5.96.1 Copyright 2007 Radical Eye Software +%%Creator: dvips(k) 5.95a Copyright 2005 Radical Eye Software %%Title: mailman-install.dvi -%%CreationDate: Wed Dec 5 17:20:46 2007 %%Pages: 27 %%PageOrder: Ascend %%BoundingBox: 0 0 595 842 @@ -12,7 +11,7 @@ %DVIPSWebPage: (www.radicaleye.com) %DVIPSCommandLine: dvips -N0 -o mailman-install.ps mailman-install %DVIPSParameters: dpi=600 -%DVIPSSource: TeX output 2007.12.05:1720 +%DVIPSSource: TeX output 2008.04.21:1057 %%BeginProcSet: tex.pro 0 0 %! /TeXDict 300 dict def TeXDict begin/N{def}def/B{bind def}N/S{exch}N/X{S @@ -66,7 +65,7 @@ rmoveto}B/y{3 2 roll p a}B/bos{/SS save N}B/eos{SS restore}B end % author = "S. Rahtz, P. MacKay, Alan Jeffrey, B. Horn, K. Berry, % W. Schmidt, P. Lehman", % version = "2.0", -% date = "27nov06", +% date = "30 October 2002", % filename = "8r.enc", % email = "tex-fonts@@tug.org", % docstring = "This is the encoding vector for Type1 and TrueType @@ -176,7 +175,7 @@ rmoveto}B/y{3 2 roll p a}B/bos{/SS save N}B/eos{SS restore}B end /currency /yen /brokenbar /section /dieresis /copyright /ordfeminine /guillemotleft /logicalnot /hyphen /registered /macron -% 0xB0 +% 0xD0 /degree /plusminus /twosuperior /threesuperior /acute /mu /paragraph /periodcentered /cedilla /onesuperior /ordmasculine /guillemotright @@ -364,8 +363,8 @@ TeXDict begin %%Page: 1 1 TeXDict begin 1 0 bop 0 83 3901 9 v 700 357 a Fz(GNU)57 b(Mailman)g(-)g(Installation)h(Man)n(ual)3368 504 y Fy(Release)30 -b(2.1)3153 859 y Fx(Barr)t(y)i(W)-5 b(arsa)n(w)3289 1213 -y Fw(December)19 b(5,)h(2007)3229 1360 y Fv(barr)r(y)g(\(at\))g(list)g +b(2.1)3153 859 y Fx(Barr)t(y)i(W)-5 b(arsa)n(w)3413 1213 +y Fw(April)20 b(21,)g(2008)3229 1360 y Fv(barr)r(y)g(\(at\))g(list)g (dot)g(org)1811 1581 y Fu(Abstract)208 1732 y Ft(This)30 b(document)j(describes)f(ho)n(w)g(to)f(install)f(GNU)h(Mailman)h(on)f (a)g(POSIX-based)g(system)h(such)g(as)h(U)t Fs(N)t(I)t(X)r diff --git a/doc/mailman-install.txt b/doc/mailman-install.txt index ab2f4af5..56a14b56 100644 --- a/doc/mailman-install.txt +++ b/doc/mailman-install.txt @@ -1,8 +1,9 @@ + #GNU mailman - installation Manual About this document... About this document... Previous Page Up one Level Next Page GNU Mailman - Installation Manual - __________________________________________________________________ + _________________________________________________________________ GNU Mailman - Installation Manual @@ -11,9 +12,9 @@ GNU Mailman - Installation Manual barry (at) list dot org Release 2.1 - December 5, 2007 + April 21, 2008 - Front Matter + Front Matter Abstract: @@ -26,8 +27,8 @@ GNU Mailman - Installation Manual 1 Installation Requirements - Please note that the information on this page may be out of date. Check - for the latest installation information on the Mailman wiki. + Please note that the information on this page may be out of date. + Check for the latest installation information on the Mailman wiki. GNU Mailman works on most POSIX-based systems such as Unix, MacOSX, or GNU/Linux. It does not currently work on Windows. You must have a mail @@ -43,7 +44,7 @@ GNU Mailman - Installation Manual system. As of this writing, Python 2.4.4 is recommended, but see the wiki page above for the latest information. - 2 Set up your system + 2 Set up your system Before installing Mailman, you need to prepare your system by adding certain users and groups. You will need to have root privileges to @@ -51,13 +52,13 @@ GNU Mailman - Installation Manual 2.1 Add the group and user - Mailman requires a unique user and group name which will own its files, - and under which its processes will run. Mailman's basic security is - based on group ownership permissions, so it's important to get this - step right^1. Typically, you will add a new user and a new group, both - called mailman. The mailman user must be a member of the mailman group. - Mailman will be installed under the mailman user and group, with the - set-group-id (setgid) bit enabled. + Mailman requires a unique user and group name which will own its + files, and under which its processes will run. Mailman's basic + security is based on group ownership permissions, so it's important to + get this step right^1. Typically, you will add a new user and a new + group, both called mailman. The mailman user must be a member of the + mailman group. Mailman will be installed under the mailman user and + group, with the set-group-id (setgid) bit enabled. If these names are already in use, you can choose different user and group names, as long as you remember these when you run configure. If @@ -74,22 +75,23 @@ GNU Mailman - Installation Manual 2.2 Create the installation directory - Typically, Mailman is installed into a single directory, which includes - both the Mailman source code and the run-time list and archive data. It - is possible to split the static program files from the variable data - files and install them in separate directories. This section will - describe the available options. + Typically, Mailman is installed into a single directory, which + includes both the Mailman source code and the run-time list and + archive data. It is possible to split the static program files from + the variable data files and install them in separate directories. This + section will describe the available options. The default is to install all of Mailman to /usr/local/mailman^2. You can change this base installation directory (referred to here as $prefix) by specifying the directory with the --prefix configure - option. If you're upgrading from a previous version of Mailman, you may - want to use the --prefix option unless you move your mailing lists. + option. If you're upgrading from a previous version of Mailman, you + may want to use the --prefix option unless you move your mailing + lists. Warning: You cannot install Mailman on a filesystem that is mounted - with the nosuid option. This will break Mailman, which relies on setgid - programs for its security. If this describes your environment, simply - install Mailman in a location that allows setgid programs. + with the nosuid option. This will break Mailman, which relies on + setgid programs for its security. If this describes your environment, + simply install Mailman in a location that allows setgid programs. Make sure the installation directory is set to group mailman (or whatever you're going to specify with --with-groupname) and has the @@ -122,15 +124,17 @@ GNU Mailman - Installation Manual permission to create a setgid file in the file system where it resides (NFS and other mounts can be configured to inhibit setgid settings). - If you've installed other GNU software, you should be familiar with the - configure script. Usually you can just cd to the directory you unpacked - the Mailman source tarball into, and run configure with no arguments: + If you've installed other GNU software, you should be familiar with + the configure script. Usually you can just cd to the directory you + unpacked the Mailman source tarball into, and run configure with no + arguments: % cd mailman-<version> % ./configure % make install - The following options allow you to customize your Mailman installation. + The following options allow you to customize your Mailman + installation. --prefix=dir Standard GNU configure option which changes the base directory @@ -139,8 +143,9 @@ GNU Mailman - Installation Manual set up as described in 2.2. --exec-prefix=dir - Standard GNU configure option which lets you specify a different - installation directory for architecture dependent binaries. + Standard GNU configure option which lets you specify a + different installation directory for architecture dependent + binaries. --with-var-prefix=dir Store mutable data under dir instead of under the $prefix or @@ -148,9 +153,9 @@ GNU Mailman - Installation Manual and list settings database. --with-python=/path/to/python - Specify an alternative Python interpreter to use for the wrapper - programs. The default is to use the interpreter found first on - your shell's $PATH. + Specify an alternative Python interpreter to use for the + wrapper programs. The default is to use the interpreter found + first on your shell's $PATH. --with-username=username-or-uid Specify a different username than mailman. The value of this @@ -188,11 +193,11 @@ GNU Mailman - Installation Manual Note: The proper value for this is dependent on your web server configuration. You must get this right, because the group id is - compiled into the CGI wrapper program for added security, and no - Mailman CGI scripts will run if this is incorrect. + compiled into the CGI wrapper program for added security, and + no Mailman CGI scripts will run if this is incorrect. - If you're using Apache, check the values for the Group option in - your httpd.conf file. + If you're using Apache, check the values for the Group option + in your httpd.conf file. --with-cgi-ext=extension Specify an extension for cgi-bin programs. The CGI wrappers @@ -254,17 +259,18 @@ GNU Mailman - Installation Manual You need to know what user your web server runs as. It may be www, apache, httpd or nobody, depending on your server's configuration. - 5 Set up your web server + 5 Set up your web server Congratulations! You've installed the Mailman software. To get everything running you need to hook Mailman up to both your web server and your mail system. - If you plan on running your mail and web servers on different machines, - sharing Mailman installations via NFS, be sure that the clocks on those - two machines are synchronized closely. You might take a look at the - file Mailman/LockFile.py; the constant CLOCK_SLOP helps the locking - mechanism compensate for clock skew in this type of environment. + If you plan on running your mail and web servers on different + machines, sharing Mailman installations via NFS, be sure that the + clocks on those two machines are synchronized closely. You might take + a look at the file Mailman/LockFile.py; the constant CLOCK_SLOP helps + the locking mechanism compensate for clock skew in this type of + environment. This section describes some of the things you need to do to connect Mailman's web interface to your web server. The instructions here are @@ -282,9 +288,9 @@ GNU Mailman - Installation Manual ScriptAlias /mailman/ $prefix/cgi-bin/ - Warning: You want to be very sure that the user id under which your CGI - scripts run is not in the mailman group you created above, otherwise - private archives will be accessible to anyone. + Warning: You want to be very sure that the user id under which your + CGI scripts run is not in the mailman group you created above, + otherwise private archives will be accessible to anyone. Copy the Mailman, Python, and GNU logos to a location accessible to your web server. E.g. with Apache, you've usually got an icons @@ -300,22 +306,22 @@ GNU Mailman - Installation Manual The default value for IMAGE_LOGOS is /icons/. Read the comment in Defaults.py.in for details. - Configure your web server to point to the Pipermail public mailing list - archives. For example, in Apache: + Configure your web server to point to the Pipermail public mailing + list archives. For example, in Apache: Alias /pipermail/ $varprefix/archives/public/ where $varprefix is usually $prefix unless you've used the --with-var-prefix option to configure. Also be sure to configure your - web server to follow symbolic links in this directory, otherwise public - Pipermail archives won't be accessible. For Apache users, consult the - FollowSymLinks option. + web server to follow symbolic links in this directory, otherwise + public Pipermail archives won't be accessible. For Apache users, + consult the FollowSymLinks option. - If you're going to be supporting internationalized public archives, you - will probably want to turn off any default charset directive for the - Pipermail directory, otherwise your multilingual archive pages won't - show up correctly. Here's an example for Apache, based on the standard - installation directories: + If you're going to be supporting internationalized public archives, + you will probably want to turn off any default charset directive for + the Pipermail directory, otherwise your multilingual archive pages + won't show up correctly. Here's an example for Apache, based on the + standard installation directories: <Directory "/usr/local/mailman/archives/public/"> AddDefaultCharset Off @@ -329,8 +335,8 @@ GNU Mailman - Installation Manual Mailman's email interface to your mail server. The instructions here are different for each mail server; if your mail server is not described in the following subsections, try to generalize from the - existing documentation, and consider contributing documentation updates - to the Mailman developers. + existing documentation, and consider contributing documentation + updates to the Mailman developers. 6.1 Using the Postfix mail server @@ -378,7 +384,6 @@ GNU Mailman - Installation Manual * Add this to the bottom of the $prefix/Mailman/mm_cfg.py file: MTA = 'Postfix' - The MTA variable names a module in the Mailman/MTA directory which contains the mail server-specific functions to be executed when a list is created or removed. @@ -401,7 +406,6 @@ GNU Mailman - Installation Manual * Hack your Postfix's main.cf file to include the following path in your alias_maps variable: /usr/local/mailman/data/aliases - Note that there should be no trailing .db. Do not include this in your alias_database variable. This is because you do not want Postfix's newaliases command to modify Mailman's aliases.db file, @@ -411,12 +415,11 @@ GNU Mailman - Installation Manual Here's an example: alias_maps = hash:/etc/postfix/aliases, hash:/usr/local/mailman/data/aliases - - * When you configure Mailman, use the --with-mail-gid=mailman switch; - this will be the default if you configured Mailman after adding the - mailman owner. Because the owner of the aliases.db file is mailman, - Postfix will execute Mailman's wrapper program as uid and gid - mailman. + * When you configure Mailman, use the --with-mail-gid=mailman + switch; this will be the default if you configured Mailman after + adding the mailman owner. Because the owner of the aliases.db file + is mailman, Postfix will execute Mailman's wrapper program as uid + and gid mailman. That's it! One caveat: when you add or remove a list, the aliases.db file will updated, but it will not automatically run postfix reload. @@ -455,14 +458,14 @@ GNU Mailman - Installation Manual Next, in your mm_cfg.py file, you will want to set the variable POSTFIX_STYLE_VIRTUAL_DOMAINS to the list of virtual domains that - Mailman should update. This may not be all of the virtual alias domains - that your Postfix installation supports! The values in this list will - be matched against the host_name attribute of mailing lists objects, - and must be an exact match. + Mailman should update. This may not be all of the virtual alias + domains that your Postfix installation supports! The values in this + list will be matched against the host_name attribute of mailing lists + objects, and must be an exact match. - Here's an example. Say that Postfix is configured to handle the virtual - domains dom1.ain, dom2.ain, and dom3.ain, and further that in your - main.cf file you've got the following settings: + Here's an example. Say that Postfix is configured to handle the + virtual domains dom1.ain, dom2.ain, and dom3.ain, and further that in + your main.cf file you've got the following settings: myhostname = mail.dom1.ain mydomain = dom1.ain @@ -495,8 +498,8 @@ GNU Mailman - Installation Manual POSTFIX_STYLE_VIRTUAL_DOMAINS = ['dom2.ain', 'dom3.ain'] - Now, any list that Mailman creates in either of those two domains, will - have the correct entries written to + Now, any list that Mailman creates in either of those two domains, + will have the correct entries written to /usr/local/mailman/data/virtual-mailman. As above with the data/aliases* files, you want to make sure that both @@ -512,16 +515,16 @@ GNU Mailman - Installation Manual * (English) http://listes.rezo.net/how.php This is a good (and simpler) alternative if you don't mind exposing an - additional hostname in the domain part of the addresses people will use - to contact your list. I.e. if people should use mylist@lists.dom.ain - instead of mylist@dom.ain. + additional hostname in the domain part of the addresses people will + use to contact your list. I.e. if people should use + mylist@lists.dom.ain instead of mylist@dom.ain. 6.2 Using the Exim mail server - Note: This section is derived from Nigel Metheringham's ``HOWTO - Using - Exim and Mailman together'', which covers Mailman 2.0.x and Exim 3. It - has been updated to cover Mailman 2.1 and Exim 4. The original document - is here: http://www.exim.org/howto/mailman.html. + Note: This section is derived from Nigel Metheringham's ``HOWTO - + Using Exim and Mailman together'', which covers Mailman 2.0.x and Exim + 3. It has been updated to cover Mailman 2.1 and Exim 4. The original + document is here: http://www.exim.org/howto/mailman.html. There is no Mailman configuration needed other than the standard options detailed in the Mailman install documentation. The Exim @@ -554,16 +557,16 @@ GNU Mailman - Installation Manual Note: The instructions in this document should work with either Exim 3 or Exim 4. In Exim 3, you must have a local_domains configuration - setting; in Exim 4, you most likely have a local_domains domainlist. If - you don't, you probably know what you're doing and can adjust + setting; in Exim 4, you most likely have a local_domains domainlist. + If you don't, you probably know what you're doing and can adjust accordingly. Similarly, in Exim 4 the concept of ``directors'' has disappeared - there are only routers now. So if you're using Exim 4, whenever this document says ``director'', read ``router''. Whether you are using Exim 3 or Exim 4, you will need to add some - macros to the main section of your Exim config file. You will also need - to define one new transport. With Exim 3, you'll need to add a new - director; with Exim 4, a new router plays the same role. + macros to the main section of your Exim config file. You will also + need to define one new transport. With Exim 3, you'll need to add a + new director; with Exim 4, a new router plays the same role. Finally, the configuration supplied here should allow co-habiting Mailman 2.0 and 2.1 installations, with the proviso that you'll @@ -572,8 +575,8 @@ GNU Mailman - Installation Manual 6.2.2 Main configuration settings - First, you need to add some macros to the top of your Exim config file. - These just make the director (router) and transport below a bit + First, you need to add some macros to the top of your Exim config + file. These just make the director (router) and transport below a bit cleaner. Obviously, you'll need to edit these based on how you configured and installed Mailman. @@ -627,10 +630,10 @@ GNU Mailman - Installation Manual 6.2.5 Router for Exim 4 In Exim 4, there's no such thing as directors - you need to add a new - router instead. Also, the canonical order of the configuration file was - changed so routers come before transports, so the router for Exim 4 - comes first here. Put this router somewhere after the ``begin routers'' - line of your config file, and remember that order matters. + router instead. Also, the canonical order of the configuration file + was changed so routers come before transports, so the router for Exim + 4 comes first here. Put this router somewhere after the ``begin + routers'' line of your config file, and remember that order matters. mailman_router: driver = accept @@ -652,44 +655,45 @@ GNU Mailman - Installation Manual Exim should be configured to allow reasonable volume - e.g. don't set max_recipients down to a silly value - and with normal degrees of security - specifically, be sure to allow relaying from 127.0.0.1, but - pretty much nothing else. Parallel deliveries and other tweaks can also - be used if you like; experiment with your setup to see what works. - Delay warning messages should be switched off or configured to only - happen for non-list mail, unless you like receiving tons of mail when - some random host is down. + pretty much nothing else. Parallel deliveries and other tweaks can + also be used if you like; experiment with your setup to see what + works. Delay warning messages should be switched off or configured to + only happen for non-list mail, unless you like receiving tons of mail + when some random host is down. 6.2.8 Problems * Mailman will send as many MAIL FROM/RCPT TO as it needs. It may result in more than 10 or 100 messages sent in one connection, which will exceed the default value of Exim's - smtp_accept_queue_per_connection value. This is bad because it will - cause Exim to switch into queue mode and severely delay delivery of - your list messages. The way to fix this is to set Mailman's - SMTP_MAX_SESSIONS_PER_CONNECTION (in $prefix/Mailman/mm_cfg.py) to - a smaller value than Exim's smtp_accept_queue_per_connection. - * Mailman should ignore Exim delay warning messages, even though Exim - should never send this to list messages. Mailman 2.1's general - bounce detection and VERP support should greatly improve the bounce - detector's hit rates. + smtp_accept_queue_per_connection value. This is bad because it + will cause Exim to switch into queue mode and severely delay + delivery of your list messages. The way to fix this is to set + Mailman's SMTP_MAX_SESSIONS_PER_CONNECTION (in + $prefix/Mailman/mm_cfg.py) to a smaller value than Exim's + smtp_accept_queue_per_connection. + * Mailman should ignore Exim delay warning messages, even though + Exim should never send this to list messages. Mailman 2.1's + general bounce detection and VERP support should greatly improve + the bounce detector's hit rates. * List existence is determined by the existence of a config.pck file for a list. If you delete lists by foul means, be aware of this. * If you are getting Exim or Mailman complaining about user ids when you send mail to a list, check that the MAILMAN_USER and - MAILMAN_GROUP match those of Mailman itself (i.e. what were used in - the configure script). Also make sure you do not have aliases in - the main alias file for the list. + MAILMAN_GROUP match those of Mailman itself (i.e. what were used + in the configure script). Also make sure you do not have aliases + in the main alias file for the list. 6.2.9 Receiver Verification Exim's receiver verification feature is very useful - it lets Exim - reject unrouteable addresses at SMTP time. However, this is most useful - for externally-originating mail that is addressed to mail in one of - your local domains. For Mailman list traffic, mail originates on your - server, and is addressed to random external domains that are not under - your control. Furthermore, each message is addressed to many recipients - - up to 500 if you use Mailman's default configuration and don't tweak - SMTP_MAX_RCPTS. + reject unrouteable addresses at SMTP time. However, this is most + useful for externally-originating mail that is addressed to mail in + one of your local domains. For Mailman list traffic, mail originates + on your server, and is addressed to random external domains that are + not under your control. Furthermore, each message is addressed to many + recipients - up to 500 if you use Mailman's default configuration and + don't tweak SMTP_MAX_RCPTS. Doing receiver verification on Mailman list traffic is a recipe for trouble. In particular, Exim will attempt to route every recipient @@ -729,8 +733,8 @@ GNU Mailman - Installation Manual bounces are themselves not bounceable. Thus, you might want to disable SMTP callback on bounce messages. - With Exim 4, you can accomplish this using something like the following - in your RCPT TO ACL: + With Exim 4, you can accomplish this using something like the + following in your RCPT TO ACL: # Accept bounces to lists even if callbacks or other checks would fail warn message = X-WhitelistedRCPT-nohdrfromcallback: Yes @@ -796,10 +800,10 @@ GNU Mailman - Installation Manual 6.2.13 List Verification - This is how a set of address tests for the Exim lists look on a working - system. The list in question is quixote-users@mems-exchange.org, and - these commands were run on the mems-exchange.org mail server ("% " - indicates the Unix shell prompt): + This is how a set of address tests for the Exim lists look on a + working system. The list in question is + quixote-users@mems-exchange.org, and these commands were run on the + mems-exchange.org mail server ("% " indicates the Unix shell prompt): % exim -bt quixote-users quixote-users@mems-exchange.org @@ -819,8 +823,8 @@ GNU Mailman - Installation Manual If your exim -bt output looks something like this, that's a start: at least it means Exim will pass the right messages to the right Mailman - commands. It by no means guarantees that your Exim/Mailman installation - is functioning perfectly, though! + commands. It by no means guarantees that your Exim/Mailman + installation is functioning perfectly, though! 6.2.14 Document History @@ -834,11 +838,11 @@ GNU Mailman - Installation Manual Warning: You may be tempted to set the DELIVERY_MODULE configuration variable in mm_cfg.py to 'Sendmail' when using the Sendmail mail server. Don't. The Sendmail.py module is misnamed - it's really a - command line based message handoff scheme as opposed to the SMTP scheme - used in SMTPDirect.py (the default). Sendmail.py has known security - holes and is provided as a proof-of-concept only^4. If you are having - problems using SMTPDirect.py fix those instead of using Sendmail.py, or - you may open your system up to security exploits. + command line based message handoff scheme as opposed to the SMTP + scheme used in SMTPDirect.py (the default). Sendmail.py has known + security holes and is provided as a proof-of-concept only^4. If you + are having problems using SMTPDirect.py fix those instead of using + Sendmail.py, or you may open your system up to security exploits. 6.3.1 Sendmail ``smrsh'' compatibility @@ -846,9 +850,9 @@ GNU Mailman - Installation Manual utility called ``smrsh'', which limits the executables that Sendmail will allow to be used as mail programs. You need to explicitly allow Mailman's wrapper program to be used with smrsh or Mailman will not - work. If mail is not getting delivered to Mailman's wrapper program and - you're getting an ``operating system error'' in your mail syslog, this - could be your problem. + work. If mail is not getting delivered to Mailman's wrapper program + and you're getting an ``operating system error'' in your mail syslog, + this could be your problem. One good way of enabling this is: @@ -857,11 +861,12 @@ GNU Mailman - Installation Manual * Figure out where smrsh expects symlinks for allowable mail programs. At the very beginning of the following output you will - see a full path to some directory, e.g. /var/adm/sm.bin or similar: + see a full path to some directory, e.g. /var/adm/sm.bin or + similar: % strings $path_to_smrsh | less - * cd into /var/adm/sm.bin, or where ever it happens to reside on your - system - alternatives include /etc/smrsh, /var/smrsh and + * cd into /var/adm/sm.bin, or where ever it happens to reside on + your system - alternatives include /etc/smrsh, /var/smrsh and /usr/local/smrsh. % cd /var/adm/sm.bin @@ -872,8 +877,8 @@ GNU Mailman - Installation Manual David Champion has contributed a recipe for more closely integrating Sendmail and Mailman, such that Sendmail will automatically recognize - and deliver to new mailing lists as they are created, without having to - manually edit alias tables. + and deliver to new mailing lists as they are created, without having + to manually edit alias tables. In the contrib directory of Mailman's source distribution, you will find four files: @@ -886,27 +891,27 @@ GNU Mailman - Installation Manual 6.3.3 Performance notes One of the surest performance killers for Sendmail users is when - Sendmail is configured to synchronously verify the recipient's host via - DNS. If it does this for messages posted to it from Mailman, you will - get horrible performance. Since Mailman usually connects via localhost - (i.e. 127.0.0.1) to the SMTP port of Sendmail, you should be sure to - configure Sendmail to not do DNS verification synchronously for - localhost connections. + Sendmail is configured to synchronously verify the recipient's host + via DNS. If it does this for messages posted to it from Mailman, you + will get horrible performance. Since Mailman usually connects via + localhost (i.e. 127.0.0.1) to the SMTP port of Sendmail, you should be + sure to configure Sendmail to not do DNS verification synchronously + for localhost connections. 6.4 Using the Qmail mail server - There are some issues that users of the qmail mail transport agent have - encountered. None of the core maintainers use qmail, so all of this - information has been contributed by the Mailman user community, - especially Martin Preishuber and Christian Tismer, with notes by Balazs - Nagy (BN) and Norbert Bollow (NB). + There are some issues that users of the qmail mail transport agent + have encountered. None of the core maintainers use qmail, so all of + this information has been contributed by the Mailman user community, + especially Martin Preishuber and Christian Tismer, with notes by + Balazs Nagy (BN) and Norbert Bollow (NB). * You might need to set the mail-gid user to either qmail, mailman, or nofiles by using the --with-mail-gid configure option. BN: it highly depends on your mail storing policy. For example if you use the simple ~alias/.qmail-* files, you can use `id -g - alias`. But if you use /var/qmail/users, the specified mail gid can - be used. + alias`. But if you use /var/qmail/users, the specified mail gid + can be used. If you are going to be directing virtual domains directly to the mailman user (using ``virtualdomains'' on a list-only domain, for example), you will have to use --with-mail-gid=gid of mailman @@ -915,18 +920,17 @@ GNU Mailman - Installation Manual * If there is a user mailman on your system, the alias mailman-owner will work only in ~mailman. You have to do a touch .qmail-owner in ~mailman directory to create this alias. - NB: An alternative, IMHO better solution is to chown root ~mailman, - that will stop qmail from considering mailman to be a user to whom - mail can be delivered. (See ``man 8 qmail-getpw''.) - * In a related issue, if you have any users with the same name as one - of your mailing lists, you will have problems if list names contain - "-" in them. Putting .qmail redirections into the user's home - directory doesn't work because the Mailman wrappers will not get - spawned with the proper GID. The solution is to put the following - lines in the /var/qmail/users/assign file: + NB: An alternative, IMHO better solution is to chown root + ~mailman, that will stop qmail from considering mailman to be a + user to whom mail can be delivered. (See ``man 8 qmail-getpw''.) + * In a related issue, if you have any users with the same name as + one of your mailing lists, you will have problems if list names + contain "-" in them. Putting .qmail redirections into the user's + home directory doesn't work because the Mailman wrappers will not + get spawned with the proper GID. The solution is to put the + following lines in the /var/qmail/users/assign file: +zope-:alias:112:11:/var/qmail/alias:-:zope-: . - where in this case the listname is e.g. zope-users. NB: Alternatively, you could host the lists on a virtual domain, and use the /var/qmail/control/virtualdomains file to put the @@ -948,30 +952,26 @@ GNU Mailman - Installation Manual Then make your aliases: .qmail => mailman@...'s letters .qmail-owner => mailman-owner's letters - For list aliases, you can either create them manually: .qmail-list => posts to the 'list' list .qmail-list-admin => posts to the 'list's owner .qmail-list-request => requests to 'list' etc - or for automatic list alias handling (when using the lists.kva.hu virtual as above), see contrib/qmail-to-mailman.py in the Mailman - source distribution. Modify the ~mailman/.qmail-default to include: + source distribution. Modify the ~mailman/.qmail-default to + include: |preline /path/to/python /path/to/qmail-to-mailman.py - and new lists will automatically be picked up. * You have to make sure that the localhost can relay. If you start qmail via inetd and tcpenv, you need some line the following in your /etc/hosts.allow file: tcp-env: 127. 10.205.200. : setenv RELAYCLIENT - where 10.205.200. is your IP address block. If you use tcpserver, then you need something like the following in your /etc/tcp.smtp file: 10.205.200.:allow,RELAYCLIENT="" 127.:allow,RELAYCLIENT="" - * BN: Bigger /var/qmail/control/concurrencyremote values work better sending outbound messages, within reason. Unless you know your system can handle it (many if not most cannot) this should not be @@ -980,8 +980,8 @@ GNU Mailman - Installation Manual in the qmail documentation. BN: Last but not least, here's a little script to generate aliases to - your lists (if for some reason you can/will not have them automatically - picked up using contrib/qmail-to-mailman.py): + your lists (if for some reason you can/will not have them + automatically picked up using contrib/qmail-to-mailman.py): This script is for the Mailman 2.0 series: @@ -1007,22 +1007,22 @@ if [ $# = 1 ]; then echo Making links to $i in the current directory... echo "|preline /usr/local/mailman/mail/mailman post $i" > .qmail-$i echo "|preline /usr/local/mailman/mail/mailman admin $i" > .qmail-$i-admin - echo "|preline /usr/local/mailman/mail/mailman bounces $i" > .qmail-$i-bounc -es + echo "|preline /usr/local/mailman/mail/mailman bounces $i" > .qmail-$i-boun +ces # The following line is for VERP - # echo "|preline /usr/local/mailman/mail/mailman bounces $i" > .qmail-$i-bou -nces-default - echo "|preline /usr/local/mailman/mail/mailman confirm $i" > .qmail-$i-confi -rm + # echo "|preline /usr/local/mailman/mail/mailman bounces $i" > .qmail-$i-bo +unces-default + echo "|preline /usr/local/mailman/mail/mailman confirm $i" > .qmail-$i-conf +irm echo "|preline /usr/local/mailman/mail/mailman join $i" > .qmail-$i-join echo "|preline /usr/local/mailman/mail/mailman leave $i" > .qmail-$i-leave echo "|preline /usr/local/mailman/mail/mailman owner $i" > .qmail-$i-owner - echo "|preline /usr/local/mailman/mail/mailman request $i" > .qmail-$i-reque -st - echo "|preline /usr/local/mailman/mail/mailman subscribe $i" > .qmail-$i-sub -scribe - echo "|preline /usr/local/mailman/mail/mailman unsubscribe $i" > .qmail-$i-u -nsubscribe + echo "|preline /usr/local/mailman/mail/mailman request $i" > .qmail-$i-requ +est + echo "|preline /usr/local/mailman/mail/mailman subscribe $i" > .qmail-$i-su +bscribe + echo "|preline /usr/local/mailman/mail/mailman unsubscribe $i" > .qmail-$i- +unsubscribe fi 6.4.1 Information on VERP @@ -1038,8 +1038,8 @@ fi The second option is a patch on SourceForge located at: - http://sourceforge.net/tracker/?func=detail&atid=300103&aid=645513&grou - p_id=103 + http://sourceforge.net/tracker/?func=detail&atid=300103&aid=645513&gro + up_id=103 This patch currently needs more testing and might best be suitable for developers or people well familiar with qmail. Having said that, this @@ -1051,10 +1051,11 @@ fi As mentioned in the 6.4 section for a virtual mail server, a patch under testing is located at: - http://sf.net/tracker/index.php?func=detail&aid=621257&group_id=103&ati - d=300103 + http://sf.net/tracker/index.php?func=detail&aid=621257&group_id=103&at + id=300103 - Again, this patch is for people familiar with their qmail installation. + Again, this patch is for people familiar with their qmail + installation. 6.4.3 More information @@ -1065,8 +1066,8 @@ fi 7 Review your site defaults - Mailman has a large number of site-wide configuration options which you - should now review and change according to your needs. Some of the + Mailman has a large number of site-wide configuration options which + you should now review and change according to your needs. Some of the options control how Mailman interacts with your environment, and other options select defaults for newly created lists^5. There are system tuning parameters and integration options. @@ -1130,14 +1131,14 @@ fi % crontab -u mailman crontab.in If you used the --with-username option, use that user name instead of - mailman for the -u argument value. If your crontab does not support the - -u option, try these commands: + mailman for the -u argument value. If your crontab does not support + the -u option, try these commands: % cd $prefix/cron % su - mailman % crontab crontab.in - 10 Start the Mailman qrunner + 10 Start the Mailman qrunner Mailman depends on a process called the ``qrunner'' to delivery all email messages it sees. You must start the qrunner by executing the @@ -1184,12 +1185,13 @@ fi % cd ../rc6.d % ln -s ../init.d/mailman K12mailman - 11 Check the hostname settings + 11 Check the hostname settings - You should check the values for DEFAULT_EMAIL_HOST and DEFAULT_URL_HOST - in Defaults.py. Make any necessary changes in the mm_cfg.py file, not - in the Defaults.py file. If you change either of these two values, - you'll want to add the following afterwards in the mm_cfg.py file: + You should check the values for DEFAULT_EMAIL_HOST and + DEFAULT_URL_HOST in Defaults.py. Make any necessary changes in the + mm_cfg.py file, not in the Defaults.py file. If you change either of + these two values, you'll want to add the following afterwards in the + mm_cfg.py file: add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST) @@ -1201,15 +1203,15 @@ fi There are two site-wide passwords that you can create from the command line, using the bin/mmsitepass script. The first is the ``site password'' which can be used anywhere a password is required in the - system. The site password will get you into the administration page for - any list, and it can be used to log in as any user. Think root for a - Unix system, so pick this password wisely! + system. The site password will get you into the administration page + for any list, and it can be used to log in as any user. Think root for + a Unix system, so pick this password wisely! The second password is a site-wide ``list creator'' password. You can use this to delegate the ability to create new mailing lists without - providing all the privileges of the site password. Of course, the owner - of the site password can also create new mailing lists, but the list - creator password is limited to just that special role. + providing all the privileges of the site password. Of course, the + owner of the site password can also create new mailing lists, but the + list creator password is limited to just that special role. To set the site password, use this command: @@ -1219,25 +1221,25 @@ fi % $prefix/bin/mmsitepass -c <list-creator-password> - It is okay not to set a list creator password, but you probably do want - a site password. + It is okay not to set a list creator password, but you probably do + want a site password. 13 Create your first mailing list For more detailed information about using Mailman, including creating and configuring mailing lists, see the Mailman List Adminstration - Manual. These instructions provide a quick guide to creating your first - mailing list via the web interface: + Manual. These instructions provide a quick guide to creating your + first mailing list via the web interface: * Start by visiting the url http://my.dom.ain/mailman/create. * Fill out the form as described in the on-screen instructions, and in the ``List creator's password'' field, type the password you - entered in section 7. Type your own email address for the ``Initial - list owner address'', and select ``Yes'' to notify the list - administrator. + entered in section 7. Type your own email address for the + ``Initial list owner address'', and select ``Yes'' to notify the + list administrator. * Click on the ``Create List'' button. - * Check your email for a message from Mailman informing you that your - new mailing list was created. + * Check your email for a message from Mailman informing you that + your new mailing list was created. * Now visit the list's administration page, either by following the link on the confirmation web page or clicking on the link from the email Mailman just sent you. Typically the url will be something @@ -1255,12 +1257,12 @@ fi mailing list. If you had any problems along the way, please see the 14 section. - 14 Troubleshooting + 14 Troubleshooting If you encounter problems with running Mailman, first check the question and answer section below. If your problem is not covered - there, check the online help, including the FAQ and the interactive FAQ - wizard. + there, check the online help, including the FAQ and the interactive + FAQ wizard. Also check for errors in your syslog files, your mail and web server log files and in Mailman's $prefix/logs/error file. If you're still @@ -1276,8 +1278,8 @@ fi Here is a list of some common questions and answers: * Problem: All Mailman web pages give a 404 File not found error. - Solution: Your web server has not been set up properly for handling - Mailman's CGI programs. Make sure you have: + Solution: Your web server has not been set up properly for + handling Mailman's CGI programs. Make sure you have: 1. configured the web server to give permissions to $prefix/cgi-bin 2. restarted the web server properly. @@ -1285,26 +1287,25 @@ fi do check these issues. * Problem: All Mailman web pages give an "Internal Server Error". Solution: The likely problem is that you are using the wrong user - or group for the CGI scripts. Check your web server's log files. If - you see a line like + or group for the CGI scripts. Check your web server's log files. + If you see a line like Attempt to exec script with invalid gid 51, expected 99 - - you will need to reinstall Mailman, specifying the proper CGI group - id, as described in the section. - * Problem: I send mail to the list, and get back mail saying the list - is not found! + you will need to reinstall Mailman, specifying the proper CGI + group id, as described in the section. + * Problem: I send mail to the list, and get back mail saying the + list is not found! Solution: You probably didn't add the necessary aliases to the system alias database, or you didn't properly integrate Mailman with your mail server. Perhaps you didn't update the alias - database, or your system requires you to run newaliases explicitly. - Refer to your server specific instructions in the 6 section. + database, or your system requires you to run newaliases + explicitly. Refer to your server specific instructions in the 6 + section. * Problem: I send mail to the list, and get back mail saying, ``unknown mailer error''. Solution: The likely problem is that you are using the wrong user or group id for the mail wrappers. Check your mail server's log files; if you see a line like Attempt to exec script with invalid gid 51, expected 99 - you will need to reinstall Mailman, specifying the proper mail group id as described in the section. * Problem: I use Postfix as my mail server and the mail wrapper @@ -1327,21 +1328,22 @@ fi and add the link there. Note further any aliases newaliases spits out will need to be adjusted to point to the secure link to the wrapper. - * Problem: I messed up when I called configure. How do I clean things - up and re-install? + * Problem: I messed up when I called configure. How do I clean + things up and re-install? Solution: % make clean % ./configure --with-the-right-options % make install - 15 Platform and operating system notes + 15 Platform and operating system notes - Generally, Mailman runs on any POSIX-based system, such as Solaris, the - various BSD variants, Linux systems, MacOSX, and other generic Unix - systems. It doesn't run on Windows. For the most part, the generic - instructions given in this document should be sufficient to get Mailman - working on any supported platform. Some operating systems have - additional recommended installation or configuration instructions. + Generally, Mailman runs on any POSIX-based system, such as Solaris, + the various BSD variants, Linux systems, MacOSX, and other generic + Unix systems. It doesn't run on Windows. For the most part, the + generic instructions given in this document should be sufficient to + get Mailman working on any supported platform. Some operating systems + have additional recommended installation or configuration + instructions. 15.1 GNU/Linux issues @@ -1358,9 +1360,9 @@ fi build as the mailman user, you need to be sure mailman is in the cctools group. * If you installed Python from your Linux distribution's package - manager (e.g. .rpms for Redhat-derived systems or .deb for Debian), - you must install the ``development'' package of Python, or you may - not get everything you need. + manager (e.g. .rpms for Redhat-derived systems or .deb for + Debian), you must install the ``development'' package of Python, + or you may not get everything you need. For example, using Python 2.2 on Debian, you will need to install the python2.2-dev package. On Redhat, you probably need the python2-devel package. @@ -1372,7 +1374,6 @@ fi import paths ImportError: No module named paths make: *** [update] Error 1 - If this happens, install the Python development package and try configure and make install again. Or install the latest version of Python from source, available from http://www.python.org. @@ -1408,8 +1409,8 @@ fi http://www.afp548.com/Articles/mail/python-mailman.html * Kathleen Webb posted her experiences in getting Mailman running on Jaguar using Sendmail. - http://mail.python.org/pipermail/mailman-users/2002-October/022944. - html + http://mail.python.org/pipermail/mailman-users/2002-October/022944 + .html * Panther server (MacOSX 10.3) comes with Mailman; Your operating system should contain documentation that will help you, and Apple has a tech document about a problem you might encounter running @@ -1423,26 +1424,26 @@ fi installation. Users of earlier versions of Mac OSX contains Sendmail and those users should look at the Sendmail installation section for tips. You should follow the basic installation steps as described - earlier in this manual, substituting as appropriate, the steps outlined - in this section. + earlier in this manual, substituting as appropriate, the steps + outlined in this section. By default, Mac OSX 10.3 'client' version does not have a fully - functional version of Postfix. Setting up a working MTA such as Postfix - is beyond the scope of this guide and you should refer to - http://www.postfix.org for tips on getting Postfix running. An easy way - to set Postfix up is to install and run Postfix Enabler, a stand-alone - tool for configuring Postfix on Mac OSX, available from + functional version of Postfix. Setting up a working MTA such as + Postfix is beyond the scope of this guide and you should refer to + http://www.postfix.org for tips on getting Postfix running. An easy + way to set Postfix up is to install and run Postfix Enabler, a + stand-alone tool for configuring Postfix on Mac OSX, available from http://www.roadstead.com/weblog/Tutorials/PostfixEnabler.html. - Likewise, Mac OSX 'client' version from 10.1 onwards includes a working - Apache webserver. This is switched on using the System Preferences - control panel under the 'Sharing tab'. A useful tool for configuring - the Apache on Mac OSX is Webmin, which can be obtained from - http://www.webmin.com. + Likewise, Mac OSX 'client' version from 10.1 onwards includes a + working Apache webserver. This is switched on using the System + Preferences control panel under the 'Sharing tab'. A useful tool for + configuring the Apache on Mac OSX is Webmin, which can be obtained + from http://www.webmin.com. - Webmin can also perform configuration for other system tasks, including - Postfix, adding jobs to your crontab, adding user and groups, plus - adding startup and shutdown jobs. + Webmin can also perform configuration for other system tasks, + including Postfix, adding jobs to your crontab, adding user and + groups, plus adding startup and shutdown jobs. In a stock installation of OSX, the requirement for Mailman is to have Python installed. Python is not installed by default, so it is advised @@ -1453,7 +1454,8 @@ fi will come in handy at a later date should you need other tools. The developer's tools are also know by the name XCode tools. - As a minimum, the Python version should be 2.2, but 2.3 is recommended. + As a minimum, the Python version should be 2.2, but 2.3 is + recommended. If you wish to add a user and group using the command line in OSX instead of via Webmin or another GUI interface, open your terminal @@ -1501,7 +1503,7 @@ tar xvf MailmanStartup.tar About this document ... - GNU Mailman - Installation Manual, December 5, 2007, Release 2.1 + GNU Mailman - Installation Manual, April 21, 2008, Release 2.1 This document was generated using the LaTeX2HTML translator. @@ -1513,7 +1515,7 @@ tar xvf MailmanStartup.tar 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 @@ -1522,23 +1524,24 @@ tar xvf MailmanStartup.tar installation is complete. .../usr/local/mailman^2 - This is the default for Mailman 2.1. Earlier versions of Mailman - installed everything under /home/mailman by default. + This is the default for Mailman 2.1. Earlier versions of + Mailman installed everything under /home/mailman by default. ... set^3 BSD users should see the 15.2 section for additional information. ... only^4 - In fact, in later versions of Mailman, this module is explicitly - sabotaged. You have to know what you're doing in order to - re-enable it. + In fact, in later versions of Mailman, this module is + explicitly sabotaged. You have to know what you're doing in + order to re-enable it. ... lists^5 - In general, changing the list defaults described in this section - will not affect any already created lists. To make changes after - a list has been created, use the web interface or the command - line scripts, such as bin/withlist and bin/config_list. + In general, changing the list defaults described in this + section will not affect any already created lists. To make + changes after a list has been created, use the web interface or + the command line scripts, such as bin/withlist and + bin/config_list. ... time^6 Note that if you're upgrading from a previous version of @@ -1550,9 +1553,9 @@ tar xvf MailmanStartup.tar ... list^7 You must subscribe to this mailing list in order to post to it, but the mailing list's archives are publicly visible. - __________________________________________________________________ + _________________________________________________________________ Previous Page Up one Level Next Page GNU Mailman - Installation Manual - __________________________________________________________________ + _________________________________________________________________ - Release 2.1, documentation updated on December 5, 2007. + Release 2.1, documentation updated on April 21, 2008. diff --git a/doc/mailman-install/about.html b/doc/mailman-install/about.html index 04ba5851..46336a70 100644 --- a/doc/mailman-install/about.html +++ b/doc/mailman-install/about.html @@ -46,7 +46,7 @@ About this document ...</a> </h1> <strong>GNU Mailman - Installation Manual</strong>, -December 5, 2007, Release 2.1 +April 21, 2008, 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. @@ -101,7 +101,7 @@ December 5, 2007, Release 2.1 </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-install/bsd-issues.html b/doc/mailman-install/bsd-issues.html index 932283e2..82fd910e 100644 --- a/doc/mailman-install/bsd-issues.html +++ b/doc/mailman-install/bsd-issues.html @@ -106,7 +106,7 @@ This disables the <b class="program">chmod g+s</b> command on installed director </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-install/create-install-dir.html b/doc/mailman-install/create-install-dir.html index e152c25f..a912cf09 100644 --- a/doc/mailman-install/create-install-dir.html +++ b/doc/mailman-install/create-install-dir.html @@ -141,7 +141,7 @@ for additional information. </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-install/customizing.html b/doc/mailman-install/customizing.html index 8600d093..77c8af5e 100644 --- a/doc/mailman-install/customizing.html +++ b/doc/mailman-install/customizing.html @@ -131,7 +131,7 @@ line scripts, such as <b class="program">bin/withlist</b> and <b class="program" </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-install/exim3-transport.html b/doc/mailman-install/exim3-transport.html index f9e25d1f..a9b2903b 100644 --- a/doc/mailman-install/exim3-transport.html +++ b/doc/mailman-install/exim3-transport.html @@ -105,7 +105,7 @@ i.e. somewhere between the first and second ``end'' line: </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-install/front.html b/doc/mailman-install/front.html index 6a068b19..6617134f 100644 --- a/doc/mailman-install/front.html +++ b/doc/mailman-install/front.html @@ -174,7 +174,7 @@ The GNU Mailman website is at <a class="url" href="http://www.list.org">http://w </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-install/index.html b/doc/mailman-install/index.html index 6fd98aca..bd4818a4 100644 --- a/doc/mailman-install/index.html +++ b/doc/mailman-install/index.html @@ -46,7 +46,7 @@ <p><b><font size="+2">Barry Warsaw</font></b></p> <p><span class="email">barry (at) list dot org</span></p> <p><strong>Release 2.1</strong><br /> -<strong>December 5, 2007</strong></p> +<strong>April 21, 2008</strong></p> <p></p> </div> </div> @@ -127,7 +127,7 @@ </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-install/mail-server.html b/doc/mailman-install/mail-server.html index 0621792b..742538d2 100644 --- a/doc/mailman-install/mail-server.html +++ b/doc/mailman-install/mail-server.html @@ -137,7 +137,7 @@ contributing documentation updates to the Mailman developers. </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-install/mailman-install.html b/doc/mailman-install/mailman-install.html index 6fd98aca..bd4818a4 100644 --- a/doc/mailman-install/mailman-install.html +++ b/doc/mailman-install/mailman-install.html @@ -46,7 +46,7 @@ <p><b><font size="+2">Barry Warsaw</font></b></p> <p><span class="email">barry (at) list dot org</span></p> <p><strong>Release 2.1</strong><br /> -<strong>December 5, 2007</strong></p> +<strong>April 21, 2008</strong></p> <p></p> </div> </div> @@ -127,7 +127,7 @@ </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-install/node10.html b/doc/mailman-install/node10.html index ad9dd805..78a478b0 100644 --- a/doc/mailman-install/node10.html +++ b/doc/mailman-install/node10.html @@ -185,7 +185,7 @@ Now restart your web server. </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-install/node12.html b/doc/mailman-install/node12.html index 14461325..01f2861f 100644 --- a/doc/mailman-install/node12.html +++ b/doc/mailman-install/node12.html @@ -136,7 +136,7 @@ virtual domain support below. </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-install/node13.html b/doc/mailman-install/node13.html index 301d090b..3a29619e 100644 --- a/doc/mailman-install/node13.html +++ b/doc/mailman-install/node13.html @@ -199,7 +199,7 @@ tables. </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-install/node15.html b/doc/mailman-install/node15.html index e5f597f4..ec621ef0 100644 --- a/doc/mailman-install/node15.html +++ b/doc/mailman-install/node15.html @@ -103,7 +103,7 @@ instead of <code>mylist@dom.ain</code>. </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-install/node16.html b/doc/mailman-install/node16.html index 2349f89d..33033492 100644 --- a/doc/mailman-install/node16.html +++ b/doc/mailman-install/node16.html @@ -124,7 +124,7 @@ those in the config fragments given below. </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-install/node17.html b/doc/mailman-install/node17.html index a133470b..0e178ac0 100644 --- a/doc/mailman-install/node17.html +++ b/doc/mailman-install/node17.html @@ -144,7 +144,7 @@ and 2.1 installations, with the proviso that you'll probably want to use </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-install/node18.html b/doc/mailman-install/node18.html index 191dea51..214e3310 100644 --- a/doc/mailman-install/node18.html +++ b/doc/mailman-install/node18.html @@ -103,7 +103,7 @@ you'll need to edit these based on how you configured and installed Mailman. </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-install/node2.html b/doc/mailman-install/node2.html index 64be98be..24e3e010 100644 --- a/doc/mailman-install/node2.html +++ b/doc/mailman-install/node2.html @@ -122,7 +122,7 @@ but see the wiki page above for the latest information. </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-install/node20.html b/doc/mailman-install/node20.html index b024c716..5ec34a7e 100644 --- a/doc/mailman-install/node20.html +++ b/doc/mailman-install/node20.html @@ -107,7 +107,7 @@ aliasfile director, or vice-versa. </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-install/node21.html b/doc/mailman-install/node21.html index 63bd2949..d4795c42 100644 --- a/doc/mailman-install/node21.html +++ b/doc/mailman-install/node21.html @@ -104,7 +104,7 @@ file, and remember that order matters. </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-install/node22.html b/doc/mailman-install/node22.html index 2c4549b5..56e96a5e 100644 --- a/doc/mailman-install/node22.html +++ b/doc/mailman-install/node22.html @@ -90,7 +90,7 @@ transports'' line of your Exim config file. </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-install/node23.html b/doc/mailman-install/node23.html index 582b11cf..1f59171c 100644 --- a/doc/mailman-install/node23.html +++ b/doc/mailman-install/node23.html @@ -94,7 +94,7 @@ mail, unless you like receiving tons of mail when some random host is down. </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-install/node24.html b/doc/mailman-install/node24.html index fa81b346..dc20c8a4 100644 --- a/doc/mailman-install/node24.html +++ b/doc/mailman-install/node24.html @@ -120,7 +120,7 @@ </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-install/node25.html b/doc/mailman-install/node25.html index ec01107d..96148363 100644 --- a/doc/mailman-install/node25.html +++ b/doc/mailman-install/node25.html @@ -127,7 +127,7 @@ from non-127.0.0.1 hosts, but it should do the trick for Mailman.) </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-install/node26.html b/doc/mailman-install/node26.html index 5f960845..a4e8db90 100644 --- a/doc/mailman-install/node26.html +++ b/doc/mailman-install/node26.html @@ -132,7 +132,7 @@ this in your <code>DATA</code> ACL: </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-install/node27.html b/doc/mailman-install/node27.html index fa2cb7fa..432cf084 100644 --- a/doc/mailman-install/node27.html +++ b/doc/mailman-install/node27.html @@ -102,7 +102,7 @@ In a nutshell, all you need to do to enable VERP with Exim is to add these lines </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-install/node28.html b/doc/mailman-install/node28.html index 6e408a2c..c1b9933f 100644 --- a/doc/mailman-install/node28.html +++ b/doc/mailman-install/node28.html @@ -114,7 +114,7 @@ and change your transport like this: </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-install/node29.html b/doc/mailman-install/node29.html index d90d55aa..1ea78249 100644 --- a/doc/mailman-install/node29.html +++ b/doc/mailman-install/node29.html @@ -116,7 +116,7 @@ functioning perfectly, though! </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-install/node3.html b/doc/mailman-install/node3.html index 80a6e488..f4b1d176 100644 --- a/doc/mailman-install/node3.html +++ b/doc/mailman-install/node3.html @@ -102,7 +102,7 @@ in this section. </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-install/node30.html b/doc/mailman-install/node30.html index d9f17f63..b00dc244 100644 --- a/doc/mailman-install/node30.html +++ b/doc/mailman-install/node30.html @@ -90,7 +90,7 @@ Overhauled/reformatted/clarified/simplified by Greg Ward </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-install/node31.html b/doc/mailman-install/node31.html index 91efe99c..33efb15b 100644 --- a/doc/mailman-install/node31.html +++ b/doc/mailman-install/node31.html @@ -121,7 +121,7 @@ what you're doing in order to re-enable it. </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-install/node32.html b/doc/mailman-install/node32.html index 87298699..5852e73d 100644 --- a/doc/mailman-install/node32.html +++ b/doc/mailman-install/node32.html @@ -140,7 +140,7 @@ One good way of enabling this is: </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-install/node33.html b/doc/mailman-install/node33.html index bfc3de5a..62f70672 100644 --- a/doc/mailman-install/node33.html +++ b/doc/mailman-install/node33.html @@ -108,7 +108,7 @@ find four files: </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-install/node34.html b/doc/mailman-install/node34.html index 84b3b2cd..fb546437 100644 --- a/doc/mailman-install/node34.html +++ b/doc/mailman-install/node34.html @@ -93,7 +93,7 @@ connections. </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-install/node36.html b/doc/mailman-install/node36.html index 36cdafc6..a0f46501 100644 --- a/doc/mailman-install/node36.html +++ b/doc/mailman-install/node36.html @@ -108,7 +108,7 @@ is the more qmail-friendly approach resulting in large performance gains. </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-install/node37.html b/doc/mailman-install/node37.html index ce29c2db..3ea518e1 100644 --- a/doc/mailman-install/node37.html +++ b/doc/mailman-install/node37.html @@ -94,7 +94,7 @@ Again, this patch is for people familiar with their qmail installation. </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-install/node38.html b/doc/mailman-install/node38.html index 6df2f96c..03480c12 100644 --- a/doc/mailman-install/node38.html +++ b/doc/mailman-install/node38.html @@ -90,7 +90,7 @@ Bollow has written about Mailman and qmail, available here: </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-install/node4.html b/doc/mailman-install/node4.html index a764dca8..07f3e2d9 100644 --- a/doc/mailman-install/node4.html +++ b/doc/mailman-install/node4.html @@ -122,7 +122,7 @@ installation is complete. </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-install/node40.html b/doc/mailman-install/node40.html index de4883e2..3d84b6e5 100644 --- a/doc/mailman-install/node40.html +++ b/doc/mailman-install/node40.html @@ -122,7 +122,7 @@ You should also subscribe yourself to the site list. </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-install/node41.html b/doc/mailman-install/node41.html index 7ffbb5e8..ba4b9e7c 100644 --- a/doc/mailman-install/node41.html +++ b/doc/mailman-install/node41.html @@ -124,7 +124,7 @@ parallel Mailman installations. </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-install/node42.html b/doc/mailman-install/node42.html index db06e877..cbfdcd20 100644 --- a/doc/mailman-install/node42.html +++ b/doc/mailman-install/node42.html @@ -151,7 +151,7 @@ following set of commands: </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-install/node43.html b/doc/mailman-install/node43.html index 972475c9..73914b7f 100644 --- a/doc/mailman-install/node43.html +++ b/doc/mailman-install/node43.html @@ -101,7 +101,7 @@ existing lists. </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-install/node44.html b/doc/mailman-install/node44.html index 2e7793fd..b35db425 100644 --- a/doc/mailman-install/node44.html +++ b/doc/mailman-install/node44.html @@ -120,7 +120,7 @@ password. </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-install/node45.html b/doc/mailman-install/node45.html index c8a8f8c5..d6330510 100644 --- a/doc/mailman-install/node45.html +++ b/doc/mailman-install/node45.html @@ -146,7 +146,7 @@ list. If you had any problems along the way, please see the </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-install/node47.html b/doc/mailman-install/node47.html index f99bb93b..687a23a7 100644 --- a/doc/mailman-install/node47.html +++ b/doc/mailman-install/node47.html @@ -105,7 +105,7 @@ recommended installation or configuration instructions. </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-install/node48.html b/doc/mailman-install/node48.html index 1412727c..a1fac2d5 100644 --- a/doc/mailman-install/node48.html +++ b/doc/mailman-install/node48.html @@ -147,7 +147,7 @@ This problem can manifest itself in other Linux distributions in </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-install/node50.html b/doc/mailman-install/node50.html index e977fa3e..94cee9d7 100644 --- a/doc/mailman-install/node50.html +++ b/doc/mailman-install/node50.html @@ -221,7 +221,7 @@ start up. </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-install/node6.html b/doc/mailman-install/node6.html index 286eacf7..a7dd98b5 100644 --- a/doc/mailman-install/node6.html +++ b/doc/mailman-install/node6.html @@ -98,7 +98,7 @@ </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-install/node7.html b/doc/mailman-install/node7.html index e4d08890..2c09fdc3 100644 --- a/doc/mailman-install/node7.html +++ b/doc/mailman-install/node7.html @@ -243,7 +243,7 @@ If you're using Apache, check the values for the <var>Group</var> option in </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-install/node8.html b/doc/mailman-install/node8.html index 1ff3838b..5abca67c 100644 --- a/doc/mailman-install/node8.html +++ b/doc/mailman-install/node8.html @@ -88,7 +88,7 @@ Once you've run <b class="program">configure</b>, you can simply run <b class="p </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-install/node9.html b/doc/mailman-install/node9.html index e08e4f38..079f838f 100644 --- a/doc/mailman-install/node9.html +++ b/doc/mailman-install/node9.html @@ -139,7 +139,7 @@ configuration. </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-install/postfix-virtual.html b/doc/mailman-install/postfix-virtual.html index 4191fe11..17e84ef7 100644 --- a/doc/mailman-install/postfix-virtual.html +++ b/doc/mailman-install/postfix-virtual.html @@ -189,7 +189,7 @@ group owned by <code>mailman</code>. </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-install/qmail-issues.html b/doc/mailman-install/qmail-issues.html index 25948d95..eb20f259 100644 --- a/doc/mailman-install/qmail-issues.html +++ b/doc/mailman-install/qmail-issues.html @@ -301,7 +301,7 @@ fi </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-install/troubleshooting.html b/doc/mailman-install/troubleshooting.html index 6b994ed1..9f1ce366 100644 --- a/doc/mailman-install/troubleshooting.html +++ b/doc/mailman-install/troubleshooting.html @@ -252,7 +252,7 @@ publicly visible. </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-member-es.dvi b/doc/mailman-member-es.dvi Binary files differindex 8d96afb5..ccc4836c 100644 --- a/doc/mailman-member-es.dvi +++ b/doc/mailman-member-es.dvi diff --git a/doc/mailman-member-es.pdf b/doc/mailman-member-es.pdf Binary files differindex 90ea543d..b4e3ff36 100644 --- a/doc/mailman-member-es.pdf +++ b/doc/mailman-member-es.pdf diff --git a/doc/mailman-member-es.ps b/doc/mailman-member-es.ps index e264a56c..ff89cb52 100644 --- a/doc/mailman-member-es.ps +++ b/doc/mailman-member-es.ps @@ -1,7 +1,6 @@ %!PS-Adobe-2.0 -%%Creator: dvips(k) 5.96.1 Copyright 2007 Radical Eye Software +%%Creator: dvips(k) 5.95a Copyright 2005 Radical Eye Software %%Title: mailman-member-es.dvi -%%CreationDate: Wed Dec 5 17:20:51 2007 %%Pages: 22 %%PageOrder: Ascend %%BoundingBox: 0 0 595 842 @@ -12,7 +11,7 @@ %DVIPSWebPage: (www.radicaleye.com) %DVIPSCommandLine: dvips -N0 -o mailman-member-es.ps mailman-member-es %DVIPSParameters: dpi=600 -%DVIPSSource: TeX output 2007.12.05:1720 +%DVIPSSource: TeX output 2008.04.21:1058 %%BeginProcSet: tex.pro 0 0 %! /TeXDict 300 dict def TeXDict begin/N{def}def/B{bind def}N/S{exch}N/X{S @@ -66,7 +65,7 @@ rmoveto}B/y{3 2 roll p a}B/bos{/SS save N}B/eos{SS restore}B end % author = "S. Rahtz, P. MacKay, Alan Jeffrey, B. Horn, K. Berry, % W. Schmidt, P. Lehman", % version = "2.0", -% date = "27nov06", +% date = "30 October 2002", % filename = "8r.enc", % email = "tex-fonts@@tug.org", % docstring = "This is the encoding vector for Type1 and TrueType @@ -176,7 +175,7 @@ rmoveto}B/y{3 2 roll p a}B/bos{/SS save N}B/eos{SS restore}B end /currency /yen /brokenbar /section /dieresis /copyright /ordfeminine /guillemotleft /logicalnot /hyphen /registered /macron -% 0xB0 +% 0xD0 /degree /plusminus /twosuperior /threesuperior /acute /mu /paragraph /periodcentered /cedilla /onesuperior /ordmasculine /guillemotright @@ -411,7 +410,7 @@ TeXDict begin TeXDict begin 1 0 bop 0 83 3901 9 v 2603 342 a Fn(GNU)58 b(Mailman)1018 506 y(Man)n(ual)e(del)h(Suscr)s(iptor)g(de)g(Listas)3368 676 y Fm(Release)30 b(2.1)3408 1031 y Fl(T)-14 b(err)r(i)32 -b(Oda)3121 1385 y Fk(5)20 b(de)g(diciembre)f(de)h(2007)3225 +b(Oda)3259 1385 y Fk(21)20 b(de)g(abril)g(de)g(2008)3225 1532 y(terri\(en\)zone12.com)1803 1735 y Fj(Resumen)208 1874 y Fi(Este)i(documento)j(describe)f(el)f(interf)o(az)g(del)g (suscriptor)h(de)g(listas)e(GNU)h(Mailman)h(2.1.)f(Este)f(manual)i @@ -581,23 +580,23 @@ b(\264)-35 b(on)17 b(o)f(subsecci)7 b(\264)-35 b(on)16 b(que)g(necesite,)h(donde)e(encuentrar)5 b(\264)-33 b(a)15 b(referencias)g(a)i(otras)g(secciones,)f(en)h(caso)g(de)f(ser)i (necesario)0 3890 y(o)i(de)g(potencial)g(utilidad.)0 -4037 y Fh(Nota:)k Fk(P)o(ara)h(los)g(prop)7 b(\264)-35 -b(ositos)24 b(de)h(este)h(documento,)c(se)k(asume)f(que)g(el)g(lector)g -(est)5 b(\264)-33 b(a)26 b(f)o(amiliarizado)d(con)i(t)5 -b(\264)-33 b(erminos)24 b(comunes)g(rela-)0 4137 y(cionados)16 -b(con)i(correo)e(electr)7 b(\264)-35 b(onico)16 b(\(por)g(ejemplo:)h(L) -n(\264)-26 b(\021nea)18 b(de)f(Asunto,)g(cuerpo)f(del)i(mensaje\))f(y)h -(sitios)g(web)g(\(por)e(ejemplo:)h(cuadro)0 4236 y(de)24 -b(lista)g(desple)o(gable,)e(bot)7 b(\264)-35 b(on\),)22 -b(o)i(los)g(puede)e(consultar)-5 b(.)23 b(T)-7 b(ambi)5 -b(\264)-33 b(en)23 b(se)i(asume)e(que)g(el)i(lector)e(ya)h(puede)e -(usar)i(lo)g(su\002cientemente)0 4336 y(bien)h(su)i(programa)c(de)j -(correo)f(electr)7 b(\264)-35 b(onico)24 b(y)i(na)n(v)o(e)o(gador)d -(web,)i(de)h(tal)g(forma)f(que)h(sean)g(claras)g(las)g(instrucciones)f -(tales)i(como)0 4435 y(\223en)m(v)n(\264)-26 b(\021e)16 -b(correo)g(electr)7 b(\264)-35 b(onico)16 b(a)i(esta)g(direcci)7 -b(\264)-35 b(on\224)15 b(o)j(\223visite)g(esta)g(p)5 -b(\264)-33 b(agina)16 b(web\224)h(o)g(\223rellene)g(el)h(formulario)d +4037 y Fh(Nota:)e Fk(P)o(ara)h(los)h(prop)7 b(\264)-35 +b(ositos)17 b(de)i(este)h(documento,)d(se)i(asume)g(que)g(el)h(lector)e +(est)5 b(\264)-33 b(a)20 b(f)o(amiliarizado)e(con)g(t)5 +b(\264)-33 b(erminos)19 b(comunes)e(relacio-)0 4137 y(nados)23 +b(con)g(correo)f(electr)7 b(\264)-35 b(onico)22 b(\(por)h(ejemplo:)g(L) +n(\264)-26 b(\021nea)23 b(de)g(Asunto,)g(cuerpo)f(del)i(mensaje\))f(y)h +(sitios)g(web)g(\(por)e(ejemplo:)h(cuadro)0 4236 y(de)h(lista)g(desple) +o(gable,)e(bot)7 b(\264)-35 b(on\),)22 b(o)i(los)g(puede)e(consultar)-5 +b(.)23 b(T)-7 b(ambi)5 b(\264)-33 b(en)23 b(se)i(asume)e(que)g(el)i +(lector)e(ya)h(puede)e(usar)i(lo)g(su\002cientemente)0 +4336 y(bien)h(su)i(programa)c(de)j(correo)f(electr)7 +b(\264)-35 b(onico)24 b(y)i(na)n(v)o(e)o(gador)d(web,)i(de)h(tal)g +(forma)f(que)h(sean)g(claras)g(las)g(instrucciones)f(tales)i(como)0 +4435 y(\223en)m(v)n(\264)-26 b(\021e)16 b(correo)g(electr)7 +b(\264)-35 b(onico)16 b(a)i(esta)g(direcci)7 b(\264)-35 +b(on\224)15 b(o)j(\223visite)g(esta)g(p)5 b(\264)-33 +b(agina)16 b(web\224)h(o)g(\223rellene)g(el)h(formulario)d (proporcionado\224.)e(Si)18 b(usted)0 4535 y(no)j(est)5 b(\264)-33 b(a)23 b(f)o(amiliarizado)d(con)h(estas)i(acciones,)e(usted) g(puede)g(desear)g(consultar)g(otra)g(documentaci)7 b(\264)-35 @@ -761,25 +760,25 @@ b Fk(El)31 b(nombre)d(del)j(servidor)e(web)h(que)g(gestiona)f(el)i (mismo)208 1725 y(utilizado)19 b(como)g(DOMINIO,)g(y)i(a)f(menudo)f(se) i(re\002ere)e(a)i(la)g(misma)f(m)5 b(\264)-33 b(aquina,)18 b(pero)i(no)f(tiene)h(que)g(ser)h(id)5 b(\264)-33 b(entico.)0 -1955 y(Como)40 b(ejemplo)f(de)h(la)g(vida)g(real,)g(si)h(usted)e(est)5 -b(\264)-33 b(a)41 b(interesado)e(en)h(la)h(lista)g(de)e(usuarios)h -(mailman)f(\(mailman-users\),)e(ust-)0 2055 y(ed)g(realizar)n(\264)-26 -b(\021a)37 b(las)h(siguientes)f(sustituciones:)g(NOMBRELIST)-8 -b(A=mailman-users,)35 b(DOMINIO=p)o(ython.or)o(g,)d(SER)-7 -b(VIDOR-)0 2155 y(WEB=mail.p)o(ython.or)o(g.)14 b(De)k(esta)h(forma,)e -(para)h(la)g(lista)h(de)f(correo)f Fe(mailman-users@p)n(ython.org)p -Fk(,)c(la)19 b(p)5 b(\264)-33 b(agina)17 b(de)h(informaci)7 -b(\264)-35 b(on)16 b(de)0 2254 y(esa)26 b(lista)g(se)f(encontrar)n -(\264)-26 b(\021a)23 b(en)i(la)h(direcci)7 b(\264)-35 -b(on)23 b(URL)j Fe(http://mail.p)n(ython.org/)o(mail)o(man/)o(listi)o -(nf)m(o/mai)o(lma)o(n-u)o(sers)20 b Fk(\(estas,)26 b(a)f(diferencia)0 -2354 y(de)20 b(la)h(mayor)n(\264)-26 b(\021a)19 b(de)h(ejemplos)f -(datos)h(en)g(este)h(documento,)d(son)i(direcciones)f(reales\).)0 -2501 y(La)28 b(mayor)n(\264)-26 b(\021a)26 b(de)h(las)h(listas)h(tendr) -5 b(\264)-33 b(an)26 b(esta)i(informaci)7 b(\264)-35 -b(on)24 b(almacenada)i(en)h(las)i(cabeceras)d Fe(List-*:)p -Fk(.)h(Muchos)f(programs)g(de)h(correo)0 2600 y(ocultar)5 -b(\264)-33 b(an)22 b(estas)i(cabeceras)f(por)f(omisi)7 +1955 y(Como)41 b(ejemplo)f(de)i(la)g(vida)f(real,)g(si)h(usted)f(est)5 +b(\264)-33 b(a)42 b(interesado)f(en)g(la)h(lista)g(de)f(usuarios)g +(mailman)g(\(mailman-users\),)e(us-)0 2055 y(ted)j(realizar)n(\264)-26 +b(\021a)41 b(las)i(siguientes)f(sustituciones:)f(NOMBRELIST)-8 +b(A=mailman-users,)40 b(DOMINIO=p)o(ython.or)o(g,)c(SER)-7 +b(VIDO-)0 2155 y(R)i(WEB=mail.p)o(ython.or)o(g.)18 b(De)k(esta)h +(forma,)d(para)h(la)h(lista)h(de)f(correo)e Fe(mailman-users@p)n +(ython.org)p Fk(,)d(la)22 b(p)5 b(\264)-33 b(agina)21 +b(de)g(informaci)7 b(\264)-35 b(on)0 2254 y(de)16 b(esa)h(lista)h(se)f +(encontrar)n(\264)-26 b(\021a)14 b(en)i(la)h(direcci)7 +b(\264)-35 b(on)15 b(URL)i Fe(http://mail.p)n(ython.org/)o(mail)o(man/) +o(listi)o(nf)m(o/mai)o(lma)o(n-u)o(sers)12 b Fk(\(estas,)k(a)h +(diferencia)0 2354 y(de)j(la)h(mayor)n(\264)-26 b(\021a)19 +b(de)h(ejemplos)f(datos)h(en)g(este)h(documento,)d(son)i(direcciones)f +(reales\).)0 2501 y(La)28 b(mayor)n(\264)-26 b(\021a)26 +b(de)h(las)h(listas)h(tendr)5 b(\264)-33 b(an)26 b(esta)i(informaci)7 +b(\264)-35 b(on)24 b(almacenada)i(en)h(las)i(cabeceras)d +Fe(List-*:)p Fk(.)h(Muchos)f(programs)g(de)h(correo)0 +2600 y(ocultar)5 b(\264)-33 b(an)22 b(estas)i(cabeceras)f(por)f(omisi)7 b(\264)-35 b(on,)23 b(as)n(\264)-26 b(\021)24 b(que)f(usted)g(tiene)g (que)g(seleccionar)g(mirar)f(todas)i(las)g(cabeceras)e(antes)i(que)f (pueda)0 2700 y(mirar)d(estas)h(cabeceras)e(informati)n(v)n(as.)0 @@ -1961,12 +1960,12 @@ b(\264)-35 b(on)18 b(sobre)i(cambios)f(globales)h(de)g(con\002guraci)7 b(\264)-35 b(on.)0 330 y(P)o(ara)20 b(seleccionar)f(su)i(tipo)f(de)g (en)m(v)n(\264)-26 b(\021os)19 b(agrupados)f(a)j(recibir)m(,)e(usando)f (el)j(interf)o(az)f(de)g(correo)f(electr)7 b(\264)-35 -b(onico:)104 543 y(1.)41 b(En)m(v)n(\264)-26 b(\021e)58 -b(un)i(correo)e(electr)7 b(\264)-35 b(onico)59 b(a)h -Fe(NOMBRELIST)-9 b(A-request@DOMINIO)57 b Fk(con)j(la)g(orden)f -Fd(set)h(dig)o(est)g(plain)f Fk(o)208 642 y Fd(set)21 -b(dig)o(est)f(mime)p Fk(.)208 775 y(Los)h(comandos)f(pueden)g(aparecer) -h(ya)g(sea)h(en)g(el)g(cuerpo)e(o)i(en)g(la)g(l)n(\264)-26 +b(onico:)104 543 y(1.)41 b(En)m(v)n(\264)-26 b(\021e)20 +b(un)g(correo)g(electr)7 b(\264)-35 b(onico)20 b(a)h +Fe(NOMBRELIST)-9 b(A-request@DOMINIO)18 b Fk(con)j(la)h(orden)d +Fd(set)j(dig)o(est)g(plain)e Fk(o)h Fd(set)h(dig)o(est)f(mi-)208 +642 y(me)p Fk(.)208 775 y(Los)g(comandos)f(pueden)g(aparecer)h(ya)g +(sea)h(en)g(el)g(cuerpo)e(o)i(en)g(la)g(l)n(\264)-26 b(\021nea)22 b(de)f(asunto)g(del)h(mensaje)f(\(mire)g(en)h(la)g(Secci)7 b(\264)-35 b(on)21 b(3.2)208 875 y(m)5 b(\264)-33 b(as)20 b(informaci)7 b(\264)-35 b(on)18 b(sobre)h(en)m(v)n(\264)-26 diff --git a/doc/mailman-member-es.txt b/doc/mailman-member-es.txt index fad4d19a..050e1508 100644 --- a/doc/mailman-member-es.txt +++ b/doc/mailman-member-es.txt @@ -1,9 +1,10 @@ + #GNU Mailman Manual del Suscriptor de Listas Contents About this document... About this document... - Previous Page Up one Level Next Page GNU Mailman - Manual del Suscriptor de Listas - __________________________________________________________________ + Previous Page Up one Level Next Page GNU Mailman + Manual del Suscriptor de Listas + _________________________________________________________________ GNU Mailman Manual del Suscriptor de Listas @@ -12,9 +13,9 @@ GNU Mailman Manual del Suscriptor de Listas terri(en)zone12.com Release 2.1 - 5 de diciembre 2007 + 21 de abril 2008 - Prefacio + Prefacio Resumen: @@ -51,16 +52,16 @@ GNU Mailman Manual del Suscriptor de Listas o 7.2 ¿Cómo puedo evitar recibir mensajes duplicados? (opción duplicates) o 7.3 ¿Cómo cambio mi dirección de suscripción? - o 7.4 ¿Cómo hago para dejar de o iniciar a recibir copias - de mis propios envÃos? (opción myposts) + o 7.4 ¿Cómo hago para dejar de o iniciar a recibir + copias de mis propios envÃos? (opción myposts) o 7.5 ¿Cómo puedo hacer para que Mailman me diga cuando mi envÃo ha sido recibido por la lista? (opción ack) o 7.6 Parece que no estoy recibiendo correo de las listas. ¿Qué deberÃa hacer? + 8 EnvÃos agrupados - o 8.1 ¿Cómo puedo iniciar o dejar de recibir los mensajes - enviados a la lista agrupados en un correo de gran - tamaño? (opción digest) + o 8.1 ¿Cómo puedo iniciar o dejar de recibir los + mensajes enviados a la lista agrupados en un correo de + gran tamaño? (opción digest) o 8.2 ¿Qué son los EnvÃos Agrupados MIME o de Texto Plano? ¿Cómo puedo decidir cuales recibir? (opción digest) @@ -72,8 +73,8 @@ GNU Mailman Manual del Suscriptor de Listas o 9.3 ¿Cómo logro o evito recibir mensajes sin tema definido? + 10 Definiendo otras opciones - o 10.1 ¿Cambiar Globalmente? ¿Definir Globalmente? ¿Qué - significa esto? + o 10.1 ¿Cambiar Globalmente? ¿Definir Globalmente? + ¿Qué significa esto? o 10.2 ¿Cómo cambio el nombre que registré en Mailman? o 10.3 ¿Cómo selecciono mi idioma preferido? o 10.4 ¿Cómo evito que mi nombre aparezca en la lista de @@ -87,13 +88,13 @@ GNU Mailman Manual del Suscriptor de Listas 1 Introducción - Este documento tiene como propósito ayudar a los miembros de una lista - de correo Mailman 2.1 a aprender a usar las caracterÃsticas de este - software, disponibles para ellos. Este cubre el uso de los interfaces - web y de correo electrónico para suscribipción y desuscripción, - cambio de opciones de suscriptor y otras tareas a nivel de suscriptor. - También responde algunas preguntas comunes de interés para miembros - de listas Mailman. + Este documento tiene como propósito ayudar a los miembros de una + lista de correo Mailman 2.1 a aprender a usar las caracterÃsticas de + este software, disponibles para ellos. Este cubre el uso de los + interfaces web y de correo electrónico para suscribipción y + desuscripción, cambio de opciones de suscriptor y otras tareas a + nivel de suscriptor. También responde algunas preguntas comunes de + interés para miembros de listas Mailman. La información para administradores de listas y de sitio se proporciona en otros documentos. @@ -109,9 +110,9 @@ GNU Mailman Manual del Suscriptor de Listas sitios web (por ejemplo: cuadro de lista desplegable, botón), o los puede consultar. También se asume que el lector ya puede usar lo suficientemente bien su programa de correo electrónico y navegador - web, de tal forma que sean claras las instrucciones tales como ``envÃe - correo electrónico a esta dirección'' o ``visite esta página web'' o - ``rellene el formulario proporcionado''. Si usted no está + web, de tal forma que sean claras las instrucciones tales como ``envà + e correo electrónico a esta dirección'' o ``visite esta página + web'' o ``rellene el formulario proporcionado''. Si usted no está familiarizado con estas acciones, usted puede desear consultar otra documentación para aprender como hacer estas cosas con su configuración particular. @@ -124,10 +125,10 @@ GNU Mailman Manual del Suscriptor de Listas El resto de este manual fue escrito por Terri Oda. Terri ha estado manteniendo listas de correo desde el año que ella alcanzó la edad - para votar en Canada, aunque las dos cosas no están relacionadas. Ella - actualmente administra las listas de correo de Linuxchix.org, asà como - tambien varios servidores más pequeños. En el mundo ajeno a la - administración de listas, Terri está haciendo un trabajo con un + para votar en Canada, aunque las dos cosas no están relacionadas. + Ella actualmente administra las listas de correo de Linuxchix.org, + asà como tambien varios servidores más pequeños. En el mundo ajeno a + la administración de listas, Terri está haciendo un trabajo con un detector de spam de vida artificial, y realmente es más una programadora que una escritora de temas técnicos. @@ -152,24 +153,25 @@ GNU Mailman Manual del Suscriptor de Listas Las listas de anuncios sirven para que una o más personas puedan enviar anuncios a un grupo de personas, en forma similar a la manera - cómo hace un editor de una revista que utiliza su lista de direcciones - postales para enviar las revistas. Por ejemplo, una banda musical - podrÃa usar una lista de anuncios para facilitar que sus seguidores - estén al tanto de sus conciertos futuros. + cómo hace un editor de una revista que utiliza su lista de + direcciones postales para enviar las revistas. Por ejemplo, una banda + musical podrÃa usar una lista de anuncios para facilitar que sus + seguidores estén al tanto de sus conciertos futuros. Una lista de discusión permite a un grupo de personas discutir temáticas entre ellos mismos, pudiendo cada uno enviar correo a la - lista y hacer que se distribuya a todos los integrantes del grupo. Esta - discusión también se puede moderar, de tal manera que sólo los + lista y hacer que se distribuya a todos los integrantes del grupo. + Esta discusión también se puede moderar, de tal manera que sólo los mensajes seleccionados se envien al grupo como un todo, o que únicamente se le permita enviar al grupo a ciertas personas. Por - ejemplo, un grupo de entusiastas de modelos de aviones podrÃan usar una - lista de discusión para compartir consejos útiles sobre la + ejemplo, un grupo de entusiastas de modelos de aviones podrÃan usar + una lista de discusión para compartir consejos útiles sobre la construcción de modelos y aviación. Algunos términos comunes: - * Un ``envÃo'' tÃpicamente denota un mensaje que se envÃa a una lista - de correo. (Piense en poner un mensaje en un tablero de anuncios.) + * Un ``envÃo'' tÃpicamente denota un mensaje que se envÃa a una + lista de correo. (Piense en poner un mensaje en un tablero de + anuncios.) * A las personas que son parte de una lista de correo electrónico normalmente se las llama ``miembros'' de la lista o ``suscriptores.'' @@ -194,15 +196,16 @@ GNU Mailman Manual del Suscriptor de Listas anuncios. Mailman tiene caracterÃsticas extensivas que lo hacen bueno para listas de suscriptores, tales como facilidad en la suscripción y desuscripción, opciones de privacidad, y la capacidad de detener - temporalmente la recepción de los envÃos a la lista. En este documento - se incluye sobre las caracterÃsticas de los miembros de las listas. + temporalmente la recepción de los envÃos a la lista. En este + documento se incluye sobre las caracterÃsticas de los miembros de las + listas. Mailman también tiene muchas caracterÃsticas que lo hacen atractivo a - administradores de listas y administradores de sitio. Estas - caracterÃsticas están cubiertas en los manuales del administrador de - listas y del sitio. + administradores de listas y administradores de sitio. Estas caracterà + sticas están cubiertas en los manuales del administrador de listas y + del sitio. - 2 Pasando de nuestros ejemplos a las listas reales + 2 Pasando de nuestros ejemplos a las listas reales A menudo es más fácil, simplemente dar un ejemplo que explicar exactamente como encontrar la dirección de una lista especÃfica. Por @@ -242,24 +245,25 @@ GNU Mailman Manual del Suscriptor de Listas direcciones reales). La mayorÃa de las listas tendrán esta información almacenada en las - cabeceras List-*:. Muchos programs de correo ocultarán estas cabeceras - por omisión, asà que usted tiene que seleccionar mirar todas las - cabeceras antes que pueda mirar estas cabeceras informativas. + cabeceras List-*:. Muchos programs de correo ocultarán estas + cabeceras por omisión, asà que usted tiene que seleccionar mirar + todas las cabeceras antes que pueda mirar estas cabeceras + informativas. 3 Interfaces de Mailman Mailman tiene dos interfaces diferentes para los suscriptores de las listas: la interfaz web y la interfaz de correo electrónico. La - mayorÃa de suscriptores de las listas de discusión usan el interfaz de - correo electrónico, ya que ésta incluye las direcciones de correo + mayorÃa de suscriptores de las listas de discusión usan el interfaz + de correo electrónico, ya que ésta incluye las direcciones de correo electrónico que usted utiliza para enviar correo a todos los suscriptores de esa lista. La interfaz que usted use para cambiar las opciones es cuestión de preferencia, ya que la mayorÃa de (pero no todas) las opciones que se pueden cambiar utilizando la interfaz web también se pueden cambiar - por correo electrónico. Usualmente es más fácil utilizar la interfaz - web para cambiar opciones, ya que la interfaz web proporciona + por correo electrónico. Usualmente es más fácil utilizar la + interfaz web para cambiar opciones, ya que la interfaz web proporciona instrucciones como parte de las mismas páginas, pero hay ocasiones en las cuales las personas prefieren la interfaz de correo electrónico, asà que las dos se proporcionan y son útiles. @@ -275,8 +279,8 @@ GNU Mailman Manual del Suscriptor de Listas páginas web. Note que las direcciones URL exactas son configurables por el administrador del sitio, asà que ellas pueden ser diferentes a las que se describen abajo. Nosotros describiremos la configuración - más común, pero consulte los detalles con su administrador de sitio o - proveedor del servicio. + más común, pero consulte los detalles con su administrador de sitio + o proveedor del servicio. =-1 @@ -303,8 +307,8 @@ GNU Mailman Manual del Suscriptor de Listas texto junto al botón marcado ``Opciones de Edición y Desuscripción'' (este está cerca del final de la página). + La página de opciones de suscriptor le permite a usted - entrar/salir y cambiar la configuración de sus opciones, asà - como también desuscribirse u obtener una copia de su + entrar/salir y cambiar la configuración de sus opciones, + asà como también desuscribirse u obtener una copia de su contraseña por correo electrónico. + Para ingresar en su página de opciones de suscriptor: Si usted aún no ha ingresado, encontrará un cuadro de texto @@ -325,12 +329,12 @@ GNU Mailman Manual del Suscriptor de Listas archiva en forma privada (por ejemplo, http://listas.ejemplo.com/pipermail/milista o http://listas.ejemplo.com/mailman/private/milista). - + Las páginas de los archivos de la lista disponen de una copia - de los mensajes enviados a la lista de correo, usualmente - agrupados por mes. En cada grupo mensual, los envÃos se - indexan por autor, fecha, hilo, y asunto. - + Nota: Pipermail es el nombre del archivador predeterminado que - viene con Mailman. Otros programas de archivado están + + Las páginas de los archivos de la lista disponen de una + copia de los mensajes enviados a la lista de correo, + usualmente agrupados por mes. En cada grupo mensual, los + envÃos se indexan por autor, fecha, hilo, y asunto. + + Nota: Pipermail es el nombre del archivador predeterminado + que viene con Mailman. Otros programas de archivado están disponibles. + Si el archivo es privado, usted necesitará suministrar su dirección de correo de suscriptor y su contraseña para @@ -364,7 +368,7 @@ GNU Mailman Manual del Suscriptor de Listas personas encargadas de la lista. * milista-request@ejemplo.com - Esta dirección alcanza un robot de correo que procesa órdenes de correo electrónico que se pueden - usar para definir opciones de suscripción de los miembros, asà + usar para definir opciones de suscripción de los miembros, asà como también para procesar otros comandos. En el Apéndice A se proporciona una lista de órdenes de correo electrónico de miembros de listas. @@ -384,8 +388,8 @@ GNU Mailman Manual del Suscriptor de Listas Las órdenes pueden aparecer en la lÃnea de asunto o en el cuerpo del mensaje. Cada comando deberÃa ir en una lÃnea separada. Si su programa de correo adiciona automáticamente una firma a sus mensajes, usted - podrÃa desear colocar la palabra ``end'' (sin las comillas) en una - lÃnea separada después de sus otras órdenes. La orden end le dice a + podrÃa desear colocar la palabra ``end'' (sin las comillas) en una là + nea separada después de sus otras órdenes. La orden end le dice a Mailman que no procese el correo electrónico después de ese punto. La órden más importante es probablemente la orden ``help'', ya que @@ -394,17 +398,17 @@ GNU Mailman Manual del Suscriptor de Listas web. En los Apéndices A y B se proporcionan referencias rápidas a las - órdenes de suscriptor (éstas se han adaptado ligeramente de la salida - de la orden help.) + órdenes de suscriptor (éstas se han adaptado ligeramente de la + salida de la orden help.) - 4 ¡Necesito hablar con un humano! + 4 ¡Necesito hablar con un humano! Si usted tiene problemas con cualquiera de estas órdenes, usted siempre puede contactar a la persona o personas encargadas de las listas utilizando las direcciones administrativas de las listas. Los - administradores de las listas pueden ayudar a resolver como hacer algo, - suscribirlo/desuscribirlo, o cambiar su configuración si usted no - puede cambiarla por alguna razón. Por favor recuerde que muchos + administradores de las listas pueden ayudar a resolver como hacer + algo, suscribirlo/desuscribirlo, o cambiar su configuración si usted + no puede cambiarla por alguna razón. Por favor recuerde que muchos administradores de listas de correo son voluntarios quienes están donando su tiempo libre para administrar la lista y ellos pueden ser gente muy ocupada. @@ -421,34 +425,34 @@ GNU Mailman Manual del Suscriptor de Listas 5 Suscripción y desuscripción Dado que suscribirse (unirse) o desuscribirse (salirse) son a menudo - las únicas cosas que un miembro de lista necesita conocer, con Mailman - éstas se pueden hacer opcionalmente sin necesidad de que usted conozca - una contraseña. + las únicas cosas que un miembro de lista necesita conocer, con + Mailman éstas se pueden hacer opcionalmente sin necesidad de que + usted conozca una contraseña. 5.1 ¿Cómo me uno a la lista? (subscribe) - Hay dos formas comunes para que usted se suscriba a una lista de correo - Mailman. + Hay dos formas comunes para que usted se suscriba a una lista de + correo Mailman. Usando el interfaz web: - 1. Vaya a la página de información de la lista a la cual usted desea - suscribirse (esta será probablemente similar a + 1. Vaya a la página de información de la lista a la cual usted + desea suscribirse (esta será probablemente similar a http://SERVIDORWEB/mailman/listinfo/NOMBRELISTA). 2. Mire la sección identificada como ``Suscribirse a NOMBRELISTA'' y rellene en los cuadros de texto. Usted puede introducir lo siguiente: + Usted debe entrar su dirección de correo electrónico. + Usted puede suministrar su nombre real. - + Usted puede seleccionar una contraseña. Si no selecciona una, - Mailman generará una para usted. + + Usted puede seleccionar una contraseña. Si no selecciona + una, Mailman generará una para usted. Advertencia: NO use una contraseña valiosa, ya que eventualmente esta contraseña se enviará por correo electrónico como texto plano. - + Si la lista soporta más de un idioma, usted puede seleccionar - su idioma preferido. Nota: Este cambio no afecta los envÃos a - la lista, solamente a los textos Mailman que vienen con el - software de la listas, tal como su página de opciones de - suscriptor. + + Si la lista soporta más de un idioma, usted puede + seleccionar su idioma preferido. Nota: Este cambio no afecta + los envÃos a la lista, solamente a los textos Mailman que + vienen con el software de la listas, tal como su página de + opciones de suscriptor. 3. Haga clic en el botón subscribe. Una nueva página deberÃa aparecer diciéndole que se ha recibido su solicitud de suscripción. Esta página le proporcionará instrucciones @@ -465,13 +469,13 @@ GNU Mailman Manual del Suscriptor de Listas coloque ahÃ. Después de seguir uno de los dos procedimientos (¡usted no necesita - llevar a cabo los dos!), hay unos pocas posibilidades dependiendo de la - configuración de la lista: - * Usted puede recibir un mensaje de correo de confirmación que usted - realmente desea suscribirse a la lista. Esto es para prevenir que - cualquier otra persona lo suscriba a la lista sin su permiso. Siga - las instrucciones dadas en el mensaje para confirmar su deseo de - estar suscrito. + llevar a cabo los dos!), hay unos pocas posibilidades dependiendo de + la configuración de la lista: + * Usted puede recibir un mensaje de correo de confirmación que + usted realmente desea suscribirse a la lista. Esto es para + prevenir que cualquier otra persona lo suscriba a la lista sin su + permiso. Siga las instrucciones dadas en el mensaje para confirmar + su deseo de estar suscrito. * Un moderador también puede necesitar confirmar su suscripción si usted se está suscribiendo a una lista cerrada. * O usted puede tener que esperar a un moderador y seguir las @@ -479,13 +483,13 @@ GNU Mailman Manual del Suscriptor de Listas Una vez hecho esto, usted muy probablemente recibirá otro mensaje, dándole la bienvenida a la lista. Este mensaje contiene información - útil, incluyendo su contraseña de la lista y algunos enlaces directos - para el cambio de sus opciones, de manera que usted puede desear - guardarlo para referencia posterior. + útil, incluyendo su contraseña de la lista y algunos enlaces + directos para el cambio de sus opciones, de manera que usted puede + desear guardarlo para referencia posterior. - Nota: La suscripción también se puede realizar de otras maneras. Mire - en el Apéndice A las órdenes de suscripción por correo electrónico - más avanzadas. + Nota: La suscripción también se puede realizar de otras maneras. + Mire en el Apéndice A las órdenes de suscripción por correo + electrónico más avanzadas. 5.2 ¿Cómo dejo la lista? (unsubscribe) @@ -493,18 +497,18 @@ GNU Mailman Manual del Suscriptor de Listas vacaciones o está demasiado ocupado para leer correos y desea suspender temporalmente la recepción de esos mensajes, usted puede desear detener la entrega de correo en lugar de desuscribirse. Esto - significa que usted mantendrá su contraseña y configuración personal - de manera que usted pueda aún, por ejemplo, aún tener acceso a los - archivos privados de la lista. Si esto es lo que usted desea, mire en - la Sección 7.1 las instrucciones para inhabilitar temporalmente la - entrega de correo. + significa que usted mantendrá su contraseña y configuración + personal de manera que usted pueda aún, por ejemplo, aún tener + acceso a los archivos privados de la lista. Si esto es lo que usted + desea, mire en la Sección 7.1 las instrucciones para inhabilitar + temporalmente la entrega de correo. Si usted realmente desea dejar la lista, hay dos formas para que usted se desuscriba de una lista de correo Mailman. Usando el interfaz web: - 1. Vaya a la página de información de la lista que usted desea dejar - (la dirección de esa página probablemente será similar a + 1. Vaya a la página de información de la lista que usted desea + dejar (la dirección de esa página probablemente será similar a http://SERVIDORWEB/mailman/listinfo/NOMBRELISTA). 2. Ubique la sección identificada como ``suscriptores de NOMBRELISTA'' (usualmente se encuentra cerca de la parte inferior @@ -521,9 +525,9 @@ GNU Mailman Manual del Suscriptor de Listas 1. Abra un programa de correo que le permita enviar correo desde la dirección que usted desee desuscribir. 2. EnvÃe un correo a la dirección de desuscripción de la lista, la - cual tendrá la forma NOMBRELISTA-leave@DOMINIO. El asunto y cuerpo - del mensaje serán ignorados, asà que no importa lo que usted - coloque ahÃ. + cual tendrá la forma NOMBRELISTA-leave@DOMINIO. El asunto y + cuerpo del mensaje serán ignorados, asà que no importa lo que + usted coloque ahÃ. Después de seguir alguno de estos procedimientos (¡usted no necesitará llevar a cabo los dos!), a usted se le enviará un correo @@ -558,7 +562,7 @@ GNU Mailman Manual del Suscriptor de Listas suscripción por correo electrónico). Mire en la Sección 6.1 más información sobre obtención de su contraseña. - 6 Contraseñas + 6 Contraseñas Cuando usted se suscribió, usted seleccionó su contraseña o Mailman se la generó. Usted probablemente tiene una copia de ella en el @@ -605,25 +609,27 @@ GNU Mailman Manual del Suscriptor de Listas Usted también puede obtener un recordatorio utilizando el interfaz de correo electrónico: - 1. EnvÃe un correo a NOMBRELISTA-request@DOMINIO con la orden password + 1. EnvÃe un correo a NOMBRELISTA-request@DOMINIO con la orden + password Los comandos pueden aparecer ya sea en el cuerpo o en la lÃnea de asunto del mensaje (mire en la Sección 3.2 mayor información sobre envÃo de órdenes de correo). Si usted no está enviando correo desde la dirección suscrita, también puede especificar esta dirección enviando la orden - password address= $<$ DIRECCIÃN $>$ . + password address=DIRECCIÃN. 6.2 ¿Cómo cambio mi contraseña? - Advertencia: NO use una contraseña valiosa, ya que esta contraseña se - puede enviar por correo como texto plano. + Advertencia: NO use una contraseña valiosa, ya que esta contraseña + se puede enviar por correo como texto plano. Desde el interfaz web: 1. Ingrese a su página de opciones de suscriptor (Mire en la Section 3.1 las instrucciones de cómo hacer esto). 2. Ubique los cuadros de texto de cambio de contraseña en el lado - derecho de la página e introduzca allà su nueva contraseña, luego - haga clic en el botón etiquetado ``Cambiar mi contraseña''. + derecho de la página e introduzca allà su nueva contraseña, + luego haga clic en el botón etiquetado ``Cambiar mi + contraseña''. Esto también se puede cambiar para múltiples listas al mismo tiempo si usted está suscrito a más de una lista en el mismo dominio. Mire @@ -632,14 +638,14 @@ GNU Mailman Manual del Suscriptor de Listas Desde el interfaz de correo electrónico: 1. EnvÃe un correo a la dirección de correo - NOMBRELISTA-request@DOMINIO con la orden password $<$ - CONTRASEÃA - ANTERIOR $>$ $<$ CONTRASEÃA - NUEVA $>$ . + NOMBRELISTA-request@DOMINIO con la orden + password CONTRASEÃA - ANTERIOR CONTRASEÃA - NUEVA. Las órdenes pueden aparecer ya sea en cuerpo o en la lÃnea de asunto del mensaje (mire en la Sección 3.2 la información sobre el envÃo de órdenes de correo). - Si usted no está enviando correo desde su dirección de membresÃa, - usted puede también especificar esta dirección con address= $<$ - DIRECCIÃN $>$ después de $<$ CONTRASEÃA-NUEVA $>$ . + Si usted no está enviando correo desde su dirección de membresà + a, usted puede también especificar esta dirección con + address=DIRECCIÃN después de CONTRASEÃA-NUEVA. Por ejemplo, si maria@micasa.com deseaba cambiar su contraseña de la lista milista, de zirc a miko, pero ella estaba enviando correo desde la dirección de la oficina maria@trabajo.com, podrÃa enviar @@ -658,7 +664,8 @@ reminders) 1. Ingrese a su página de opciones de suscriptor (mire en la Sección 3.1 las instrucciones de cómo hacer esto). 2. Ubique la sección identificada como ``Obtener recordatorio de - contraseña para esta lista'' y cambie el valor en forma apropiada. + contraseña para esta lista'' y cambie el valor en forma + apropiada. Esto también se puede cambiar para múltiples listas al mismo tiempo si usted está suscrito a más de una lista en el mismo dominio. Mire @@ -683,9 +690,9 @@ reminders) correo, ya no podrá recibir mensajes, pero aún será un suscriptor y como tal retendrá su contraseña y su configuración. - Esto puede ser práctico en muchos casos diferentes. Por ejemplo, usted - podrÃa salir de vacaciones o necesitar un descanso de la lista porque - está demasiado ocupado para leer cualquier correo extra. + Esto puede ser práctico en muchos casos diferentes. Por ejemplo, + usted podrÃa salir de vacaciones o necesitar un descanso de la lista + porque está demasiado ocupado para leer cualquier correo extra. También, muchas listas de correo únicamente permiten a los suscriptores enviar mensajes a la lista, asà que si usted comunmente @@ -697,9 +704,9 @@ reminders) Usted también puede usar su suscripción como un medio para leer archivos privados, inclusive en una lista que pueda ser demasiado ocupada para que usted haga enviar los mensajes directamente a su - buzón de correo. Todo lo que necesita hacer es suscribirse, desactivar - la entrega de correo, y usar su contraseña y dirección de correo - electrónico para acceder a los archivos. + buzón de correo. Todo lo que necesita hacer es suscribirse, + desactivar la entrega de correo, y usar su contraseña y dirección de + correo electrónico para acceder a los archivos. Para desactivar/activar la entrega de correo usando el interfaz web: 1. Ingrese a su página de opciones (mire las instrucciones en la @@ -718,24 +725,24 @@ reminders) 1. EnvÃe un correo a NOMBRELISTA-request@DOMINIO con la orden set delivery off o set delivery on. Las órdenes pueden aparecer ya sea en el cuerpo o en la lÃnea de - asunto del mensaje (mire en la Sección 3.2 más información sobre - envÃo de órdenes de correo). - 2. Seleccione ``off'' para parar la recepción de los envÃos, y ``on'' - para iniciar a recibirlos otra vez. + asunto del mensaje (mire en la Sección 3.2 más información + sobre envÃo de órdenes de correo). + 2. Seleccione ``off'' para parar la recepción de los envÃos, y + ``on'' para iniciar a recibirlos otra vez. 7.2 ¿Cómo puedo evitar recibir mensajes duplicados? (opción duplicates) Mailman no puede impedir completamente que usted reciba mensajes duplicados, pero puede ayudar. Una razón común para que la gente reciba múltiples copias de un correo es que el remitente haya usado - una función ``responder al grupo'' para enviar correo tanto a la lista - como a algún número de individuos. Si usted desea evitar recibir - estos mensajes, se puede configurar Mailman para que revise y mire si - usted está en las lÃneas To: o Cc: del mensaje. Si su dirección - aparece ahÃ, entonces se le puede indicar a Mailman que no le envÃe - otra copia. Esto significa que usted recibirá solamente la copia - enviada por el remitente, y no una copia que haya sido alterada por - Mailman (incluir cabeceras y piés, borrar adjuntos, etc.). + una función ``responder al grupo'' para enviar correo tanto a la + lista como a algún número de individuos. Si usted desea evitar + recibir estos mensajes, se puede configurar Mailman para que revise y + mire si usted está en las lÃneas To: o Cc: del mensaje. Si su + dirección aparece ahÃ, entonces se le puede indicar a Mailman que no + le envÃe otra copia. Esto significa que usted recibirá solamente la + copia enviada por el remitente, y no una copia que haya sido alterada + por Mailman (incluir cabeceras y piés, borrar adjuntos, etc.). Para activar/desactivar esta opción usando el interfaz web: 1. Ingrese a su página de opciones de suscriptor (mire en la @@ -749,12 +756,13 @@ reminders) en la Sección 10.1 la información sobre cambios globales de configuración. - Para activar/desactivar esto usando el interfaz de correo electrónico: + Para activar/desactivar esto usando el interfaz de correo + electrónico: 1. EnvÃe un correo a NOMBRELISTA-request@DOMINIO con la orden set duplicates on o set duplicates off. Las órdenes pueden aparecer ya sea en el cuerpo o en la lÃnea de - asunto del mensaje (mire en la Sección 3.2 más información sobre - envÃo de órdenes de correo). + asunto del mensaje (mire en la Sección 3.2 más información + sobre envÃo de órdenes de correo). 2. Seleccione ``on'' para recibir copias de los mensajes que ya le hayan enviado, seleccione ``off'' para evitar recibir esos duplicados. @@ -779,11 +787,11 @@ reminders) No hay una forma especial de hacer esto desde el interfaz de correo electrónico, pero usted puede suscribirse y desuscribirse para - conseguir más o menos el mismo efecto (mire en las Secciones 5.1 y 5.2 - más información sobre suscripción y desuscripción). + conseguir más o menos el mismo efecto (mire en las Secciones 5.1 y + 5.2 más información sobre suscripción y desuscripción). -7.4 ¿Cómo hago para dejar de o iniciar a recibir copias de mis propios envÃos? -(opción myposts) +7.4 ¿Cómo hago para dejar de o iniciar a recibir copias de mis propios envà +os? (opción myposts) Por omisión en Mailman, usted recibe una copia de todos los mensajes que usted envÃa a la lista. A algunas personas les gusta esto ya que @@ -802,9 +810,9 @@ reminders) Para hacer esto usando el interfaz web: 1. Ingrese a su página de opciones de suscriptor (mire en la Sección 3.1 las instrucciones de cómo hacer esto). - 2. Ubique la sección identificada como ``¿Recibir sus propios envÃos - a la lista?'', seleccione ``Si'' para recibir copias de sus propios - mensajes, y ``No'' para evitar recibirlos. + 2. Ubique la sección identificada como ``¿Recibir sus propios envà + os a la lista?'', seleccione ``Si'' para recibir copias de sus + propios mensajes, y ``No'' para evitar recibirlos. Para hacer esto usando el interfaz de correo: 1. EnvÃe un correo a NOMBRELISTA-request@DOMINIO con la orden @@ -819,11 +827,12 @@ reminders) recibido por la lista? (opción ack) En la mayorÃa de las listas, usted simplemente recibirá una copia de - su correo cuando éste se haya ido, no obstante, esta opción puede ser - útil para usted, si esta opción está desactivada (ver Section 7.4), - su entrega de correo está desactivada (ver Section 7.1), usted no - está suscrito a ese tema (ver Section 9.2) o usted simplemente desea - una confirmación de mensaje recibido extra del sistema. + su correo cuando éste se haya ido, no obstante, esta opción puede + ser útil para usted, si esta opción está desactivada (ver + Section 7.4), su entrega de correo está desactivada (ver + Section 7.1), usted no está suscrito a ese tema (ver Section 9.2) o + usted simplemente desea una confirmación de mensaje recibido extra + del sistema. Nota: Si usted no está suscrito a la lista, no se puede usar esta opción. Usted debe, ya sea, revisar los archivos por su cuenta (si la @@ -833,17 +842,18 @@ recibido por la lista? (opción ack) Para utilizar esta opción usando el interfaz web: 1. Ingrese a su página de opciones de suscriptor (mire en la Sección 3.1 mayores detalles de cómo hacer esto). - 2. Ubique la sección identficada como ``¿Recibir correos de acuso de - rebibo cuando usted envÃa correo a la lista?'' Seleccione ``Si'' - para recibir un correo haciéndole saber que se ha recibido su - envÃo y ``No'' para evitar recibir tal mensaje de acuso de recibo. + 2. Ubique la sección identficada como ``¿Recibir correos de acuso + de rebibo cuando usted envÃa correo a la lista?'' Seleccione + ``Si'' para recibir un correo haciéndole saber que se ha recibido + su envÃo y ``No'' para evitar recibir tal mensaje de acuso de + recibo. Para utilizar esta opción usando el interfaz de correo electrónico: 1. EnvÃe un correo a NOMBRELISTA-request@DOMINIO con la orden set ack on o set ack off. Las órdenes pueden aparecer ya sea en el cuerpo o en la lÃnea de - asunto del mensaje. Mire en la Sección 3.2 más información sobre - el envÃo de órdenes de correo. + asunto del mensaje. Mire en la Sección 3.2 más información + sobre el envÃo de órdenes de correo. 2. Seleccione ``on'' si usted desea recibir correo haciéndole saber que se ha recibido su envÃo y ``off'' para evitar recibir tal mensaje de acuso de recibo. @@ -854,16 +864,16 @@ recibido por la lista? (opción ack) * Durante un cierto lapso de tiempo nadie ha enviado correo a la lista o listas en las cuales usted está suscrito. Para revisar si este es el caso, intente accediendo a los archivos - de la lista (asumiendo que la lista tiene archivos). Si la lista no - tiene archivos, puede preguntar a otro suscriptor (mire en la + de la lista (asumiendo que la lista tiene archivos). Si la lista + no tiene archivos, puede preguntar a otro suscriptor (mire en la Sección 3.1 la ayuda para encontrar los archivos de una lista). Nota: Generalmente se considera descortés envÃar mensajes de prueba a la lista entera. Si usted siente la necesidad de probar que la lista está trabajando y por alguna razón usted no puede simplemente redactar un mensaje regular a la lista, es menos perturbador solicitar un mensaje de ayuda a la dirección - administrativa de la lista (NOMBRELISTA-request@DOMINIO) para mirar - si trabaja, o contactar al administrador de la lista para + administrativa de la lista (NOMBRELISTA-request@DOMINIO) para + mirar si trabaja, o contactar al administrador de la lista para preguntarle si la lista está operando normalmente. * Su dirección de correo está causando mensajes devueltos y por ello el software de la lista le ha deshabilitado la entrega de @@ -887,37 +897,38 @@ recibido por la lista? (opción ack) enviarse usted mismo un mensaje de prueba desde otra cuenta o pedirle a un amigo que le envÃe un mensaje de prueba para asegurarse que su dirección suscrita está trabajando. - Para revisar si esta puede ser la razón por la cual usted no está - recibiendo mensajes, ingrese a su página de opciones (consulte en - la Sección 3.1 más detalles de cómo hacer esto) y mire sus - opciones. Si se ha desactivado su suscripción o si Mailman ha - recibido mensajes devueltos provenientes de su dirección de - correo, usted encontrará un gran mensaje en la parte superior de - esta página. + Para revisar si esta puede ser la razón por la cual usted no + está recibiendo mensajes, ingrese a su página de opciones + (consulte en la Sección 3.1 más detalles de cómo hacer esto) y + mire sus opciones. Si se ha desactivado su suscripción o si + Mailman ha recibido mensajes devueltos provenientes de su + dirección de correo, usted encontrará un gran mensaje en la + parte superior de esta página. Para reactivar la entrega de correo, ubique una opción - identificada como ``Entrega del correo'' y seleccione ``Habilitar'' - para iniciar de nuevo a recibir el correo. Para deshacerse de su - puntaje de mensajes devueltos, usted puede desactivar y luego - volver a activar la entrega. Más instrucciones sobre la - desactivación o activación de la entrega del correo se encuentran - en la Sección 7.1. + identificada como ``Entrega del correo'' y seleccione + ``Habilitar'' para iniciar de nuevo a recibir el correo. Para + deshacerse de su puntaje de mensajes devueltos, usted puede + desactivar y luego volver a activar la entrega. Más instrucciones + sobre la desactivación o activación de la entrega del correo se + encuentran en la Sección 7.1. Nota: Aún si usted no estuviera inhabilitado en el momento en que - revisa, usted podrÃa estar recibiendo mensajes devueltos y no haber - alcanzado el lÃmite para que su suscripción se desactive. Usted - puede necesitar revisar de nuevo. + revisa, usted podrÃa estar recibiendo mensajes devueltos y no + haber alcanzado el lÃmite para que su suscripción se desactive. + Usted puede necesitar revisar de nuevo. * Hay un retardo o interrupción en las redes existentes entre usted y el servidor de listas. Por mucho que nos gustarÃa, Internet no es 100% confiable ni siempre es rápida. Algunas veces los mensajes simplemente demoran mucho tiempo en llegar. Trate de ser paciente, especialmente si el - servidor está alejado (en términos de redes, no geográficamente, - aunque a menudo lo uno implica lo otro) de su proveedor de servicio - de Internet. + servidor está alejado (en términos de redes, no + geográficamente, aunque a menudo lo uno implica lo otro) de su + proveedor de servicio de Internet. Para revisar si esta podrÃa ser la causa de su problema, usted - puede probar realizando un ping al servidor de la lista o trazar la - ruta entre usted y él (las instrucciones de cómo hacer esto varÃa - de una plataforma a otra, asà que usted puede desear usar un motor - de búsqueda para encontrar aquellas más apropiadas para usted). + puede probar realizando un ping al servidor de la lista o trazar + la ruta entre usted y él (las instrucciones de cómo hacer esto + varÃa de una plataforma a otra, asà que usted puede desear usar un + motor de búsqueda para encontrar aquellas más apropiadas para + usted). * El servidor de correo o Mailman podrÃan no estar funcionando correctamente. Esto puede ocurrir si el sistema está sobrecargado con virus o spam y el sistema de correo que aloja Mailman tiene @@ -925,12 +936,12 @@ recibido por la lista? (opción ack) Para revisar si este es el caso, pruebe utilizando el interfaz web de la lista y trate de enviar un mensaje a NOMBRELISTA-request@DOMINIO con la orden ``help'' (sin las - comillas) en la lÃnea de Asunto:. Si nada de esto funciona después - de un razonable lapso de tiempo, ese puede ser el problema. Usted - puede desear contactar al administrador de la lista o al - administrador del sitio. + comillas) en la lÃnea de Asunto:. Si nada de esto funciona + después de un razonable lapso de tiempo, ese puede ser el + problema. Usted puede desear contactar al administrador de la + lista o al administrador del sitio. - 8 EnvÃos agrupados + 8 EnvÃos agrupados 8.1 ¿Cómo puedo iniciar o dejar de recibir los mensajes enviados a la lista agrupados en un correo de gran tamaño? (opción digest) @@ -959,14 +970,14 @@ agrupados en un correo de gran tamaño? (opción digest) Las órdenes pueden aparecer ya sea en el cuerpo o el la lÃnea de asunto de un mensaje (ver en la Sección 3.2 más información sobre el envÃo de órdenes de correo). - 2. Seleccione ``off'' si usted desea recibir los mensajes cada uno por - separado y seleccione ``plain'' o ``mime'' para recibir los + 2. Seleccione ``off'' si usted desea recibir los mensajes cada uno + por separado y seleccione ``plain'' o ``mime'' para recibir los mensajes agrupados en un gran correo, en forma periódica. Mire en - la Sección 8.2 más información sobre envÃos agrupados en formato - MIME versus texto plano. + la Sección 8.2 más información sobre envÃos agrupados en + formato MIME versus texto plano. -8.2 ¿Qué son los EnvÃos Agrupados MIME o de Texto Plano? ¿Cómo puedo decidir -cuales recibir? (opción digest) +8.2 ¿Qué son los EnvÃos Agrupados MIME o de Texto Plano? ¿Cómo puedo +decidir cuales recibir? (opción digest) MIME es la sigla de Multipurpose Internet Mail Extensions (Extensiones Multipropósito de Correo de Internet). Se usa para enviar por correo @@ -974,8 +985,9 @@ cuales recibir? (opción digest) ejemplo, se podrÃa usar MIME si usted fuera a enviar una fotografÃa de su perro a un amigo). - Un envÃo agrupado en formato MIME contiene cada mensaje como un adjunto - dentro del mensaje, junto con un resumen de la tabla de contenido. + Un envÃo agrupado en formato MIME contiene cada mensaje como un + adjunto dentro del mensaje, junto con un resumen de la tabla de + contenido. Un envÃo agrupado en formato texto plano es una forma más simple de envÃo agrupado, el cual deberÃa ser legible aún en los lectores de @@ -997,8 +1009,8 @@ cuales recibir? (opción digest) 2. Ubique la sección identificada como ``¿Recibir envÃos agrupados MIME o de texto plano?'' Seleccione ``MIME'' para recibir los envÃos agrupados en formato - MIME, o ``Plain text'' para recibir los envÃos agrupados en formato - de texto plano. + MIME, o ``Plain text'' para recibir los envÃos agrupados en + formato de texto plano. Esto también se puede cambiar para múltiples listas al mismo tiempo si usted está suscrito a más de una lista en el mismo dominio. Mire @@ -1010,8 +1022,8 @@ cuales recibir? (opción digest) 1. EnvÃe un correo electrónico a NOMBRELISTA-request@DOMINIO con la orden set digest plain o set digest mime. Los comandos pueden aparecer ya sea en el cuerpo o en la lÃnea de - asunto del mensaje (mire en la Sección 3.2 más información sobre - envÃo de órdenes de correo). + asunto del mensaje (mire en la Sección 3.2 más información + sobre envÃo de órdenes de correo). 2. Seleccione ``plain'' para recibir los envÃos agrupados en formato de texto plano, o ``mime'' para recibir los envÃos agrupados en formato MIME. @@ -1019,8 +1031,8 @@ cuales recibir? (opción digest) 9 Temas de listas de correo Algunas listas están configuradas para que Mailman maneje diferentes - temas. Por ejemplo, la lista de cursos en Linuxchix.org es una lista de - discusión para cursos que se están dictando para miembros de + temas. Por ejemplo, la lista de cursos en Linuxchix.org es una lista + de discusión para cursos que se están dictando para miembros de linuxchix, y a menudo, hay varios cursos que se están dictando al mismo tiempo (por ejemplo, redes para principiantes, programación en C, etiquetado de documentos LaTeX). @@ -1032,10 +1044,10 @@ cuales recibir? (opción digest) el tema correcto. Usualmente, ello requiere adicionar una palabra o etiqueta de algún tipo a la lÃnea de asunto (por ejemplo: [Redes] ¿Qué tipos de cables necesito?) o asegurarse que la lÃnea Palabras - claves: tiene la información correcta (por omisión, usted puede poner - una sección Palabras claves: en el comienzo del cuerpo de su mensaje, - pero esto lo puede configurar su administrador de la lista). Note que - estas etiquetas no son sensibles a minúsculas/mayúsculas. + claves: tiene la información correcta (por omisión, usted puede + poner una sección Palabras claves: en el comienzo del cuerpo de su + mensaje, pero esto lo puede configurar su administrador de la lista). + Note que estas etiquetas no son sensibles a minúsculas/mayúsculas. 9.1 ¿Cómo puedo asegurarme que mis envÃos tienen el tema apropiado? @@ -1045,65 +1057,65 @@ cuales recibir? (opción digest) * una expresión regular (regexp) * una descripción - Usted puede mirar esta información ingresando a su página de opciones - de suscriptor (ver en la Sección 3.1 más detalles de cómo hacer - esto) y haciendo clic en el enlace ``Detalles'' de cualquiera de los - temas que le interesen. + Usted puede mirar esta información ingresando a su página de + opciones de suscriptor (ver en la Sección 3.1 más detalles de cómo + hacer esto) y haciendo clic en el enlace ``Detalles'' de cualquiera de + los temas que le interesen. Para enviar un mensaje sobre un determinado tema, usted necesita asegurarse que las Palabras claves: o las cabeceras de Asunto: de su mensaje concuerdan con la expresión regular de ese tema. Una expresión regular es un patrón que puede coincidir con más de una cosa. Realmente las expresiones regulares pueden ser mucho más - complejas, asà que usted puede sencillamente preguntar al administrador - de la lista si usted no sabe como crear cabeceras o colas de una - expresión dada. + complejas, asà que usted puede sencillamente preguntar al + administrador de la lista si usted no sabe como crear cabeceras o + colas de una expresión dada. Si realmente usted desea saber más sobre expresiones regulares, siga - leyendo, pero para la mayor parte, su administador de la lista deberÃa - incluir en la descripción del tema, lo que usted necesita adicionar a - sus Palabras Claves o lÃnea de Asunto para que coincida con el patrón - del tema. - - La mayorÃa de expresiones de temas Mailman corresponderan a expresiones - regulares bastante simples, asà que en este documento simplemente se - darán algunos ejemplos comunes. Las expresiones regulares son un - poquito complejas para enseñar aquà en unas pocas lÃneas, asà que si - usted realmente desea entender como trabajan, usted deberÃa encontrar - un instructivo o referencia en otro lado (por ejemplo, DevShed tiene un - buen instructivo en + leyendo, pero para la mayor parte, su administador de la lista deberà + a incluir en la descripción del tema, lo que usted necesita adicionar + a sus Palabras Claves o lÃnea de Asunto para que coincida con el + patrón del tema. + + La mayorÃa de expresiones de temas Mailman corresponderan a + expresiones regulares bastante simples, asà que en este documento + simplemente se darán algunos ejemplos comunes. Las expresiones + regulares son un poquito complejas para enseñar aquà en unas pocas + lÃneas, asà que si usted realmente desea entender como trabajan, usted + deberÃa encontrar un instructivo o referencia en otro lado (por + ejemplo, DevShed tiene un buen instructivo en http://www.devshed.com/Server_Side/Administration/RegExp/) Aquà hay algunos ejemplos de posibles expresiones regulares y lÃneas concordantes: - Expresión Regular LÃneas concordantes - zuff Palabras Claves: zuff - zuff Palabras Claves: ZUFF - zuff Palabras Claves: Zuff - zuff Palabras Claves: amarilis, zuff, puré de manzana - zuff Asunto: [zuff] ¿Tienes lo necesario para el zuff? - zuff Asunto: ¿Tienes lo apropiado para el zuff? - zuff Asunto: ¿Qué es zuff? - \[zuff\] Palabras Claves: [zuff] - \[zuff\] Asunto: [zuff] ¿Tienes lo necesario? - \[zuff\] Asunto: Tutoriales en lÃnea de zuff (Re: [zuff] ¿Qué es - zuff?) + Expresión Regular LÃneas concordantes + zuff Palabras Claves: zuff + zuff Palabras Claves: ZUFF + zuff Palabras Claves: Zuff + zuff Palabras Claves: amarilis, zuff, puré de manzana + zuff Asunto: [zuff] ¿Tienes lo necesario para el zuff? + zuff Asunto: ¿Tienes lo apropiado para el zuff? + zuff Asunto: ¿Qué es zuff? + \[zuff\] Palabras Claves: [zuff] + \[zuff\] Asunto: [zuff] ¿Tienes lo necesario? + \[zuff\] Asunto: Tutoriales en lÃnea de zuff (Re: [zuff] ¿Qué es + zuff?) Unas pocas notas: - * Las concordancias no son sensibles a mayúsculas/minúsculas, asà + * Las concordancias no son sensibles a mayúsculas/minúsculas, asà que si concuerda zuff, lo hará ZUFF, zuFF, y cualquier otra variación en el uso de las mayúsculas/minúsculas. - * Algunos caracteres tienen un significado especial en una expresión - regular, asà que para concordar especÃficamente con esos - caracteres, ellos deben ser ``escapados'' con una diagonal inversa - (\). Como usted puede ver en los ejemplos de arriba, los + * Algunos caracteres tienen un significado especial en una + expresión regular, asà que para concordar especÃficamente con + esos caracteres, ellos deben ser ``escapados'' con una diagonal + inversa (\). Como usted puede ver en los ejemplos de arriba, los paréntesis rectangulares ([ y ]) son unos de esos caracteres (otros incluyen ``.'', ``?'', y ``*''). La diagonal inversa - también se usa para otras cosas (no es broma la complejidad de las - expresiones regulares: consulte en otra documentación los detalles - sobre otros usos del caracter de diagonal inversa), pero este es el - uso más probable en una expresión de tema. + también se usa para otras cosas (no es broma la complejidad de + las expresiones regulares: consulte en otra documentación los + detalles sobre otros usos del caracter de diagonal inversa), pero + este es el uso más probable en una expresión de tema. 9.2 ¿Cómo me suscribo a algunos o a todos los temas de una lista? @@ -1133,27 +1145,28 @@ cuales recibir? (opción digest) Algunos mensajes no corresponderán con ninguno de los patrones de temas definidos. Usted puede escoger recibir o ignorar tales mensajes que no coinciden. Si usted desea recibir todos los mensajes enviados a - la lista, asegúrse que usted no está suscrito a ningún tema - especÃfico (ver Sección 9.2). + la lista, asegúrse que usted no está suscrito a ningún tema especà + fico (ver Sección 9.2). - Si usted únicamente está suscrito a algunos temas, usted puede elegir - si recibe o no recibe mensajes sin tema definido, de la misma forma - cómo usted puede seleccionar suscribirse únicamente a ciertos temas. + Si usted únicamente está suscrito a algunos temas, usted puede + elegir si recibe o no recibe mensajes sin tema definido, de la misma + forma cómo usted puede seleccionar suscribirse únicamente a ciertos + temas. Para cambiar esta opción: 1. Ingrese a su página de opciones de suscriptor (mire en la Sección 3.1 los detalles de cómo hacer esto). - 2. Ubique la sección identificado como ``¿Desea recibir mensajes que - no concuerden con algún filtro de tema?'' + 2. Ubique la sección identificado como ``¿Desea recibir mensajes + que no concuerden con algún filtro de tema?'' Si usted desea recibir mensajes sin tema definido, seleccione ``Si''. Si usted no desea recibir tales mensajes, seleccione ``No''. This setting has no effect if you are not subscribed to any topics. - Este cambio no tiene efecto si usted no está suscrito a algún tema de - las listas. + Este cambio no tiene efecto si usted no está suscrito a algún tema + de las listas. - 10 Definiendo otras opciones + 10 Definiendo otras opciones 10.1 ¿Cambiar Globalmente? ¿Definir Globalmente? ¿Qué significa esto? @@ -1210,10 +1223,10 @@ cuales recibir? (opción digest) soporta un idioma. Si su lista no soporta el idioma que usted preferirÃa usar, puede - contactar al administrador de la lista (NOMBRELISTA-owner@DOMINIO) para - mirar si se puede adicionar, pero recuerde que esto puede representar - mayor trabajo y el administrador de la lista o del sitio pueden no - tener el tiempo necesario o la capacidad de hacerlo. + contactar al administrador de la lista (NOMBRELISTA-owner@DOMINIO) + para mirar si se puede adicionar, pero recuerde que esto puede + representar mayor trabajo y el administrador de la lista o del sitio + pueden no tener el tiempo necesario o la capacidad de hacerlo. Si el idioma de su elección no está disponible porque no existe traducción para Mailman, por favor considere ofrecer su tiempo como @@ -1234,35 +1247,35 @@ hide) Si usted por alguna razón no desea que su dirección de correo aparezca en la lista de suscriptores, puede optar por tenerla oculta. - Las razones comunes para hacer esto incluyen el evitar correo basura no - solicitado (spam). Por omisión la lista de suscriptores se oculta para - bloquear a recolectores de spam, pero si usted siente que esto es + Las razones comunes para hacer esto incluyen el evitar correo basura + no solicitado (spam). Por omisión la lista de suscriptores se oculta + para bloquear a recolectores de spam, pero si usted siente que esto es insuficiente, es bastante fácil eliminar su dirección de la lista de de suscriptores dada en las páginas de información o mediante una - solicitud de correo electrónico (note que esto no oculta su dirección - de los administradores de la lista). Si usted desea mire en la - Sección 11.2 más información sobre lo que Mailman hace para ayudar a - evitar el spam. + solicitud de correo electrónico (note que esto no oculta su + dirección de los administradores de la lista). Si usted desea mire en + la Sección 11.2 más información sobre lo que Mailman hace para + ayudar a evitar el spam. Para cambiar esta opción utilizando el interfaz web: 1. Ingrese a su página de opciones de suscriptor (mire en la Sección 3.1 instrucciones sobre cómo hacer esto). 2. Vaya a la sección identificada como ``¿Ocultarse de la lista de - suscriptores?'' y escoja ``Si'' para ocultar su nombre de la lista, - o ``No'' para permitir que su nombre aparezca en la lista. + suscriptores?'' y escoja ``Si'' para ocultar su nombre de la + lista, o ``No'' para permitir que su nombre aparezca en la lista. Para cambiar esta opción utilizando el interfaz de correo electrónico: 1. EnvÃe un correo a NOMBRELISTA-request@DOMINIO con la órden set hide on o set hide off. Las órdenes puede aparecer ya sea en el cuerpo o en la lÃnea de - asunto del mensaje (mire en la Sección 3.2 más información sobre - el envÃo de órdenes de correo. - 2. Seleccione ``on'' para ocultar su dirección de correo electrónico - de la lista de membresÃa, u ``off'' para dejar de ocultar su - dirección. + asunto del mensaje (mire en la Sección 3.2 más información + sobre el envÃo de órdenes de correo. + 2. Seleccione ``on'' para ocultar su dirección de correo + electrónico de la lista de membresÃa, u ``off'' para dejar de + ocultar su dirección. - 11 Otras preguntas comunes + 11 Otras preguntas comunes 11.1 ¿Cómo puedo consultar los archivos de la lista? @@ -1283,39 +1296,39 @@ hide) Mire en la Sección 3.1 más información sobre búsqueda de direcciones de una lista. -11.2 ¿Qué hace Mailman para ayudar a protegerme de correo basura no solicitado -(spam)? +11.2 ¿Qué hace Mailman para ayudar a protegerme de correo basura no +solicitado (spam)? - Los archivos de una lista técnica pueden incluir respuestas a un rango - de preguntas diferentes. A menudo, la gente que ha enviado estas + Los archivos de una lista técnica pueden incluir respuestas a un + rango de preguntas diferentes. A menudo, la gente que ha enviado estas respuestas estarÃa gustoso de ayudar a alguien que no entiende completamente la respuesta, y no le preocuparÃa dar su dirección para ese propósito. Pero aunque serÃa maravilloso si todos nos puedieramos - contactar unos a otros con facilidad, también queremos asegurarnos que - la gente que envÃa spam no abuse de la lista ni de los archivos de la - lista. + contactar unos a otros con facilidad, también queremos asegurarnos + que la gente que envÃa spam no abuse de la lista ni de los archivos de + la lista. Para hacer que un rango de opciones esté disponible a los administradores de listas, Mailman permite una variedad de configuraciones para ayudar a proteger las direcciones de correo. - Muchos de estas configuraciones son opcionales para el administrador de - la lista, asà que su lista particular puede estar configurada en forma - diferente. Los administradores de listas deben encontrar un punto de - equilibrio entre proteger a suscriptores y hacerlo difÃcil para que la - gente se ponga en contacto. + Muchos de estas configuraciones son opcionales para el administrador + de la lista, asà que su lista particular puede estar configurada en + forma diferente. Los administradores de listas deben encontrar un + punto de equilibrio entre proteger a suscriptores y hacerlo difÃcil + para que la gente se ponga en contacto. * Lista de suscriptores + El administrador de la lista puede seleccionar entre tener la - lista de suscriptores pública, visible únicamente a miembros - de la lista, o visible únicamente a administradores de la - lista. + lista de suscriptores pública, visible únicamente a + miembros de la lista, o visible únicamente a administradores + de la lista. + La lista de suscriptores se muestra con las direcciones disimuladas para que a los recolectores de spam se les dificulte obtener su dirección. + Usted puede mantener su dirección oculta de la lista de suscriptores (mire más información en la Sección 10.4). - + Nota: La lista entera de suscriptores siempre está disponible - a los administradores de la lista. + + Nota: La lista entera de suscriptores siempre está + disponible a los administradores de la lista. * Archivos de la lista + El administrador de la lista pueden elegir que los archivos sean públicos, visibles únicamente a suscriptores @@ -1325,23 +1338,24 @@ hide) contienen únicamente direcciones disimuladas. Existen otros programas de archivado que modifican las direcciones en diferentes grados para que permanezcan menos legibles. - + Si usted desea estar más seguro, puede definir la cabecera de - correo ``X-No-archive: yes'' y Mailman no archivará sus + + Si usted desea estar más seguro, puede definir la cabecera + de correo ``X-No-archive: yes'' y Mailman no archivará sus envÃos. Similarmente, puede definir la cabecera de correo ``X-Archive: no'' para inhabilitar el archivado. Advertencia: Esto no evita que otros suscritores reenvÃen sus mensajes, posiblemente aún, incluyendo su dirección de correo electrónico. * EnvÃos limitados a las listas - + El administrador de la lista puede elegir quien puede envÃar a - la lista. La mayorÃa de las listas, se moderan (un moderador o - administrador revisa cada envÃo), se configuran para que - solamente los suscriptores puedan enviar a la lista, o se - permite que cualquier persona pueda enviar a la lista. + + El administrador de la lista puede elegir quien puede envÃar + a la lista. La mayorÃa de las listas, se moderan (un + moderador o administrador revisa cada envÃo), se configuran + para que solamente los suscriptores puedan enviar a la lista, + o se permite que cualquier persona pueda enviar a la lista. + Permitiendo que solamente los suscriptores puedan enviar a la lista, Mailman a menudo bloquea todo el spam y algunos virus - que se envÃan a la lista. Como tal, esta es una configuración - bastante común utilizada por los administradores de listas. + que se envÃan a la lista. Como tal, esta es una + configuración bastante común utilizada por los + administradores de listas. * Listas anónimas + Las listas también se pueden volver completamente anónimas: toda la información que identifique al remitente se elimina @@ -1355,13 +1369,13 @@ hide) 1 Referencia rápida de órdenes de correo electrónico - * confirm $<$ CADENA-DE-CONFIRMACIÃN $>$ + * confirm CADENA-DE-CONFIRMACIÃN + Confirma una acción. La cadena de confirmación es obligatoria y se deberÃa enviar en la respuesta al mensaje de confirmación enviado por Mailman. * end - + Termina el procesamiento de órdenes. Utilice esta orden si su - programa de correo añade automáticamente un archivo de + + Termina el procesamiento de órdenes. Utilice esta orden si + su programa de correo añade automáticamente un archivo de firma. * help + Recibe una copia del mensaje de ayuda. @@ -1370,64 +1384,64 @@ hide) * lists + Obtiene una listado de las listas de correo (cuyos nombres se muestran públicamente), del servidor GNU Mailman. - * password [ $<$ CONTRASEÃA-ANTERIOR $>$ $<$ CONTRASEÃA-NUEVA $>$ ] - [address= $<$ DIRECCIÃN $>$ ] + * password [CONTRASEÃA-ANTERIOR CONTRASEÃA-NUEVA] + [address=DIRECCIÃN] + Obtiene o cambia su contraseña. Sin argumentos, devuelve su contraseña actual. Usted puede cambiar su contraseña - indicando los argumentos $<$ CONTRASEÃA-ANTERIOR $>$ y $<$ - CONTRASEÃA-NUEVA $>$ + indicando los argumentos CONTRASEÃA-ANTERIOR y + CONTRASEÃA-NUEVA * set ... + Cambia o muestra sus opciones de membresÃa. Use `set help' (sin las comillas) para obtener una lista más detallada de las opciones que puede cambiar. Esta lista también se presenta en el Apéndice B. - Use `set show' (sin las comillas) para mirar la configuración - actual de sus opciones. - * subscribe [ $<$ CONTRASEÃA $>$ ] [digest|nodigest] [address= $<$ - DIRECCIÃN $>$ ] + Use `set show' (sin las comillas) para mirar la + configuración actual de sus opciones. + * subscribe [CONTRASEÃA] [digest|nodigest] [address=DIRECCIÃN] + Suscribirse a la lista de correo. Usted debe proporcionar su - contraseña para desuscribirse o cambiar sus opciones, pero si - omite la contraseña, Mailman le generará una. Usted puede - obtener recordatorios de su contraseña periódicamente. + contraseña para desuscribirse o cambiar sus opciones, pero + si omite la contraseña, Mailman le generará una. Usted + puede obtener recordatorios de su contraseña + periódicamente. El siguiente parámetro puede ser ya sea: `nodigest' o `digest' (sin comillas). Si usted desea suscribir una dirección diferente de la dirección desde donde está - enviando esta solicitud, puede especificar `address= $<$ - DIRECCIÃN $>$ ' (sin paréntesis angulares ni comillas). - * unsubscribe [ $<$ CONTRASEÃA $>$ ] [address= $<$ DIRECCIÃN $>$ ] + enviando esta solicitud, puede especificar + `address=DIRECCIÃN' (sin paréntesis angulares ni comillas). + * unsubscribe [CONTRASEÃA] [address=DIRECCIÃN] + Desuscribirse de la lista de correo. Si usted suministra una contraseña, ésta debe concordar con su contraseña actual. Si se omite, el sistema le enviará un mensaje de confirmación para desuscribir la dirección. Si usted desea desuscribir una dirección diferente a la dirección desde - donde envÃa esta solicitud, puede especificar `address= $<$ - DIRECCIÃN $>$ ' (sin paréntesis angulares ni comillas). - * who [ $<$ CONTRASEÃA $>$ ] [address= $<$ DIRECCIÃN $>$ ] + donde envÃa esta solicitud, puede especificar + `address=DIRECCIÃN' (sin paréntesis angulares ni comillas). + * who [CONTRASEÃA] [address=DIRECCIÃN] + Muestra quien pertenece a la lista de correo. La lista está limitada únicamente a los suscriptores, y usted debe proporcionar su contraseña de membresÃa para obtenerla. Si usted está enviando desde una dirección diferente a su dirección de membresÃa, especifique su dirección de - membresÃa con `address= $<$ DIRECCIÃN $>$ ' (sin paréntesis - angulares ni comillas). + membresÃa con `address=DIRECCIÃN' (sin paréntesis angulares + ni comillas). 2 Referencia rápida de opciones del suscriptor * set help + Muestra esta ayuda detallada. - * set show [address= $<$ DIRECCIÃN $>$ ] + * set show [address=DIRECCIÃN] + Muestra la configuración actual de sus opciones. Si usted - está enviando desde una dirección diferente de su dirección - de membresÃa, especifique su dirección de membresÃa con - `address= $<$ DIRECCIÃN $>$ ' (sin paréntesis angulares ni - comillas). - * set authenticate $<$ CONTRASEÃA $>$ [address= $<$ DIRECCIÃN $>$ ] + está enviando desde una dirección diferente de su + dirección de membresÃa, especifique su dirección de + membresÃa con `address=DIRECCIÃN' (sin paréntesis angulares + ni comillas). + * set authenticate CONTRASEÃA [address=DIRECCIÃN] + Para cambiar cualquiera de sus opciones, usted debe incluir este comando primero, junto con su contraseña de membresÃa. Si usted está enviando desde una dirección diferente de su dirección de membresÃa, especifique su dirección de - membresÃa con `address= $<$ DIRECCIÃN $>$ ' (sin paréntesis - angulares ni comillas). + membresÃa con `address=DIRECCIÃN' (sin paréntesis angulares + ni comillas). * set ack on set ack off + Cuando se activa la opción `ack', usted recibirá un mensaje @@ -1463,8 +1477,8 @@ hide) set duplicates off + Use `set duplicates off' si usted desea que Mailman no le envÃe mensajes si su dirección está explicitamente en los - campos To: o Cc: del mensaje. Esto puede reducir el número de - envÃos duplicados que usted recibe. + campos To: o Cc: del mensaje. Esto puede reducir el número + de envÃos duplicados que usted recibe. * set reminders on set reminders off + Use `set reminders off' si usted desea desactivar el @@ -1472,8 +1486,8 @@ hide) Sobre este documento... - GNU Mailman Manual del Suscriptor de Listas, 5 de diciembre 2007, - Release 2.1 + GNU Mailman Manual del Suscriptor de Listas, 21 de abril 2008, Release + 2.1 This document was generated using the LaTeX2HTML translator. @@ -1485,10 +1499,10 @@ hide) 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. - __________________________________________________________________ + _________________________________________________________________ - Previous Page Up one Level Next Page GNU Mailman - Manual del Suscriptor de Listas - __________________________________________________________________ + Previous Page Up one Level Next Page GNU Mailman + Manual del Suscriptor de Listas + _________________________________________________________________ - Release 2.1, documentation updated on 5 de diciembre 2007. + Release 2.1, documentation updated on 21 de abril 2008. diff --git a/doc/mailman-member-es/about.html b/doc/mailman-member-es/about.html index 35101164..3c49a3a1 100644 --- a/doc/mailman-member-es/about.html +++ b/doc/mailman-member-es/about.html @@ -48,7 +48,7 @@ Sobre este documento...</a> </h1> <strong>GNU Mailman Manual del Suscriptor de Listas</strong>, -5 de diciembre 2007, Release 2.1 +21 de abril 2008, 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. @@ -104,7 +104,7 @@ Sobre este documento...</a> </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on 5 de diciembre 2007.</span> +<span class="release-info">Release 2.1, documentation updated on 21 de abril 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-member-es/contents.html b/doc/mailman-member-es/contents.html index b9de97a6..d1d27eda 100644 --- a/doc/mailman-member-es/contents.html +++ b/doc/mailman-member-es/contents.html @@ -153,7 +153,7 @@ solicitado (spam)?</a> </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on 5 de diciembre 2007.</span> +<span class="release-info">Release 2.1, documentation updated on 21 de abril 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-member-es/front.html b/doc/mailman-member-es/front.html index 0fd6f439..9436dbfc 100644 --- a/doc/mailman-member-es/front.html +++ b/doc/mailman-member-es/front.html @@ -102,7 +102,7 @@ responde algunas preguntas comunes de interés para miembros de listas Mailman. </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on 5 de diciembre 2007.</span> +<span class="release-info">Release 2.1, documentation updated on 21 de abril 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-member-es/index.html b/doc/mailman-member-es/index.html index 2591eea6..a6167752 100644 --- a/doc/mailman-member-es/index.html +++ b/doc/mailman-member-es/index.html @@ -46,7 +46,7 @@ <p><b><font size="+2">Terri Oda</font></b></p> <p>terri(en)zone12.com</p> <p><strong>Release 2.1</strong><br /> -<strong>5 de diciembre 2007</strong></p> +<strong>21 de abril 2008</strong></p> <p></p> </div> </div> @@ -162,7 +162,7 @@ solicitado (spam)?</a> </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on 5 de diciembre 2007.</span> +<span class="release-info">Release 2.1, documentation updated on 21 de abril 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-member-es/mailman-member-es.html b/doc/mailman-member-es/mailman-member-es.html index 2591eea6..a6167752 100644 --- a/doc/mailman-member-es/mailman-member-es.html +++ b/doc/mailman-member-es/mailman-member-es.html @@ -46,7 +46,7 @@ <p><b><font size="+2">Terri Oda</font></b></p> <p>terri(en)zone12.com</p> <p><strong>Release 2.1</strong><br /> -<strong>5 de diciembre 2007</strong></p> +<strong>21 de abril 2008</strong></p> <p></p> </div> </div> @@ -162,7 +162,7 @@ solicitado (spam)?</a> </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on 5 de diciembre 2007.</span> +<span class="release-info">Release 2.1, documentation updated on 21 de abril 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-member-es/node10.html b/doc/mailman-member-es/node10.html index 7234b537..935aeb60 100644 --- a/doc/mailman-member-es/node10.html +++ b/doc/mailman-member-es/node10.html @@ -173,7 +173,7 @@ salida de la orden <var>help</var>.) </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on 5 de diciembre 2007.</span> +<span class="release-info">Release 2.1, documentation updated on 21 de abril 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-member-es/node11.html b/doc/mailman-member-es/node11.html index ff172bfe..c4f84227 100644 --- a/doc/mailman-member-es/node11.html +++ b/doc/mailman-member-es/node11.html @@ -106,7 +106,7 @@ mayor información sobre cómo encontrar la página de información de su lista. </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on 5 de diciembre 2007.</span> +<span class="release-info">Release 2.1, documentation updated on 21 de abril 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-member-es/node12.html b/doc/mailman-member-es/node12.html index 4a294e6b..9948ddbc 100644 --- a/doc/mailman-member-es/node12.html +++ b/doc/mailman-member-es/node12.html @@ -103,7 +103,7 @@ opcionalmente sin necesidad de que usted conozca una contraseña. </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on 5 de diciembre 2007.</span> +<span class="release-info">Release 2.1, documentation updated on 21 de abril 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-member-es/node13.html b/doc/mailman-member-es/node13.html index ca72c932..c0f98dc8 100644 --- a/doc/mailman-member-es/node13.html +++ b/doc/mailman-member-es/node13.html @@ -176,7 +176,7 @@ más avanzadas. </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on 5 de diciembre 2007.</span> +<span class="release-info">Release 2.1, documentation updated on 21 de abril 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-member-es/node14.html b/doc/mailman-member-es/node14.html index de4e4453..63e6f8b7 100644 --- a/doc/mailman-member-es/node14.html +++ b/doc/mailman-member-es/node14.html @@ -170,7 +170,7 @@ Sección <a href="node16.html#sec:getpassword">6.1</a> más información so </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on 5 de diciembre 2007.</span> +<span class="release-info">Release 2.1, documentation updated on 21 de abril 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-member-es/node15.html b/doc/mailman-member-es/node15.html index b09cdf6c..805ad927 100644 --- a/doc/mailman-member-es/node15.html +++ b/doc/mailman-member-es/node15.html @@ -113,7 +113,7 @@ reminders)</a> </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on 5 de diciembre 2007.</span> +<span class="release-info">Release 2.1, documentation updated on 21 de abril 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-member-es/node16.html b/doc/mailman-member-es/node16.html index e68a1fda..5aa0e1bd 100644 --- a/doc/mailman-member-es/node16.html +++ b/doc/mailman-member-es/node16.html @@ -150,7 +150,7 @@ Si usted no está enviando correo desde la dirección suscrita, también </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on 5 de diciembre 2007.</span> +<span class="release-info">Release 2.1, documentation updated on 21 de abril 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-member-es/node17.html b/doc/mailman-member-es/node17.html index 05172807..7c8b74fb 100644 --- a/doc/mailman-member-es/node17.html +++ b/doc/mailman-member-es/node17.html @@ -163,7 +163,7 @@ Por ejemplo, si <span class="email">maria@micasa.com</span> deseaba cambiar su c </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on 5 de diciembre 2007.</span> +<span class="release-info">Release 2.1, documentation updated on 21 de abril 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-member-es/node18.html b/doc/mailman-member-es/node18.html index d0514284..01e68b46 100644 --- a/doc/mailman-member-es/node18.html +++ b/doc/mailman-member-es/node18.html @@ -128,7 +128,7 @@ Las órdenes pueden aparecer ya sea en el cuerpo o en la lÃnea de asunto del </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on 5 de diciembre 2007.</span> +<span class="release-info">Release 2.1, documentation updated on 21 de abril 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-member-es/node19.html b/doc/mailman-member-es/node19.html index 3267d3f2..30dd93ee 100644 --- a/doc/mailman-member-es/node19.html +++ b/doc/mailman-member-es/node19.html @@ -106,7 +106,7 @@ sido recibido por la lista? (opción ack)</a> </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on 5 de diciembre 2007.</span> +<span class="release-info">Release 2.1, documentation updated on 21 de abril 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-member-es/node20.html b/doc/mailman-member-es/node20.html index 3c1800af..776ff5d3 100644 --- a/doc/mailman-member-es/node20.html +++ b/doc/mailman-member-es/node20.html @@ -152,7 +152,7 @@ Las órdenes pueden aparecer ya sea en el cuerpo o en la lÃnea de asunto </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on 5 de diciembre 2007.</span> +<span class="release-info">Release 2.1, documentation updated on 21 de abril 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-member-es/node21.html b/doc/mailman-member-es/node21.html index 9187ab71..898332a8 100644 --- a/doc/mailman-member-es/node21.html +++ b/doc/mailman-member-es/node21.html @@ -138,7 +138,7 @@ Las órdenes pueden aparecer ya sea en el cuerpo o en la lÃnea de asunto </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on 5 de diciembre 2007.</span> +<span class="release-info">Release 2.1, documentation updated on 21 de abril 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-member-es/node22.html b/doc/mailman-member-es/node22.html index 4fffbd78..a48258e2 100644 --- a/doc/mailman-member-es/node22.html +++ b/doc/mailman-member-es/node22.html @@ -119,7 +119,7 @@ menos el mismo efecto (mire en las Secciones <a href="node13.html#sec:subsc </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on 5 de diciembre 2007.</span> +<span class="release-info">Release 2.1, documentation updated on 21 de abril 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-member-es/node23.html b/doc/mailman-member-es/node23.html index c5209e48..5b527745 100644 --- a/doc/mailman-member-es/node23.html +++ b/doc/mailman-member-es/node23.html @@ -133,7 +133,7 @@ Para hacer esto usando el interfaz de correo: </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on 5 de diciembre 2007.</span> +<span class="release-info">Release 2.1, documentation updated on 21 de abril 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-member-es/node24.html b/doc/mailman-member-es/node24.html index 7e02ccf4..556f395f 100644 --- a/doc/mailman-member-es/node24.html +++ b/doc/mailman-member-es/node24.html @@ -137,7 +137,7 @@ Las órdenes pueden aparecer ya sea en el cuerpo o en la lÃnea de asunto del </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on 5 de diciembre 2007.</span> +<span class="release-info">Release 2.1, documentation updated on 21 de abril 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-member-es/node25.html b/doc/mailman-member-es/node25.html index 576877fe..55fceec1 100644 --- a/doc/mailman-member-es/node25.html +++ b/doc/mailman-member-es/node25.html @@ -200,7 +200,7 @@ Para revisar si este es el caso, pruebe utilizando el interfaz web de </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on 5 de diciembre 2007.</span> +<span class="release-info">Release 2.1, documentation updated on 21 de abril 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-member-es/node26.html b/doc/mailman-member-es/node26.html index 8b7c2c8f..9c14c0de 100644 --- a/doc/mailman-member-es/node26.html +++ b/doc/mailman-member-es/node26.html @@ -100,7 +100,7 @@ decidir cuales recibir? (opción digest)</a> </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on 5 de diciembre 2007.</span> +<span class="release-info">Release 2.1, documentation updated on 21 de abril 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-member-es/node27.html b/doc/mailman-member-es/node27.html index af10c527..4b750ddc 100644 --- a/doc/mailman-member-es/node27.html +++ b/doc/mailman-member-es/node27.html @@ -140,7 +140,7 @@ Las órdenes pueden aparecer ya sea en el cuerpo o el la lÃnea de asunto </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on 5 de diciembre 2007.</span> +<span class="release-info">Release 2.1, documentation updated on 21 de abril 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-member-es/node28.html b/doc/mailman-member-es/node28.html index 1adf5be7..0a711eee 100644 --- a/doc/mailman-member-es/node28.html +++ b/doc/mailman-member-es/node28.html @@ -161,7 +161,7 @@ Los comandos pueden aparecer ya sea en el cuerpo o en la lÃnea de </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on 5 de diciembre 2007.</span> +<span class="release-info">Release 2.1, documentation updated on 21 de abril 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-member-es/node29.html b/doc/mailman-member-es/node29.html index 57c48d66..45bd5cc4 100644 --- a/doc/mailman-member-es/node29.html +++ b/doc/mailman-member-es/node29.html @@ -122,7 +122,7 @@ minúsculas/mayúsculas. </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on 5 de diciembre 2007.</span> +<span class="release-info">Release 2.1, documentation updated on 21 de abril 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-member-es/node3.html b/doc/mailman-member-es/node3.html index 689495f9..b15612f2 100644 --- a/doc/mailman-member-es/node3.html +++ b/doc/mailman-member-es/node3.html @@ -130,7 +130,7 @@ particular. </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on 5 de diciembre 2007.</span> +<span class="release-info">Release 2.1, documentation updated on 21 de abril 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-member-es/node30.html b/doc/mailman-member-es/node30.html index cba5359e..ff99257b 100644 --- a/doc/mailman-member-es/node30.html +++ b/doc/mailman-member-es/node30.html @@ -186,7 +186,7 @@ Unas pocas notas: </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on 5 de diciembre 2007.</span> +<span class="release-info">Release 2.1, documentation updated on 21 de abril 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-member-es/node31.html b/doc/mailman-member-es/node31.html index a00ab2f0..c16d1bb3 100644 --- a/doc/mailman-member-es/node31.html +++ b/doc/mailman-member-es/node31.html @@ -121,7 +121,7 @@ Si algún tema está definido, usted puede seleccionar aquelos que </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on 5 de diciembre 2007.</span> +<span class="release-info">Release 2.1, documentation updated on 21 de abril 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-member-es/node32.html b/doc/mailman-member-es/node32.html index 2583c511..7dacc0bc 100644 --- a/doc/mailman-member-es/node32.html +++ b/doc/mailman-member-es/node32.html @@ -121,7 +121,7 @@ de las listas. </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on 5 de diciembre 2007.</span> +<span class="release-info">Release 2.1, documentation updated on 21 de abril 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-member-es/node33.html b/doc/mailman-member-es/node33.html index 7d35abd9..6d151296 100644 --- a/doc/mailman-member-es/node33.html +++ b/doc/mailman-member-es/node33.html @@ -103,7 +103,7 @@ </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on 5 de diciembre 2007.</span> +<span class="release-info">Release 2.1, documentation updated on 21 de abril 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-member-es/node34.html b/doc/mailman-member-es/node34.html index 10957e0e..b1ae486b 100644 --- a/doc/mailman-member-es/node34.html +++ b/doc/mailman-member-es/node34.html @@ -99,7 +99,7 @@ suspender la entrega de correo de todas las listas. </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on 5 de diciembre 2007.</span> +<span class="release-info">Release 2.1, documentation updated on 21 de abril 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-member-es/node35.html b/doc/mailman-member-es/node35.html index d796833b..c787cd5e 100644 --- a/doc/mailman-member-es/node35.html +++ b/doc/mailman-member-es/node35.html @@ -110,7 +110,7 @@ información sobre cambios globales de configuración. </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on 5 de diciembre 2007.</span> +<span class="release-info">Release 2.1, documentation updated on 21 de abril 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-member-es/node36.html b/doc/mailman-member-es/node36.html index 2dcd482d..acc4ef82 100644 --- a/doc/mailman-member-es/node36.html +++ b/doc/mailman-member-es/node36.html @@ -143,7 +143,7 @@ usted musita un poco, i18n inclusive suena un tanto como </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on 5 de diciembre 2007.</span> +<span class="release-info">Release 2.1, documentation updated on 21 de abril 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-member-es/node37.html b/doc/mailman-member-es/node37.html index a43badd3..ab30d8c0 100644 --- a/doc/mailman-member-es/node37.html +++ b/doc/mailman-member-es/node37.html @@ -134,7 +134,7 @@ Las órdenes puede aparecer ya sea en el cuerpo o en la lÃnea de asunto del </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on 5 de diciembre 2007.</span> +<span class="release-info">Release 2.1, documentation updated on 21 de abril 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-member-es/node38.html b/doc/mailman-member-es/node38.html index 0304d8ed..3cf7e631 100644 --- a/doc/mailman-member-es/node38.html +++ b/doc/mailman-member-es/node38.html @@ -101,7 +101,7 @@ solicitado (spam)?</a> </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on 5 de diciembre 2007.</span> +<span class="release-info">Release 2.1, documentation updated on 21 de abril 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-member-es/node39.html b/doc/mailman-member-es/node39.html index 081c9654..c320f26f 100644 --- a/doc/mailman-member-es/node39.html +++ b/doc/mailman-member-es/node39.html @@ -108,7 +108,7 @@ direcciones de una lista. </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on 5 de diciembre 2007.</span> +<span class="release-info">Release 2.1, documentation updated on 21 de abril 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-member-es/node4.html b/doc/mailman-member-es/node4.html index f36ed6ca..4edbd761 100644 --- a/doc/mailman-member-es/node4.html +++ b/doc/mailman-member-es/node4.html @@ -110,7 +110,7 @@ documento. </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on 5 de diciembre 2007.</span> +<span class="release-info">Release 2.1, documentation updated on 21 de abril 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-member-es/node40.html b/doc/mailman-member-es/node40.html index 9ef4058b..ede39e4e 100644 --- a/doc/mailman-member-es/node40.html +++ b/doc/mailman-member-es/node40.html @@ -201,7 +201,7 @@ pueden no ser suficientes. </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on 5 de diciembre 2007.</span> +<span class="release-info">Release 2.1, documentation updated on 21 de abril 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-member-es/node41.html b/doc/mailman-member-es/node41.html index ae5fa9a0..f419723f 100644 --- a/doc/mailman-member-es/node41.html +++ b/doc/mailman-member-es/node41.html @@ -313,7 +313,7 @@ El siguiente parámetro puede ser ya sea: `nodigest' o `digest' (sin </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on 5 de diciembre 2007.</span> +<span class="release-info">Release 2.1, documentation updated on 21 de abril 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-member-es/node42.html b/doc/mailman-member-es/node42.html index 64f61354..a5786de1 100644 --- a/doc/mailman-member-es/node42.html +++ b/doc/mailman-member-es/node42.html @@ -259,7 +259,7 @@ set reminders off </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on 5 de diciembre 2007.</span> +<span class="release-info">Release 2.1, documentation updated on 21 de abril 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-member-es/node5.html b/doc/mailman-member-es/node5.html index f95048e3..278fa818 100644 --- a/doc/mailman-member-es/node5.html +++ b/doc/mailman-member-es/node5.html @@ -141,7 +141,7 @@ Algunos términos comunes: </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on 5 de diciembre 2007.</span> +<span class="release-info">Release 2.1, documentation updated on 21 de abril 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-member-es/node6.html b/doc/mailman-member-es/node6.html index 6fac75ec..e21b35d2 100644 --- a/doc/mailman-member-es/node6.html +++ b/doc/mailman-member-es/node6.html @@ -101,7 +101,7 @@ están cubiertas en los manuales del administrador de listas y del sitio. </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on 5 de diciembre 2007.</span> +<span class="release-info">Release 2.1, documentation updated on 21 de abril 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-member-es/node7.html b/doc/mailman-member-es/node7.html index d341322c..f0232206 100644 --- a/doc/mailman-member-es/node7.html +++ b/doc/mailman-member-es/node7.html @@ -135,7 +135,7 @@ que pueda mirar estas cabeceras informativas. </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on 5 de diciembre 2007.</span> +<span class="release-info">Release 2.1, documentation updated on 21 de abril 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-member-es/node8.html b/doc/mailman-member-es/node8.html index 873a0145..771fcd3f 100644 --- a/doc/mailman-member-es/node8.html +++ b/doc/mailman-member-es/node8.html @@ -114,7 +114,7 @@ dos se proporcionan y son útiles. </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on 5 de diciembre 2007.</span> +<span class="release-info">Release 2.1, documentation updated on 21 de abril 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-member-es/node9.html b/doc/mailman-member-es/node9.html index 759e6046..398ae5a1 100644 --- a/doc/mailman-member-es/node9.html +++ b/doc/mailman-member-es/node9.html @@ -199,7 +199,7 @@ detalles con su administrador de sitio o proveedor del servicio. </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on 5 de diciembre 2007.</span> +<span class="release-info">Release 2.1, documentation updated on 21 de abril 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-member.dvi b/doc/mailman-member.dvi Binary files differindex 75058a19..e5f4db4c 100644 --- a/doc/mailman-member.dvi +++ b/doc/mailman-member.dvi diff --git a/doc/mailman-member.pdf b/doc/mailman-member.pdf Binary files differindex b1f2c2b9..a556b9b0 100644 --- a/doc/mailman-member.pdf +++ b/doc/mailman-member.pdf diff --git a/doc/mailman-member.ps b/doc/mailman-member.ps index 4bc9f1a7..a1f13611 100644 --- a/doc/mailman-member.ps +++ b/doc/mailman-member.ps @@ -1,7 +1,6 @@ %!PS-Adobe-2.0 -%%Creator: dvips(k) 5.96.1 Copyright 2007 Radical Eye Software +%%Creator: dvips(k) 5.95a Copyright 2005 Radical Eye Software %%Title: mailman-member.dvi -%%CreationDate: Wed Dec 5 17:20:57 2007 %%Pages: 20 %%PageOrder: Ascend %%BoundingBox: 0 0 595 842 @@ -12,7 +11,7 @@ %DVIPSWebPage: (www.radicaleye.com) %DVIPSCommandLine: dvips -N0 -o mailman-member.ps mailman-member %DVIPSParameters: dpi=600 -%DVIPSSource: TeX output 2007.12.05:1720 +%DVIPSSource: TeX output 2008.04.21:1101 %%BeginProcSet: tex.pro 0 0 %! /TeXDict 300 dict def TeXDict begin/N{def}def/B{bind def}N/S{exch}N/X{S @@ -66,7 +65,7 @@ rmoveto}B/y{3 2 roll p a}B/bos{/SS save N}B/eos{SS restore}B end % author = "S. Rahtz, P. MacKay, Alan Jeffrey, B. Horn, K. Berry, % W. Schmidt, P. Lehman", % version = "2.0", -% date = "27nov06", +% date = "30 October 2002", % filename = "8r.enc", % email = "tex-fonts@@tug.org", % docstring = "This is the encoding vector for Type1 and TrueType @@ -176,7 +175,7 @@ rmoveto}B/y{3 2 roll p a}B/bos{/SS save N}B/eos{SS restore}B end /currency /yen /brokenbar /section /dieresis /copyright /ordfeminine /guillemotleft /logicalnot /hyphen /registered /macron -% 0xB0 +% 0xD0 /degree /plusminus /twosuperior /threesuperior /acute /mu /paragraph /periodcentered /cedilla /onesuperior /ordmasculine /guillemotright @@ -408,7 +407,7 @@ TeXDict begin TeXDict begin 1 0 bop 0 83 3901 9 v 551 341 a Fn(GNU)57 b(Mailman)g(-)g(List)h(Member)f(Man)n(ual)3368 488 y Fm(Release)30 b(2.1)3408 842 y Fl(T)-14 b(err)r(i)32 -b(Oda)3289 1197 y Fk(December)19 b(5,)h(2007)3243 1343 +b(Oda)3413 1197 y Fk(April)20 b(21,)g(2008)3243 1343 y(terri\(at\)zone12.com)1811 1545 y Fj(Abstract)208 1683 y Fi(This)j(document)i(describes)g(the)e(list)g(member)i(interf)o(ace)f (for)f(GNU)h(Mailman)g(2.1.)38 b(It)23 b(contains)h(instructions)h(for) diff --git a/doc/mailman-member.txt b/doc/mailman-member.txt index 2a795865..c84640ab 100644 --- a/doc/mailman-member.txt +++ b/doc/mailman-member.txt @@ -1,8 +1,9 @@ - #GNU mailman - list Member Manual Contents About this document... About - this document... - Previous Page Up one Level Next Page GNU Mailman - List Member Manual - __________________________________________________________________ + #GNU mailman - list Member Manual Contents About this document... + About this document... + + Previous Page Up one Level Next Page GNU Mailman - List Member Manual + _________________________________________________________________ GNU Mailman - List Member Manual @@ -11,9 +12,9 @@ GNU Mailman - List Member Manual terri(at)zone12.com Release 2.1 - December 5, 2007 + April 21, 2008 - Front Matter + Front Matter Abstract: @@ -58,8 +59,8 @@ Contents + 8 Digests o 8.1 How can I start or stop getting the list posts grouped into one big email? (digest option) - o 8.2 What are MIME and Plain Text Digests? How do I change - which one I get? (digest option) + o 8.2 What are MIME and Plain Text Digests? How do I + change which one I get? (digest option) + 9 Mailing list topics o 9.1 How do I make sure that my post has the right topic? o 9.2 How do I subscribe to all or only some topics on a @@ -79,7 +80,7 @@ Contents + 1 Email commands quick reference + 2 Member options quick reference - 1 Introduction + 1 Introduction This document is intended to help the members of a Mailman 2.1 mailing list learn to use the features available to them. It covers the use of @@ -98,13 +99,13 @@ Contents Note: For the purposes of this document, we assume that the reader is familiar with common terms related to email (eg: Subject line, body of - the message) and web sites (eg: drop-down box, button) or can look them - up. We also assume that the reader can already use his or her email - program and web browser well enough that instructions such as "send - email to this address" or "visit this web page" or "fill in the form - provided" are clear. If you are not familiar with these actions, you - may want to consult other documentation to learn how to do these things - with your particular setup. + the message) and web sites (eg: drop-down box, button) or can look + them up. We also assume that the reader can already use his or her + email program and web browser well enough that instructions such as + "send email to this address" or "visit this web page" or "fill in the + form provided" are clear. If you are not familiar with these actions, + you may want to consult other documentation to learn how to do these + things with your particular setup. 1.1 Acknowledgements @@ -128,16 +129,16 @@ Contents information is being sent. If you were a magazine publisher, you would have a list of the mailing addresses of all the subscribers to the magazine. In the case of an electronic mailing list, we use a list of - email addresses from people interested in hearing about or discussing a - given topic. + email addresses from people interested in hearing about or discussing + a given topic. Two common types of email mailing lists are announcement lists and discussion lists. Announcement lists are are used so that one person or group can send announcements to a group of people, much like a magazine publisher's - mailing list is used to send out magazines. For example, a band may use - a mailing list to let their fan base know about their upcoming + mailing list is used to send out magazines. For example, a band may + use a mailing list to let their fan base know about their upcoming concerts. A discussion list is used to allow a group of people to discuss topics @@ -145,23 +146,23 @@ Contents have it distributed to everyone in the group. This discussion may also be moderated, so only selected posts are sent on to the group as a whole, or only certain people are allowed to send to the group. For - example, a group of model plane enthusiasts might use a mailing list to - share tips about model construction and flying. + example, a group of model plane enthusiasts might use a mailing list + to share tips about model construction and flying. Some common terms: - * A "post" typically denotes a message sent to a mailing list. (Think - of posting a message on a bulletin board.) + * A "post" typically denotes a message sent to a mailing list. + (Think of posting a message on a bulletin board.) * People who are part of an electronic mailing list are usually called the list's "members" or "subscribers." * "List administrators" are the people in charge of maintaining that one list. Lists may have one or more administrators. - * A list may also have people in charge of reading posts and deciding - if they should be sent on to all subscribers. These people are - called list moderators. + * A list may also have people in charge of reading posts and + deciding if they should be sent on to all subscribers. These + people are called list moderators. * Often more than one electronic mailing list will be run using the - same piece of software. The person who maintains the software which - runs the lists is called the "site administrator." Often the site - administrator also administrates individual lists. + same piece of software. The person who maintains the software + which runs the lists is called the "site administrator." Often the + site administrator also administrates individual lists. 1.3 GNU Mailman @@ -189,8 +190,8 @@ Contents typical list address. The capital letters used for the list-specific parts of each address should make it easier to see what should be changed for each list. Although specific list configurations may be - different, you will probably be able to just replace the words given in - capital letters with the appropriate values for a real list: + different, you will probably be able to just replace the words given + in capital letters with the appropriate values for a real list: LISTNAME The name of your list. @@ -199,36 +200,36 @@ Contents The name of the mail server which handles that list. WEBSERVER - The name of the web server which handles the list web interface. - This may be the same as DOMAIN, and often refers to the same - machine, but does not have to be identical. + The name of the web server which handles the list web + interface. This may be the same as DOMAIN, and often refers to + the same machine, but does not have to be identical. As a real-life example, if you are interested in the mailman-users list, you'd make the following substitutions: LISTNAME=mailman-users, DOMAIN=python.org, WEBSERVER=mail.python.org. As such, for the - mailman-users@python.org mailing list, the list information page can be - found at the URL http://mail.python.org/mailman/listinfo/mailman-users. - (These, unlike most of the examples given in this document, are real - addresses.) + mailman-users@python.org mailing list, the list information page can + be found at the URL + http://mail.python.org/mailman/listinfo/mailman-users. (These, unlike + most of the examples given in this document, are real addresses.) Most lists will have this information stored in the List-*: headers. Many mail programs will hide these by default, so you may have to choose to view full headers before you can see these informational headers. - 3 Mailman's interfaces + 3 Mailman's interfaces Mailman has two different interfaces for the list subscriber: the web - interface and the email interface. Most discussion list subscribers use - the email interface, since this includes the email address you use to - send mail to all the subscribers of that list. + interface and the email interface. Most discussion list subscribers + use the email interface, since this includes the email address you use + to send mail to all the subscribers of that list. The interface you use for changing options is largely a matter of preference, since most (but not all) of the options which can be - changed from the web interface can also be changed by email. Usually it - is easier to use the web interface for changing options, since the web - interface provides instructions as you go, but there are times when - people may prefer the email interface, so both are provided. + changed from the web interface can also be changed by email. Usually + it is easier to use the web interface for changing options, since the + web interface provides instructions as you go, but there are times + when people may prefer the email interface, so both are provided. 3.1 The web interface @@ -238,10 +239,10 @@ Contents options do. Every mailing list is also accessible by a number of web pages. Note - that the exact URLs are configurable by the site administrator, so they - may be different than what's described below. We'll describe the most - common configuration, but check with your site administrator or hosting - service for details. + that the exact URLs are configurable by the site administrator, so + they may be different than what's described below. We'll describe the + most common configuration, but check with your site administrator or + hosting service for details. List information (listinfo) page @@ -251,19 +252,19 @@ Contents + The listinfo page is the starting point for the subscriber interface. As one would assume from the name it's given, it contains information about the LISTNAME list. Usually all the - other subscriber pages can be accessed from this point, so you - really only need to know this one address. + other subscriber pages can be accessed from this point, so + you really only need to know this one address. Member options page + Usually found at http://WEBSERVER/mailman/options/LISTNAME/EMAIL (For example, - http://lists.example.com/mailman/options/mylist/kathy@here.com - ) + http://lists.example.com/mailman/options/mylist/kathy@here.co + m) + This page can also be accessed by going to the listinfo page - and entering your email address into the box beside the button - marked "Unsubscribe or Edit Options" (this is near the bottom - of the page). + and entering your email address into the box beside the + button marked "Unsubscribe or Edit Options" (this is near the + bottom of the page). + The member options page allows you to log in/out and change your list settings, as well as unsubscribe or get a copy of your password mailed to you. @@ -284,11 +285,11 @@ Contents http://lists.example.com/pipermail/mylist or http://lists.example.com/mailman/private/mylist) + The list archive pages have copies of the posts sent to the - mailing list, usually grouped by month. In each monthly group, - the posts are usually indexed by author, date, thread, and - subject. - + Note: Pipermail is the name of the default archiver that comes - with Mailman. Other archive programs are available. + mailing list, usually grouped by month. In each monthly + group, the posts are usually indexed by author, date, thread, + and subject. + + Note: Pipermail is the name of the default archiver that + comes with Mailman. Other archive programs are available. + If the archive is private, you will need to supply your subscribed email address and your password to log in. (See Section 6.1 for more information on getting your password.) @@ -298,8 +299,8 @@ Contents Every mailing list has a set of email addresses to which messages can be sent. There's always one address for posting messages to the list, one address to which bounces are sent, and addresses for processing - email commands. For a fictional mailing list called mylist@example.com, - you'd find these addresses: + email commands. For a fictional 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. @@ -310,8 +311,8 @@ Contents * 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. + 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. This is the address you use if you need to contact the person or people in charge. @@ -323,9 +324,10 @@ Contents members whose 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. + 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. @@ -334,15 +336,15 @@ Contents administrators, but this address only exists for compatibility with older versions of Mailman. - For changing options, we use the LISTNAME-request address (for example, - mylist-request@example.com). + For changing options, we use the LISTNAME-request address (for + example, mylist-request@example.com). Commands can appear in the subject line or the body of the message. Each command should be on a separate line. If your mail program - automatically appends a signature to your messages, you may want to put - the word "end" (without the quotes) on a separate line after your other - commands. The end command tells Mailman not to process the email after - that point. + automatically appends a signature to your messages, you may want to + put the word "end" (without the quotes) on a separate line after your + other commands. The end command tells Mailman not to process the email + after that point. The most important command is probably the "help" command, since it makes Mailman return a message full of useful information about the @@ -352,7 +354,7 @@ Contents Appendices A and B. (These have been slightly adapted from the output of the help command.) - 4 I need to talk to a human! + 4 I need to talk to a human! If you have any trouble with any of these commands, you can always reach the person or people in charge of a list by using the list @@ -373,9 +375,9 @@ Contents 5 Subscribing and unsubscribing - Since subscribing (joining) and unsubscribing (leaving) lists are often - the only things a list member needs to know, these can both be done - without requiring you to know a password. + Since subscribing (joining) and unsubscribing (leaving) lists are + often the only things a list member needs to know, these can both be + done without requiring you to know a password. 5.1 How do I join a list? (subscribe) @@ -394,9 +396,9 @@ Contents Warning: Do NOT use a valuable password, since this password may be mailed to you in plain text. + If the list supports more than one language, you may be able - to choose your preferred language. Note: This setting does not - affect posts to the list, only pre-prepared Mailman texts such - as your member options page. + to choose your preferred language. Note: This setting does + not affect posts to the list, only pre-prepared Mailman texts + such as your member options page. 3. Press the subscribe button. A new page should appear telling you that your request has been sent. @@ -404,29 +406,29 @@ Contents 1. Open a mail program which sends mail from the address you want to subscribe. 2. Send a mail to the list subscription address, which will be in the - form LISTNAME-join@DOMAIN. The subject and body of the message will - be ignored, so it doesn't matter what you put there. + form LISTNAME-join@DOMAIN. The subject and body of the message + will be ignored, so it doesn't matter what you put there. - After following one of these sets of instructions (you don't need to do - both!), there are a few possible outcomes depending upon the settings - for that list. + After following one of these sets of instructions (you don't need to + do both!), there are a few possible outcomes depending upon the + settings for that list. * You may receive an email message asking for confirmation that you - really want to be subscribed to the list. This is to prevent anyone - from subscribing you to lists without your permission. Follow the - instructions given in the message to confirm your wish to be - subscribed. + really want to be subscribed to the list. This is to prevent + anyone from subscribing you to lists without your permission. + Follow the instructions given in the message to confirm your wish + to be subscribed. * A moderator may also need to confirm your subscription if you are subscribing to a limited list. - * Or you may have to wait for a moderator and follow the instructions - in the confirmation mail. + * Or you may have to wait for a moderator and follow the + instructions in the confirmation mail. Once this is done, you will likely receive another message welcoming you to the list. This message contains some useful information including your list password and some quick links for changing your options, so you may want to save it for later reference. - Note: Subscribing can be done in other ways as well. See Appendix A for - more advanced email subscribing commands. + Note: Subscribing can be done in other ways as well. See Appendix A + for more advanced email subscribing commands. 5.2 How do I leave a list? (unsubscribe) @@ -460,28 +462,28 @@ Contents form LISTNAME-leave@DOMAIN. The subject and body of this message will be ignored, so it doesn't matter what you put there. - After following one of these sets of instructions (you don't need to do - both!), you will be sent a confirmation mail and must follow the - instructions given in that mail to complete the unsubscription. This is - to stop people from unsubscribing you without your permission. In + After following one of these sets of instructions (you don't need to + do both!), you will be sent a confirmation mail and must follow the + instructions given in that mail to complete the unsubscription. This + is to stop people from unsubscribing you without your permission. In addition, a moderator may need to approve your unsubscription. If you do not receive this confirmation mail with instructions, make - sure that you typed your email address correctly (if you were using the - web interface to unsubscribe) and that the address you tried to + sure that you typed your email address correctly (if you were using + the web interface to unsubscribe) and that the address you tried to unsubscribe is, indeed, actually subscribed to that list. For security reasons, Mailman generates the same member options page regardless of whether the address entered is subscribed or not. This means that - people cannot use this part of the web interface to find out if someone - is subscribed to the list, but it also means that it's hard to tell if - you just made a typo. + people cannot use this part of the web interface to find out if + someone is subscribed to the list, but it also means that it's hard to + tell if you just made a typo. Once your unsubscription has been processed, you will will probably receive another message confirming your unsubscription from the list, and at that point you should stop receiving messages. - If you wish to skip the confirmation process (for example, you might be - unsubscribing an address which no longer works), it is possible to + If you wish to skip the confirmation process (for example, you might + be unsubscribing an address which no longer works), it is possible to bypass it by using your password instead and either logging in to your options page using it (See Section 3.1), or sending it with your email commands to LISTNAME-request (See Appendix A for advanced email @@ -493,24 +495,24 @@ Contents Your password was either set by you or generated by Mailman when you subscribed. You probably got a copy of it in a welcome message sent when you joined the list, and you may also receive a reminder of it - every month. It is used to verify your identity to Mailman so that only - the holder of the password (you!) and the administrators can view and - change your settings. + every month. It is used to verify your identity to Mailman so that + only the holder of the password (you!) and the administrators can view + and change your settings. Warning: Do NOT use a valuable password for Mailman, since it can be sent in plain text to you. 6.1 How do I get my password? - If you've forgotten your password and haven't saved the welcome message - or any reminder messages, you can always get a reminder through the web - interface: + If you've forgotten your password and haven't saved the welcome + message or any reminder messages, you can always get a reminder + through the web interface: - 1. Go to the list information page for the list from which you wish to - get your password (This will probably be something like + 1. Go to the list information page for the list from which you wish + to get your password (This will probably be something like http://WEBSERVER/mailman/listinfo/LISTNAME) - 2. Look for the section marked "LISTNAME subscribers" (this section is - usually found near the bottom of the page). + 2. Look for the section marked "LISTNAME subscribers" (this section + is usually found near the bottom of the page). 3. There should be a button marked "Unsubscribe or Edit Options." Enter your email address in the box beside this button and press the button. @@ -523,9 +525,9 @@ Contents address you used is, indeed, actually subscribed to that list. For security reasons, Mailman generates the same member options page regardless of whether the address entered is subscribed or not. This - means that people cannot use this part of the web interface to find out - if someone is subscribed to the list, but it also means that it's hard - to tell if you just made a typo. + means that people cannot use this part of the web interface to find + out if someone is subscribed to the list, but it also means that it's + hard to tell if you just made a typo. You can also get a reminder using the email interface, 1. Send a mail to LISTNAME-request@DOMAIN with the command password @@ -533,8 +535,8 @@ Contents message. (See Section 3.2 for more information about sending mail commands.) If you are not sending mail from your subscribed address, you can - also specify this address by sending the command password address= - $<$ ADDRESS $>$ . + also specify this address by sending the command + password address=ADDRESS. 6.2 How do I change my password? @@ -548,31 +550,30 @@ Contents page and enter your new password in the appropriate boxes, then press the button marked "Change My Password." - This can also be changed for multiple lists at the same time if you are - subscribed to more than one list on the same domain. See Section 10.1 - for information about changing settings globally. + This can also be changed for multiple lists at the same time if you + are subscribed to more than one list on the same domain. See + Section 10.1 for information about changing settings globally. From the email interface: - 1. Send a mail to LISTNAME-request@DOMAIN with the command password - $<$ OLDPASSWORD $>$ $<$ NEWPASSWORD $>$ . + 1. Send a mail to LISTNAME-request@DOMAIN with the command + password OLDPASSWORD NEWPASSWORD. Commands can appear in either the body or the subject of the message. (See Section 3.2 for more information about sending mail commands.) If you are not sending mail from your membership address, you can - also specify this address with address= $<$ ADDRESS $>$ after $<$ - NEWPASSWORD $>$ . - For example, if kathy@here.com wanted to change her mylist password - from zirc to miko, but she was sending mail from her work address - kathy@work.com, she could send a message to + also specify this address with address=ADDRESS after NEWPASSWORD. + For example, if kathy@here.com wanted to change her mylist + password from zirc to miko, but she was sending mail from her work + address kathy@work.com, she could send a message to mylist-request@example.com with the subject set to password zirc miko address=kathy@here.com. 6.3 How do I turn password reminders on or off? (reminders option) If you don't wish to the reminder email including your password every - month, you can disable it from the member options page. (You can always - get the password mailed out when you actually want it. See Section 6.1 - for instructions.) + month, you can disable it from the member options page. (You can + always get the password mailed out when you actually want it. See + Section 6.1 for instructions.) Using the web interface: 1. Log in to your member options page. (See Section 3.1 for @@ -580,9 +581,9 @@ Contents 2. Look for the section marked "Get password reminder email for this list?" and change the value accordingly. - This can also be changed for multiple lists at the same time if you are - subscribed to more than one list on the same domain. See Section 10.1 - for information about changing settings globally. + This can also be changed for multiple lists at the same time if you + are subscribed to more than one list on the same domain. See + Section 10.1 for information about changing settings globally. Using the email interface: 1. Send a mail to LISTNAME-request@DOMAIN with the command @@ -593,35 +594,36 @@ Contents 2. Set it to "on" to receive reminders, and "off" to stop receiving reminders. - 7 Changing mail delivery + 7 Changing mail delivery 7.1 How do I turn mail delivery on or off? (delivery option) - You may wish to temporarily stop getting messages from the list without - having to unsubscribe. If you disable mail delivery, you will no longer - receive messages, but will still be a subscriber and will retain your - password and other settings. + You may wish to temporarily stop getting messages from the list + without having to unsubscribe. If you disable mail delivery, you will + no longer receive messages, but will still be a subscriber and will + retain your password and other settings. This can be handy in a many different cases. For example, you could be - going on vacation or need a break from the list because you're too busy - to read any extra mail. Many mailing lists also allow only subscribers - to post to the list, so if you commonly send mail from more than one - address (eg, one address for at home and another for when you're - travelling), you may want to have more than one subscribed account, but - have only one of them actually receive mail. You can also use this as a - way to read private archives even on a list which may be too busy for - you to have sent directly to your mailbox. All you need to do is - subscribe, disable mail delivery, and use your password and email to - log in to the archives. + going on vacation or need a break from the list because you're too + busy to read any extra mail. Many mailing lists also allow only + subscribers to post to the list, so if you commonly send mail from + more than one address (eg, one address for at home and another for + when you're travelling), you may want to have more than one subscribed + account, but have only one of them actually receive mail. You can also + use this as a way to read private archives even on a list which may be + too busy for you to have sent directly to your mailbox. All you need + to do is subscribe, disable mail delivery, and use your password and + email to log in to the archives. To disable/enable mail delivery using the web interface: 1. Log in to your options page. (See Section 3.1 for instructions.) - 2. Go down to the section marked "Mail delivery" and select "Disabled" - to stop receiving mail, and "Enabled" to start receiving mail. + 2. Go down to the section marked "Mail delivery" and select + "Disabled" to stop receiving mail, and "Enabled" to start + receiving mail. - This can also be changed for multiple lists at the same time if you are - subscribed to more than one list on the same domain. See Section 10.1 - for information about changing settings globally. + This can also be changed for multiple lists at the same time if you + are subscribed to more than one list on the same domain. See + Section 10.1 for information about changing settings globally. To disable/enable mail delivery using the email interface: 1. Send a mail to LISTNAME-request@DOMAIN with the command @@ -648,9 +650,9 @@ Contents 2. Scroll down to the bottom of the page to the section marked "Avoid duplicate copies of messages?" and change the value accordingly. - This can also be changed for multiple lists at the same time if you are - subscribed to more than one list on the same domain. See Section 10.1 - for information about changing settings globally. + This can also be changed for multiple lists at the same time if you + are subscribed to more than one list on the same domain. See + Section 10.1 for information about changing settings globally. To turn this on or off using the email interface: 1. Send a mail to LISTNAME-request@DOMAIN with the command @@ -671,8 +673,8 @@ Contents 3. If you wish to change your address for all subscriptions using the old address, select the "Change globally" box. If you have subscriptions under another address or for lists on a different - domain, these will have to be done separately. See Section 10.1 for - more information about changing settings globally. + domain, these will have to be done separately. See Section 10.1 + for more information about changing settings globally. There is no special way to do this from the email interface, but you can subscribe and unsubscribe for more or less the same effect. (See @@ -708,8 +710,8 @@ Contents 2. Set it to "on" to receive copies of your own posts, and "off" to avoid receiving them. -7.5 How can I get Mailman to tell me when my post has been received by the list? -(ack option) +7.5 How can I get Mailman to tell me when my post has been received by the +list? (ack option) On most lists, you will simply receive a copy of your mail when it has gone through the list software, but if this is disabled (See @@ -746,12 +748,12 @@ Contents There are a few common reasons for this: * No one has sent any mail to the list(s) you're on for a little while. - To check if this is the case, try visiting the archives of the list - (assuming that the list has archives). If the list has no archives, - you may have to ask another subscriber. (See Section 3.1 for help - in finding the list archives.) - Note: Generally, it is considered impolite to send test messages to - the entire list. If you feel a need to test that the list is + To check if this is the case, try visiting the archives of the + list (assuming that the list has archives). If the list has no + archives, you may have to ask another subscriber. (See Section 3.1 + for help in finding the list archives.) + Note: Generally, it is considered impolite to send test messages + to the entire list. If you feel a need to test that the list is working and for some reason you cannot simply compose a regular message to the list, it is less disruptive to send a help message to the list request address (LISTNAME-request@DOMAIN) to see if @@ -766,8 +768,9 @@ Contents example, the subscriber has found a new internet service provider and forgot to unsubscribe the old address), as well as addresses which are temporarily out-of-service (for example, the subscriber - has used up all of the allotted space for his or her email account, - or the subscriber's mail provider is experiencing difficulties). + has used up all of the allotted space for his or her email + account, or the subscriber's mail provider is experiencing + difficulties). Even if you are unaware of any difficulties with your mail provider, it is a good idea to check this. Some popular webmail providers and internet servers are not as reliable as one might @@ -781,9 +784,9 @@ Contents marked "Mail Delivery" - if it is set to "Disabled," set it to "Enabled" to start receiving mail again. (For more instructions on disabling or enabling mail delivery, see Section 7.1.) - Note: Even if you have not been disabled at the time you check, you - could be bouncing messages and not have reached the threshold for - your subscription to be disabled. You may need to check again. + Note: Even if you have not been disabled at the time you check, + you could be bouncing messages and not have reached the threshold + for your subscription to be disabled. You may need to check again. * There is a delay or break in the networks between you and the list server. No matter what many of us would like, the internet is not 100% @@ -791,8 +794,8 @@ Contents long time to get to you. Try to be patient, especially if the server is far (in terms of networks, not geography, although often one implies the other) from your internet service provider. - To check if this might be causing your problem, you can try pinging - the list server or tracing the route between you and it. + To check if this might be causing your problem, you can try + pinging the list server or tracing the route between you and it. (Instructions on how to do this varies from platform to platform, so you may want to use a search engine to find those appropriate for you.) @@ -815,15 +818,15 @@ Contents moderately busy list, this typically means you get one email per day, although it may be more or less frequent depending upon the list. - You may also want to look at Section 8.2 which discusses MIME and plain - text digests. + You may also want to look at Section 8.2 which discusses MIME and + plain text digests. To turn digest mode on or off using the web interface, 1. Log in to your member options page. (See Section 3.1 for more details on how to do this.) 2. Look for the section marked "Set Digest Mode." - Set it to "On" to receive messages bundled together in digests. Set - it to "Off" to receive posts separately. + Set it to "On" to receive messages bundled together in digests. + Set it to "Off" to receive posts separately. To turn digest mode on or off using the email interface, 1. Send a mail to LISTNAME-request@DOMAIN with the command @@ -831,10 +834,10 @@ Contents Commands can appear in either the body or the subject of the message. (See Section 3.2 for more information about sending mail commands.) - 2. Set it to "off" if you wish to receive individual posts separately, - and to "plain" or "mime" to receive posts grouped into one large - mail. See Section 8.2 for more information on plain versus MIME - digests. + 2. Set it to "off" if you wish to receive individual posts + separately, and to "plain" or "mime" to receive posts grouped into + one large mail. See Section 8.2 for more information on plain + versus MIME digests. 8.2 What are MIME and Plain Text Digests? How do I change which one I get? (digest option) @@ -862,12 +865,12 @@ Contents 1. Log in to your member options page. (See Section 3.1 for more details on how to do this.) 2. Look for the section marked "Get MIME or Plain Text Digests?." - Set it to "MIME" to receive digests in MIME format, or "Plain text" - to receive digests in plain text format. + Set it to "MIME" to receive digests in MIME format, or "Plain + text" to receive digests in plain text format. - This can also be changed for multiple lists at the same time if you are - subscribed to more than one list on the same domain. See Section 10.1 - for information about changing settings globally. + This can also be changed for multiple lists at the same time if you + are subscribed to more than one list on the same domain. See + Section 10.1 for information about changing settings globally. To set your digest type using the email interface, 1. Send a mail to LISTNAME-request@DOMAIN with the command @@ -875,18 +878,18 @@ Contents Commands can appear in either the body or the subject of the message. (See Section 3.2 for more information about sending mail commands.) - 2. Set it to "plain" to get posts bundled into a plain text digest, or - "mime" to get posts bundled together into a MIME digest. + 2. Set it to "plain" to get posts bundled into a plain text digest, + or "mime" to get posts bundled together into a MIME digest. 9 Mailing list topics Some lists are set up so that different topics are handled by Mailman. - For example, the courses list on Linuxchix.org is a discussion list for - courses being run by linuxchix members, and often there are several - courses being run at the same time. (eg: Networking for beginners, C - programming, LaTeX document mark up.) Each of the courses being run is - a separate topic on the list so that people can choose only to receive - the course they want to take. + For example, the courses list on Linuxchix.org is a discussion list + for courses being run by linuxchix members, and often there are + several courses being run at the same time. (eg: Networking for + beginners, C programming, LaTeX document mark up.) Each of the courses + being run is a separate topic on the list so that people can choose + only to receive the course they want to take. These topics must be configured by the list administrator, but it is the responsibility of each poster to make sure that their post is put @@ -899,7 +902,8 @@ Contents 9.1 How do I make sure that my post has the right topic? - When a list administrator defines a topic, he or she sets three things: + When a list administrator defines a topic, he or she sets three + things: * a topic name * a regular expression (regexp) * a description @@ -925,29 +929,29 @@ Contents Here are some examples of possible regular expressions and matching lines: -Regular expression Matching lines -zuff Keywords: zuff -zuff Keywords: ZUFF -zuff Keywords: Zuff -zuff Keywords: amaryllis, zuff, applesauce -zuff Subject: [zuff] Do you have the right stuff for zuff? -zuff Subject: Do you have the right stuff for zuff? -zuff Subject: What is zuff? -\[zuff\] Keywords: [zuff] -\[zuff\] Subject: [zuff] Do you have the right stuff? -\[zuff\] Subject: Online zuff tutorials (was Re: [zuff] What is zuff?) + Regular expression Matching lines + zuff Keywords: zuff + zuff Keywords: ZUFF + zuff Keywords: Zuff + zuff Keywords: amaryllis, zuff, applesauce + zuff Subject: [zuff] Do you have the right stuff for zuff? + zuff Subject: Do you have the right stuff for zuff? + zuff Subject: What is zuff? + \[zuff\] Keywords: [zuff] + \[zuff\] Subject: [zuff] Do you have the right stuff? + \[zuff\] Subject: Online zuff tutorials (was Re: [zuff] What is zuff?) A few notes: - * The matching is case-insensitive, so if zuff matches, so will ZUFF, - zuFF, and any other variations in capitalization. - * Some characters have special meaning in a regular expression, so to - match those characters specifically, they must be "escaped" with a - backslash (\). As you can see in the above example, [ and ] are - such characters. (Others include ".", "?", and "*"). The backslash - is also used for other things (I wasn't kidding about regular - expressions being complex: consult other documentation for details - about other uses of the backslash character), but this is the most - likely use in a topic expression. + * The matching is case-insensitive, so if zuff matches, so will + ZUFF, zuFF, and any other variations in capitalization. + * Some characters have special meaning in a regular expression, so + to match those characters specifically, they must be "escaped" + with a backslash (\). As you can see in the above example, [ and ] + are such characters. (Others include ".", "?", and "*"). The + backslash is also used for other things (I wasn't kidding about + regular expressions being complex: consult other documentation for + details about other uses of the backslash character), but this is + the most likely use in a topic expression. 9.2 How do I subscribe to all or only some topics on a list? @@ -955,24 +959,24 @@ zuff Subject: What is zuff? choose to subscribe to only part of a list by selecting the topics you want to receive. - If you wish to get all messages sent to the list, make sure you are not - subscribed to any topics. + If you wish to get all messages sent to the list, make sure you are + not subscribed to any topics. 1. Log in to your member options page. (See Section 3.1 for more details on how to do this.) 2. Look for the section marked "Which topic categories would you like to subscribe to?" - If any topics are defined, you can select those you wish. If you do - not select any topics of interest, you will receive all posts sent - to the list. + If any topics are defined, you can select those you wish. If you + do not select any topics of interest, you will receive all posts + sent to the list. You probably also want to look at Section 9.3 which discusses changing your settings for messages where no topic is set. 9.3 How do I get or avoid getting messages with no topic set? - If you wish to get all messages sent to the list, make sure you are not - subscribed to any specific topic. (See Section 9.2.) + If you wish to get all messages sent to the list, make sure you are + not subscribed to any specific topic. (See Section 9.2.) If you are only subscribed to some topics, you can either choose to either receive or not receive messages with no topic set, much the way @@ -981,24 +985,24 @@ zuff Subject: What is zuff? To change this setting, 1. Log in to your member options page. (See Section 3.1 for more details on how to do this.) - 2. Look for the section marked "Do you want to receive message that do - not match any topic filter?" - If you wish to receive messages with no topic set, select "Yes." If - you do not wish to receive such messages, choose "No." + 2. Look for the section marked "Do you want to receive message that + do not match any topic filter?" + If you wish to receive messages with no topic set, select "Yes." + If you do not wish to receive such messages, choose "No." This setting has no effect if you are not subscribed to any topics. - 10 Setting other options + 10 Setting other options 10.1 Change Globally? Set Globally? What does that mean? For some of the options given in your member options page, there is a tick-box which says "Change Globally" or "Set Globally." This means that if you change this option, you can also have the change made for - all your other list subscriptions with the same address to lists on the - same domain. This can be handy if, for example, you want to make sure - all your passwords are the same, or you are going on vacation and want - to turn off mail delivery from all the lists. + all your other list subscriptions with the same address to lists on + the same domain. This can be handy if, for example, you want to make + sure all your passwords are the same, or you are going on vacation and + want to turn off mail delivery from all the lists. 10.2 How do I change my name as Mailman knows it? @@ -1008,26 +1012,26 @@ zuff Subject: What is zuff? 2. In the section marked "Changing your LISTNAME membership information," enter your new name in the appropriate box. - This can also be changed for multiple lists at the same time if you are - subscribed to more than one list on the same domain. See Section 10.1 - for information about changing settings globally. + This can also be changed for multiple lists at the same time if you + are subscribed to more than one list on the same domain. See + Section 10.1 for information about changing settings globally. Note: You do not need to have a subscription name set. 10.3 How do I set my preferred language? Mailman is available with many different languages. (For a complete - listing see http://mailman.sourceforge.net/i18n.html.) This means that, - if your list has other languages enabled, you may be able to have the - web interface, etc. in a language of your choice. + listing see http://mailman.sourceforge.net/i18n.html.) This means + that, if your list has other languages enabled, you may be able to + have the web interface, etc. in a language of your choice. Note: This does NOT necessarily mean that all the posts sent to the list will be in the language you selected. Only the pre-prepared texts presented by Mailman will be affected by this setting. Posts are in whatever language the poster uses. - Your preferred language is set when you subscribe (see Section5.1), and - can be changed later if the list supports more than one language. + Your preferred language is set when you subscribe (see Section5.1), + and can be changed later if the list supports more than one language. To change your preferred language in Mailman, 1. Log in to your member options page. (See Section 3.1 for @@ -1037,33 +1041,34 @@ zuff Subject: What is zuff? drop-down list of languages, the list you are on probably only supports one language. - If your list does not support the language you would prefer to use, you - may contact the list administrator (LISTNAME-owner@DOMAIN) to see if it - can be added, but remember that this may mean some work that the list - and/or site administrator(s) do not have time or the ability to do. + If your list does not support the language you would prefer to use, + you may contact the list administrator (LISTNAME-owner@DOMAIN) to see + if it can be added, but remember that this may mean some work that the + list and/or site administrator(s) do not have time or the ability to + do. If your language of choice is not available because no translation exists for Mailman, please consider volunteering your time as a translator. For more information you may want to consult the mailman-i18n mailing list at - http://mail.python.org/mailman/listinfo/mailman-i18n. (i18n is a common - short-hand for "internationalization" because the word starts with an - i, ends with an n, and has 18 letters in between. If you mumble a bit, - i18n even sounds a bit like "internationalization.") + http://mail.python.org/mailman/listinfo/mailman-i18n. (i18n is a + common short-hand for "internationalization" because the word starts + with an i, ends with an n, and has 18 letters in between. If you + mumble a bit, i18n even sounds a bit like "internationalization.") 10.4 How do I avoid having my name appear on the subscribers list? (the hide option) - If you do not want to have your email address show up on the subscriber - list for any reason, you can opt to have it concealed. + If you do not want to have your email address show up on the + subscriber list for any reason, you can opt to have it concealed. Common reasons for doing this include avoiding unsolicited bulk email (spam). By default, the subscribers list is obscured to hinder spam harvesters, but if you feel this is insufficient it's easy enough to remove address from the subscriber list given in the information pages - or by email request. (Note that this does not conceal your address from - the list administrators.) You may wish to see Section 11.2 for more - information on what Mailman can do to help avoid spam. + or by email request. (Note that this does not conceal your address + from the list administrators.) You may wish to see Section 11.2 for + more information on what Mailman can do to help avoid spam. To change this setting using the web interface: 1. Log in to your member options page. (See Section 3.1 for @@ -1073,8 +1078,8 @@ option) your name to appear on the list. To change this setting using the email interface: - 1. Send a mail to LISTNAME-request@DOMAIN with the command set hide on - or set hide off. + 1. Send a mail to LISTNAME-request@DOMAIN with the command + set hide on or set hide off. Commands can appear in either the body or the subject of the message. (See Section 3.2 for more information about sending mail commands.) @@ -1086,12 +1091,12 @@ option) 11.1 How do I view the list archives? If the list has archives, they can be viewed by going to a web page - address. This address usually linked from the list information page and - can be found in the List-Archive: of every list message unless your - list administrator has disabled these headers. (Many mail programs hide - the List-Archive: mail header, so you may have to tell your mail - program to allow you to view full headers before you will be able to - see it.) + address. This address usually linked from the list information page + and can be found in the List-Archive: of every list message unless + your list administrator has disabled these headers. (Many mail + programs hide the List-Archive: mail header, so you may have to tell + your mail program to allow you to view full headers before you will be + able to see it.) Public archives usually have addresses of the form http://WEBSERVER/pipermail/LISTNAME/ and private archives usually have @@ -1100,31 +1105,33 @@ option) See Section 3.1 for more information on finding the addresses of a list. -11.2 What does Mailman do to help protect me from unsolicited bulk email (spam)? +11.2 What does Mailman do to help protect me from unsolicited bulk email +(spam)? - A technical list's archives may include answers to a range of different - questions. Often, the people who have posted these answers would be - happy to help someone who doesn't quite understand the answer, and - don't mind giving their address out for that purpose. But although it - would be wonderful if everyone could contact each other easily, we also - want to make sure that the list and list archives are not abused by - people who send spam. + A technical list's archives may include answers to a range of + different questions. Often, the people who have posted these answers + would be happy to help someone who doesn't quite understand the + answer, and don't mind giving their address out for that purpose. But + although it would be wonderful if everyone could contact each other + easily, we also want to make sure that the list and list archives are + not abused by people who send spam. To make a range of options available to list administrators, Mailman allows a variety of configurations to help protect email addresses. Many of these settings are optional to the list administrator, so your particular list may be set up in many ways. List administrators must - walk a fine line between protecting subscribers and making it difficult - for people to get in touch. + walk a fine line between protecting subscribers and making it + difficult for people to get in touch. * Subscriber lists + The list administrator can choose to have the subscriber list public, viewable only to list members, or viewable only to list administrators. + The subscriber list is shown with the addresses obscured to - make it difficult for spam harvesters to collect your address. - + You can choose to have your address hidden from the subscriber - list. (See Section 10.4 for more information.) + make it difficult for spam harvesters to collect your + address. + + You can choose to have your address hidden from the + subscriber list. (See Section 10.4 for more information.) + Note: The entire subscriber list is always available to the list administrators. * List archives @@ -1143,8 +1150,8 @@ option) * Limited posting to the lists + The list administrator can choose who can post to the list. Most lists are either moderated (a moderator or administrator - reviews each posting), set so only subscribers may post to the - list, or allow anyone to post to the list. + reviews each posting), set so only subscribers may post to + the list, or allow anyone to post to the list. + By allowing only subscribers to post to a list, Mailman often blocks all spam and some viruses from being sent through the list. As such, this is a fairly common setting used by list @@ -1160,9 +1167,9 @@ option) determined people, so be aware that the protections used may not be enough. - 1 Email commands quick reference + 1 Email commands quick reference - * confirm $<$ CONFIRMATION-STRING $>$ + * confirm CONFIRMATION-STRING + Confirm an action. The confirmation-string is required and should be supplied within a mailback confirmation notice. * end @@ -1175,59 +1182,57 @@ option) * lists + See a list of the public mailing lists on this GNU Mailman server. - * password [ $<$ OLDPASSWORD $>$ $<$ NEWPASSWORD $>$ ] [address= $<$ - ADDRESS $>$ ] + * password [OLDPASSWORD NEWPASSWORD] [address=ADDRESS] + Retrieve or change your password. With no arguments, this - returns your current password. With arguments $<$ OLDPASSWORD - $>$ and $<$ NEWPASSWORD $>$ you can change your password. + returns your current password. With arguments OLDPASSWORD and + NEWPASSWORD you can change your password. * set ... + Set or view your membership options. Use `set help' (without the quotes) to get a more detailed - list of the options you can change. This list is also given in - Appendix B. + list of the options you can change. This list is also given + in Appendix B. Use `set show' (without the quotes) to view your current option settings. - * subscribe [ $<$ PASSWORD $>$ ] [digest|nodigest] [address= $<$ - ADDRESS $>$ ] - + Subscribe to this mailing list. Your password must be given to - unsubscribe or change your options, but if you omit the + * subscribe [PASSWORD] [digest|nodigest] [address=ADDRESS] + + Subscribe to this mailing list. Your password must be given + to unsubscribe or change your options, but if you omit the password, one will be generated for you. You may be periodically reminded of your password. The next argument may be either: `nodigest' or `digest' (no quotes!). If you wish to subscribe an address other than the - address you sent this request from, you may specify `address= - $<$ ADDRESS $>$ ' (no brackets around the email address, and + address you sent this request from, you may specify + `address=ADDRESS' (no brackets around the email address, and no quotes!) - * unsubscribe [ $<$ PASSWORD $>$ ] [address= $<$ ADDRESS $>$ ] + * unsubscribe [PASSWORD] [address=ADDRESS] + Unsubscribe from the mailing list. If given, your password must match your current password. If omitted, a confirmation email will be sent to the unsubscribing address. If you wish - to unsubscribe an address other than the address you sent this - request from, you may specify `address= $<$ ADDRESS $>$ ' (no + to unsubscribe an address other than the address you sent + this request from, you may specify `address=ADDRESS' (no brackets around the email address, and no quotes!) - * who [ $<$ PASSWORD $>$ ] [address= $<$ ADDRESS $>$ ] + * who [PASSWORD] [address=ADDRESS] + See everyone who is on this mailing list. The roster is limited to list members only, and you must supply your membership password to retrieve it. If you're posting from an address other than your membership address, specify your - membership address with `address= $<$ ADDRESS $>$ ' (no - brackets around the email address, and no quotes!) + membership address with `address=ADDRESS' (no brackets around + the email address, and no quotes!) - 2 Member options quick reference + 2 Member options quick reference * set help + Show this detailed help. - * set show [address= $<$ ADDRESS $>$ ] + * set show [address=ADDRESS] + View your current option settings. If you're posting from an address other than your membership address, specify your - membership address with `address= $<$ ADDRESS $>$ ' (no - brackets around the email address, and no quotes!). - * set authenticate $<$ PASSWORD $>$ [address= $<$ ADDRESS $>$ ] + membership address with `address=ADDRESS' (no brackets around + the email address, and no quotes!). + * set authenticate PASSWORD [address=ADDRESS] + To set any of your options, you must include this command first, along with your membership password. If you're posting from an address other than your membership address, specify - your membership address with `address= $<$ ADDRESS $>$ ' (no - brackets around the email address, and no quotes!). + your membership address with `address=ADDRESS' (no brackets + around the email address, and no quotes!). * set ack on set ack off + When the `ack' option is turned on, you will receive an @@ -1240,8 +1245,8 @@ option) postings immediately when they are posted. Use `set digest plain' if instead you want to receive postings bundled into a plain text digest (i.e. RFC 1153 digest). Use `set digest - mime' if instead you want to receive postings bundled together - into a MIME digest. + mime' if instead you want to receive postings bundled + together into a MIME digest. * set delivery on set delivery off + Turn delivery on or off. This does not unsubscribe you, but @@ -1260,8 +1265,8 @@ option) * set duplicates on set duplicates off + Use `set duplicates off' if you want Mailman not to send you - messages if your address is explicitly mentioned in the To: or - Cc: fields of the message. This can reduce the number of + messages if your address is explicitly mentioned in the To: + or Cc: fields of the message. This can reduce the number of duplicate postings you will receive. * set reminders on set reminders off @@ -1270,7 +1275,7 @@ option) About this document ... - GNU Mailman - List Member Manual, December 5, 2007, Release 2.1 + GNU Mailman - List Member Manual, April 21, 2008, Release 2.1 This document was generated using the LaTeX2HTML translator. @@ -1282,9 +1287,9 @@ option) 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. - __________________________________________________________________ + _________________________________________________________________ - Previous Page Up one Level Next Page GNU Mailman - List Member Manual - __________________________________________________________________ + Previous Page Up one Level Next Page GNU Mailman - List Member Manual + _________________________________________________________________ - Release 2.1, documentation updated on December 5, 2007. + Release 2.1, documentation updated on April 21, 2008. diff --git a/doc/mailman-member/about.html b/doc/mailman-member/about.html index 6af1744d..aea9d4e2 100644 --- a/doc/mailman-member/about.html +++ b/doc/mailman-member/about.html @@ -48,7 +48,7 @@ About this document ...</a> </h1> <strong>GNU Mailman - List Member Manual</strong>, -December 5, 2007, Release 2.1 +April 21, 2008, 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. @@ -104,7 +104,7 @@ December 5, 2007, Release 2.1 </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-member/contents.html b/doc/mailman-member/contents.html index 30a3d2f1..4011197f 100644 --- a/doc/mailman-member/contents.html +++ b/doc/mailman-member/contents.html @@ -151,7 +151,7 @@ I get? (digest option)</a> </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-member/front.html b/doc/mailman-member/front.html index 54f6c1b2..89164eef 100644 --- a/doc/mailman-member/front.html +++ b/doc/mailman-member/front.html @@ -102,7 +102,7 @@ of interest to Mailman list members. </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-member/index.html b/doc/mailman-member/index.html index 0e84ca05..d60ade52 100644 --- a/doc/mailman-member/index.html +++ b/doc/mailman-member/index.html @@ -46,7 +46,7 @@ <p><b><font size="+2">Terri Oda</font></b></p> <p>terri(at)zone12.com</p> <p><strong>Release 2.1</strong><br /> -<strong>December 5, 2007</strong></p> +<strong>April 21, 2008</strong></p> <p></p> </div> </div> @@ -163,7 +163,7 @@ I get? (digest option)</a> </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-member/mailman-member.html b/doc/mailman-member/mailman-member.html index 0e84ca05..d60ade52 100644 --- a/doc/mailman-member/mailman-member.html +++ b/doc/mailman-member/mailman-member.html @@ -46,7 +46,7 @@ <p><b><font size="+2">Terri Oda</font></b></p> <p>terri(at)zone12.com</p> <p><strong>Release 2.1</strong><br /> -<strong>December 5, 2007</strong></p> +<strong>April 21, 2008</strong></p> <p></p> </div> </div> @@ -163,7 +163,7 @@ I get? (digest option)</a> </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-member/node10.html b/doc/mailman-member/node10.html index ac06c6d9..f54f0593 100644 --- a/doc/mailman-member/node10.html +++ b/doc/mailman-member/node10.html @@ -175,7 +175,7 @@ adapted from the output of the <var>help</var> command.) </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-member/node11.html b/doc/mailman-member/node11.html index e7efe3c5..bcea78c3 100644 --- a/doc/mailman-member/node11.html +++ b/doc/mailman-member/node11.html @@ -106,7 +106,7 @@ information on finding the list information page for your list </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-member/node12.html b/doc/mailman-member/node12.html index e998fe55..ce0bef10 100644 --- a/doc/mailman-member/node12.html +++ b/doc/mailman-member/node12.html @@ -103,7 +103,7 @@ requiring you to know a password. </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-member/node13.html b/doc/mailman-member/node13.html index 50b4cab5..c8a8c8dc 100644 --- a/doc/mailman-member/node13.html +++ b/doc/mailman-member/node13.html @@ -174,7 +174,7 @@ Appendix <a href="node41.html#a:commands">A</a> for more advanced email sub </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-member/node14.html b/doc/mailman-member/node14.html index 1ba2e183..ad162a8d 100644 --- a/doc/mailman-member/node14.html +++ b/doc/mailman-member/node14.html @@ -167,7 +167,7 @@ information on getting your password. </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-member/node15.html b/doc/mailman-member/node15.html index 01abef0d..629332e2 100644 --- a/doc/mailman-member/node15.html +++ b/doc/mailman-member/node15.html @@ -114,7 +114,7 @@ sent in plain text to you.</span> </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-member/node16.html b/doc/mailman-member/node16.html index ad52a62d..775304ec 100644 --- a/doc/mailman-member/node16.html +++ b/doc/mailman-member/node16.html @@ -147,7 +147,7 @@ If you are not sending mail from your subscribed address, you can also </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-member/node17.html b/doc/mailman-member/node17.html index 6af4f59c..e71ad202 100644 --- a/doc/mailman-member/node17.html +++ b/doc/mailman-member/node17.html @@ -161,7 +161,7 @@ For example, if <span class="email">kathy@here.com</span> wanted to change her < </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-member/node18.html b/doc/mailman-member/node18.html index 3574e495..18d5beff 100644 --- a/doc/mailman-member/node18.html +++ b/doc/mailman-member/node18.html @@ -126,7 +126,7 @@ Commands can appear </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-member/node19.html b/doc/mailman-member/node19.html index 79064340..41f2f8db 100644 --- a/doc/mailman-member/node19.html +++ b/doc/mailman-member/node19.html @@ -106,7 +106,7 @@ by the list? (ack option)</a> </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-member/node20.html b/doc/mailman-member/node20.html index d4e2629f..efde3cc5 100644 --- a/doc/mailman-member/node20.html +++ b/doc/mailman-member/node20.html @@ -142,7 +142,7 @@ Commands can appear </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-member/node21.html b/doc/mailman-member/node21.html index 99055444..1294f2a5 100644 --- a/doc/mailman-member/node21.html +++ b/doc/mailman-member/node21.html @@ -135,7 +135,7 @@ Commands can appear </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-member/node22.html b/doc/mailman-member/node22.html index a60ec418..1d5995b6 100644 --- a/doc/mailman-member/node22.html +++ b/doc/mailman-member/node22.html @@ -111,7 +111,7 @@ on subscribing and unsubscribing.) </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-member/node23.html b/doc/mailman-member/node23.html index 86eef9fd..6303afad 100644 --- a/doc/mailman-member/node23.html +++ b/doc/mailman-member/node23.html @@ -133,7 +133,7 @@ Commands can appear </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-member/node24.html b/doc/mailman-member/node24.html index e3a03ee0..455382e0 100644 --- a/doc/mailman-member/node24.html +++ b/doc/mailman-member/node24.html @@ -139,7 +139,7 @@ Commands can appear </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-member/node25.html b/doc/mailman-member/node25.html index 7c5e1241..08fbe649 100644 --- a/doc/mailman-member/node25.html +++ b/doc/mailman-member/node25.html @@ -181,7 +181,7 @@ To test if this is a case, try visiting the list's web interface and </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-member/node26.html b/doc/mailman-member/node26.html index 6fec44f6..445e633b 100644 --- a/doc/mailman-member/node26.html +++ b/doc/mailman-member/node26.html @@ -100,7 +100,7 @@ I get? (digest option)</a> </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-member/node27.html b/doc/mailman-member/node27.html index 6abb8708..3ccd3f69 100644 --- a/doc/mailman-member/node27.html +++ b/doc/mailman-member/node27.html @@ -136,7 +136,7 @@ Commands can appear </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-member/node28.html b/doc/mailman-member/node28.html index 4c58c01d..6c4bfdf1 100644 --- a/doc/mailman-member/node28.html +++ b/doc/mailman-member/node28.html @@ -153,7 +153,7 @@ Commands can appear </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-member/node29.html b/doc/mailman-member/node29.html index ffbca818..954c6074 100644 --- a/doc/mailman-member/node29.html +++ b/doc/mailman-member/node29.html @@ -124,7 +124,7 @@ Note that these tags are case-insensitive. </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-member/node3.html b/doc/mailman-member/node3.html index e36bf987..967ed7d4 100644 --- a/doc/mailman-member/node3.html +++ b/doc/mailman-member/node3.html @@ -131,7 +131,7 @@ setup.</span> </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-member/node30.html b/doc/mailman-member/node30.html index 0e1607f5..dd83e773 100644 --- a/doc/mailman-member/node30.html +++ b/doc/mailman-member/node30.html @@ -177,7 +177,7 @@ A few notes: </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-member/node31.html b/doc/mailman-member/node31.html index 80ac9948..64177ce7 100644 --- a/doc/mailman-member/node31.html +++ b/doc/mailman-member/node31.html @@ -119,7 +119,7 @@ changing your settings for messages where no topic is set. </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-member/node32.html b/doc/mailman-member/node32.html index d7e1c619..6aed2af3 100644 --- a/doc/mailman-member/node32.html +++ b/doc/mailman-member/node32.html @@ -116,7 +116,7 @@ This setting has no effect if you are not subscribed to any topics. </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-member/node33.html b/doc/mailman-member/node33.html index 653867b8..50a72be3 100644 --- a/doc/mailman-member/node33.html +++ b/doc/mailman-member/node33.html @@ -103,7 +103,7 @@ </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-member/node34.html b/doc/mailman-member/node34.html index 91b16d87..636b79c8 100644 --- a/doc/mailman-member/node34.html +++ b/doc/mailman-member/node34.html @@ -100,7 +100,7 @@ vacation and want to turn off mail delivery from all the lists. </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-member/node35.html b/doc/mailman-member/node35.html index c278f976..1001d320 100644 --- a/doc/mailman-member/node35.html +++ b/doc/mailman-member/node35.html @@ -111,7 +111,7 @@ You do not need to have a subscription name set.</span> </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-member/node36.html b/doc/mailman-member/node36.html index 33f2dbf9..3c4621f1 100644 --- a/doc/mailman-member/node36.html +++ b/doc/mailman-member/node36.html @@ -135,7 +135,7 @@ i18n even sounds a bit like "internationalization.") </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-member/node37.html b/doc/mailman-member/node37.html index 0f4a0c61..73f1fa19 100644 --- a/doc/mailman-member/node37.html +++ b/doc/mailman-member/node37.html @@ -133,7 +133,7 @@ Commands can appear </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-member/node38.html b/doc/mailman-member/node38.html index 1af269e7..112d44cb 100644 --- a/doc/mailman-member/node38.html +++ b/doc/mailman-member/node38.html @@ -101,7 +101,7 @@ </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-member/node39.html b/doc/mailman-member/node39.html index dc032e20..da027b14 100644 --- a/doc/mailman-member/node39.html +++ b/doc/mailman-member/node39.html @@ -104,7 +104,7 @@ list. </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-member/node4.html b/doc/mailman-member/node4.html index f00b627b..4bcd5540 100644 --- a/doc/mailman-member/node4.html +++ b/doc/mailman-member/node4.html @@ -105,7 +105,7 @@ Proofreading thanks go to Margaret McCarthy and Jason Walton. </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-member/node40.html b/doc/mailman-member/node40.html index 4c75cb55..a1de406b 100644 --- a/doc/mailman-member/node40.html +++ b/doc/mailman-member/node40.html @@ -190,7 +190,7 @@ people, so be aware that the protections used may not be enough. </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-member/node41.html b/doc/mailman-member/node41.html index 4f1997b1..b9fc552d 100644 --- a/doc/mailman-member/node41.html +++ b/doc/mailman-member/node41.html @@ -312,7 +312,7 @@ The next argument may be either: `nodigest' or `digest' (no quotes!). </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-member/node42.html b/doc/mailman-member/node42.html index d21eed72..de81240c 100644 --- a/doc/mailman-member/node42.html +++ b/doc/mailman-member/node42.html @@ -258,7 +258,7 @@ set reminders off </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-member/node5.html b/doc/mailman-member/node5.html index 4b4e34ec..9c44df07 100644 --- a/doc/mailman-member/node5.html +++ b/doc/mailman-member/node5.html @@ -134,7 +134,7 @@ Some common terms: </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-member/node6.html b/doc/mailman-member/node6.html index b9fa7ad8..0414df10 100644 --- a/doc/mailman-member/node6.html +++ b/doc/mailman-member/node6.html @@ -100,7 +100,7 @@ manuals. </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-member/node7.html b/doc/mailman-member/node7.html index 8e722813..74ca7ea6 100644 --- a/doc/mailman-member/node7.html +++ b/doc/mailman-member/node7.html @@ -133,7 +133,7 @@ full headers before you can see these informational headers. </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-member/node8.html b/doc/mailman-member/node8.html index 5004cdf6..797afdde 100644 --- a/doc/mailman-member/node8.html +++ b/doc/mailman-member/node8.html @@ -113,7 +113,7 @@ provided. </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> diff --git a/doc/mailman-member/node9.html b/doc/mailman-member/node9.html index f0a2c836..3be8f3b4 100644 --- a/doc/mailman-member/node9.html +++ b/doc/mailman-member/node9.html @@ -187,7 +187,7 @@ Pipermail is the name of the default archiver that </div> </div> <hr /> -<span class="release-info">Release 2.1, documentation updated on December 5, 2007.</span> +<span class="release-info">Release 2.1, documentation updated on April 21, 2008.</span> </div> <!--End of Navigation Panel--> |