Pc @ sZ d d k l Z d d k l Z d d k l Z d d k l Z d e f d YZ d S( i( t mm_cfg( t _( t days( t GUIBaset Bouncec B s/ e Z d Z d d Z d Z d Z RS( c C s d t d f S( Nt bounces Bounce processing( R ( t self( ( s[ /builddir/build/BUILDROOT/mailman-2.1.12-18.el6.i386//usr/lib/mailman/Mailman/Gui/Bounce.pyt GetConfigCategory s c C s~ | d j o d St d t d d t i t d t d f d t d t d f d
t i d d t d t d
f d t i d d t d f d t i d d t d f d t i d d t d f t d d t i t d t d f d t d t d f d t i t d t d f d t d t d f d t i t d t d f d t d t d f g S( NR s-
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.s Bounce detection sensitivityt bounce_processingt Not Yesi s3 Should Mailman perform automatic bounce processing?s By setting this value to <em>No</em>, you disable all
automatic bounce processing for this list, however bounce
messages will still be discarded so that the list administrator
isn't inundated with them.t bounce_score_thresholdi s The maximum member bounce score before the member's
subscription is disabled. This value can be a floating point
number.s 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.t bounce_info_stale_afters The number of days after which a member's bounce information
is discarded, if no new bounces have been received in the
interim. This value must be an integer.t bounce_you_are_disabled_warningssF How many <em>Your Membership Is Disabled</em> warnings a
disabled member should get before their address is removed from
the mailing list. Set to 0 to immediately remove an address from
the list once their bounce score exceeds the threshold. This
value must be an integer.t) bounce_you_are_disabled_warnings_intervals The number of days between sending the <em>Your Membership
Is Disabled</em> warnings. This value must be an integer.t
Notificationst& bounce_unrecognized_goes_to_list_owners Should Mailman send you, the list owner, any bounce messages
that failed to be detected by the bounce processor? <em>Yes</em>
is recommended.s While Mailman's bounce detector is fairly robust, it's
impossible to detect every bounce format in the world. You
should keep this variable set to <em>Yes</em> for two reasons: 1)
If this really is a permanent bounce from one of your members,
you should probably manually remove them from your list, and 2)
you might want to send the message on to the Mailman developers
so that this new format can be added to its known set.
<p>If you really can't be bothered, then set this variable to
<em>No</em> and all non-detected bounces will be discarded
without further processing.
<p><b>Note:</b> This setting will also affect all messages sent
to your list's -admin address. This address is deprecated and
should never be used, but some people may still send mail to this
address. If this happens, and this variable is set to
<em>No</em> those messages too will get discarded. You may want
to set up an
<a href="?VARHELP=autoreply/autoresponse_admin_text">autoresponse
message</a> for email to the -owner and -admin address.t bounce_notify_owner_on_disablesr Should Mailman notify you, the list owner, when bounces
cause a member's subscription to be disabled?s
By setting this value to <em>No</em>, you turn off
notification messages that are normally sent to the list owners
when a member's delivery is disabled due to excessive bounces.
An attempt to notify the member will always be made.t bounce_notify_owner_on_removalsg Should Mailman notify you, the list owner, when bounces
cause a member to be unsubscribed?s By setting this value to <em>No</em>, you turn off
notification messages that are normally sent to the list owners
when a member is unsubscribed due to excessive bounces. An
attempt to notify the member will always be made.( t NoneR R t Togglet Number( R t mlistt categoryt subcat( ( s[ /builddir/build/BUILDROOT/mailman-2.1.12-18.el6.i386//usr/lib/mailman/Mailman/Gui/Bounce.pyt
GetConfigInfo sT
) ! c C s. y | d j o t | } n | d j o t | } n | d j o t t | } n{ | d j o t | } n^ | d j o t t | } n; | d j o t | } n | d j o t | } n Wn3 t j
o' | i t d d t d
d SXt i | | | | | d S( NR R R R
R R R s_ Bad value for <a href="?VARHELP=bounce/%(property)s"
>%(property)s</a>: %(val)st tags Error: ( t intt floatR t
ValueErrort addErrorR R t _setValue( R R t propertyt valt doc( ( s[ /builddir/build/BUILDROOT/mailman-2.1.12-18.el6.i386//usr/lib/mailman/Mailman/Gui/Bounce.pyR s,
c C s/ | d j o d St t | | t d S( NR R i ( s bounce_info_stale_afters) bounce_you_are_disabled_warnings_interval( R R t getattrR ( R R t kindt varnamet params( ( s[ /builddir/build/BUILDROOT/mailman-2.1.12-18.el6.i386//usr/lib/mailman/Mailman/Gui/Bounce.pyt getValue s
N( t __name__t
__module__R R R R R' ( ( ( s[ /builddir/build/BUILDROOT/mailman-2.1.12-18.el6.i386//usr/lib/mailman/Mailman/Gui/Bounce.pyR s N( t MailmanR t Mailman.i18nR t Mailman.mm_cfgR t Mailman.Gui.GUIBaseR R ( ( ( s[ /builddir/build/BUILDROOT/mailman-2.1.12-18.el6.i386//usr/lib/mailman/Mailman/Gui/Bounce.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`
