Browsing German translation

Don't show this notice anymore
Before translating, be sure to go through GNU Mailman translators instructions.
110 of 88 results
565.

who
See everyone who is on this mailing 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/Commands/cmd_who.py:29
566.

who password [address=<address>]
See everyone who is on this mailing list. The roster is limited to
list members only, and you must supply your membership password to
retrieve it. If you're posting from an address other than your
membership address, specify your membership address with
`address=<address>' (no brackets around the email address, and no
quotes!)
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/Commands/cmd_who.py:34
638.
These policies control the automatic bounce processing system
in Mailman. Here's an overview of how it works.

<p>When a bounce is received, Mailman tries to extract two pieces
of information from the message: the address of the member the
message was intended for, and the severity of the problem causing
the bounce. The severity can be either <em>hard</em> or
<em>soft</em> meaning either a fatal error occurred, or a
transient error occurred. When in doubt, a hard severity is used.

<p>If no member address can be extracted from the bounce, then the
bounce is usually discarded. Otherwise, each member is assigned a
<em>bounce score</em> and every time we encounter a bounce from
this member we increment the score. Hard bounces increment by 1
while soft bounces increment by 0.5. We only increment the bounce
score once per day, so even if we receive ten hard bounces from a
member per day, their score will increase by only 1 for that day.

<p>When a member's bounce score is greater than the
<a href="?VARHELP=bounce/bounce_score_threshold">bounce score
threshold</a>, the subscription is disabled. Once disabled, the
member will not receive any postings from the list until their
membership is explicitly re-enabled (either by the list
administrator or the user). However, they will receive occasional
reminders that their membership has been disabled, and these
reminders will include information about how to re-enable their
membership.

<p>You can control both the
<a href="?VARHELP=bounce/bounce_you_are_disabled_warnings">number
of reminders</a> the member will receive and the
<a href="?VARHELP=bounce/bounce_you_are_disabled_warnings_interval"
>frequency</a> with which these reminders are sent.

<p>There is one other important configuration variable; after a
certain period of time -- during which no bounces from the member
are received -- the bounce information is
<a href="?VARHELP=bounce/bounce_info_stale_after">considered
stale</a> and discarded. Thus by adjusting this value, and the
score threshold, you can control how quickly bouncing members are
disabled. You should tune both of these to the frequency and
traffic volume of your 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)
In Ubuntu:
Diese Richtlinien steuern das automatische Bounce-Verarbeitungssystem

in Mailman. Hier ist eine Übersicht, wie es funktioniert.

<p>Wenn eine Bounce empfangen wurde, versucht Mailman zwei Teile aus
der Nachricht auszulesen: Die Adresse des Mitglieds für welches die
Nachricht bestimmt war und den Schweregrad der Ursache für die Bounce.
Der Schweregrad kann als <em>hard</em> oder
<em>soft</em> eingestuft werden, je nachdem ob ein schwerwiegender oder
ein vorrübergehender Fehler auftrat. Im Zweifel wird hard verwendet.

<p>Wenn keine Mitgliedsadresse aus der Bounce extrahiert werden kann,
wird diese Bounce normalerweise verworfen. Sonst wird jedem Mitglied eine
<em>Bounce-Punktzahl </em> zugerechnet und jedes Mal, wenn von diesem
Mitglied eine Bounce eingeht, wird die Punktzahl erhöht. Hard Bounces erhöhen um 1,
während soft Bounces um 0,5 erhöhen. Die Bounce-Punktzahl wird nur
einmal pro Tag erhöht, also wenn wir zehn hard Bounces pro Tag von einem Mitglied
empfangen, wird seine Punktzahl nur um 1 für diesen Tag erhöht.

<p>Ist die Bounce-Punktzahl eine Mitglieds größer als die
<a href="?VARHELP=bounce/bounce_score_threshold">Bounce-Grenze
</a>, wird das Abonnement gesperrt. Einmal gesperrt, erhält
das Mitglied keine weiteren Sendungen von der Liste bis seine
Mitgliedschaft explizit reaktiviert wird (entweder durch den Listen-
Administrator oder den Benutzer). Allerdings erhält er gelegentlich
Erinnerungen, dass seine Mitgliedschaft gesperrt wurde. Diese Erinnerungen
enthalten Informationen darüber, wie er seine Mitgliedschaft reaktivieren
kann.

<p>Sie können zwei Dinge festlegen, die
<a href="?VARHELP=bounce/bounce_you_are_disabled_warnings">Anzahl
der Erinnerungen</a>, welche das Mitglied erhält und den
<a href="?VARHELP=bounce/bounce_you_are_disabled_warnings_interval"
>Rhythmus</a> in welchem diese Errinnerungen veschickt werden sollen.

<p>Es gibt eine weitere wichtige Konfigurationsvariable; Nach einer
bestimmten Zeitspanne -- in der keine Bounces dieses Mitglieds eingehen
-- wird die Bounce Information als
<a href="?VARHELP=bounce/bounce_info_stale_after">veraltet
</a> betrachtet und verworfen. Deshalb können Sie durch das Anpassen dieses Wertes und der
Bounce-Grenze festlegen, wie schnell eine Mitgliedschaft deaktiviert werden soll.
Sie sollten Beide Werte auf die Erscheinungshäufigkeit und das Datenvolumen
Ihrer Liste abstimmen.
Suggested by Hendrik Knackstedt on 2012-04-27
Located in Mailman/Gui/Bounce.py:32
658.
Policies concerning the content of list traffic.

<p>Content filtering works like this: when a message is
received by the list and you have enabled content filtering, the
individual attachments are first compared to the
<a href="?VARHELP=contentfilter/filter_mime_types">filter
types</a>. If the attachment type matches an entry in the filter
types, it is discarded.

<p>Then, if there are <a
href="?VARHELP=contentfilter/pass_mime_types">pass types</a>
defined, any attachment type that does <em>not</em> match a
pass type is also discarded. If there are no pass types defined,
this check is skipped.

<p>After this initial filtering, any <tt>multipart</tt>
attachments that are empty are removed. If the outer message is
left empty after this filtering, then the whole message is
discarded.

<p> Then, each <tt>multipart/alternative</tt> section will
be replaced by just the first alternative that is non-empty after
filtering if
<a href="?VARHELP=contentfilter/collapse_alternatives"
>collapse_alternatives</a> is enabled.

<p>Finally, any <tt>text/html</tt> parts that are left in the
message may be converted to <tt>text/plain</tt> if
<a href="?VARHELP=contentfilter/convert_html_to_plaintext"
>convert_html_to_plaintext</a> is enabled and the site is
configured to allow these conversions.
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/ContentFilter.py:42
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.
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/ContentFilter.py:130
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)
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:143
726.
This is the address set in the <tt>Reply-To:</tt> header
when the <a
href="?VARHELP=general/reply_goes_to_list">reply_goes_to_list</a>
option is set to <em>Explicit address</em>.

<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.net/essays/reply-to.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, specify the explicit <tt>Reply-To:</tt> address here. You
must also specify <tt>Explicit address</tt> in the
<tt>reply_goes_to_list</tt>
variable.

<p>Note that if the original message contains a
<tt>Reply-To:</tt> header, it will not be changed.
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:228
818.
When a message is posted to the list, a series of
moderation steps are take to decide whether the a moderator must
first approve the message or not. This section contains the
controls for moderation of both member and non-member postings.

<p>Member postings are held for moderation if their
<b>moderation flag</b> is turned on. You can control whether
member postings are moderated by default or not.

<p>Non-member postings can be automatically
<a href="?VARHELP=privacy/sender/accept_these_nonmembers"
>accepted</a>,
<a href="?VARHELP=privacy/sender/hold_these_nonmembers">held for
moderation</a>,
<a href="?VARHELP=privacy/sender/reject_these_nonmembers"
>rejected</a> (bounced), or
<a href="?VARHELP=privacy/sender/discard_these_nonmembers"
>discarded</a>,
either individually or as a group. Any
posting from a non-member who is not explicitly accepted,
rejected, or discarded, will have their posting filtered by the
<a href="?VARHELP=privacy/sender/generic_nonmember_action">general
non-member rules</a>.

<p>In the text boxes below, add one address per line; start the
line with a ^ character to designate a <a href=
"http://www.python.org/doc/current/lib/module-re.html"
>Python regular expression</a>. When entering backslashes, do so
as if you were using Python raw strings (i.e. you generally just
use a single backslash).

<p>Note that non-regexp matches are always done first.
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:162
827.
Postings from any of these non-members will be automatically
accepted with no further moderation applied. Add member
addresses one per line; start the line with a ^ character to
designate a regular expression match.
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:244
849.
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.

Note that headers are collected from all the attachments
(except for the mailman administrivia message) and
matched against the regular expressions. With this feature,
you can effectively sort out messages with dangerous file
types or file name extensions.
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:391
110 of 88 results

This translation is managed by translation group mailman-translators.

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

Contributors to this translation: Daniel Winzen, Dennis Baudys, Hendrik Knackstedt, Kristjan SCHMIDT, Laura Ohrndorf, Marco Dieckhoff, Peer Heinlein, Sascha Bluhme, Sascha Herres, Tobias Bannert, dt, pehkaher, pheinlein.