Browsing Vietnamese translation

669.

One of these actions is take when the message matches one of
the content filtering rules, meaning, the top-level
content type matches one of the <a
href="?VARHELP=contentfilter/filter_mime_types"
>filter_mime_types</a>, or the top-level content type does
<strong>not</strong> match one of the
<a href="?VARHELP=contentfilter/pass_mime_types"
>pass_mime_types</a>, or if after filtering the subparts of the
message, the message ends up empty.

<p>Note this action is not taken if after filtering the message
still contains content. In that case the message is always
forwarded on to the list membership.

<p>When messages are discarded, a log entry is written
containing the Message-ID of the discarded message. When
messages are rejected or forwarded to the list owner, a reason
for the rejection is included in the bounce message to the
original author. When messages are preserved, they are saved in
a special queue directory on disk for the site administrator to
view (and possibly rescue) but otherwise discarded. This last
option is only available if enabled by the site
administrator.

716.

This text will be prepended to subject lines of messages
posted to the list, to distinguish mailing list messages in in
mailbox summaries. Brevity is premium here, it's ok to shorten
long mailing list names to something more concise, as long as it
still identifies the mailing list.
You can also add a sequencial number by %%d substitution
directive. eg.; [listname %%d] -> [listname 123]
(listname %%05d) -> (listname 00123)

1205.

po2templ.py

Extract templates from language po file.

Usage: po2templ.py languages

1206.

Run one or more qrunners, once or repeatedly.

Each named runner class is run in round-robin fashion. In other words, the
first named runner is run to consume all the files currently in its
directory. When that qrunner is done, the next one is run to consume all the
files in /its/ directory, and so on. The number of total iterations can be
given on the command line.

Usage: %(PROGRAM)s [options]

Options:

-r runner[:slice:range]
--runner=runner[:slice:range]
Run the named qrunner, which must be one of the strings returned by
the -l option. Optional slice:range if given, is used to assign
multiple qrunner processes to a queue. range is the total number of
qrunners for this queue while slice is the number of this qrunner from
[0..range).

If using the slice:range form, you better make sure that each qrunner
for the queue is given the same range value. If slice:runner is not
given, then 1:1 is used.

Multiple -r options may be given, in which case each qrunner will run
once in round-robin fashion. The special runner `All' is shorthand
for a qrunner for each listed by the -l option.

--once
-o
Run each named qrunner exactly once through its main loop. Otherwise,
each qrunner runs indefinitely, until the process receives a SIGTERM
or SIGINT.

-l/--list
Shows the available qrunner names and exit.

-v/--verbose
Spit out more debugging information to the logs/qrunner log file.

-s/--subproc
This should only be used when running qrunner as a subprocess of the
mailmanctl startup script. It changes some of the exit-on-error
behavior to work better with that framework.

-h/--help
Print this message and exit.

runner is required unless -l or -h is given, and it must be one of the names
displayed by the -l switch.

1244.

templ2pot.py -- convert mailman template (en) to pot format.

Usage: templ2pot.py inputfile ...

Options:

-h, --help

Inputfiles are english templates. Outputs are written to stdout.

1329.

The administrative requests are displayed in one of two ways, on a <a
href="%(summaryurl)s">summary page</a>, and on a <em>details</em>
page. The summary page contains pending subscription and
unsubscription requests, as well as postings being held for your
approval, grouped by sender email address. The details page contains
a more detailed view of each held message, including the all the
message's headers and an excerpt of the message body.

<p>On all the pages, the following actions are available:

<ul>
<li><b>Defer</b> -- Defer your decision until later. No action is
taken now for this pending administrative request, but for held
postings, you can still forward or preserve the message (see
below).

<li><b>Approve</b> -- Approve the message, sending it on to the list.
For membership requests, approve the change in membership status.

<li><b>Reject</b> -- Reject the message, sending a rejection notice to
the sender, and discarding the original message. For membership
requests, reject the change in membership status. In either case,
you should add a reason for the rejection in the accompanying text
box.

<li><b>Discard</b> -- Throw away the original message, without sending
a rejection notice. For membership requests, this simply discards
the request without notice to the person making the request. This
is usually the action you want to take for known spam.
</ul>

<p>For held messages, turn on the <b>Preserve</b> option if you want
to save a copy of the message for the site administrator. This is
useful for abusive messages that you want to discard, but need to keep
a record of for later inspection.

<p>Turn on the <b>Forward to</b> option, and fill in the forwarding
address if you want to forward the message to someone else not on the
list. To edit a held message before it is sent on to the list, you
should forward the message to yourself (or the list owners), and
discard the original message. Then, when the message shows up in your
mailbox, make your edits and resend the message to the list, including
an <tt>Approved:</tt> header with the list password as its value. It
is proper netiquette in this case to include a note in the resent
message, explaining that you have modified the text.

<p>If the sender is a list member who is being moderated, you can
optionally clear their moderation flag. This is useful when your list
is configured to put new members on probation, and you've decided that
this member can be trusted to post to the list without approval.

<p>If the sender is not a list member, you can add the email address to
a <em>sender filter</em>. Sender filters are described on the <a
href="%(filterurl)s">sender filter privacy page</a>, and may be one of
<b>auto-accept</b> (Accepts), <b>auto-hold</b> (Holds),
<b>auto-reject</b> (Rejects), or <b>auto-discard</b> (Discards). This
option will not be available if the address is already on one of the
sender filters.

<p>When you're finished, click on the <em>Submit All Data</em> button
at the top or bottom of the page. This button will submit all
selected actions for all administrative requests that you've made a
decision for.

<p><a href="%(summaryurl)s">Return to the summary page</a>.

1330.

This page contains a subset of the <em>%(listname)s</em> mailing list
postings that are being held for your approval. It currently shows
%(description)s

<p>For each administrative request, please select the action to take,
clicking on the <b>Submit All Data</b> when finished. More detailed
instructions are available <a href="%(detailsurl)s">here</a>.

<p>You can also <a href="%(summaryurl)s">view a summary</a> of all
pending requests.

1331.

This page contains a summary of the current set of administrative
requests requiring your approval for the
<a href="%(adminurl)s"><em>%(listname)s</em> mailing list</a>.
First, you will find the list of pending
subscription and unsubscription requests, if any, followed by any
postings being held for your approval.

<p>For each administrative request, please select the action to take,
clicking on the <b>Submit All Data</b> button when finished.
<a href="%(detailsurl)s">More detailed instructions</a> are also
available.

<p>You can also <a href="%(viewallurl)s">view the details</a> of all
held postings.

1332.

%(member)s has been successfully subscribed to %(listname)s.

1333.

%(member)s has been removed from %(listname)s.