------------------------------------------------------------
revno: 115
fixes bug: https://launchpad.net/bugs/1427327
committer: Mark Sapiro <m...@msapiro.net>
branch nick: admin
timestamp: Mon 2015-03-02 14:52:17 -0800
message:
Fixed some typos and missing '^' in Mailman-admin manual.
modified:
doc/mailman-admin.tex
--
lp:mailman-administrivia
https://code.launchpad.net/~mailman-administrivia/mailman-administrivia/admin
Your team Mailman Checkins is subscribed to branch lp:mailman-administrivia.
To unsubscribe from this branch go to
https://code.launchpad.net/~mailman-administrivia/mailman-administrivia/admin/+edit-subscription
=== modified file 'doc/mailman-admin.tex'
--- doc/mailman-admin.tex 2014-05-11 05:08:28 +0000
+++ doc/mailman-admin.tex 2015-03-02 22:52:17 +0000
@@ -97,7 +97,7 @@
subscription options, as well as process other commands.
\item mylist-boun...@example.com -- This address receives bounces from
- members who's addresses have become either temporarily or
+ 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
@@ -145,7 +145,7 @@
\subsection{A List's Web Pages}
Every mailing list is also accessible by a number of web pages. Note
-that the exact urls is configurable by the site administrator, so they
+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 default configuration, but check with your site administrator
or hosting service for details.
@@ -203,7 +203,7 @@
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
+Every message in the queues is 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
@@ -336,14 +336,14 @@
to the \mailheader{Subject}. Mailman is careful not to add a
prefix when the header already has one, as is the case in replies
for example. The prefix can also contain characters in the list's
- preferred language. In this case, because of vagarities of the
+ preferred language. In this case, because of the vagaries of the
email standards, you may or may not want to add a trailing space.
\item[from_is_list]
This applies to all non-digest messages sent by the list. For settings
that apply only to messages whose \mailheader{From} domain publishes a
DMARC \code{p=reject} or \code{p=quarantine} policy, see the
- \code{dmarc_moderaction_action} description in section
+ \code{dmarc_moderation_action} description in section
\ref{sender-filters}.
If set to \emph{Munge From}, it replaces the \mailheader{From} header
@@ -381,7 +381,7 @@
agnostic as possible, but our biases may still peak through.
\mailheader{Reply-To} is a header that is commonly used to redirect
-replies to messages. Exactly what happens when your uses reply to
+replies to messages. Exactly what happens when your users reply to
such a message depends on the mail readers your users use, and what
functions they provide. Usually, there is both a ``reply to sender''
button and a ``reply to all'' button. If people use these buttons
@@ -457,7 +457,7 @@
\subsubsection{Umbrella list settings}
-TBD. Note that umbrella lists are deprecated and will be replace with
+TBD. Note that umbrella lists are deprecated and will be replaced with
a better mechanism for Mailman 3.0.
\subsubsection{Notifications}
@@ -590,7 +590,7 @@
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
+ contact your mailing list. Also note 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.
@@ -670,7 +670,7 @@
the list administrative pages will be displayed in. Also any
messages sent to the list owners by Mailman will be sent in this
language. This option is presented as a drop-down list containing
- the language enabled in the \code{available_languages} variable.
+ the languages enabled in the \code{available_languages} variable.
\item[available_languages]
This set of checkboxes contains all the natural languages that
@@ -705,7 +705,7 @@
The \emph{Membership Management} category is unlike the other
administrative categories. It doesn't contain configuration variables
or list settings. Instead, it presents a number of pages that allow
-you to manage the membership of you list. This includes pages for
+you to manage the membership of your list. This includes pages for
subscribing and unsubscribing members, and for searching for members,
and for changing various member-specific settings.
@@ -715,7 +715,7 @@
\subsection{The Non-digest Options Category}
Mailman delivers messages to users via two modes. List members can
-elect to receive postings in bundles call \emph{digests} one or a few
+elect to receive postings in bundles called \emph{digests} one or a few
times a day, or they can receive messages immediately whenever the
message is posted to the list. This latter delivery mode is also
called \emph{non-digest delivery}. There are two administrative
@@ -787,7 +787,7 @@
required\footnote{The site administrator can configure lists to use a
simpler interpolation format, where \code{\$list_name} or
\code{\$\{list_name\}} would be substituted with the mailing list's
-name. Ask your site administrator if the've configured your list this
+name. Ask your site administrator if they've configured your list this
way.}.
For example, a footer containing the following text:
@@ -885,7 +885,7 @@
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
+adhere to the \rfc{1153} digest standard. They retain some, but not
all of the original messages, but can also include a summary and
headers and footers.
@@ -1014,11 +1014,11 @@
Many of the fields in this section are text boxes accepting addresses,
one per line. Unless otherwise noted, these also accept regular
expressions which will be matched against an address, if the line
-begins with a \^ (caret) character.
+begins with a \textasciicircum \ (caret) character.
\subsubsection{Subscription rules}
-This subcategory controls the rules for exposing the existance of this
+This subcategory controls the rules for exposing the existence of this
list, and for what new members must do in order to subscribe to the
list.
@@ -1079,7 +1079,7 @@
employees to unsubscribe from the company newsletter.
\item[ban_list]
- This contains a list of addresses (or regular expressiosn), one
+ This contains a list of addresses (or regular expressions), one
per line, that are banned from ever subscribing to your mailing
list. If a match occurs during the subscription process, the
request will be automatically rejected, and the requester will get
@@ -1093,7 +1093,7 @@
just list members, or just to the list administrators. In the
former case, a user must enter a valid member's address and
password before they can view the roster. In the latter case, a
- list administrator's password must be enter; if a matching admin
+ list administrator's password must be entered; if a matching admin
password is entered, address field is ignored.
\item[obscure_addresses]
@@ -1105,9 +1105,9 @@
\subsubsection{Sender filters\label{sender-filters}}
-When a message is posted to the list, a series of moderation criteria are
+When a message is posted to the list, a series of moderation criteria is
applied to determine the disposition of the message. This section
-contains the modeation controls for postings from both members and
+contains the moderation controls for postings from both members and
non-members.
\begin{description}
@@ -1184,9 +1184,9 @@
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).
+\textasciicircum \ (caret) character. These address lists are always
+consulted in the order in which they're presented on this page (i.e.
+accepts first, followed by holds, rejections, and discards).
\begin{description}
\item[accept_these_nonmembers]
@@ -1202,7 +1202,7 @@
\item[reject_these_nonmembers]
Postings from non-members whose addresses match this list are
rejected, i.e. bounced back to the original sender. There
- currently is no way to add additional text to the rejection
+ is currently no way to add additional text to the rejection
message.
\item[discard_these_nonmembers]
@@ -1222,7 +1222,7 @@
When messages from non-members are discarded, either because the
sender address matched \code{discard_these_nonmembers}, or because
\code{generic_nonmember_action} is \emph{Discard}, you can choose
- whether such messages are forwarded to the lsit administrators or
+ whether such messages are forwarded to the list administrators or
not.
\end{description}
@@ -1261,7 +1261,7 @@
This section provides some adjuncts to spam fighting tools; it
doesn't replace dedicated anti-spam tools such as SpamAssassin or
-Spambayes.
+SpamBayes.
\begin{description}
\item[bounce_matching_headers]
@@ -1339,9 +1339,9 @@
floating point number.
\item[bounce_info_stale_after]
- Thenumber of days after which a member's bounce information is
+ The number of days after which a member's bounce information is
considered stale. If no new bounces have been received in the
- interrim, the bounce score is reset to zero. This value must be
+ interim, the bounce score is reset to zero. This value must be
an integer.
\item[bounce_you_are_disabled_warnings]
_______________________________________________
Mailman-checkins mailing list
Mailman-checkins@python.org
Unsubscribe:
https://mail.python.org/mailman/options/mailman-checkins/archive%40jab.org
