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
Barry A. Warsaw 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
-September 28, 2013
Barry A. Warsaw
Release 2.1
-September 28, 2013
-These variables, grouped under the general list personality section, -control some public information about the mailing list. - -
-
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
.
-
--
moderator
addresses (see below).
-
--
owner
addresses. For example, when
- you email mylist-owner@example.com
, both the owner and
- moderator addresses will receive a copy of the message.
-
--
-
-
-
- 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.
-
-
-
-
-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 @@
moderator
variable in the
%(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:
_internal_name
is
equivalent.
user_address
and user_delivered_to
is used, but it's
@@ -310,7 +310,7 @@ way.
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:
@@ -180,7 +180,7 @@ href="http://www.faqs.org/rfcs/rfc1153.html">RFC 1153 format as described ab
-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. - -
-
-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.
-
-
-
-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_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). - -
-
-
-
-
-
-
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 @@