From 91ac8e2e8559192969c6877a779d47283e39cb09 Mon Sep 17 00:00:00 2001 From: Mark Sapiro Date: Thu, 29 Jan 2015 20:06:26 -0800 Subject: Bumped branch version to: 2.1.19rc1 --- doc/mailman-admin/about.html | 4 +- doc/mailman-admin/contents.html | 2 +- doc/mailman-admin/front.html | 2 +- doc/mailman-admin/index.html | 4 +- doc/mailman-admin/internals.pl | 14 ++- doc/mailman-admin/labels.pl | 20 +++- doc/mailman-admin/mailman-admin.html | 4 +- doc/mailman-admin/node10.html | 206 --------------------------------- doc/mailman-admin/node11.html | 12 +- doc/mailman-admin/node12.html | 2 +- doc/mailman-admin/node13.html | 2 +- doc/mailman-admin/node14.html | 6 +- doc/mailman-admin/node15.html | 2 +- doc/mailman-admin/node16.html | 2 +- doc/mailman-admin/node17.html | 2 +- doc/mailman-admin/node18.html | 14 +-- doc/mailman-admin/node19.html | 10 +- doc/mailman-admin/node20.html | 4 +- doc/mailman-admin/node21.html | 14 +-- doc/mailman-admin/node22.html | 215 ----------------------------------- doc/mailman-admin/node23.html | 12 +- doc/mailman-admin/node24.html | 2 +- doc/mailman-admin/node25.html | 2 +- doc/mailman-admin/node26.html | 2 +- doc/mailman-admin/node27.html | 2 +- doc/mailman-admin/node28.html | 2 +- doc/mailman-admin/node29.html | 2 +- doc/mailman-admin/node3.html | 2 +- doc/mailman-admin/node30.html | 2 +- doc/mailman-admin/node31.html | 2 +- doc/mailman-admin/node32.html | 2 +- doc/mailman-admin/node33.html | 2 +- doc/mailman-admin/node34.html | 2 +- doc/mailman-admin/node35.html | 2 +- doc/mailman-admin/node4.html | 2 +- doc/mailman-admin/node5.html | 2 +- doc/mailman-admin/node6.html | 2 +- doc/mailman-admin/node7.html | 2 +- doc/mailman-admin/node8.html | 6 +- doc/mailman-admin/node9.html | 14 +-- 40 files changed, 105 insertions(+), 502 deletions(-) delete mode 100644 doc/mailman-admin/node10.html delete mode 100644 doc/mailman-admin/node22.html (limited to 'doc/mailman-admin') diff --git a/doc/mailman-admin/about.html b/doc/mailman-admin/about.html index 38175547..9f835788 100644 --- a/doc/mailman-admin/about.html +++ b/doc/mailman-admin/about.html @@ -48,7 +48,7 @@ About this document ... GNU Mailman - List Administration Manual, -September 28, 2013, Release 2.1 +January 29, 2015, Release 2.1

This document was generated using the LaTeX2HTML translator. @@ -104,7 +104,7 @@ September 28, 2013, Release 2.1


-Release 2.1, documentation updated on September 28, 2013. +Release 2.1, documentation updated on January 29, 2015. diff --git a/doc/mailman-admin/contents.html b/doc/mailman-admin/contents.html index 9aaac7a4..d30e04a8 100644 --- a/doc/mailman-admin/contents.html +++ b/doc/mailman-admin/contents.html @@ -118,7 +118,7 @@ Contents
-Release 2.1, documentation updated on September 28, 2013. +Release 2.1, documentation updated on January 29, 2015. diff --git a/doc/mailman-admin/front.html b/doc/mailman-admin/front.html index 21956da1..3228bc57 100644 --- a/doc/mailman-admin/front.html +++ b/doc/mailman-admin/front.html @@ -106,7 +106,7 @@ other manuals.
-Release 2.1, documentation updated on September 28, 2013. +Release 2.1, documentation updated on January 29, 2015. diff --git a/doc/mailman-admin/index.html b/doc/mailman-admin/index.html index a48be55f..8b4fc88f 100644 --- a/doc/mailman-admin/index.html +++ b/doc/mailman-admin/index.html @@ -45,7 +45,7 @@

GNU Mailman - List Administration Manual

Barry A. Warsaw

Release 2.1
-September 28, 2013

+January 29, 2015

@@ -122,7 +122,7 @@
-Release 2.1, documentation updated on September 28, 2013. +Release 2.1, documentation updated on January 29, 2015. diff --git a/doc/mailman-admin/internals.pl b/doc/mailman-admin/internals.pl index 8ef71735..d250b6a4 100644 --- a/doc/mailman-admin/internals.pl +++ b/doc/mailman-admin/internals.pl @@ -1,4 +1,4 @@ -# LaTeX2HTML 2002-2-1 (1.71) +# LaTeX2HTML 2008 (1.71) # Associate internals original text with physical files. @@ -6,12 +6,20 @@ $key = q/front/; $ref_files{$key} = "$dir".q|node1.html|; $noresave{$key} = "$nosave"; +$key = q/about/; +$ref_files{$key} = "$dir".q|node36.html|; +$noresave{$key} = "$nosave"; + $key = q/contents/; $ref_files{$key} = "$dir".q|node2.html|; $noresave{$key} = "$nosave"; -$key = q/about/; -$ref_files{$key} = "$dir".q|node36.html|; +$key = q/sender-filters/; +$ref_files{$key} = "$dir".q|node22.html|; +$noresave{$key} = "$nosave"; + +$key = q/general-personality/; +$ref_files{$key} = "$dir".q|node10.html|; $noresave{$key} = "$nosave"; 1; diff --git a/doc/mailman-admin/labels.pl b/doc/mailman-admin/labels.pl index 4dcf994b..9445661c 100644 --- a/doc/mailman-admin/labels.pl +++ b/doc/mailman-admin/labels.pl @@ -2,14 +2,22 @@ # Associate labels original text with physical files. -$key = q/front/; -$external_labels{$key} = "$URL/" . q|node1.html|; +$key = q/sender-filters/; +$external_labels{$key} = "$URL/" . q|node22.html|; $noresave{$key} = "$nosave"; $key = q/contents/; $external_labels{$key} = "$URL/" . q|node2.html|; $noresave{$key} = "$nosave"; +$key = q/general-personality/; +$external_labels{$key} = "$URL/" . q|node10.html|; +$noresave{$key} = "$nosave"; + +$key = q/front/; +$external_labels{$key} = "$URL/" . q|node1.html|; +$noresave{$key} = "$nosave"; + $key = q/about/; $external_labels{$key} = "$URL/" . q|node36.html|; $noresave{$key} = "$nosave"; @@ -21,5 +29,13 @@ $noresave{$key} = "$nosave"; # labels from external_latex_labels array. +$key = q/general-personality/; +$external_latex_labels{$key} = q|2.1|; +$noresave{$key} = "$nosave"; + +$key = q/sender-filters/; +$external_latex_labels{$key} = q|2.7|; +$noresave{$key} = "$nosave"; + 1; diff --git a/doc/mailman-admin/mailman-admin.html b/doc/mailman-admin/mailman-admin.html index a48be55f..8b4fc88f 100644 --- a/doc/mailman-admin/mailman-admin.html +++ b/doc/mailman-admin/mailman-admin.html @@ -45,7 +45,7 @@

GNU Mailman - List Administration Manual

Barry A. Warsaw

Release 2.1
-September 28, 2013

+January 29, 2015

@@ -122,7 +122,7 @@
-Release 2.1, documentation updated on September 28, 2013. +Release 2.1, documentation updated on January 29, 2015. diff --git a/doc/mailman-admin/node10.html b/doc/mailman-admin/node10.html deleted file mode 100644 index a4016d5f..00000000 --- a/doc/mailman-admin/node10.html +++ /dev/null @@ -1,206 +0,0 @@ - - - - - - - - - - - - - - -2.1.1 General list personality - - - - - -

-2.1.1 General list personality -

- -

-These variables, grouped under the general list personality section, -control some public information about the mailing list. - -

-

-
real_name
-
Every mailing list has both a posting name and a real - name. The posting name shows up in urls and in email addresses, - e.g. the mylist in mylist@example.com. The posting - name is always presented in lower case, with alphanumeric - characters and no spaces. The list's real name is used in some - public information and email responses, such as in the general - list overview. The real name can differ from the posting name by - case only. For example, if the posting name is mylist, the - real name can be MyList. - -

-

-
owner
-
This variable contains a list of email addresses, one address per - line, of the list owners. These addresses are used whenever the - list owners need to be contacted, either by the system or by end - users. Often, these addresses are used in combination with the - moderator addresses (see below). - -

-

-
moderator
-
This variable contains a list of email addresses, one address per - line, of the list moderators. These addresses are often used in - combination with the owner addresses. For example, when - you email mylist-owner@example.com, both the owner and - moderator addresses will receive a copy of the message. - -

-

-
description
-
In the general list overview page, which shows you every available - mailing list, each list is displayed with a short description. - The contents of this variable is that description. Note that in - emails from the mailing list, this description is also used in the - comment section of the To: address. This text should - be relatively short and no longer than one line. - -

-

-
info
-
This variable contains a longer description of the mailing list. - It is included at the top of the list's information page, and it - can contain HTML. However, blank lines will be automatically - converted into paragraph breaks. Preview your HTML though, - because unclosed or invalid HTML can prevent display of parts of - the list information page. - -

-

-
subject_prefix
-
This is a string that will be prepended to the - Subject: header of any message posted to the list. - For example, if a message is posted to the list with a - Subject: like: - -

-

-    Subject: This is a message
-
- -

-and the subject_prefix is [My List] (note the - trailing space!), then the message will be received like so: - -

-

-    Subject: [My List] This is a message
-
- -

-If you leave subject_prefix empty, no prefix will be added - to the Subject:. Mailman is careful not to add a - prefix when the header already has one, as is the case in replies - for example. The prefix can also contain characters in the list's - preferred language. In this case, because of vagarities of the - email standards, you may or may not want to add a trailing space. - -

-

-
from_is_list
-
Setting this variable to Yes causes the From: - address to be replaced by the list address so that policies like - ADSP or DMARC can be applied. - -

-

-
anonymous_list
-
This variable allows you to turn on some simple anonymizing - features of Mailman. When you set this option to Yes, - Mailman will remove or replace the From:, - Sender:, and Reply-To: fields of any - message posted to the list. - -

-Note that this option is simply an aid for anonymization, it - doesn't guarantee it. For example, a poster's identity could be - evident in their signature, or in other mail headers, or even in - the style of the content of the message. There's little Mailman - can do about this kind of identity leakage. -

-
- -

- -

- - - - diff --git a/doc/mailman-admin/node11.html b/doc/mailman-admin/node11.html index c52ad0d7..fded1ca8 100644 --- a/doc/mailman-admin/node11.html +++ b/doc/mailman-admin/node11.html @@ -7,7 +7,7 @@ - + @@ -20,7 +20,7 @@
Previous: - + Up: 2.1 The General Options Next: @@ -165,7 +165,7 @@ When you set this variable to Explicit address, the value
Explicit address, the value
Previous: - + Up: 2.1 The General Options Next: @@ -192,7 +192,7 @@ When you set this variable to Explicit address, the value

-Release 2.1, documentation updated on September 28, 2013. +Release 2.1, documentation updated on January 29, 2015. diff --git a/doc/mailman-admin/node12.html b/doc/mailman-admin/node12.html index e7e5c3b4..a2beea94 100644 --- a/doc/mailman-admin/node12.html +++ b/doc/mailman-admin/node12.html @@ -92,7 +92,7 @@ a better mechanism for Mailman 3.0.
-Release 2.1, documentation updated on September 28, 2013. +Release 2.1, documentation updated on January 29, 2015. diff --git a/doc/mailman-admin/node13.html b/doc/mailman-admin/node13.html index 9e3c5546..52084f13 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
-Release 2.1, documentation updated on September 28, 2013. +Release 2.1, documentation updated on January 29, 2015. diff --git a/doc/mailman-admin/node14.html b/doc/mailman-admin/node14.html index 984d2399..1797dbb9 100644 --- a/doc/mailman-admin/node14.html +++ b/doc/mailman-admin/node14.html @@ -131,7 +131,7 @@ It's generally not a good idea to change this value, since its

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 @@ -153,7 +153,7 @@ However, not all mail readers are standards compliant yet, and if
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 @@ -199,7 +199,7 @@ href="http://www.faqs.org/rfcs/rfc2369.html">RFC 2369. However for some ann
-Release 2.1, documentation updated on September 28, 2013. +Release 2.1, documentation updated on January 29, 2015. diff --git a/doc/mailman-admin/node15.html b/doc/mailman-admin/node15.html index e73e6d8f..5484177d 100644 --- a/doc/mailman-admin/node15.html +++ b/doc/mailman-admin/node15.html @@ -112,7 +112,7 @@ password, be sure to fill in the moderator variable in the
-Release 2.1, documentation updated on September 28, 2013. +Release 2.1, documentation updated on January 29, 2015. diff --git a/doc/mailman-admin/node16.html b/doc/mailman-admin/node16.html index f28dd3f1..3f9f318b 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
-Release 2.1, documentation updated on September 28, 2013. +Release 2.1, documentation updated on January 29, 2015. diff --git a/doc/mailman-admin/node17.html b/doc/mailman-admin/node17.html index 10e3f779..1f27ea0f 100644 --- a/doc/mailman-admin/node17.html +++ b/doc/mailman-admin/node17.html @@ -100,7 +100,7 @@ Management section.
-Release 2.1, documentation updated on September 28, 2013. +Release 2.1, documentation updated on January 29, 2015. diff --git a/doc/mailman-admin/node18.html b/doc/mailman-admin/node18.html index 27ab167e..009d101e 100644 --- a/doc/mailman-admin/node18.html +++ b/doc/mailman-admin/node18.html @@ -140,7 +140,7 @@ 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 required2. + href="#foot322">2.

For example, a footer containing the following text: @@ -175,7 +175,7 @@ and footers:

list_name
This is the canonical name of the mailing list. In other words it's the posting address of the list3. + href="#foot323">3.

@@ -227,7 +227,7 @@ are also available:
user_delivered_to
The case-preserved address that the user subscribed to the mailing list with4. + href="#foot324">4.

@@ -249,7 +249,7 @@ are also available:



Footnotes

-
... +
... required2
The site administrator can configure lists to use a @@ -259,14 +259,14 @@ name. Ask your site administrator if the've configured your list this way.
-
... list... list3
For backward compatibility, the variable _internal_name is equivalent.
-
... with... with4
Usually it makes no difference which of user_address and user_delivered_to is used, but it's @@ -310,7 +310,7 @@ way.
-Release 2.1, documentation updated on September 28, 2013. +Release 2.1, documentation updated on January 29, 2015. diff --git a/doc/mailman-admin/node19.html b/doc/mailman-admin/node19.html index 9808cdff..3a67a9c7 100644 --- a/doc/mailman-admin/node19.html +++ b/doc/mailman-admin/node19.html @@ -71,7 +71,7 @@ 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. @@ -89,7 +89,7 @@ the message with a Urgent: header, where the val header is the list administrator's password. Non-digest members will receive the message like normal, but digest members will receive the message immediately5. + href="#foot195">5.

Here are the variables which control digest delivery: @@ -114,7 +114,7 @@ Here are the variables which control 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.

@@ -180,7 +180,7 @@ href="http://www.faqs.org/rfcs/rfc1153.html">RFC 1153 format as described ab



Footnotes

-
... immediately... immediately5
They'll also receive the message in the digest. @@ -220,7 +220,7 @@ digest.
-Release 2.1, documentation updated on September 28, 2013. +Release 2.1, documentation updated on January 29, 2015. diff --git a/doc/mailman-admin/node20.html b/doc/mailman-admin/node20.html index 6e0b980f..1929e013 100644 --- a/doc/mailman-admin/node20.html +++ b/doc/mailman-admin/node20.html @@ -131,7 +131,7 @@ begins with a (caret) character. @@ -171,7 +171,7 @@ begins with a (caret) character.
-Release 2.1, documentation updated on September 28, 2013. +Release 2.1, documentation updated on January 29, 2015. diff --git a/doc/mailman-admin/node21.html b/doc/mailman-admin/node21.html index f2908b2c..569aae9f 100644 --- a/doc/mailman-admin/node21.html +++ b/doc/mailman-admin/node21.html @@ -6,10 +6,10 @@ - + - + 2.7.1 Subscription rules @@ -26,7 +26,7 @@ href="node20.html">Up one Level GNU Mailman - List Administration Manual Up: 2.7 The Privacy Options Next: - +
@@ -175,7 +175,7 @@ list. href="node20.html">Up one Level GNU Mailman - List Administration Manual Up: 2.7 The Privacy Options Next: - +
-Release 2.1, documentation updated on September 28, 2013. +Release 2.1, documentation updated on January 29, 2015. diff --git a/doc/mailman-admin/node22.html b/doc/mailman-admin/node22.html deleted file mode 100644 index d1e79c9f..00000000 --- a/doc/mailman-admin/node22.html +++ /dev/null @@ -1,215 +0,0 @@ - - - - - - - - - - - - - - -2.7.2 Sender filters - - - - - -

-2.7.2 Sender filters -

- -

-When a message is posted to the list, a series of moderation criteria are -applied to determine the disposition of the message. This section -contains the modeation controls for postings from both members and -non-members. - -

-

-
default_member_moderation
-
Member postings are held for moderation if their moderation - flag is turned on. Note that only the list administrators can - change the value of a member's moderation flag. - -

-You can control whether new members get their moderation flag - turned on or off by default when they subscribe to the list. By - turning this flag off by default, postings by members will be - allowed without further intervention (barring other restrictions - such as size or implicit recipient lists - see below). By - turning the flag on, you can quarantine new member postings to - make sure that they meet your criteria for netiquette, topicality, - etc. Once you determine that the new member understands the - community's posting rules, you can turn off their moderation flag - and let their postings go through unstopped. - -

-E-newsletter style lists can also be set up by using the - moderation flag. By setting the member_moderation_action - to Reject, and by turning off the moderation flag for just - the few approved senders, your list will operate in essentially a - one-way direction. Note that you'd also need to reject or discard - postings from non-members. - -

-

-
member_moderation_action
-
This is the action to take for postings from a member who's - moderation flag is set. For typical discussion lists, you'll - likely set this to Hold so that the list moderator will get - a chance to manually approve, reject, or discard the message. For - e-newsletter and announcement lists, you might want to set this to - Reject or Discard. - -

-Note that when a moderated member posts to your list, and the - member_moderation_action is set to Hold, the message - will appear on the administrative requests page. When you dispose - of the message, you will be given an opportunity to clear the - moderation flag at the same time. If you're quarantining new - posts, this makes it very convenient to both approve a new - member's post and de-moderate them at the same time. - -

-

-
member_moderation_notice
-
When a member's moderation flag is turned on and - member_moderation_action is Reject, this variable - contains the text sent in the rejection notice. -
-
- -

-The next batch of variables controls what happens when non-members -post messages to the list. Each of these accepts one email address -per line; regular expressions are allowed if the line starts with the -(caret) character. These address lists are always consulted in the -order in which they're presented on this page (i.e. accepts first, -followed by holds, rejections, and discards). - -

-

-
accept_these_nonmembers
-
Postings from non-members whose addresses match this list are - accepted, barring other list restrictions due to size, implicit - recipients, etc. You might want to add alternative addresses of - approved posters to this list. - -

-

-
hold_these_nonmembers
-
Postings from non-members whose addresses match this list are - held for moderator approval. - -

-

-
reject_these_nonmembers
-
Postings from non-members whose addresses match this list are - rejected, i.e. bounced back to the original sender. There - currently is no way to add additional text to the rejection - message. - -

-

-
discard_these_nonmembers
-
Postings from non-members whose addresses match this list are - discarded, with no bounce back message. You might want to add the - addresses of known spammers to this list. - -

-

-
generic_nonmember_action
-
This variable controls what happens to non-member posts when the - address of the sender doesn't match any of the above four lists. - If you set this to Hold, the posting will appear on the - administrative requests page, and you will be given an opportunity - to add the non-member to one of the above four lists at the same - time you dispose of the held message. - -

-

-
forward_auto_discards
-
When messages from non-members are discarded, either because the - sender address matched discard_these_nonmembers, or because - generic_nonmember_action is Discard, you can choose - whether such messages are forwarded to the lsit administrators or - not. -
-
- -

- -

- - - - diff --git a/doc/mailman-admin/node23.html b/doc/mailman-admin/node23.html index 35f8830d..d98654f1 100644 --- a/doc/mailman-admin/node23.html +++ b/doc/mailman-admin/node23.html @@ -7,7 +7,7 @@ - + @@ -20,7 +20,7 @@
Previous: - + Up: 2.7 The Privacy Options Next: @@ -98,7 +98,7 @@ If the list is not explicitly addressed and this setting is turned
Previous: - + Up: 2.7 The Privacy Options Next: @@ -125,7 +125,7 @@ If the list is not explicitly addressed and this setting is turned

-Release 2.1, documentation updated on September 28, 2013. +Release 2.1, documentation updated on January 29, 2015. diff --git a/doc/mailman-admin/node24.html b/doc/mailman-admin/node24.html index 7e66b2dc..9344e5c8 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
-Release 2.1, documentation updated on September 28, 2013. +Release 2.1, documentation updated on January 29, 2015. diff --git a/doc/mailman-admin/node25.html b/doc/mailman-admin/node25.html index 7b1eb802..5a03afa8 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.
-Release 2.1, documentation updated on September 28, 2013. +Release 2.1, documentation updated on January 29, 2015. diff --git a/doc/mailman-admin/node26.html b/doc/mailman-admin/node26.html index bd79eeac..f25a7330 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
-Release 2.1, documentation updated on September 28, 2013. +Release 2.1, documentation updated on January 29, 2015. diff --git a/doc/mailman-admin/node27.html b/doc/mailman-admin/node27.html index bd2307c3..4454dd6a 100644 --- a/doc/mailman-admin/node27.html +++ b/doc/mailman-admin/node27.html @@ -93,7 +93,7 @@ even be used to manage moderated newsgroups.
-Release 2.1, documentation updated on September 28, 2013. +Release 2.1, documentation updated on January 29, 2015. diff --git a/doc/mailman-admin/node28.html b/doc/mailman-admin/node28.html index ad1c0d82..2b7c9157 100644 --- a/doc/mailman-admin/node28.html +++ b/doc/mailman-admin/node28.html @@ -86,7 +86,7 @@
-Release 2.1, documentation updated on September 28, 2013. +Release 2.1, documentation updated on January 29, 2015. diff --git a/doc/mailman-admin/node29.html b/doc/mailman-admin/node29.html index 786638ae..2ea50c72 100644 --- a/doc/mailman-admin/node29.html +++ b/doc/mailman-admin/node29.html @@ -86,7 +86,7 @@
-Release 2.1, documentation updated on September 28, 2013. +Release 2.1, documentation updated on January 29, 2015. diff --git a/doc/mailman-admin/node3.html b/doc/mailman-admin/node3.html index 87bf070e..1c5230fd 100644 --- a/doc/mailman-admin/node3.html +++ b/doc/mailman-admin/node3.html @@ -121,7 +121,7 @@ manual for more details.
-Release 2.1, documentation updated on September 28, 2013. +Release 2.1, documentation updated on January 29, 2015. diff --git a/doc/mailman-admin/node30.html b/doc/mailman-admin/node30.html index efcf9ea3..5518ab55 100644 --- a/doc/mailman-admin/node30.html +++ b/doc/mailman-admin/node30.html @@ -87,7 +87,7 @@
-Release 2.1, documentation updated on September 28, 2013. +Release 2.1, documentation updated on January 29, 2015. diff --git a/doc/mailman-admin/node31.html b/doc/mailman-admin/node31.html index 297679ee..a1f2cc84 100644 --- a/doc/mailman-admin/node31.html +++ b/doc/mailman-admin/node31.html @@ -86,7 +86,7 @@
-Release 2.1, documentation updated on September 28, 2013. +Release 2.1, documentation updated on January 29, 2015. diff --git a/doc/mailman-admin/node32.html b/doc/mailman-admin/node32.html index 7cb64501..17d5059a 100644 --- a/doc/mailman-admin/node32.html +++ b/doc/mailman-admin/node32.html @@ -86,7 +86,7 @@
-Release 2.1, documentation updated on September 28, 2013. +Release 2.1, documentation updated on January 29, 2015. diff --git a/doc/mailman-admin/node33.html b/doc/mailman-admin/node33.html index e20d7d3f..f54db63c 100644 --- a/doc/mailman-admin/node33.html +++ b/doc/mailman-admin/node33.html @@ -86,7 +86,7 @@
-Release 2.1, documentation updated on September 28, 2013. +Release 2.1, documentation updated on January 29, 2015. diff --git a/doc/mailman-admin/node34.html b/doc/mailman-admin/node34.html index ced74540..329bb1ce 100644 --- a/doc/mailman-admin/node34.html +++ b/doc/mailman-admin/node34.html @@ -90,7 +90,7 @@
-Release 2.1, documentation updated on September 28, 2013. +Release 2.1, documentation updated on January 29, 2015. diff --git a/doc/mailman-admin/node35.html b/doc/mailman-admin/node35.html index 923f26f8..9ac5b92e 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.
-Release 2.1, documentation updated on September 28, 2013. +Release 2.1, documentation updated on January 29, 2015. diff --git a/doc/mailman-admin/node4.html b/doc/mailman-admin/node4.html index 39a9718c..ff9467e0 100644 --- a/doc/mailman-admin/node4.html +++ b/doc/mailman-admin/node4.html @@ -152,7 +152,7 @@ older versions of Mailman.
-Release 2.1, documentation updated on September 28, 2013. +Release 2.1, documentation updated on January 29, 2015. diff --git a/doc/mailman-admin/node5.html b/doc/mailman-admin/node5.html index 8f35de73..4e895a49 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.
-Release 2.1, documentation updated on September 28, 2013. +Release 2.1, documentation updated on January 29, 2015. diff --git a/doc/mailman-admin/node6.html b/doc/mailman-admin/node6.html index 2485c636..01c30bee 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.
-Release 2.1, documentation updated on September 28, 2013. +Release 2.1, documentation updated on January 29, 2015. diff --git a/doc/mailman-admin/node7.html b/doc/mailman-admin/node7.html index e570a613..0cd168e1 100644 --- a/doc/mailman-admin/node7.html +++ b/doc/mailman-admin/node7.html @@ -139,7 +139,7 @@ stored for appending to digests.
-Release 2.1, documentation updated on September 28, 2013. +Release 2.1, documentation updated on January 29, 2015. diff --git a/doc/mailman-admin/node8.html b/doc/mailman-admin/node8.html index 44f3ec93..43ccae69 100644 --- a/doc/mailman-admin/node8.html +++ b/doc/mailman-admin/node8.html @@ -108,7 +108,7 @@ will always be the category page that you submitted.