Browsing Croatian translation

627.

Each subscriber is assigned a bounce score, as a floating
point number. Whenever Mailman receives a bounce from a list
member, that member's score is incremented. Hard bounces (fatal
errors) increase the score by 1, while soft bounces (temporary
errors) increase the score by 0.5. Only one bounce per day
counts against a member's score, so even if 10 bounces are
received for a member on the same day, their score will increase
by just 1.

This variable describes the upper limit for a member's bounce
score, above which they are automatically disabled, but not
removed from the mailing list.

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.

954.

The message headers matched a filter rule

955.

Message rejected by filter rule match

961.

[Message discarded by content filter]

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 `-'.

1027.

Already a member: %(member)s

1028.

Bad/Invalid email address: blank line

1029.

Bad/Invalid email address: %(member)s