Pc
@ sv d Z d d k l Z d d k l Z d d k l Z d d k l Z d d k l Z d Z
d e f d
YZ d S( s< GUI component for managing the non-digest delivery options.
i( t mm_cfg( t Utils( t _( t GUIBase( t ALLOWEDSt user_addresst user_delivered_tot
user_passwordt user_namet user_optionsurlt NonDigestc B s& e Z d Z d d Z d Z RS( c C s d t d f S( Nt nondigests Non-digest options( R ( t self( ( s^ /builddir/build/BUILDROOT/mailman-2.1.12-18.el6.i386//usr/lib/mailman/Mailman/Gui/NonDigest.pyt GetConfigCategory" s c
C s | d j o d St i } t d d t i t d t d f d t d f g } t i oP | i d t i t d t d t d f d t d
t d f g n t i d d
| d d } t i o t d } n d } | i d t i
d | f d t d t d | | f d t i
d | f d t d t d | | f g | i d t i t d t d f d t d t d f g | i t d d t i d | f d t d t d f d! t i d | f d t d" t d# f g | S($ NR s7 Policies concerning immediately delivered list traffic.t
nondigestablet Not Yesi s` Can subscribers choose to receive mail immediately, rather
than in batched digests?t personalizes Full Personalizations" Should Mailman personalize each non-digest delivery?
This is often useful for announce-only lists, but <a
href="?VARHELP=nondigest/personalize">read the details</a>
section for a discussion of important performance
issues.s; Normally, Mailman sends the regular delivery messages to
the mail server in batches. This is much more efficent
because it reduces the amount of traffic between Mailman and
the mail server.
<p>However, some lists can benefit from a more personalized
approach. In this case, Mailman crafts a new message for
each member on the regular delivery list. Turning this
feature on may degrade the performance of your site, so you
need to carefully consider whether the trade-off is worth it,
or whether there are other ways to accomplish what you want.
You should also carefully monitor your system load to make
sure it is acceptable.
<p>Select <em>No</em> to disable personalization and send
messages to the members in batches. Select <em>Yes</em> to
personalize deliveries and allow additional substitution
variables in message headers and footers (see below). In
addition, by selecting <em>Full Personalization</em>, the
<code>To</code> header of posted messages will be modified to
include the member's address instead of the list's posting
address.
<p>When personalization is enabled, a few more expansion
variables that can be included in the <a
href="?VARHELP=nondigest/msg_header">message header</a> and
<a href="?VARHELP=nondigest/msg_footer">message footer</a>.
<p>These additional substitution variables will be available
for your headers and footers, when this feature is enabled:
<ul><li><b>user_address</b> - The address of the user,
coerced to lower case.
<li><b>user_delivered_to</b> - The case-preserved address
that the user is subscribed with.
<li><b>user_password</b> - The user's password.
<li><b>user_name</b> - The user's full name.
<li><b>user_optionsurl</b> - The url to the user's option
page.
</ul>
s
headfoot.htmlt mlistt raws When <a href="?VARHELP=nondigest/personalize">personalization</a> is enabled
for this list, additional substitution variables are allowed in your headers
and footers:
<ul><li><b>user_address</b> - The address of the user,
coerced to lower case.
<li><b>user_delivered_to</b> - The case-preserved address
that the user is subscribed with.
<li><b>user_password</b> - The user's password.
<li><b>user_name</b> - The user's full name.
<li><b>user_optionsurl</b> - The url to the user's option
page.
</ul>
t t
msg_headeri
i s1 Header added to mail sent to regular list memberssN Text prepended to the top of every immediately-delivery
message. t
msg_footers1 Footer added to mail sent to regular list memberssP Text appended to the bottom of every immediately-delivery
message. t scrub_nondigests. Scrub attachments of regular delivery message?s When you scrub attachments, they are stored in archive
area and links are made in the message so that the member can
access via web browser. If you want the attachments totally
disappear, you can use content filter options.s
Sibling listst regular_exclude_listsi s Other mailing lists on this site whose members are
excluded from the regular (non-digest) delivery if those
list addresses appear in a To: or Cc: header.s{ The list addresses should be written in full mail address
format (e.g. mailman@example.com). Do not specify this list
address mutually in the exclude list configuration page of the
other list, or members of both lists won't get any message.
Note also that the site administrator may prohibit cross domain
siblings.t regular_include_listss Other mailing lists on this site whose members are
included in the regular (non-digest) delivery if those
list addresses don't appear in a To: or Cc: header.s The list addresses should be written in full mail address
format (e.g. mailman@example.com). Note also that the site
administrator may prohibit cross domain siblings.( t NoneR t TEXTFIELDWIDTHR t Togglet! OWNERS_CAN_ENABLE_PERSONALIZATIONt extendt RadioR t maketextt Textt EmailList( R R t categoryt subcatt WIDTHt infot headfoott extra( ( s^ /builddir/build/BUILDROOT/mailman-2.1.12-18.el6.i386//usr/lib/mailman/Mailman/Gui/NonDigest.pyt
GetConfigInfo% sX
!
!(
! c C s t t } | i o | i t n | d j o1 | i | | | | | } | d j o d Sn t i | | | | | d S( NR R ( s
msg_headers
msg_footer( t listR R R t PERSONALIZED_ALLOWEDSt _convertStringR R t _setValue( R R t propertyt valt doct alloweds( ( s^ /builddir/build/BUILDROOT/mailman-2.1.12-18.el6.i386//usr/lib/mailman/Mailman/Gui/NonDigest.pyR- s
N( t __name__t
__module__R
R R) R- ( ( ( s^ /builddir/build/BUILDROOT/mailman-2.1.12-18.el6.i386//usr/lib/mailman/Mailman/Gui/NonDigest.pyR
! s N( R R R R R ( t __doc__t MailmanR R t Mailman.i18nR t Mailman.Gui.GUIBaseR t Mailman.Gui.DigestR R+ R
( ( ( s^ /builddir/build/BUILDROOT/mailman-2.1.12-18.el6.i386//usr/lib/mailman/Mailman/Gui/NonDigest.pyt <module> s
y~or5J ={Eeu磝Qk ᯘG{?+]ן?wM3X^歌>{7پK>on\jy R g/=fOroNVv~Y+ NGuÝHWyw[eQʨSb> >}Gmx[o[<{Ϯ_qF vM IENDB`
