Browsing Estonian translation

Don't show this notice anymore
Before translating, be sure to go through Ubuntu Translators instructions and Estonian guidelines.

These translations are shared with GNU Mailman 2.1 series template mailman.

17 of 7 results
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.
There are line breaks here. Each one represents a line break. Start a new line in the equivalent position in the translation.
There are leading/trailing spaces here. Each one represents a space character. Enter a space in the equivalent position in the translation.
(no translation yet)
Located in Mailman/Gui/General.py:169
821.
Alternate addresses that are acceptable when
`require_explicit_destination' is enabled. This option takes a
list of regular expressions, one per line, which is matched
against every recipient address in the message. The matching is
performed with Python's re.match() function, meaning they are
anchored to the start of the string.

<p>For backwards compatibility with Mailman 1.1, if the regexp
does not contain an `@', then the pattern is matched against just
the local part of the recipient address. If that match fails, or
if the pattern does contain an `@', then the pattern is matched
against the entire recipient address.

<p>Matching against the local part is deprecated; in a future
release, the pattern will always be matched against the entire
recipient address.
There are line breaks here. Each one represents a line break. Start a new line in the equivalent position in the translation.
There are leading/trailing spaces here. Each one represents a space character. Enter a space in the equivalent position in the translation.
(no translation yet)
Located in Mailman/Gui/Privacy.py:518
857.
This setting determines the moderation policy of the
newsgroup and its interaction with the moderation policy of the
mailing list. This only applies to the newsgroup that you are
gatewaying <em>to</em>, so if you are only gatewaying from
Usenet, or the newsgroup you are gatewaying to is not moderated,
set this option to <em>None</em>.

<p>If the newsgroup is moderated, you can set this mailing list
up to be the moderation address for the newsgroup. By selecting
<em>Moderated</em>, an additional posting hold will be placed in
the approval process. All messages posted to the mailing list
will have to be approved before being sent on to the newsgroup,
or to the mailing list membership.

<p><em>Note that if the message has an <tt>Approved</tt> header
with the list's administrative password in it, this hold test
will be bypassed, allowing privileged posters to send messages
directly to the list and the newsgroup.</em>

<p>Finally, if the newsgroup is moderated, but you want to have
an open posting policy anyway, you should select <em>Open list,
moderated group</em>. The effect of this is to use the normal
Mailman moderation facilities, but to add an <tt>Approved</tt>
header to all messages that are gatewayed to Usenet.
There are line breaks here. Each one represents a line break. Start a new line in the equivalent position in the translation.
There are leading/trailing spaces here. Each one represents a space character. Enter a space in the equivalent position in the translation.
(no translation yet)
Located in Mailman/Gui/Usenet.py:68
1078.
Clean up an .mbox archive file.

The archiver looks for Unix-From lines separating messages in an mbox archive
file. For compatibility, it specifically looks for lines that start with
"From " -- i.e. the letters capital-F, lowercase-r, o, m, space, ignoring
everything else on the line.

Normally, any lines that start "From " in the body of a message should be
escaped such that a > character is actually the first on a line. It is
possible though that body lines are not actually escaped. This script
attempts to fix these by doing a stricter test of the Unix-From lines. Any
lines that start "From " but do not pass this stricter test are escaped with a
> character.

Usage: cleanarch [options] < inputfile > outputfile
Options:
-s n
--status=n
Print a # character every n lines processed

-q / --quiet
Don't print changed line information to standard error.

-n / --dry-run
Don't actually output anything.

-h / --help
Print this message and exit
There are line breaks here. Each one represents a line break. Start a new line in the equivalent position in the translation.
There are leading/trailing spaces here. Each one represents a space character. Enter a space in the equivalent position in the translation.
(no translation yet)
Located in bin/cleanarch:20
1093.
Configure a list from a text file description.

Usage: config_list [options] listname

Options:
--inputfile filename
-i filename
Configure the list by assigning each module-global variable in the
file to an attribute on the list object, then saving the list. The
named file is loaded with execfile() and must be legal Python code.
Any variable that isn't already an attribute of the list object is
ignored (a warning message is printed). See also the -c option.

A special variable named `mlist' is put into the globals during the
execfile, which is bound to the actual MailList object. This lets you
do all manner of bizarre thing to the list object, but BEWARE! Using
this can severely (and possibly irreparably) damage your mailing list!

--outputfile filename
-o filename
Instead of configuring the list, print out a list's configuration
variables in a format suitable for input using this script. In this
way, you can easily capture the configuration settings for a
particular list and imprint those settings on another list. filename
is the file to output the settings to. If filename is `-', standard
out is used.

--checkonly
-c
With this option, the modified list is not actually changed. Only
useful with -i.

--verbose
-v
Print the name of each attribute as it is being changed. Only useful
with -i.

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

The options -o and -i are mutually exclusive.

There are line breaks here. Each one represents a line break. Start a new line in the equivalent position in the translation.
There are leading/trailing spaces here. Each one represents a space character. Enter a space in the equivalent position in the translation.
(no translation yet)
Located in bin/config_list:20
1141.
Primary start-up and shutdown script for Mailman's qrunner daemon.

This script starts, stops, and restarts the main Mailman queue runners, making
sure that the various long-running qrunners are still alive and kicking. It
does this by forking and exec'ing the qrunners and waiting on their pids.
When it detects a subprocess has exited, it may restart it.

The qrunners respond to SIGINT, SIGTERM, and SIGHUP. SIGINT and SIGTERM both
cause the qrunners to exit cleanly, but the master will only restart qrunners
that have exited due to a SIGINT. SIGHUP causes the master and the qrunners
to close their log files, and reopen then upon the next printed message.

The master also responds to SIGINT, SIGTERM, and SIGHUP, which it simply
passes on to the qrunners (note that the master will close and reopen its own
log files on receipt of a SIGHUP). The master also leaves its own process id
in the file data/master-qrunner.pid but you normally don't need to use this
pid directly. The `start', `stop', `restart', and `reopen' commands handle
everything for you.

Usage: %(PROGRAM)s [options] [ start | stop | restart | reopen ]

Options:

-n/--no-restart
Don't restart the qrunners when they exit because of an error or a
SIGINT. They are never restarted if they exit in response to a
SIGTERM. Use this only for debugging. Only useful if the `start'
command is given.

-u/--run-as-user
Normally, this script will refuse to run if the user id and group id
are not set to the `mailman' user and group (as defined when you
configured Mailman). If run as root, this script will change to this
user and group before the check is made.

This can be inconvenient for testing and debugging purposes, so the -u
flag means that the step that sets and checks the uid/gid is skipped,
and the program is run as the current user and group. This flag is
not recommended for normal production environments.

Note though, that if you run with -u and are not in the mailman group,
you may have permission problems, such as begin unable to delete a
list's archives through the web. Tough luck!

-s/--stale-lock-cleanup
If mailmanctl finds an existing master lock, it will normally exit
with an error message. With this option, mailmanctl will perform an
extra level of checking. If a process matching the host/pid described
in the lock file is running, mailmanctl will still exit, but if no
matching process is found, mailmanctl will remove the apparently stale
lock and make another attempt to claim the master lock.

-q/--quiet
Don't print status messages. Error messages are still printed to
standard error.

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

Commands:

start - Start the master daemon and all qrunners. Prints a message and
exits if the master daemon is already running.

stop - Stops the master daemon and all qrunners. After stopping, no
more messages will be processed.

restart - Restarts the qrunners, but not the master process. Use this
whenever you upgrade or update Mailman so that the qrunners will
use the newly installed code.

reopen - This will close all log files, causing them to be re-opened the
next time a message is written to them
There are line breaks here. Each one represents a line break. Start a new line in the equivalent position in the translation.
There are leading/trailing spaces here. Each one represents a space character. Enter a space in the equivalent position in the translation.
(no translation yet)
Located in bin/mailmanctl:20
1266.
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 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
There are line breaks here. Each one represents a line break. Start a new line in the equivalent position in the translation.
There are leading/trailing spaces here. Each one represents a space character. Enter a space in the equivalent position in the translation.
(no translation yet)
Located in bin/withlist:19
17 of 7 results

This translation is managed by Ubuntu Estonian Translators, assigned by Ubuntu Translators.

You are not logged in. Please log in to work on translations.

Contributors to this translation: Anti Veeranna.