Browsing Catalan translation

1155.

Regenerate Mailman specific aliases from scratch.

The actual output depends on the value of the `MTA' variable in your mm_cfg.py
file.

Usage: genaliases [options]
Options:

-q/--quiet
Some MTA output can include more verbose help text. Use this to tone
down the verbosity.

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

1205.

po2templ.py

Extract templates from language po file.

Usage: po2templ.py languages

1211.

Remove members from a list.

Usage:
remove_members [options] [listname] [addr1 ...]

Options:

--file=file
-f file
Remove member addresses found in the given file. If file is
`-', read stdin.

--all
-a
Remove all members of the mailing list.
(mutually exclusive with --fromall)

--fromall
Removes the given addresses from all the lists on this system
regardless of virtual domains if you have any. This option cannot be
used -a/--all. Also, you should not specify a listname when using
this option.

--nouserack
-n
Don't send the user acknowledgements. If not specified, the list
default value is used.

--noadminack
-N
Don't send the admin acknowledgements. If not specified, the list
default value is used.

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

listname is the name of the mailing list to use.

addr1 ... are additional addresses to remove.

1216.

Reset the passwords for members of a mailing list.

This script resets all the passwords of a mailing list's members. It can also
be used to reset the lists of all members of all mailing lists, but it is your
responsibility to let the users know that their passwords have been changed.

This script is intended to be run as a bin/withlist script, i.e.

% bin/withlist -l -r reset_pw listname [options]

Options:
-v / --verbose
Print what the script is doing.

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.

1283.

Ignoring bad pended data: %(key)s: %(val)s

1284.

WARNING: Ignoring duplicate pending ID: %(id)s.

1300.

General framework for interacting with a mailing list object.

There are two ways to use this script: interactively or programmatically.
Using it interactively allows you to play with, examine and modify a MailList
object from Python's interactive interpreter. When running interactively, a
MailList object called `m' will be available in the global namespace. It also
loads the class MailList into the global namespace.

Programmatically, you can write a function to operate on a MailList object,
and this script will take care of the housekeeping (see below for examples).
In that case, the general usage syntax is:

%% bin/withlist [options] listname [args ...]

Options:

-l / --lock
Lock the list when opening. Normally the list is opened unlocked
(e.g. for read-only operations). You can always lock the file after
the fact by typing `m.Lock()'

Note that if you use this option, you should explicitly call m.Save()
before exiting, since the interpreter's clean up procedure will not
automatically save changes to the MailList object (but it will unlock
the list).

-i / --interactive
Leaves you at an interactive prompt after all other processing is
complete. This is the default unless the -r option is given.

--run [module.]callable
-r [module.]callable
This can be used to run a script with the opened MailList object.
This works by attempting to import `module' (which must be in the
directory containing withlist, or already be accessible on your
sys.path), and then calling `callable' from the module. callable can
be a class or function; it is called with the MailList object as the
first argument. If additional args are given on the command line,
they are passed as subsequent positional args to the callable.

Note that `module.' is optional; if it is omitted then a module with
the name `callable' will be imported.

The global variable `r' will be set to the results of this call.

--all / -a
This option only works with the -r option. Use this if you want to
execute the script on all mailing lists. When you use -a you should
not include a listname argument on the command line. The variable `r'
will be a list of all the results.

--quiet / -q
Suppress all status messages.

--help / -h
Print this message and exit


Here's an example of how to use the -r option. Say you have a file in the
Mailman installation directory called `listaddr.py', with the following
two functions:

def listaddr(mlist):
print mlist.GetListEmail()

def requestaddr(mlist):
print mlist.GetRequestEmail()

Now, from the command line you can print the list's posting address by running
the following from the command line:

%% bin/withlist -r listaddr mylist
Loading list: mylist (unlocked)
Importing listaddr ...
Running listaddr.listaddr() ...
mylist@myhost.com

And you can print the list's request address by running:

%% bin/withlist -r listaddr.requestaddr mylist
Loading list: mylist (unlocked)
Importing listaddr ...
Running listaddr.requestaddr() ...
mylist-request@myhost.com

As another example, say you wanted to change the password for a particular
user on a particular list. You could put the following function in a file
called `changepw.py':

from Mailman.Errors import NotAMemberError

def changepw(mlist, addr, newpasswd):
try:
mlist.setMemberPassword(addr, newpasswd)
mlist.Save()
except NotAMemberError:
print 'No address matched:', addr

and run this from the command line:
%% bin/withlist -l -r changepw mylist somebody@somewhere.org foobar

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.