Browsing Portuguese translation

780.

Confirm (*) - email confirmation required <br>
Require approval - require list administrator
approval for subscriptions <br>
Confirm and approve - both confirm and approve

<p>(*) when someone requests a subscription,
Mailman sends them a notice with a unique
subscription request number that they must reply to
in order to subscribe.<br> This prevents
mischievous (or malicious) people from creating
subscriptions for others without their consent.

785.

When members want to leave a list, they will make an
unsubscription request, either via the web or via email.
Normally it is best for you to allow open unsubscriptions so that
users can easily remove themselves from mailing lists (they get
really upset if they can't get off lists!).

<p>For some lists though, you may want to impose moderator
approval before an unsubscription request is processed. Examples
of such lists include a corporate mailing list that all employees
are required to be members of.

797.

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.

800.

Each list member has a <em>moderation flag</em> which says
whether messages from the list member can be posted directly to
the list, or must first be approved by the list moderator. When
the moderation flag is turned on, list member postings must be
approved first. You, the list administrator can decide whether a
specific individual's postings will be moderated or not.

<p>When a new member is subscribed, their initial moderation flag
takes its value from this option. Turn this option off to accept
member postings by default. Turn this option on to, by default,
moderate member postings first. You can always manually set an
individual member's moderation bit by using the
<a href="%(adminurl)s/members">membership management
screens</a>.

819.

Many (in fact, most) spams do not explicitly name their
myriad destinations in the explicit destination addresses - in
fact often the To: field has a totally bogus address for
obfuscation. The constraint applies only to the stuff in the
address before the '@' sign, but still catches all such spams.

<p>The cost is that the list will not accept unhindered any
postings relayed from other addresses, unless

<ol>
<li>The relaying address has the same name, or

<li>The relaying address name is included on the options that
specifies acceptable aliases for the list.

</ol>

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.

826.

Filter rules to match against the headers of a message.

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.

828.

Legacy anti-spam filters

830.

Use this option to prohibit posts according to specific
header values. The target value is a regular-expression for
matching against the specified header. The match is done
disregarding letter case. Lines beginning with '#' are ignored
as comments.

<p>For example:<pre>to: .*@public.com </pre> says to hold all
postings with a <em>To:</em> mail header containing '@public.com'
anywhere among the addresses.

<p>Note that leading whitespace is trimmed from the regexp. This
can be circumvented in a number of ways, e.g. by escaping or
bracketing it.