Browsing Czech translation

705.

This option controls what Mailman does to the
<tt>Reply-To:</tt> header in messages flowing through this
mailing list. When set to <em>Poster</em>, no <tt>Reply-To:</tt>
header is added by Mailman, although if one is present in the
original message, it is not stripped. Setting this value to
either <em>This list</em> or <em>Explicit address</em> causes
Mailman to insert a specific <tt>Reply-To:</tt> header in all
messages, overriding the header in the original message if
necessary (<em>Explicit address</em> inserts the value of <a
href="?VARHELP=general/reply_to_address">reply_to_address</a>).

<p>There are many reasons not to introduce or override the
<tt>Reply-To:</tt> header. One is that some posters depend on
their own <tt>Reply-To:</tt> settings to convey their valid
return address. Another is that modifying <tt>Reply-To:</tt>
makes it much more difficult to send private replies. See <a
href="http://www.unicom.com/pw/reply-to-harmful.html">`Reply-To'
Munging Considered Harmful</a> for a general discussion of this
issue. See <a
href="http://www.metasystema.org/essays/reply-to-useful.mhtml">Reply-To
Munging Considered Useful</a> for a dissenting opinion.

<p>Some mailing lists have restricted posting privileges, with a
parallel list devoted to discussions. Examples are `patches' or
`checkin' lists, where software changes are posted by a revision
control system, but discussion about the changes occurs on a
developers mailing list. To support these types of mailing
lists, select <tt>Explicit address</tt> and set the
<tt>Reply-To:</tt> address below to point to the parallel
list.

827.

Each header filter rule has two parts, a list of regular
expressions, one per line, and an action to take. Mailman
matches the message's headers against every regular expression in
the rule and if any match, the message is rejected, held, or
discarded based on the action you specify. Use <em>Defer</em> to
temporarily disable a rule.

You can have more than one filter rule for your list. In that
case, each rule is matched in turn, with processing stopped after
the first match.

1026.

Add members to a list from the command line.

Usage:
add_members [options] listname

Options:

--regular-members-file=file
-r file
A file containing addresses of the members to be added, one
address per line. This list of people become non-digest
members. If file is `-', read addresses from stdin. Note that
-n/--non-digest-members-file are deprecated synonyms for this option.

--digest-members-file=file
-d file
Similar to above, but these people become digest members.

--welcome-msg=<y|n>
-w <y|n>
Set whether or not to send the list members a welcome message,
overriding whatever the list's `send_welcome_msg' setting is.

--admin-notify=<y|n>
-a <y|n>
Set whether or not to send the list administrators a notification on
the success/failure of these subscriptions, overriding whatever the
list's `admin_notify_mchanges' setting is.

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

listname
The name of the Mailman list you are adding members to. It must
already exist.

You must supply at least one of -r and -d options. At most one of the
files can be `-'.

1037.

Rebuild a list's archive.

Use this command to rebuild the archives for a mailing list. You may want to
do this if you edit some messages in an archive, or remove some messages from
an archive.

Usage: %(PROGRAM)s [options] <listname> [<mbox>]

Where options are:
-h / --help
Print this help message and exit.

-q / --quiet
Make the archiver output less verbose.

--wipe
First wipe out the original archive before regenerating. You usually
want to specify this argument unless you're generating the archive in
chunks.

-s N
--start=N
Start indexing at article N, where article 0 is the first in the mbox.
Defaults to 0.

-e M
--end=M
End indexing at article M. This script is not very efficient with
respect to memory management, and for large archives, it may not be
possible to index the mbox entirely. For that reason, you can specify
the start and end article numbers.

Where <mbox> is the path to a list's complete mbox archive. Usually this will
be some path in the archives/private directory. For example:

%% bin/arch mylist archives/private/mylist.mbox/mylist.mbox

<mbox> is optional. If it is missing, it is calculated.

1041.

Fix the MM2.1b4 archives.

Usage: %(PROGRAM)s [options] file ...

Where options are:
-h / --help
Print this help message and exit.

Only use this to `fix' some archive database files that may have gotten
written in Mailman 2.1b4 with some bogus data. Use like this from your
$PREFIX directory

%% %(PROGRAM)s `grep -l _mlist archives/private/*/database/*-article`

(note the backquotes are required)

You will need to run `bin/check_perms -f' after running this script.

1042.

Change a list's password.

Prior to Mailman 2.1, list passwords were kept in crypt'd format -- usually.
Some Python installations didn't have the crypt module available, so they'd
fall back to md5. Then suddenly the Python installation might grow a crypt
module and all list passwords would be broken.

In Mailman 2.1, all list and site passwords are stored in SHA1 hexdigest
form. This breaks list passwords for all existing pre-Mailman 2.1 lists, and
since those passwords aren't stored anywhere in plain text, they cannot be
retrieved and updated.

Thus, this script generates new passwords for a list, and optionally sends it
to all the owners of the list.

Usage: change_pw [options]

Options:

--all / -a
Change the password for all lists.

--domain=domain
-d domain
Change the password for all lists in the virtual domain `domain'. It
is okay to give multiple -d options.

--listname=listname
-l listname
Change the password only for the named list. It is okay to give
multiple -l options.

--password=newpassword
-p newpassword
Use the supplied plain text password `newpassword' as the new password
for any lists that are being changed (as specified by the -a, -d, and
-l options). If not given, lists will be assigned a randomly
generated new password.

--quiet / -q
Don't notify list owners of the new password. You'll have to have
some other way of letting the list owners know the new password
(presumably out-of-band).

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

1047.

The site administrator at %(hostname)s has changed the password for your
mailing list %(listname)s. It is now

%(notifypassword)s

Please be sure to use this for all future list administration. You may want
to log in now to your list and change the password to something more to your
liking. Visit your list admin page at

%(adminurl)s

1048.

Check a list's config database file for integrity.

All of the following files are checked:

config.pck
config.pck.last
config.db
config.db.last
config.safety

It's okay if any of these are missing. config.pck and config.pck.last are
pickled versions of the config database file for 2.1a3 and beyond. config.db
and config.db.last are used in all earlier versions, and these are Python
marshals. config.safety is a pickle written by 2.1a3 and beyond when the
primary config.pck file could not be read.

Usage: %(PROGRAM)s [options] [listname [listname ...]]

Options:

--all / -a
Check the databases for all lists. Otherwise only the lists named on
the command line are checked.

--verbose / -v
Verbose output. The state of every tested file is printed.
Otherwise only corrupt files are displayed.

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

1051.

%(file)s: okay

1052.

Check the permissions for the Mailman installation.

Usage: %(PROGRAM)s [-f] [-v] [-h]

With no arguments, just check and report all the files that have bogus
permissions or group ownership. With -f (and run as root), fix all the
permission problems found. With -v be verbose.