Current File : //lib/mailman/Mailman/Gui/General.pyo
�
��ac @ s� d Z d d l Z d d l m Z d d l m Z d d l m Z d d l m Z d d l m Z d d l
m Z d d l m
Z
d Z d e
f d � � YZ d S( s2 MailList mixin class managing the general options.i����N( t IntType( t mm_cfg( t Utils( t Errors( t _( t Document( t GUIBaset hidet ackt notmetoot nodupest Generalc B s5 e Z d � Z d � Z d � Z d � Z d � Z RS( c C s d t d � f S( Nt generals General Options( R ( t self( ( sa /builddir/build/BUILDROOT/mailman-2.1.15-30.el7_9.2.x86_64/usr/lib/mailman/Mailman/Gui/General.pyt GetConfigCategory$ s c ' C s� | d k r d St j } i t j d 6t j d 6t j d 6t j d 6} i t d � d 6t d � d 6t d � d 6t d � d 6} g t D] } | j | | @^ q� } g t D] } | | ^ q� } t d
� t d � d t j
| d
t d � t d � f d t j d | f d
t d � t d � f d t j d | f d
t d � t d � f d t j
| d
t d � t d � f d t j d | f d
t d � t d � f d t j
| d
t d � t d � f d! t j
t d" � t d# � t d$ � f d
t d% � t d& � f d' t j
t d" � t d( � f d
t d) � f t d* � d+ t j
t d" � t d( � f d
t d, � f d- t j
t d. � t d/ � t d0 � f d
t d1 � t d2 � f d3 t j | d
t d4 � t d5 � f t d6 � d7 t j
t d" � t d( � f d
t d8 � t d9 � f d: t j
| d
t d; � t d< � f t d= � d> t j
t d" � t d( � f d
t d? � t d@ � f dA t j dB | f d
t dC � t dD � f dE t j
t d" � t d( � f d
t dF � t dG � f dH t j dB | f d
t dI � f dJ t j
t d" � t d( � f d
t dK � f dL t j
t d" � t d( � f d
t dM � t dN � f dO t j
t d" � t d( � f d
t dP � f dQ t j
t d" � t d( � f d
t dR � f t dS � dT t j t d" � t d( � f d
t dU � t dV � f dW t j | | d
t f d
t dX � t dY � f dZ t j
t d" � t d( � f d
t d[ � t d\ � f d] t j d d
t d^ � f d_ t j d d
t d` � f da t j | d
t db � t dc � f g! }
t j r�|
j dd t j
t d" � t d( � f d
t de � t df � f � n |
j dg t j
t d" � t d( � f d
t dh � t di � f � t j r�|
j dj t j
t d" � t d( � f d
t dk � t dl � f � n |
j dm t j d d
t dn � f � |
S(o NR R R R R
s Conceal the member's addresss Acknowledge the member's postings) Do not send a copy of a member's own posts; Filter out duplicate messages to list members (if possible)s] Fundamental list characteristics, including descriptive
info and basic behaviors.s General list personalityt real_namei s6 The public name of this list (make case-changes only).s� The capitalization of this name can be changed to make it
presentable in polite company as a proper noun, or to make an
acronym part all upper case, etc. However, the name will be
advertised as the email address (e.g., in subscribe confirmation
notices), so it should <em>not</em> be otherwise altered. (Email
addresses are not case sensitive, but they are sensitive to
almost everything else :-)t owneri sv The list administrator email addresses. Multiple
administrator addresses, each on separate line is okay.s� There are two ownership roles associated with each mailing
list. The <em>list administrators</em> are the people who have
ultimate control over all parameters of this mailing list. They
are able to change any list configuration variable available
through these administration web pages.
<p>The <em>list moderators</em> have more limited permissions;
they are not able to change any list configuration variable, but
they are allowed to tend to pending administration requests,
including approving or rejecting held subscription requests, and
disposing of held postings. Of course, the <em>list
administrators</em> can also tend to pending requests.
<p>In order to split the list ownership duties into
administrators and moderators, you must
<a href="passwords">set a separate moderator password</a>,
and also provide the <a href="?VARHELP=general/moderator">email
addresses of the list moderators</a>. Note that the field you
are changing here specifies the list administrators.t moderatorsn The list moderator email addresses. Multiple
moderator addresses, each on separate line is okay.s� There are two ownership roles associated with each mailing
list. The <em>list administrators</em> are the people who have
ultimate control over all parameters of this mailing list. They
are able to change any list configuration variable available
through these administration web pages.
<p>The <em>list moderators</em> have more limited permissions;
they are not able to change any list configuration variable, but
they are allowed to tend to pending administration requests,
including approving or rejecting held subscription requests, and
disposing of held postings. Of course, the <em>list
administrators</em> can also tend to pending requests.
<p>In order to split the list ownership duties into
administrators and moderators, you must
<a href="passwords">set a separate moderator password</a>,
and also provide the email addresses of the list moderators in
this section. Note that the field you are changing here
specifies the list moderators.t descriptions% A terse phrase identifying this list.s� This description is used when the mailing list is listed with
other mailing lists, or in headers, and so forth. It should
be as succinct as you can get it, while still identifying what
the list is.t infoi s� An introductory description - a few paragraphs - about the
list. It will be included, as html, at the top of the listinfo
page. Carriage returns will end a paragraph - see the details
for more info.s� The text will be treated as html <em>except</em> that
newlines will be translated to <br> - so you can use links,
preformatted text, etc, but don't put in carriage returns except
where you mean to separate paragraphs. And review your changes -
bad html (like some unterminated HTML constructs) can prevent
display of the entire listinfo page.t subject_prefixs) Prefix for subject line of list postings.s This text will be prepended to subject lines of messages
posted to the list, to distinguish mailing list messages 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 sequential number by %%d substitution
directive. eg.; [listname %%d] -> [listname 123]
(listname %%05d) -> (listname 00123)
t from_is_listt Nos
Munge Froms Wrap Messages� Replace the From: header address with the list's posting
address to mitigate issues stemming from the original From:
domain's DMARC or similar policies.s� Several protocols now in wide use attempt to ensure that use
of the domain in the author's address (ie, in the From: header
field) is authorized by that domain. These protocols may be
incompatible with common list features such as footers, causing
participating email services to bounce list traffic merely
because of the address in the From: field. <b>This has resulted
in members being unsubscribed despite being perfectly able to
receive mail.</b>
<p>
The following actions are applied to all list messages when
selected here. To apply these actions only to messages where the
domain in the From: header is determined to use such a protocol,
see the <a
href="?VARHELP=privacy/sender/dmarc_moderation_action">
dmarc_moderation_action</a> settings under Privacy options...
-> Sender filters.
<p>Settings:<p>
<dl>
<dt>No</dt>
<dd>Do nothing special. This is appropriate for anonymous lists.
It is appropriate for dedicated announcement lists, unless the
From: address of authorized posters might be in a domain with a
DMARC or similar policy. It is also appropriate if you choose to
use dmarc_moderation_action other than Accept for this list.</dd>
<dt>Munge From</dt>
<dd>This action replaces the poster's address in the From: header
with the list's posting address and adds the poster's address to
the addresses in the original Reply-To: header.</dd>
<dt>Wrap Message</dt>
<dd>Just wrap the message in an outer message with the From:
header containing the list's posting address and with the original
From: address added to the addresses in the original Reply-To:
header and with Content-Type: message/rfc822. This is effectively
a one message MIME format digest.</dd>
</dl>
<p>The transformations for anonymous_list are applied before
any of these actions. It is not useful to apply actions other
than No to an anonymous list, and if you do so, the result may
be surprising.
<p>The Reply-To: header munging actions below interact with these
actions as follows:
<p> first_strip_reply_to = Yes will remove all the incoming
Reply-To: addresses but will still add the poster's address to
Reply-To: for all three settings of reply_goes_to_list which
respectively will result in just the poster's address, the
poster's address and the list posting address or the poster's
address and the explicit reply_to_address in the outgoing
Reply-To: header. If first_strip_reply_to = No the poster's
address in the original From: header, if not already included in
the Reply-To:, will be added to any existing Reply-To:
address(es).
<p>These actions, whether selected here or via <a
href="?VARHELP=privacy/sender/dmarc_moderation_action">
dmarc_moderation_action</a>, do not apply to messages in digests
or archives or sent to usenet via the Mail<->News gateways.
<p>If <a
href="?VARHELP=privacy/sender/dmarc_moderation_action">
dmarc_moderation_action</a> applies to this message with an
action other than Accept, that action rather than this is
appliedt anonymous_listt Yessx Hide the sender of a message, replacing it with the list
address (Removes From, Sender and Reply-To fields)s! <tt>Reply-To:</tt> header mungingt first_strip_reply_tos� Should any existing <tt>Reply-To:</tt> header found in the
original message be stripped? If so, this will be done
regardless of whether an explict <tt>Reply-To:</tt> header is
added by Mailman or not.t reply_goes_to_listt Posters This lists Explicit addresss� Where are replies to list messages directed?
<tt>Poster</tt> is <em>strongly</em> recommended for most mailing
lists.s� 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.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, select <tt>Explicit address</tt> and set the
<tt>Reply-To:</tt> address below to point to the parallel
list.t reply_to_addresss# Explicit <tt>Reply-To:</tt> header.sb 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.s Umbrella list settingst
umbrella_listsZ Send password reminders to, eg, "-owner" address instead of
directly to user.sr Set this to yes when this list is intended to cascade only
to other mailing lists. When set, meta notices like
confirmations and password reminders will be directed to an
address derived from the member's address - it will have the
value of "umbrella_member_suffix" appended to the member's
account name.t umbrella_member_suffixs� Suffix for use when this list is an umbrella for other
lists, according to setting of previous "umbrella_list"
setting.s When "umbrella_list" is set to indicate that this list has
other mailing lists as members, then administrative notices like
confirmations and password reminders need to not be sent to the
member list addresses, but rather to the owner of those member
lists. In that case, the value of this setting is appended to
the member's account name for such notices. `-owner' is the
typical choice. This setting has no effect when "umbrella_list"
is "No".t
Notificationst send_reminderss Send monthly password reminders?s� Turn this on if you want password reminders to be sent once
per month to your members. Note that members may disable their
own individual password reminders.t welcome_msgi sK List-specific text prepended to new-subscriber welcome
messages4 This value, if any, will be added to the front of the
new-subscriber welcome message. The rest of the welcome message
already describes the important addresses and URLs for the
mailing list, so you don't need to include any of that kind of
stuff here. This should just contain mission-specific kinds of
things, like etiquette policies or team orientation, or that kind
of thing.
<p>Note that this text will be wrapped, according to the
following rules:
<ul><li>Each paragraph is filled so that no line is longer than
70 characters.
<li>Any line that begins with whitespace is not filled.
<li>A blank line separates paragraphs.
</ul>t send_welcome_msgs1 Send welcome message to newly subscribed members?s Turn this off only if you plan on subscribing people manually
and don't want them to know that you did so. This option is most
useful for transparently migrating lists from some other mailing
list manager to Mailman.t goodbye_msgsw Text sent to people leaving the list. If empty, no special
text will be added to the unsubscribe message.t send_goodbye_msgs; Send goodbye message to members when they are unsubscribed?t admin_immed_notifys| Should the list moderators get immediate notice of new
requests, as well as daily notices about collected ones?sZ List moderators (and list administrators) are sent daily
reminders of requests pending approval, like subscriptions to a
moderated list, or postings that are being held for one reason or
another. Setting this option causes notices to be sent
immediately on the arrival of new requests as well.t admin_notify_mchangessM Should administrator get notices of subscribes and
unsubscribes?t respond_to_post_requestss< Send mail to poster when their posting is held for approval?s Additional settingst emergencys) Emergency moderation of all list traffic.s� When this option is enabled, all list traffic is emergency
moderated, i.e. held for moderation. Turn this option on when
your list is experiencing a flamewar and you want a cooling off
period.t new_member_optionss} Default options for new members joining this list.<input
type="hidden" name="new_member_options" value="ignore">s~ When a new member is subscribed to this list, their initial
set of options is taken from this variable's setting.t
administriviasn (Administrivia filter) Check postings and intercept ones
that seem to be administrative requests?s7 Administrivia tests will check postings to see whether it's
really meant as an administrative request (like subscribe,
unsubscribe, etc), and will add it to the the administrative
requests queue, notifying the administrator of the new request,
in the process.t max_message_sizesU Maximum length in kilobytes (KB) of a message body. Use 0
for no limit.t admin_member_chunksizesR Maximum number of members to show on one page of the
Membership List.t host_names& Host name this list prefers for email.s: The "host_name" is the preferred name for email to
mailman-related addresses on this host, and generally should be
the mail host's exchanger address, if any. This setting can be
useful for selecting among alternative names of a host that has
multiple addresses.t include_rfc2369_headerss� Should messages from this mailing list include the
<a href="http://www.faqs.org/rfcs/rfc2369.html">RFC 2369</a>
(i.e. <tt>List-*</tt>) headers? <em>Yes</em> is highly
recommended.sj RFC 2369 defines a set of List-* headers that are
normally added to every message sent to the list membership.
These greatly aid end-users who are using standards compliant
mail readers. They should normally always be enabled.
<p>However, not all mail readers are standards compliant yet,
and if you have a large number of members who are using
non-compliant mail readers, they may be annoyed at these
headers. You should first try to educate your members as to
why these headers exist, and how to hide them in their mail
clients. As a last resort you can disable these headers, but
this is not recommended (and in fact, your ability to disable
these headers may eventually go away).t include_list_post_headers7 Should postings include the <tt>List-Post:</tt> header?sy The <tt>List-Post:</tt> header is one of the headers
recommended by
<a href="http://www.faqs.org/rfcs/rfc2369.html">RFC 2369</a>.
However for some <em>announce-only</em> mailing lists, only a
very select group of people are allowed to post to the list; the
general membership is usually not allowed to post. For lists of
this nature, the <tt>List-Post:</tt> header is misleading.
Select <em>No</em> to disable the inclusion of this header. (This
does not affect the inclusion of the other <tt>List-*:</tt>
headers.)t include_sender_headers� Should the <tt>Sender</tt> header be rewritten for this
mailing list to avoid stray bounces? <em>Yes</em> is
recommended.sB <a href="http://www.faqs.org/rfcs/rfc2822.html">RFC
2822</a> defines the <tt>Sender</tt> header and defines it
as "the mailbox of the agent responsible for the actual
transmission of the message." Mailman replaces this header
by default with the list's bounce address.
<p>While it is debatable if Mailman is such an agent, setting
this header helps directing bounces from some broken MTAs to
the right destination. On the other hand, some mail
readers show unexpected behaviour if this header is set (like
missing addresses in forwarded mails and copies sent to the
bounce address on reply-to-all), so it can be disabled
here.t max_days_to_holdsd Discard held messages older than this number of days.
Use 0 for no automatic discarding.( t NoneR t TEXTFIELDWIDTHt ConcealSubscriptiont AcknowledgePostst DontReceiveOwnPostst DontReceiveDuplicatesR t OPTIONSR) t Stringt EmailListt Textt Radiot Emailt Togglet Checkboxt Numbert Hostt ALLOW_RFC2369_OVERRIDESt appendt ALLOW_SENDER_OVERRIDES( R
t mlistt categoryt subcatt WIDTHt bitfieldst bitdescrst ot optvalst opttextt rtn( ( sa /builddir/build/BUILDROOT/mailman-2.1.15-30.el7_9.2.x86_64/usr/lib/mailman/Mailman/Gui/General.pyt
GetConfigInfo' sB
$ !; ! ! ! ! ! ! ! ! ! ! !
c C s� | d k r@ | j � | j � j � k r@ | j t d � � n�| d k r� | j } t | t � rm t } n t j } x? | D]7 } t j | } | | k r� | | O} q} | | M} q} W| | _ n4| d k r� t
j | | j � | _
n
| d k r:| | j k r�t
j | � r+| j t d � � q7| | _ q�n� | d k rx| d k sbt | t � rx| j t d � � n� | d
k r�y t
j d | � Wn' t j k
r�| j t d � � q�Xt j | | | | | � n t j | | | | | � d S(
NR sr <b>real_name</b> attribute not
changed! It must differ from the list's name by case
only.R) R R s The <b>info</b> attribute you saved
contains suspicious HTML that could potentially expose your users to cross-site
scripting attacks. This change has therefore been rejected. If you still want
to make these changes, you must have shell access to your Mailman server.
This change can be made with bin/withlist or with bin/config_list by setting
mlist.info.
R, i s\ <b>admin_member_chunksize</b> attribute not
changed! It must be an integer > 0.R- s user@sW <b>host_name</b> attribute not changed!
It must be a valid domain name.( t lowert
internal_namet addErrorR R) t
isinstanceR R8 R t OPTINFOR t canonstrt preferred_languageR R t suspiciousHTMLR t
ValidateEmailR t EmailAddressErrorR t _setValue( R
RE t propertyt valt doct newoptst optst optt bitfield( ( sa /builddir/build/BUILDROOT/mailman-2.1.15-30.el7_9.2.x86_64/usr/lib/mailman/Mailman/Gui/General.pyRZ sH
c C sK | j j � rG | j d k rG | j t d � � d | _ d | _ n d S( Ni sp You cannot add a Reply-To: to an explicit
address if that address is blank. Resetting these values.t i ( R t stripR RR R ( R
RE R] ( ( sa /builddir/build/BUILDROOT/mailman-2.1.15-30.el7_9.2.x86_64/usr/lib/mailman/Mailman/Gui/General.pyt
_postValidate> s
c C s& | d k r d St j | j | j � S( NR ( R2 R t
uncanonstrR RV ( R
RE t kindt varnamet params( ( sa /builddir/build/BUILDROOT/mailman-2.1.15-30.el7_9.2.x86_64/usr/lib/mailman/Mailman/Gui/General.pyt getValueG s ( t __name__t
__module__R RO RZ Rd Ri ( ( ( sa /builddir/build/BUILDROOT/mailman-2.1.15-30.el7_9.2.x86_64/usr/lib/mailman/Mailman/Gui/General.pyR # s � � 9 ( s hides acks notmetoos nodupes( t __doc__t ret typesR t MailmanR R R t Mailman.i18nR t Mailman.htmlformatR t Mailman.Gui.GUIBaseR R8 R ( ( ( sa /builddir/build/BUILDROOT/mailman-2.1.15-30.el7_9.2.x86_64/usr/lib/mailman/Mailman/Gui/General.pyt <module> s
Mini Shell