' O . O LQ Z Q w MR + R ; R V -S ' S U T V N ` Vb d e d
af lf xf 9 f R g i %i i U i Mj j k _ m n o ~p ! !q ! Cq eq wq & q % q ! q q & r =r Mr \r mr r r r r r r Z s Z os s s s s t ` t t & t t R t 5 $u Zu : -v hv mv tv v v w v !w >w < Bw w Yx - rx x x # x 8 x 5 +y 3 ay * y y ( y ! z & &z , Mz . zz ' z 3 z { !{ ( 4{ , ]{ { C { { & | = '| / e| ! | ' | $ | , } 4 1} P f} % } 7 } , ~ = B~ ! ~ * ~ & ~ % ~ & J A + Ԁ I K 1 n }
- Ȃ
@ 9 B | ׃ 7 ( / X m + a % [ " ) ΅ / J b _ T 1 I W < W ! f y r 8 S $ , ό 6 % ύ ( ώ ) % " H c 0 z * ֏ \ J L T # f V & } u h 4 h ! ۙ ݙ 5 ߙ - 4 E % z b К * 3 O ^ F 6 . 4 c s ' ֜
+ ) :
d % r 7 P П . ! P f l Ӡ ! 7 0 : ߨ
& * 1 H ^ $ x B A , 1 . ^ 3 ݬ ߬ # > ? T * ) 3 I b z ) 4 ® , K i _ % 3 % Y ' U ( / ϱ r T 9 + e W
_ m C ~ ` · # ? F Y u ' / ˸ ? 4 ; p 9 ҹ Y Z i # ) i & 6 G
7 * B m - 0 R S [ u % ? \ M u !
& C b T s % . " $ 8 T ] c i p } / 5 < M + f 5
" 2 A J * R d } 0 ) o p } i o ~ ) / 3 ) R $ | ;
C Q ! k # 0 # 8 2 H , { #
; 7 R
[ q y ' c 1 [ # s ]
h x 6 O ' # 5 $ E j 1 _ 4
x C
)
9
% & + $ R 0 w % F 2 1 H 0 z x 6 . m e . * , ! % " F i ? ' > ^ . # E Q i ! (
! 6 ! K! q d! ! ! ! ! ! ! ! " " " ! "" ( D" m" # # # 3#
Q# _# {# # ! g% % % ) % % Z % A' ]' s' 0 ' ' U ' Z ,( Y ( X ( a :) ) 3 ) ) q, , K , , ' ,
- *- D- K- S- Z-
_- m- / - 3 - - . 2 -. `. $ h. % . . |0 ` 0 y 0 m1 F4 J4
P4 ^4 q4 4 U 4 4 4 " 5 &5 65 J5 a5 v5 5 5 D 5 5 6 ! <6 % ^6 6 6 ! 6 6 6 6 6 6 # 7 $7
7 7 0 7 7 - 7 8 2 88 ; k8 8 8 8 8 8 9 !9 <9 p N9 9 9 9 9
: : 0 =: n: : :
: ! : 4 : & ; /; < J; ; ; ; # ; ; < 8< P< : c< % < < b < 6 ,@ cI % mI I 8 I I I 9 J J = J
K #K 'K 0K L "L *L _ .L L A L L K L ;R VR vR R R * R R S S 4S FS XS wS
S S S ( S S S T T V 5 %V [V aV <W X / .X 7 ^X X X
HY SY ) gY Y Y Y Y , Y Z 8 /Z 7 hZ 9 \ ^ f` ` ; ` ) ` ` ' a , ,a
Ya n n o 'o Go fo w vo % t u #u j -u ! x x x z 8 z { { !{ # 5 5 L \ ߄ J + P v dž - +
< # < $ W | . " Î ( ; 5 < q : Ϗ %
0 Z 0 U 1 ) ! # 7 ; E M _ c " u g ) _ g r } 3 " $ W G J O : ) J
M X u
K K 7 E | } / [ * & & ݥ &
z ̦ ܦ " ȧ ѧ ا ' ) > h ը , B ] s " * & " P < = [ ˳ N ' w v
: \ y O ɽ 3 6 7 I 6 ̿ * L J # a 9 ; v N n ! ; 0 ] 1 O r Y v 4
5 ? 6 u 7 ' 7 0 D u P r } 6 Y 7 " [ % C V m _ 6 # V s -
| q x n Y p s \ + f 7 ( -
; . 1 P
g z T t 4 E I R & " " 3 V b < w k , 3 7 ? @ ! ! " 9! \! w! & ! ! - " " " " " # ! 7# Y# ! p# 6 # + # # . $ # ?$ $ c$ 9 $ $ $ u' ~) 0 C+ t+ + + + 0 + + , , -, I, / d, 6 , ( , 0 , %- , /- \- . . . 5 3. i. - r. . 0 2 v 9 ~ 9 G y: b < 0 $? g U? ? # @ @ A C 1 _D D pI I I I I . I I J ( J 5 IJ 5 J 4 J 2 J 2 K ] PK ; K * K p P P }Q % 7R ! ]R $ R R G R - S = 6T tT 1 U , FU . sU U 6V V G W ' W X (Y Y ' Z @Z 3 Z 3 $[ X[ & q[ ~ [ p \ . \ ! ] ] ^ K ` b e & ng C j D j k
<k Jk ^k % n 6 @n 7 wn n H n # o # 6o Zo yo o C o P o P <p c p V p Hr V s ns Ht % t ! t !u 8u Ju eu |u u u # u u / u %
v 0v Jv dv kv xv v v g v 6
w 8 Dw }w w w w " w ! x >x \x , }x x x x x x x x x
y
y ' y 4 Gy |y y y y y y / y { z z z z z z z { { { #{ 0{ :{ [{ p{ { { { # { { { | " |
,| 7| ?| F|
Y| g| q| z| ~| | . | | | | | | | } } 4 !} , V} } } $ } } . } } ~ + ~ A~ ) Q~ {~ 8 ~ 8 ~ ~ ) H O ^ * d " Y & G W ރ 6 + ˄ : g 2 r B i
Ɩ ֖ , ֗ I n v ^ , 0 E & _ ' Π ( # 4 H Y j ơ R O 3 ʢ _ ٢ 9 H f N v $ ţ 3 դ ٤ n 8 ۥ 1 & צ ) 9 ; ; u 9 & + - # Y & } ; 5 ( 7 ? w & % ک Q q 3 ; 1 ! / " Q t " 5 I 4 @ Q - 7 0 J % d J խ * - = c k ϯ ] l u ~ $ Ӱ ! ߰ < " > a & y & . DZ + " 3 F V $ v R ' " / R s ( ? a E V & ô E D 4 E V 6 ! = / ] v
7 ' J r * ( J ( s ! 9 ѻ ' 3 P F J l پ Z F Z J S C M ! , " 6 > 0 u ] ( ( 4 Q E 5 * 4 D T j w m Q ' E - ! s J , * 3 U ^ t ~ " , @ . X + 4 % $ / . T < / / 3 L d ! * 2 Q p ' ! p , - ' % , 6 c m q g c v E < B 9 % @ G Z y ( / @ . 9 h ! $ " ) [ B , O | " " " < < ; x
i w 3
! 8 K d z ! # ! & - @ P Z a k { ' . 5 E " X { ! . > K 4 I ~ ! l ! U b M a % n * $
/ H w O "
$ 0 # U y
; 6
. < D T $ a 8 $ q x p $ 6 z I _
l ,) E) M [) + + + + + , ", 6, H, 6 g, e , - u - 1 - - 3 - - * - ) ). ( S. |. . 3 / ( / ' / 0 #0 = 0 \ 0 < I2 2 6 0 +6 + \6 $ 6 $ 6 ! 6 6
7 )7 F7 _7 t7 \9 " }: : :; Z; n; + ; = = e = @> Y> r> $ > > ( > ! > M ? N? [? b? i? p? w? ~? ? ? ? ? $ ? [ ? =@ \@ c@ ( p@ @ @ @ @ B $ B ! B B B D D -D . GD vD ' D 9 D 9 D 9 /E B iE E 4 E K E CH YH 9 rH H - H H H I I I $I )I 6I ' SI & {I I I , I J & J 3J RJ 7L J KL V L w L eO lO sO O O O H O O O P P -P @P SP `P
pP
~P = P P ! P Q - 'Q UQ _Q iQ Q Q Q Q Q $ Q w Q
fR tR ~R R . R R / R 9 S 9 US S S S S S S Y
T dT zT T T T ! T T U +U >U ]U # gU @ U / U U G V dV $ V V V V $ V W ,W - ?W mW W W W Y a a a E a b b M b b 2 b *c 1c ;c Ec d %d ,d A 0d rd ? vd d } d Ni fi i i i % i i
j j $j 4j Dj Wj aj kj rj j j j j j l - l l l m pn - n n n n o o = o o p p *p * :p $ ep 9 p p r wt u u J u u v v :v Yv ! 7 G Z w
( ʈ $ ! ܋ ! э e Y i $ q Ւ B ז d ] h Ɨ % 2 Ι ' ) h 6 ; 2 ( n N ʞ # = D N $ [ 6 ͟ 0 < 5 ! r 1 Ơ d ף $ < * a ( ! פ
! 7 : > " y , f ɨ ) 0 u Z ; Щ N C [ & ƪ G ӫ ; W + ( H . < w K z Ư 9 [ 9 7 ϱ u } 0 ʲ ( ij $ ( C j V ! $ 0 ( U ~ 0 8 ? U b u ' ʶ ! : P
] k
w N ' * v 6 2 G ! 3 i w z g ~ s Q 0 3 5 ' Y ] M l y } u M z = 0 & q W p q ' X B _ 5 ; A * } 0 + = N h Y 5 ` S 8 B z R y i n + . g 1 8 [ A U U I o ' y 6 ' 0 8 v i
E a q T V ` / % * B @ k
# ( 3 \ * F q ~ ; 0 L } * & 9
D E N " \ I$ 6 % % % & ,& % 0& V& u& & & & * & . & ! -' * O' z' ( ' ' W( a( h( 5 ( ( ( ( * , T 2 ] 2 ! K3 E m5 0 7 Z 7 ?8 9 <9 : ; - T< < ' $A LA SA
WA
eA + sA A A $ A ' A , B * FB ' qB ' B c B 6 %C z \C X F 0G H H H ! H H 8 I ?I / 4J dJ + J % K + AK c mK K nL : M $ BM gM N ' N 0 N O ( O 6 O P 3 &P o ZP B P
Q * Q R y R yT B uV j X v #Z 8 \ 8 \ ] &] 3] G] $ _ D ` - _` ` = ` % ` &
a 1a Oa ha < |a T a Q b E `b : b c E d d p je & e f f 2f Gf Vf mf tf f % f f 5 f f g 6g Mg Tg ag vg ~g ^ g % g h 1h Hh gh h h h h & h ) %i Oi Vi Zi ^i wi i i i i i * i / i j !j (j 5j Kj [j ' oj j k ,k ?k Yk lk k k k k k k k k k ' l 7l Tl [l |l l l * l l l l l l m m m !m (m 6 /m fm mm wm m m m m
m / m % n .n 5n $ <n an , }n n n , n n
o $o ' +o ; So o o o o o o ! o p ( *p
NOTE NOTE NOTE NOTE NOTE
You are upgrading an existing Mailman installation, but I can't tell what
version you were previously running.
If you are upgrading from Mailman 1.0b9 or earlier you will need to
manually update your mailing lists. For each mailing list you need to
copy the file templates/options.html lists/<listname>/options.html.
However, if you have edited this file via the Web interface, you will have
to merge your changes into this file, otherwise you will lose your
changes.
NOTE NOTE NOTE NOTE NOTE
confirm <confirmation-string>
Confirm an action. The confirmation-string is required and should be
supplied by a mailback confirmation notice.
echo [args]
Simply echo an acknowledgement. Args are echoed back unchanged.
end
Stop processing commands. Use this if your mail program automatically
adds a signature file.
help
Print this help message.
info
Get information about this mailing list.
lists
See a list of the public mailing lists on this GNU Mailman server.
password [<oldpassword> <newpassword>] [address=<address>]
Retrieve or change your password. With no arguments, this returns
your current password. With arguments <oldpassword> and <newpassword>
you can change your password.
If you're posting from an address other than your membership address,
specify your membership address with `address=<address>' (no brackets
around the email address, and no quotes!). Note that in this case the
response is always sent to the subscribed address.
set ...
Set or view your membership options.
Use `set help' (without the quotes) to get a more detailed list of the
options you can change.
Use `set show' (without the quotes) to view your current option
settings.
set help
Show this detailed help.
set show [address=<address>]
View your current option settings. If you're posting from an address
other than your membership address, specify your membership address
with `address=<address>' (no brackets around the email address, and no
quotes!).
set authenticate <password> [address=<address>]
To set any of your options, you must include this command first, along
with your membership password. If you're posting from an address
other than your membership address, specify your membership address
with `address=<address>' (no brackets around the email address, and no
quotes!).
set ack on
set ack off
When the `ack' option is turned on, you will receive an
acknowledgement message whenever you post a message to the list.
set digest plain
set digest mime
set digest off
When the `digest' option is turned off, you will receive postings
immediately when they are posted. Use `set digest plain' if instead
you want to receive postings bundled into a plain text digest
(i.e. RFC 1153 digest). Use `set digest mime' if instead you want to
receive postings bundled together into a MIME digest.
set delivery on
set delivery off
Turn delivery on or off. This does not unsubscribe you, but instead
tells Mailman not to deliver messages to you for now. This is useful
if you're going on vacation. Be sure to use `set delivery on' when
you return from vacation!
set myposts on
set myposts off
Use `set myposts off' to not receive copies of messages you post to
the list. This has no effect if you're receiving digests.
set hide on
set hide off
Use `set hide on' to conceal your email address when people request
the membership list.
set duplicates on
set duplicates off
Use `set duplicates off' if you want Mailman to not send you messages
if your address is explicitly mentioned in the To: or Cc: fields of
the message. This can reduce the number of duplicate postings you
will receive.
set reminders on
set reminders off
Use `set reminders off' if you want to disable the monthly password
reminder for this mailing list.
subscribe [password] [digest|nodigest] [address=<address>]
Subscribe to this mailing list. Your password must be given to
unsubscribe or change your options, but if you omit the password, one
will be generated for you. You may be periodically reminded of your
password.
The next argument may be either: `nodigest' or `digest' (no quotes!).
If you wish to subscribe an address other than the address you sent
this request from, you may specify `address=<address>' (no brackets
around the email address, and no quotes!)
unsubscribe [password] [address=<address>]
Unsubscribe from the mailing list. If given, your password must match
your current password. If omitted, a confirmation email will be sent
to the unsubscribing address. If you wish to unsubscribe an address
other than the address you sent this request from, you may specify
`address=<address>' (no brackets around the email address, and no
quotes!)
who password
See everyone who is on this mailing list. The roster is limited to
list administrators and moderators only; you must supply the list
admin or moderator password to retrieve the roster.
%(listname)s has both public and private mbox archives. Since this list
currently uses private archiving, I'm installing the private mbox archive
-- %(o_pri_mbox_file)s -- as the active archive, and renaming
%(o_pub_mbox_file)s
to
%(o_pub_mbox_file)s.preb6
You can integrate that into the archives if you want by using the 'arch'
script.
- Done.
- Ignored:
- Unprocessed:
Check a given Mailman translation, making sure that variables and
tags referenced in translation are the same variables and tags in
the original templates and catalog.
Usage:
cd $MAILMAN_DIR
%(program)s [-q] <lang>
Where <lang> is your country code (e.g. 'it' for Italy) and -q is
to ask for a brief summary.
ERROR:
The locks for some lists could not be acquired. This means that either
Mailman was still active when you upgraded, or there were stale locks in the
%(lockdir)s directory.
You must put Mailman into a quiescent state and remove all stale locks, then
re-run "make update" manually. See the INSTALL and UPGRADE files for details.
Pending posts:
To finish removing your mailing list, you must edit your /etc/aliases (or
equivalent) file by removing the following lines, and possibly running the
`newaliases' program:
## %(listname)s mailing list
Usage:
You are subscribed to this list with the case-preserved address
<em>%(cpuser)s</em>. You have successfully canceled the posting of your message with
the Subject: header <em>%(subject)s</em> to the mailing list
%(listname)s. You have successfully changed your address on the %(listname)s
mailing list from <b>%(oldaddr)s</b> to <b>%(newaddr)s</b>. You
can now <a href="%(optionsurl)s">proceed to your membership
login page</a>. You have successfully confirmed your subscription request for
"%(addr)s" to the %(listname)s mailing list. A separate
confirmation message will be sent to your email address, along
with your password, and other useful information and links.
<p>You can now
<a href="%(optionsurl)s">proceed to your membership login
page</a>. You have successfully confirmed your subscription request to the
mailing list %(listname)s, however final approval is required from
the list moderator before you will be subscribed. Your request
has been forwarded to the list moderator, and you will be notified
of the moderator's decision. You have successfully re-enabled your membership in the
%(listname)s mailing list. You can now <a
href="%(optionsurl)s">visit your member options page</a>.
You have successfully unsubscribed from the %(listname)s mailing
list. You can now <a href="%(listinfourl)s">visit the list's main
information page</a>. You were not invited to this mailing list. The invitation has
been discarded, and both list administrators have been
alerted. Description: %(description)s Requests to: %(requestaddr)s ack %(onoff)s address not found: checking gid and mode for %(path)s checking permissions on: %(path)s checking set-gid for %(path)s clone address added: clone address is already a member: digest mime digest off digest plain duplicates %(onoff)s hide %(onoff)s myposts %(onoff)s new list owners: original address removed: reminders %(onoff)s scanning list owners: unknown file in the way, moving
%(o_pri_mbox_file)s
to
%(newname)s unknown file in the way, moving
%(o_pub_mbox_file)s
to
%(newname)s %(file)s: okay Thread %(size)i bytes (%(count)d of %(total)d) (Digest mode) (but we obscure the addresses so they are not
easily recognizable by spammers). (requires authorization) (requires confirmation)<br> <br> <p>Enter your If you leave the field blank, you will be prompted for
your email address The last bounce received from you was dated %(date)s To visit the general information page for an unadvertised list,
open a URL similar to this one, but with a '/' and the %(adj)s
list name appended.
<p>List administrators, you can visit and password to visit the subscribers list: <p><center> at bytes from %(remote)s is already a member subscribers: to find the management interface for your list.
<p>If you are having trouble using the lists, please contact ## %(listname)s mailing list %%% %(address)s is not a member of the %(listname)s mailing list %(address)s was invited to a different mailing
list, but in a deliberate malicious attempt they tried to confirm the
invitation to your list. We just thought you'd like to know. No further
action by you is required. %(allcnt)s members total %(allcnt)s members total, %(membercnt)s shown %(day)i %(month)s %(year)i %(days)d %(units)s %(dbdir)s "other" perms must be 000 %(dbfile)s owned by %(owner)s (must be owned by %(user)s %(dbfile)s permissions must be 0664 (got %(octmode)s) %(file)s permissions must be 0664 (got %(octmode)s) %(host)s mailing list memberships reminder %(hostname)s Mailing Lists %(hostname)s mailing lists - Admin Links %(i)3d. List name: %(realname)s %(listfullname)s mailing list reminder %(listinfo_link)s list run by %(owner_link)s %(listname)s %(msg)s not found as %(filename)s %(listname)s mailing list probe message %(listname)s post from %(sender)s requires approval %(messages)d messages found %(month)s %(year)i %(name)s runs the %(runnername)s qrunner %(newaddr)s is already a member of the list. %(ord)s quarter %(year)i %(path)s bad group (has: %(groupname)s, expected %(MAILMAN_GROUP)s) %(path)s must be set-gid %(private)s must not be other-readable %(pwfile)s permissions must be exactly 0640 (got %(octmode)s) %(realname)s -- Edit html for %(template_info)s %(realname)s -- HTML Page Editing %(realname)s Administration (%(label)s) %(realname)s Administrative Database %(realname)s Administrative Database Results %(realname)s Digest, Vol %(volume)d, Issue %(issue)d %(realname)s Mailing list Configuration Help
<br><em>%(varname)s</em> Option %(realname)s administrative interface %(realname)s list: member options for user %(safeuser)s %(realname)s list: member options login page %(realname)s mailing list administration<br>%(label)s Section %(realname)s post acknowledgement %(realname)s roster authentication failed. %(realname)s subscription notification %(realname)s unsubscribe notification %(safetemplatename)s: Invalid template %(wday)s %(mon)s %(day)2i %(hh)02i:%(mm)02i:%(ss)02i %(tzname)s %(year)04i %(wrapper)s must be set-gid %s has both public and private mbox archives. Since this list
currently uses public archiving, I'm installing the public mbox file
archive file (%s) as the active one, and renaming
%s
to
%s.preb6
You can integrate that into the archives if you want by using the 'arch'
script.
<blank line> (<i>%(which)s is only available to the list
members.</i>) (<i>%(which)s is only available to the list
administrator.</i>) (Administrivia filter) Check postings and intercept ones
that seem to be administrative requests? (Note - you are subscribing to a list of mailing lists, so the %(type)s notice will be sent to the admin address for your membership, %(addr)s.)<p> (as owner) (fixing) (help) (locked) (no change) (no subject) (unlocked) - %(o_tmpl)s doesn't exist, leaving untouched - Results: - This list looks like it might have <= b4 list templates around - both %(o_tmpl)s and %(n_tmpl)s exist, leaving untouched - moved %(o_tmpl)s to %(n_tmpl)s - nothing to update here - updating old private mbox file - updating old public mbox file - usenet watermarks updated and gate_watermarks removed -------------- next part --------------
--all requires --run ...after this one. ...before this one. ...or specify a file to upload: ; it was disabled by the list administrator ; it was disabled by you ; it was disabled due to excessive bounces. The
last bounce was received on %(date)s ; it was disabled for unknown reasons <----- start object %(cnt)s -----> <P>Currently, there are no archives. </P> <b><i>either</i></b> <b>Cancel</b> and return to list administration <b>ack</b> -- Does the member get acknowledgements of their
posts? <b>digest</b> -- Does the member get messages in digests?
(otherwise, individual messages) <b>hide</b> -- Is the member's address concealed on
the list of subscribers? <b>language</b> -- Language preferred by the user <b>mod</b> -- The user's personal moderation flag. If this is
set, postings from them will be moderated, otherwise they will be
approved. <b>nodupes</b> -- Does the member want to avoid duplicates of the
same message? <b>nomail</b> -- Is delivery to the member disabled? If so, an
abbreviation will be given describing the reason for the disabled
delivery:
<ul><li><b>U</b> -- Delivery was disabled by the user via their
personal options page.
<li><b>A</b> -- Delivery was disabled by the list
administrators.
<li><b>B</b> -- Delivery was disabled by the system due to
excessive bouncing from the member's address.
<li><b>?</b> -- The reason for disabled delivery isn't known.
This is the case for all memberships which were disabled
in older versions of Mailman.
</ul> <b>not metoo</b> -- Does the member want to avoid copies of their
own postings? <b>plain</b> -- If getting digests, does the member get plain
text digests? (otherwise, MIME) <b>real_name</b> attribute not
changed! It must differ from the list's name by case
only. <b>unsub</b> -- Click on this to unsubscribe the member. <br>(Details for <b>%(varname)s</b>) <br>(Edit <b>%(varname)s</b>) <br><em>...specify a file to upload</em><br> <br><em><strong>Note:</strong>
setting this value performs an immediate action but does not modify
permanent state.</em> <br>Return to the <em>(%(num_concealed)d private members not shown)</em> <em>(1 private member not shown)</em> <em><strong>Warning:</strong> changing this option here
could cause other screens to be out-of-sync. Be sure to reload any other
pages that are displaying this option for this mailing list. You can also
<em>Enter the text below, or...</em><br> <em>Message with id #%(id)d is corrupted. <em>Message with id #%(id)d was lost. <em>No topics defined</em> <em>Not available</em> <em>The sender is now a member of this list</em> <em>Yes, I really want to unsubscribe</em> <em>not available</em> <li>Set everyone's moderation bit, including
those members not currently visible <missing> <p>%(note)s
<p>You may have disabled list delivery intentionally,
or it may have been triggered by bounces from your email
address. In either case, to re-enable delivery, change the
%(link)s option below. Contact %(mailto)s if you have any
questions or need assistance. <p>(Note that this is an umbrella list, intended to
have only other mailing lists as members. Among other things,
this means that your confirmation request will be sent to the
`%(sfx)s' account for your address.) <p>(Send questions and comments to <p>... <b><i>or</i></b> select your entry from
the subscribers list (see above). <p><em>To view more members, click on the appropriate
range listed below:</em> <p>Below is a listing of all the public mailing lists on
%(hostname)s. Click on a list name to get more information about
the list, or to subscribe, unsubscribe, and change the preferences
on your subscription. <p>Below is the collection of publicly-advertised
%(mailmanlink)s mailing lists on %(hostname)s. Click on a list
name to visit the configuration pages for that list. <p>There currently are no publicly-advertised
%(mailmanlink)s mailing lists on %(hostname)s. <p>There currently are no publicly-advertised %(mailmanlink)s
mailing lists on %(hostname)s. <p>We have received some recent bounces from your
address. Your current <em>bounce score</em> is %(score)s out of a
maximum of %(total)s. Please double check that your subscribed
address is correct and that there are no problems with delivery to
this address. Your bounce score will be automatically reset if
the problems are corrected soon. <tt>Reply-To:</tt> header munging <ul><li><b>Hold</b> -- this holds the message for approval
by the list moderators.
<p><li><b>Reject</b> -- this automatically rejects the message by
sending a bounce notice to the post's author. The text of the
bounce notice can be <a
href="?VARHELP=privacy/sender/member_moderation_notice"
>configured by you</a>.
<p><li><b>Discard</b> -- this simply discards the message, with
no notice sent to the post's author.
</ul> ? A A confirmation message has been sent to %(newaddr)s. A digest has been sent. A list name is required A reminder of your password has been emailed to you. A terse phrase identifying this list. Accept Accepts Acknowledge the member's posting Action to take for postings from non-members for which no
explicit action is defined. Action to take on all these held messages: Action to take when a message matches the content filtering
rules. Action to take when a moderated member posts to the
list. Action: Add <b>%(esender)s</b> to one of these sender filters: Add a non-fuzzy translation to the dictionary. Add new item... Added : %(s)s Additional Member Tasks Additional settings Additionally, forward this message to: Address/name/time Address: Addresses did not match! Addresses in this list are banned outright from subscribing
to this mailing list, with no further moderation required. Add
addresses one per line; start the line with a ^ character to
designate a regular expression match. Addresses may not be blank Admin address: Administrative requests for mailing list: Administrator Administrator passwords did not match 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. Advertise this list when people ask what lists are on this
machine? After content filtering, the message was empty Again to confirm password: Alias names (regexps) which qualify as explicit to or cc
destination names for this list. All runs all the above qrunners Already a member Already a member: %(member)s Also delete archives? 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. Always An HTML attachment was scrubbed...
URL: %(url)s
An attempt was made to subscribe your address to the mailing list
%(listaddr)s. You are already subscribed to this mailing list.
Note that the list membership is not public, so it is possible that a bad
person was trying to probe the list for its membership. This would be a
privacy violation if we let them do this, but we didn't.
If you submitted the subscription request and forgot that you were already
subscribed to the list, then you can ignore this message. If you suspect that
an attempt is being made to covertly discover whether you are a member of this
list, and you are worried about your privacy, then feel free to send a message
to the list administrator at %(listowner)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. Anyone Approve Apr April Archive messages? Archiving Options As needed Aug August Authentication failed. Authorization failed. Auto-discard notification Auto-generate initial list password? Auto-responder Auto-responder characteristics.<p>
In the text fields below, string interpolation is performed with
the following key/value substitutions:
<p><ul>
<li><b>listname</b> - <em>gets the name of the mailing list</em>
<li><b>listurl</b> - <em>gets the list's listinfo URL</em>
<li><b>requestemail</b> - <em>gets the list's -request address</em>
<li><b>owneremail</b> - <em>gets the list's -owner address</em>
</ul>
<p>For each text field, you can either enter the text directly into the text
box, or you can specify a file on your local system to upload as the text. Auto-response for your message to the "%(realname)s" mailing list Auto-response text to send to -owner emails. Auto-response text to send to -request emails. Auto-response text to send to mailing list posters. Awaiting moderator approval B Bad --digest option: %(kind)s Bad --nomail option: %(why)s Bad MIME type ignored: %(spectype)s Bad URL specification Bad approval password given. Held message is still being held. Bad argument to -a/--admin-notify: %(arg)s Bad argument to -w/--welcome-msg: %(arg)s Bad argument: %(arg)s Bad arguments: %(pargs)s Bad arguments: %(strargs)s Bad choice: %(yesno)s Bad command: %(command)s Bad confirmation string Bad digest specifier: %(arg)s Bad email address for option %(k)s: %(v)s Bad email address for option %(property)s: %(error)s Bad email address provided Bad moderation flag value Bad owner email address: %(s)s Bad queue directory: %(qdir)s Bad regular expression: Bad set command: %(subcmd)s Bad status number: %(arg)s Bad value for <a href="?VARHELP=bounce/%(property)s"
>%(property)s</a>: %(val)s Bad/Invalid email address Bad/Invalid email address: %(member)s Bad/Invalid email address: blank line Badly formed options entry:
%(record)s Ban <b>%(esender)s</b> from ever subscribing to this
mailing list Ban list Batched-delivery digest characteristics. Below, enter additional text to be added to the
top of your invitation or the subscription notification. Include at least
one blank line at the end... Blind carbon copies or other implicit destinations are
not allowed. Try reposting your message by explicitly including the list
address in the To: or Cc: fields. Bounce action notification Bounce detection sensitivity Bounce processing By clicking on the <em>Remind</em> button, your
password will be emailed to you. By clicking on the <em>Unsubscribe</em> button, a
confirmation message will be emailed to you. This message will have a
link that you should click on to complete the removal process (you can
also confirm by email; see the instructions in the confirmation
message). By default, should new list member postings be moderated? 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. 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. 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. CGI script error Can list members choose to receive list traffic bunched in digests? Can subscribers choose to receive mail immediately, rather
than in batched digests? Can't have empty html page. Cancel Cancel and discard Cancel held message posting Cancel my subscription request Cancel posting Cannot open mbox file %(mbox)s: %(msg)s Cannot read address file: %(filename)s: %(msg)s Cannot read both digest and normal members from standard input. Cannot unshunt message %(filebase)s, skipping:
%(e)s Cannot unsubscribe non-members: Catalan Ceiling on acceptable number of recipients for a posting. Change My Address and Name Change My Password Change a list's password.
Prior to Mailman 2.1, list passwords were kept in crypt'd format -- usually.
Some Python installations didn't have the crypt module available, so they'd
fall back to md5. Then suddenly the Python installation might grow a crypt
module and all list passwords would be broken.
In Mailman 2.1, all list and site passwords are stored in SHA1 hexdigest
form. This breaks list passwords for all existing pre-Mailman 2.1 lists, and
since those passwords aren't stored anywhere in plain text, they cannot be
retrieved and updated.
Thus, this script generates new passwords for a list, and optionally sends it
to all the owners of the list.
Usage: change_pw [options]
Options:
--all / -a
Change the password for all lists.
--domain=domain
-d domain
Change the password for all lists in the virtual domain `domain'. It
is okay to give multiple -d options.
--listname=listname
-l listname
Change the password only for the named list. It is okay to give
multiple -l options.
--password=newpassword
-p newpassword
Use the supplied plain text password `newpassword' as the new password
for any lists that are being changed (as specified by the -a, -d, and
-l options). If not given, lists will be assigned a randomly
generated new password.
--quiet / -q
Don't notify list owners of the new password. You'll have to have
some other way of letting the list owners know the new password
(presumably out-of-band).
--help / -h
Print this help message and exit.
Change address Change list ownership passwords Change of address request confirmed Changing passwords for list: %(listname)s Check a list's config database file for integrity.
All of the following files are checked:
config.pck
config.pck.last
config.db
config.db.last
config.safety
It's okay if any of these are missing. config.pck and config.pck.last are
pickled versions of the config database file for 2.1a3 and beyond. config.db
and config.db.last are used in all earlier versions, and these are Python
marshals. config.safety is a pickle written by 2.1a3 and beyond when the
primary config.pck file could not be read.
Usage: %(PROGRAM)s [options] [listname [listname ...]]
Options:
--all / -a
Check the databases for all lists. Otherwise only the lists named on
the command line are checked.
--verbose / -v
Verbose output. The state of every tested file is printed.
Otherwise only corrupt files are displayed.
--help / -h
Print this text and exit.
Check for pending admin requests and mail the list owners if necessary.
Usage: %(PROGRAM)s [options]
Options:
-h/--help
Print this message and exit.
Check the permissions for the Mailman installation.
Usage: %(PROGRAM)s [-f] [-v] [-h]
With no arguments, just check and report all the files that have bogus
permissions or group ownership. With -f (and run as root), fix all the
permission problems found. With -v be verbose.
Chinese (China) Chinese (Taiwan) Clean up an .mbox archive file.
The archiver looks for Unix-From lines separating messages in an mbox archive
file. For compatibility, it specifically looks for lines that start with
"From " -- i.e. the letters capital-F, lowercase-r, o, m, space, ignoring
everything else on the line.
Normally, any lines that start "From " in the body of a message should be
escaped such that a > character is actually the first on a line. It is
possible though that body lines are not actually escaped. This script
attempts to fix these by doing a stricter test of the Unix-From lines. Any
lines that start "From " but do not pass this stricter test are escaped with a
> character.
Usage: cleanarch [options] < inputfile > outputfile
Options:
-s n
--status=n
Print a # character every n lines processed
-q / --quiet
Don't print changed line information to standard error.
-n / --dry-run
Don't actually output anything.
-h / --help
Print this message and exit
Clear Form Clear this member's <em>moderate</em> flag Click here for the list of Click here to hide the legend for this table. Click here to include the legend for this table. Click here to reload this page. Click on a link to visit your options page for the
requested mailing list. Click on the message number to view the individual
message, or you can Clone a member address.
Cloning a member address means that a new member will be added who has all the
same options and passwords as the original member address. Note that this
operation is fairly trusting of the user who runs it -- it does no
verification to the new address, it does not send out a welcome message, etc.
The existing member's subscription is usually not modified in any way. If you
want to remove the old address, use the -r flag. If you also want to change
any list admin addresses, use the -a flag.
Usage:
clone_member [options] fromoldaddr tonewaddr
Where:
--listname=listname
-l listname
Check and modify only the named mailing lists. If -l is not given,
then all mailing lists are scanned from the address. Multiple -l
options can be supplied.
--remove
-r
Remove the old address from the mailing list after it's been cloned.
--admin
-a
Scan the list admin addresses for the old address, and clone or change
them too.
--quiet
-q
Do the modifications quietly.
--nomodify
-n
Print what would be done, but don't actually do it. Inhibits the
--quiet flag.
--help
-h
Print this help message and exit.
fromoldaddr (`from old address') is the old address of the user. tonewaddr
(`to new address') is the new address of the user.
Computing threaded index
Conceal the member's address Configuration Categories Configure a list from a text file description.
Usage: config_list [options] listname
Options:
--inputfile filename
-i filename
Configure the list by assigning each module-global variable in the
file to an attribute on the list object, then saving the list. The
named file is loaded with execfile() and must be legal Python code.
Any variable that isn't already an attribute of the list object is
ignored (a warning message is printed). See also the -c option.
A special variable named `mlist' is put into the globals during the
execfile, which is bound to the actual MailList object. This lets you
do all manner of bizarre thing to the list object, but BEWARE! Using
this can severely (and possibly irreparably) damage your mailing list!
--outputfile filename
-o filename
Instead of configuring the list, print out a list's configuration
variables in a format suitable for input using this script. In this
way, you can easily capture the configuration settings for a
particular list and imprint those settings on another list. filename
is the file to output the settings to. If filename is `-', standard
out is used.
--checkonly
-c
With this option, the modified list is not actually changed. Only
useful with -i.
--verbose
-v
Print the name of each attribute as it is being changed. Only useful
with -i.
--help
-h
Print this help message and exit.
The options -o and -i are mutually exclusive.
Confirm 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. Confirm administrator password: Confirm and approve Confirm change of address request Confirm initial password: Confirm moderator password: Confirm subscription request Confirm unsubscription request Confirmation from your email address is required, to prevent anyone from
subscribing you without permission. Instructions are being sent to you at
%(email)s. Please note your subscription will not start until you confirm
your subscription. Confirmation string was empty. Confirmation string: Confirmation succeeded Content filtered message notification Content filtering Continue awaiting approval Convert a list's interpolation strings from %-strings to $-strings.
This script is intended to be run as a bin/withlist script, i.e.
% bin/withlist -l -r convert <mylist>
Could not open file for reading: %(filename)s. Could not open file for writing: Create List Create a %(hostname)s Mailing List Create another list Creating archive directory Croatian Czech Daily Danish Database Updated... Dec December Default language for this list. Default options for new members joining this list.<input
type="hidden" name="new_member_options" value="ignore"> Defer Delete Delete this list Delete this mailing list Delivered by Mailman<br>version %(version)s Description Description: Description: %(description)s Detailed instructions for the administrative database Digest Digest Footer Digest Header Digest members: Digest options Disabled Discard Discard all messages marked <em>Defer</em> Discard held messages older than this number of days.
Use 0 for no automatic discarding. Discard held messages.
Usage:
discard [options] file ...
Options:
--help / -h
Print this help message and exit.
--quiet / -q
Don't print status messages.
Discarded held msg #%(id)s for list %(listname)s Discards Do not send a copy of a member's own post Downgrade detected, from version %(hexlversion)s to version %(hextversion)s
This is probably not safe.
Exiting. Dry run mode Dump the contents of any Mailman `database' file.
Usage: %(PROGRAM)s [options] filename
Options:
--marshal/-m
Assume the file contains a Python marshal, overridding any automatic
guessing.
--pickle/-p
Assume the file contains a Python pickle, overridding any automatic
guessing.
--noprint/-n
Don't attempt to pretty print the object. This is useful if there's
some problem with the object and you just want to get an unpickled
representation. Useful with `python -i bin/dumpdb <file>'. In that
case, the root of the tree will be left in a global called "msg".
--help/-h
Print this help message and exit
If the filename ends with `.db', then it is assumed that the file contains a
Python marshal. If the file ends with `.pck' then it is assumed to contain a
Python pickle. In either case, if you want to override the default assumption
-- or if the file ends in neither suffix -- use the -p or -m flags.
Dutch 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>. 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. Each topic keyword is actually a regular expression, which is
matched against certain parts of a mail message, specifically the
<code>Keywords:</code> and <code>Subject:</code> message headers.
Note that the first few lines of the body of the message can also
contain a <code>Keywords:</code> and <code>Subject:</code>
"header" on which matching is also performed. Edit HTML : Error Edit Options Edit the public HTML pages and text files Email My Password To Me Email address: Emergency hold on all list traffic is in effect Emergency moderation of all list traffic is enabled Emergency moderation of all list traffic. Empty list passwords are not allowed Enabled Encode the
<a href="?VARHELP=general/subject_prefix">subject
prefix</a> even when it consists of only ASCII characters? End of English (USA) Enter confirmation cookie Enter new administrator password: Enter new moderator password: Enter one address per line below... Enter the email of the person running the list: Enter the name of the list: Error Error Unsubscribing: Error inviting: Error opening list "%(listname)s", skipping.
%(e)s Error opening list %(listname)s... skipping. Error subscribing: Error: Estonian Euskara Explicit <tt>Reply-To:</tt> header. Explicit address Feb February Filter out duplicate messages to list members (if possible) Filter rules to match against the headers of a message. Finalizing Find all lists that a member's address is on.
Usage:
find_member [options] regex [regex [...]]
Where:
--listname=listname
-l listname
Include only the named list in the search.
--exclude=listname
-x listname
Exclude the named list from the search.
--owners
-w
Search list owners as well as members.
--help
-h
Print this help message and exit.
regex
A Python regular expression to match against.
The interaction between -l and -x is as follows. If any -l option is given
then only the named list will be included in the search. If any -x option is
given but no -l option is given, then all lists will be search except those
specifically excluded.
Regular expression syntax is Perl5-like, using the Python re module. Complete
specifications are at:
https://docs.python.org/2/library/re.html
Address matches are case-insensitive, but case-preserved addresses are
displayed.
Find member %(link)s: Finnish First Fix the MM2.1b4 archives.
Usage: %(PROGRAM)s [options] file ...
Where options are:
-h / --help
Print this help message and exit.
Only use this to `fix' some archive database files that may have gotten
written in Mailman 2.1b4 with some bogus data. Use like this from your
$PREFIX directory
%% %(PROGRAM)s `grep -l _mlist archives/private/*/database/*-article`
(note the backquotes are required)
You will need to run `bin/check_perms -f' after running this script.
Fixing language templates: %(listname)s Footer added to every digest Footer added to mail sent to regular list members For some reason, %(mbox_dir)s exists as a file. This won't work with
b6, so I'm renaming it to %(mbox_dir)s.tmp and proceeding. For some unknown reason Forward messages (individually) to: Forward of moderated message Forward to List Owner Forwarding options Fourth French Fri From: Full Personalization Fundamental list characteristics, including descriptive
info and basic behaviors. General Options General framework for interacting with a mailing list object.
There are two ways to use this script: interactively or programmatically.
Using it interactively allows you to play with, examine and modify a MailList
object from Python's interactive interpreter. When running interactively, a
MailList object called `m' will be available in the global namespace. It also
loads the class MailList into the global namespace.
Programmatically, you can write a function to operate on a MailList object,
and this script will take care of the housekeeping (see below for examples).
In that case, the general usage syntax is:
%% bin/withlist [options] listname [args ...]
Options:
-l / --lock
Lock the list when opening. Normally the list is opened unlocked
(e.g. for read-only operations). You can always lock the file after
the fact by typing `m.Lock()'
Note that if you use this option, you should explicitly call m.Save()
before exiting, since the interpreter's clean up procedure will not
automatically save changes to the MailList object (but it will unlock
the list).
-i / --interactive
Leaves you at an interactive prompt after all other processing is
complete. This is the default unless the -r option is given.
--run [module.]callable
-r [module.]callable
This can be used to run a script with the opened MailList object.
This works by attempting to import `module' (which must be in the
directory containing withlist, or already be accessible on your
sys.path), and then calling `callable' from the module. callable can
be a class or function; it is called with the MailList object as the
first argument. If additional args are given on the command line,
they are passed as subsequent positional args to the callable.
Note that `module.' is optional; if it is omitted then a module with
the name `callable' will be imported.
The global variable `r' will be set to the results of this call.
--all / -a
This option only works with the -r option. Use this if you want to
execute the script on all mailing lists. When you use -a you should
not include a listname argument on the command line. The variable `r'
will be a list of all the results.
--quiet / -q
Suppress all status messages.
--help / -h
Print this message and exit
Here's an example of how to use the -r option. Say you have a file in the
Mailman installation directory called `listaddr.py', with the following
two functions:
def listaddr(mlist):
print mlist.GetListEmail()
def requestaddr(mlist):
print mlist.GetRequestEmail()
Now, from the command line you can print the list's posting address by running
the following from the command line:
%% bin/withlist -r listaddr mylist
Loading list: mylist (unlocked)
Importing listaddr ...
Running listaddr.listaddr() ...
mylist@myhost.com
And you can print the list's request address by running:
%% bin/withlist -r listaddr.requestaddr mylist
Loading list: mylist (unlocked)
Importing listaddr ...
Running listaddr.requestaddr() ...
mylist-request@myhost.com
As another example, say you wanted to change the password for a particular
user on a particular list. You could put the following function in a file
called `changepw.py':
from Mailman.Errors import NotAMemberError
def changepw(mlist, addr, newpasswd):
try:
mlist.setMemberPassword(addr, newpasswd)
mlist.Save()
except NotAMemberError:
print 'No address matched:', addr
and run this from the command line:
%% bin/withlist -l -r changepw mylist somebody@somewhere.org foobar
General list information page General list personality Generate binary message catalog from textual translation description.
This program converts a textual Uniforum-style message catalog (.po file) into
a binary GNU catalog (.mo file). This is essentially the same function as the
GNU msgfmt program, however, it is a simpler implementation.
Usage: msgfmt.py [OPTIONS] filename.po
Options:
-o file
--output-file=file
Specify the output file to write to. If omitted, output will go to a
file named filename.mo (based off the input file name).
-h
--help
Print this message and exit.
-V
--version
Display version information and exit.
German Gnu's Not Unix Go to list archives Go to the general list information page Gzip'd Text%(sz)s HTML Unchanged. HTML attachment scrubbed and removed HTML successfully updated. Header added to every digest Header added to mail sent to regular list members Header filter rules require a pattern.
Incomplete filter rules will be ignored. Header filters Hide the sender of a message, replacing it with the list
address (Removes From, Sender and Reply-To fields) Hit enter to notify %(listname)s owner... Hold Hold posts with header value matching a specified regexp. Holds Host name this list prefers for email. Hostile address (illegal characters) Hostile address (illegal characters): %(member)s Hostile subscription attempt detected 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. How many body lines should the topic matcher scan? How often should a new archive volume be started? How often should a new digest volume be started? Hungarian If a posting has this number, or more, of recipients, it is
held for admin approval. Use 0 for no ceiling. If you reject this post,<br>please explain (optional): If you reply to this message, keeping the Subject: header intact, Mailman will
discard the held message. Do this if the message is spam. If you reply to
this message and include an Approved: header with the list password in it, the
message will be approved for posting to the list. The Approved: header can
also appear in the first line of the body of the reply. If you supply a password, you must confirm it. If your mailing list's default language uses a non-ASCII
character set and the prefix contains non-ASCII characters, the
prefix will always be encoded according to the relevant
standards. However, if your prefix contains only ASCII
characters, you may want to set this option to <em>Never</em> to
disable prefix encoding. This can make the subject headers
slightly more readable for users with mail readers that don't
properly handle non-ASCII encodings.
<p>Note however, that if your mailing list receives both encoded
and unencoded subject headers, you might want to choose <em>As
needed</em>. Using this setting, Mailman will not encode ASCII
prefixes when the rest of the header contains only ASCII
characters, but if the original header contains non-ASCII
characters, it will encode the prefix. This avoids an ambiguity
in the standards which could cause some mail readers to display
extra, or missing spaces between the prefix and the original
header. Ignore : %(addr)30s Ignoring bad pended data: %(key)s: %(val)s Ignoring changes to deleted member: %(user)s Ignoring held msg w/bad id: %(f)s Ignoring non-held message: %(f)s Ignoring non-text/plain MIME parts Illegal Email Address Illegal email address provided Illegal list name: %(s)s Illegal option: %(opt)s Importing %(module)s... In order to change your membership option, you must
first log in by giving your %(extra)smembership password in the section
below. If you don't remember your membership password, you can have it
emailed to you by clicking on the button below. If you just want to
unsubscribe from this list, click on the <em>Unsubscribe</em> button and a
confirmation message will be sent to you.
<p><strong><em>Important:</em></strong> From this point on, you must have
cookies enabled in your browser, otherwise none of your changes will take
effect.
Increment the digest volume number and reset the digest number to one.
Usage: %(PROGRAM)s [options] [listname ...]
Options:
--help/-h
Print this message and exit.
The lists named on the command line are bumped. If no list names are given,
all lists are bumped.
Initial %(listname)s password: Initial list of supported languages. <p>Note that if you do not
select at least one initial language, the list will use the server
default language of %(deflang)s Initial list owner address: Initial list password: Initial list passwords do not match Inject a message from a file into Mailman's incoming queue.
Usage: inject [options] [filename]
Options:
-h / --help
Print this text and exit.
-l listname
--listname=listname
The name of the list to inject this message to. Required.
-q queuename
--queue=queuename
The name of the queue to inject the message to. The queuename must be
one of the directories inside the qfiles directory. If omitted, the
incoming queue is used.
filename is the name of the plaintext message file to inject. If omitted,
standard input is used.
Interrupted... Invalid : %(addr)30s Invalid confirmation string. It is
possible that you are attempting to confirm a request for an
address that has already been unsubscribed. Invalid options to CGI script Invalid options to CGI script. Invalid value for property: %(k)s Invalid value for variable: %(property)s Invite Is archive file source for public or private archival? Is qrunner even running? Is the list moderator's approval required for unsubscription
requests? (<em>No</em> is recommended) Italian Jan January Japanese Jul July Jun June Korean Language options Languages supported by this list. Last autoresponse notification for today Leave the initial password (and confirmation) fields
blank if you want Mailman to autogenerate the list
passwords. Legacy anti-spam filters List List Characteristics List Helpbot: %(requestaddr)s List Identity List Owners: %(owneraddr)s List admin only List all the owners of a mailing list.
Usage: %(program)s [options] listname ...
Where:
--all-vhost=vhost
-v=vhost
List the owners of all the mailing lists for the given virtual host.
--all
-a
List the owners of all the mailing lists on this system.
--help
-h
Print this help message and exit.
`listname' is the name of the mailing list to print the owners of. You can
have more than one named list on the command line.
List already exists: %(listname)s List already exists: %(safelistname)s List creator's (authentication) password: List members 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. List my other subscriptions List name is required List name is required. List name must not include "@": %(safelistname)s List name: %(listname)s List of addresses which are banned from membership in this
mailing list. List of non-member addresses whose postings should be
automatically accepted. List of non-member addresses whose postings will be
automatically discarded. List of non-member addresses whose postings will be
automatically rejected. List of non-member addresses whose postings will be
immediately held for moderation. List password: List subscriptions for %(safeuser)s on %(hostname)s List the owners of a mailing list, or all mailing lists.
Usage: %(PROGRAM)s [options] [listname ...]
Options:
-w / --with-listnames
Group the owners by list names and include the list names in the
output. Otherwise, the owners will be sorted and uniquified based on
the email address.
-m / --moderators
Include the list moderators in the output.
-h / --help
Print this help message and exit.
listname
Print the owners of the specified lists. More than one can appear
after the options. If there are no listnames provided, the owners of
all the lists will be displayed.
List topic keywords List traffic archival policies. List-specific text prepended to new-subscriber welcome
message List: List: %(listname)s, Owners: %(owners)s Lithuanian Loading list %(listname)s Log in Log out Logout MIME Mail delivery Mail<->News gateways Mail-to-News and News-to-Mail gateway services. Mailing list creation request for list %(listname)s Mailing list creation results Mailing list deletion results Mailing list removal request for list %(listname)s Mailman Mailman %(varname)s List Option Help Mailman Administrative Database Error Mailman prefixes <tt>Subject:</tt> headers with
<a href="?VARHELP=general/subject_prefix">text you can
customize</a> and normally, this prefix shows up in messages
gatewayed to Usenet. You can set this option to <em>No</em> to
disable the prefix on gated messages. Of course, if you turn off
normal <tt>Subject:</tt> prefixes, they won't be prefixed for
gated messages either. Mailman privacy alert Mailman won't accept the given email address as a valid address.
(E.g. it must have an @ in it.) Make your changes in the following section, then submit them
using the <em>Submit Your Changes</em> button below. 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> Mar March Mass Removals Mass Subscriptions Mass Removal Mass Subscription Maximum length in kilobytes (KB) of a message body. Use 0
for no limit. May Member filters Member name successfully changed. Membership List Membership exposure Membership re-enabled. Membership List Membership Management... Message Excerpt: Message Headers: Message body is too big: %(size)d bytes with a limit of
%(limit)d KB Message has a suspicious header Message has implicit destination Message may contain administrivia Message rejected by filter rule match Moderated Moderator Moderator passwords did not match Mon Monthly More information: %(listurl)s Move rule down Move rule up Must have a listname and a filename Must posts have list named in destination (to, cc) field
(or be among the acceptable alias names, specified below)? Name of list: Name: Natural language (internationalization) options. Never New %(listname)s password: %(notifypassword)s New %(pwdesc)s password: New password for member %(member)40s: %(randompw)s New subscription request to list %(realname)s from %(addr)s New unsubscription request from %(realname)s by %(addr)s News server settings No No address given No argument to -f given No child with pid: %(pid)s No command given. No commands were found in this message.
To obtain instructions, send a message containing just the word "help".
No filename given. No list name supplied. No list named: No listname given No lists to search No matching mailing lists found No one can subscribe to the digest of this list! No problems found No reason given No runner name given. No subject No such list "%(listname)s"
%(e)s No such list (or list already deleted): %(listname)s No such list <em>%(safelistname)s</em> No such list: %(listname)s No such list: %(listname)s. Removing its residual archives. No such member: %(addr)s No such member: %(safeuser)s. No updates are necessary. No valid address found to subscribe No valid variable name found. Non-digest (regular) members: Non-digest options Non-member filters Non-members are not allowed to post messages to this list. Non-standard property restored: %(k)s None None - no verification steps (<em>Not
Recommended </em>)<br>
Confirm (*) - email confirmation step 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. 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 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>
Norwegian Not a valid email address: %(toaddr)s Not authenticated Not removing archives. Reinvoke with -a to remove them. Not subscribed Note: Since this is a list of mailing lists, administrative
notices like the password reminder will be sent to
your membership administrative address, %(addr)s. Note: your list delivery is currently disabled%(reason)s. Nothing to do. Notice: %(discarded)d old request(s) automatically expired.
Notifications Nov November Number of days between auto-responses to either the mailing
list or -request/-owner address from the same poster. Set to
zero (or negative) for no grace period (i.e. auto-respond to
every message). Oct October Off Okay, the list moderator will still have the
opportunity to approve or reject this message. On Once a month, your password will be emailed to you as a reminder. One of -i or -o is required One of these actions is taken when the message matches one of
the content filtering rules, meaning, the top-level
content type matches one of the <a
href="?VARHELP=contentfilter/filter_mime_types"
>filter_mime_types</a>, or the top-level content type does
<strong>not</strong> match one of the
<a href="?VARHELP=contentfilter/pass_mime_types"
>pass_mime_types</a>, or if after filtering the subparts of the
message, the message ends up empty.
<p>Note this action is not taken if after filtering the message
still contains content. In that case the message is always
forwarded on to the list membership.
<p>When messages are discarded, a log entry is written
containing the Message-ID of the discarded message. When
messages are rejected or forwarded to the list owner, a reason
for the rejection is included in the bounce message to the
original author. When messages are preserved, they are saved in
a special queue directory on disk for the site administrator to
view (and possibly rescue) but otherwise discarded. This last
option is only available if enabled by the site
administrator. Only one -f switch allowed Only one of -i or -o is allowed Open list, moderated group Original Message Other Administrative Activities Overview of all %(hostname)s mailing lists PID unreadable in: %(pidfile)s Password // URL Password change failed. Password changed. Password reminder Password successfully changed. Password: Password: Passwords Passwords did not match! Passwords do not match; no changes made. Passwords may not be blank Pattern (as regexp): Pending subscriptions: Perform all necessary upgrades.
Usage: %(PROGRAM)s [options]
Options:
-f/--force
Force running the upgrade procedures. Normally, if the version number
of the installed Mailman matches the current version number (or a
`downgrade' is detected), nothing will be done.
-h/--help
Print this text and exit.
Use this script to help you update to the latest release of Mailman from
some previous version. It knows about versions back to 1.0b4 (?).
Permanently ban from this list Permanently remove mailing list <em>%(realname)s</em> Plain Please do *not* post administrative requests to the mailing
list. If you wish to subscribe, visit %(listurl)s or send a message with the
word `help' in it to the request address, %(request)s, for further
instructions. Please enter the confirmation string
(i.e. <em>cookie</em>) that you received in your email message, in the box
below. Then hit the <em>Submit</em> button to proceed to the next
confirmation step. Please specify either -p or -m. Please trim the recipient list; it is too long. Policies concerning immediately delivered list traffic. Polish Poll the NNTP servers for messages to be gatewayed to mailing lists.
Usage: gate_news [options]
Where options are
--help
-h
Print this text and exit.
Portuguese Portuguese (Brazil) Post by non-member to a members-only list Post to moderated list Posted message canceled Poster Posting Held for Approval Posting of your message titled "%(subject)s" Posting to a moderated newsgroup Posting to a restricted list by sender requires approval Postings from any of these non-members will be automatically
discarded. That is, the message will be thrown away with no
further processing or notification. The sender will not receive
a notification or a bounce, however the list moderators can
optionally <a href="?VARHELP=privacy/sender/forward_auto_discards"
>receive copies of auto-discarded messages.</a>.
<p>Add member addresses one per line; start the line with a ^
character to designate a regular expression match. Postings from any of these non-members will be automatically
rejected. In other words, their messages will be bounced back to
the sender with a notification of automatic rejection. This
option is not appropriate for known spam senders; their messages
should be
<a href="?VARHELP=privacy/sender/discard_these_nonmembers"
>automatically discarded</a>.
<p>Add member addresses one per line; start the line with a ^
character to designate a regular expression match. Postings from any of these non-members will be immediately
and automatically held for moderation by the list moderators.
The sender will receive a notification message which will allow
them to cancel their held message. Add member addresses one per
line; start the line with a ^ character to designate a regular
expression match. Postings to: %(postaddr)s Preferred language: Prefix <tt>Subject:</tt> headers on postings gated to news? Prefix for subject line of list postings. Preserve Preserve message for site administrator Preserve messages for the site administrator Primary start-up and shutdown script for Mailman's qrunner daemon.
This script starts, stops, and restarts the main Mailman queue runners, making
sure that the various long-running qrunners are still alive and kicking. It
does this by forking and exec'ing the qrunners and waiting on their pids.
When it detects a subprocess has exited, it may restart it.
The qrunners respond to SIGINT, SIGTERM, and SIGHUP. SIGINT and SIGTERM both
cause the qrunners to exit cleanly, but the master will only restart qrunners
that have exited due to a SIGINT. SIGHUP causes the master and the qrunners
to close their log files, and reopen then upon the next printed message.
The master also responds to SIGINT, SIGTERM, and SIGHUP, which it simply
passes on to the qrunners (note that the master will close and reopen its own
log files on receipt of a SIGHUP). The master also leaves its own process id
in the file data/master-qrunner.pid but you normally don't need to use this
pid directly. The `start', `stop', `restart', and `reopen' commands handle
everything for you.
Usage: %(PROGRAM)s [options] [ start | stop | restart | reopen ]
Options:
-n/--no-restart
Don't restart the qrunners when they exit because of an error or a
SIGINT. They are never restarted if they exit in response to a
SIGTERM. Use this only for debugging. Only useful if the `start'
command is given.
-u/--run-as-user
Normally, this script will refuse to run if the user id and group id
are not set to the `mailman' user and group (as defined when you
configured Mailman). If run as root, this script will change to this
user and group before the check is made.
This can be inconvenient for testing and debugging purposes, so the -u
flag means that the step that sets and checks the uid/gid is skipped,
and the program is run as the current user and group. This flag is
not recommended for normal production environments.
Note though, that if you run with -u and are not in the mailman group,
you may have permission problems, such as begin unable to delete a
list's archives through the web. Tough luck!
-s/--stale-lock-cleanup
If mailmanctl finds an existing master lock, it will normally exit
with an error message. With this option, mailmanctl will perform an
extra level of checking. If a process matching the host/pid described
in the lock file is running, mailmanctl will still exit, but if no
matching process is found, mailmanctl will remove the apparently stale
lock and make another attempt to claim the master lock.
-q/--quiet
Don't print status messages. Error messages are still printed to
standard error.
-h/--help
Print this message and exit.
Commands:
start - Start the master daemon and all qrunners. Prints a message and
exits if the master daemon is already running.
stop - Stops the master daemon and all qrunners. After stopping, no
more messages will be processed.
restart - Restarts the qrunners, but not the master process. Use this
whenever you upgrade or update Mailman so that the qrunners will
use the newly installed code.
reopen - This will close all log files, causing them to be re-opened the
next time a message is written to them
Print the Mailman version.
Privacy options... Private Archive Error Private Archive Error - %(msg)s Private archive file not found Problems found: Process disabled members, recommended once per day.
This script cruises through every mailing list looking for members whose
delivery is disabled. If they have been disabled due to bounces, they will
receive another notification, or they may be removed if they've received the
maximum number of notifications.
Use the --byadmin, --byuser, and --unknown flags to also send notifications to
members whose accounts have been disabled for those reasons. Use --all to
send the notification to all disabled members.
Usage: %(PROGRAM)s [options]
Options:
-h / --help
Print this message and exit.
-o / --byadmin
Also send notifications to any member disabled by the list
owner/administrator.
-m / --byuser
Also send notifications to any member disabled by themselves.
-u / --unknown
Also send notifications to any member disabled for unknown reasons
(usually a legacy disabled address).
-b / --notbybounce
Don't send notifications to members disabled because of bounces (the
default is to notify bounce disabled members).
-a / --all
Send notifications to all disabled members.
-f / --force
Send notifications to disabled members even if they're not due a new
notification yet.
-l listname
--listname=listname
Process only the given list, otherwise do all lists.
Public mailing lists at %(hostname)s: Python Powered Quarterly 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). Re-enable mailing list membership Re-enable membership Re-generate the Pipermail gzip'd archive flat files.
This script should be run nightly from cron. When run from the command line,
the following usage is understood:
Usage: %(program)s [-v] [-h] [listnames]
Where:
--verbose
-v
print each file as it's being gzip'd
--help
-h
print this message and exit
listnames
Optionally, only compress the .txt files for the named lists. Without
this, all archivable lists are processed.
Re-opening all log files Re-run as %(MAILMAN_USER)s (or root) with -f flag to fix Reason for refusal Reason: Rebuild a list's archive.
Use this command to rebuild the archives for a mailing list. You may want to
do this if you edit some messages in an archive, or remove some messages from
an archive.
Usage: %(PROGRAM)s [options] <listname> [<mbox>]
Where options are:
-h / --help
Print this help message and exit.
-q / --quiet
Make the archiver output less verbose.
--wipe
First wipe out the original archive before regenerating. You usually
want to specify this argument unless you're generating the archive in
chunks.
-s N
--start=N
Start indexing at article N, where article 0 is the first in the mbox.
Defaults to 0.
-e M
--end=M
End indexing at article M. This script is not very efficient with
respect to memory management, and for large archives, it may not be
possible to index the mbox entirely. For that reason, you can specify
the start and end article numbers.
Where <mbox> is the path to a list's complete mbox archive. Usually this will
be some path in the archives/private directory. For example:
%% bin/arch mylist archives/private/mylist.mbox/mylist.mbox
<mbox> is optional. If it is missing, it is calculated.
Receive digests? Received: Recipient filters Recipient filters Reduce disk space usage for Pipermail archives.
Usage: %(PROGRAM)s [options] file ...
Where options are:
-h / --help
Print this help message and exit.
Only use this to 'fix' archive -article database files that have been written
with Mailman 2.1.3 or earlier and have html_body attributes in them. These
attributes can cause huge amounts of memory bloat and impact performance for
high activity lists, particularly those where large text postings are made to
them.
Example:
%% ls -1 archives/private/*/database/*-article | xargs %(PROGRAM)s
You should run `bin/check_perms -f' after running this script.
You will probably want to delete the -article.bak files created by this script
when you are satisfied with the results.
This script is provided for convenience purposes only. It isn't supported.
Regenerate Mailman specific aliases from scratch.
The actual output depends on the value of the `MTA' variable in your mm_cfg.py
file.
Usage: genaliases [options]
Options:
-q/--quiet
Some MTA output can include more verbose help text. Use this to tone
down the verbosity.
-h/--help
Print this message and exit.
Regexp: Regular Reject Rejects Remind Remove message attachments that don't have a matching
content type. Leave this field blank to skip this filter
test. Remove message attachments that don't have a matching
filename extension. Leave this field blank to skip this filter
test. Remove message attachments that have a matching content
type. Remove message attachments that have a matching filename
extension. Remove the components of a mailing list with impunity - beware!
This removes (almost) all traces of a mailing list. By default, the lists
archives are not removed, which is very handy for retiring old lists.
Usage:
rmlist [-a] [-h] listname
Where:
--archives
-a
Remove the list's archives too, or if the list has already been
deleted, remove any residual archives.
--help
-h
Print this help message and exit.
Removed: %(s)s Removing %(msg)s Request to mailing list %(realname)s rejected Requested topic is not valid: %(topicname)s Require approval Reset a list's web_page_url attribute to the default setting.
This script is intended to be run as a bin/withlist script, i.e.
% bin/withlist -l -r fix_url listname [options]
Options:
-u urlhost
--urlhost=urlhost
Look up urlhost in the virtual host table and set the web_page_url and
host_name attributes of the list to the values found. This
essentially moves the list from one virtual domain to another.
Without this option, the default web_page_url and host_name values are
used.
-v / --verbose
Print what the script is doing.
If run standalone, it prints this help text and exits.
Reset the passwords for members of a mailing list.
This script resets all the passwords of a mailing list's members. It can also
be used to reset the lists of all members of all mailing lists, but it is your
responsibility to let the users know that their passwords have been changed.
This script is intended to be run as a bin/withlist script, i.e.
% bin/withlist -l -r reset_pw listname [options]
Options:
-v / --verbose
Print what the script is doing.
Resetting %(n)s BYBOUNCEs disabled addrs with no bounce info Restarting Mailman's master qrunner Return the generated output. Return to the Romanian Run this program as root or as the %(name)s user, or use -u. Running %(module)s.%(callable)s()... Russian Sat Saving list Scrub attachments of regular delivery message? Search regular expression required Search... Second Select page to edit: Send "list created" email to list owner? Send goodbye message to members when they are unsubscribed? Send mail to poster when their posting is held for approval? Send monthly password reminders? Send notifications of new subscriptions to the list owner? Send notifications to the list owner? Send password reminders for all lists to all users.
This program scans all mailing lists and collects users and their passwords,
grouped by the list's host_name if mm_cfg.VIRTUAL_HOST_OVERVIEW is true. Then
one email message is sent to each unique user (per-virtual host) containing
the list passwords and options url for the user. The password reminder comes
from the mm_cfg.MAILMAN_SITE_LIST, which must exist.
Usage: %(PROGRAM)s [options]
Options:
-l listname
--listname=listname
Send password reminders for the named list only. If omitted,
reminders are sent for all lists. Multiple -l/--listname options are
allowed.
-h/--help
Print this message and exit.
Send password reminders to, eg, "-owner" address instead of
directly to user. Send unsubscription acknowledgement to the user? Send welcome message to newly subscribed members? Send welcome messages to new subscribers? Sender discarded message via web. Sender is explicitly forbidden Sender filters Sep September Serbian Server Local Time Set Set the site password, prompting from the terminal.
The site password can be used in most if not all places that the list
administrator's password can be used, which in turn can be used in most places
that a list users password can be used.
Usage: %(PROGRAM)s [options] [password]
Options:
-c/--listcreator
Set the list creator password instead of the site password. The list
creator is authorized to create and remove lists, but does not have
the total power of the site administrator.
-h/--help
Print this help message and exit.
If password is not given on the command line, it will be prompted for.
Setting host_name to: %(mailhost)s Setting this option causes member email addresses to be
transformed when they are presented on list web pages (both in
text and as links), so they're not trivially recognizable as
email addresses. The intention is to prevent the addresses
from being snarfed up by automated web scanners for use by
spammers. Setting this option instructs Mailman to start a new volume
with the next digest sent out. Setting web_page_url to: %(web_page_url)s Should Mailman convert <tt>text/html</tt> parts to plain
text? This conversion happens after MIME attachments have been
stripped. Should Mailman filter the content of list traffic according
to the settings below? Should Mailman notify you, the list owner, when bounces
cause a member to be unsubscribed? Should Mailman notify you, the list owner, when bounces
cause a member's subscription to be disabled? Should Mailman perform automatic bounce processing? 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. Should Mailman send an auto-response to emails sent to the
-owner address? Should Mailman send an auto-response to emails sent to the
-request address? If you choose yes, decide whether you want
Mailman to discard the original email, or forward it on to the
system as a normal mail command. Should Mailman send an auto-response to mailing list
posters? Should Mailman send the next digest right now, if it is not
empty? Should Mailman send you, the list owner, any bounce messages
that failed to be detected by the bounce processor? <em>Yes</em>
is recommended. Should Mailman start a new digest volume? Should a digest be dispatched daily when the size threshold isn't reached? Should administrator get notices of subscribes and
unsubscribes? 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. Should messages from non-members, which are automatically
discarded, be forwarded to the list moderator? 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. Should new members be quarantined before they
are allowed to post unmoderated to this list? Answer <em>Yes</em> to hold
new member postings for moderator approval by default. Should new posts to the mailing list be sent to the
newsgroup? Should new posts to the newsgroup be sent to the mailing
list? Should postings include the <tt>List-Post:</tt> header? Should the list moderators get immediate notice of new
requests, as well as daily notices about collected ones? Should the topic filter be enabled or disabled? Show member addresses so they're not directly recognizable
as email addresses? Show the contents of one or more Mailman queue files.
Usage: show_qfiles [options] qfile ...
Options:
-q / --quiet
Don't print `helpful' message delimiters.
-h / --help
Print this text and exit.
Example: show_qfiles qfiles/shunt/*.pck
Shutting down Mailman's master qrunner Site list is missing: %(sitelistname)s Size: Skipped content of type %(partctype)s
Slovenian Some unknown error occurred while creating the list.
Please contact the site administrator for assistance. Spam Filter Regexp: Spam Filter Rule %(i)d Spam filters Spanish (Spain) Stale pid file removed. Starting Mailman's master qrunner. States table for the finite-states-machine parser:
0 idle
1 filename-or-comment
2 msgid
3 msgstr
4 end
Subject: Submit Submit All Data Submit Changes Submit My Changes Submit Your Changes Subscribe Subscribe results page Subscribe these users now or invite them? Subscribe to list %(listname)s Subscribed: %(member)s Subscribing Subscription Requests Subscription request Subscription request confirmed Subscription request succeeded. Subscription rules Successfully Removed: Successfully Unsubscribed: Successfully invited: Successfully subscribed: Suffix for use when this list is an umbrella for other
lists, according to setting of previous "umbrella_list"
setting. Sun Swedish Synchronize a mailing list's membership with a flat file.
This script is useful if you have a Mailman mailing list and a sendmail
:include: style list of addresses (also as is used in Majordomo). For every
address in the file that does not appear in the mailing list, the address is
added. For every address in the mailing list that does not appear in the
file, the address is removed. Other options control what happens when an
address is added or removed.
Usage: %(PROGRAM)s [options] -f file listname
Where `options' are:
--no-change
-n
Don't actually make the changes. Instead, print out what would be
done to the list.
--welcome-msg[=<yes|no>]
-w[=<yes|no>]
Sets whether or not to send the newly added members a welcome
message, overriding whatever the list's `send_welcome_msg' setting
is. With -w=yes or -w, the welcome message is sent. With -w=no, no
message is sent.
--goodbye-msg[=<yes|no>]
-g[=<yes|no>]
Sets whether or not to send the goodbye message to removed members,
overriding whatever the list's `send_goodbye_msg' setting is. With
-g=yes or -g, the goodbye message is sent. With -g=no, no message is
sent.
--digest[=<yes|no>]
-d[=<yes|no>]
Selects whether to make newly added members receive messages in
digests. With -d=yes or -d, they become digest members. With -d=no
(or if no -d option given) they are added as regular members.
--notifyadmin[=<yes|no>]
-a[=<yes|no>]
Specifies whether the admin should be notified for each subscription
or unsubscription. If you're adding a lot of addresses, you
definitely want to turn this off! With -a=yes or -a, the admin is
notified. With -a=no, the admin is not notified. With no -a option,
the default for the list is used.
--file <filename | ->
-f <filename | ->
This option is required. It specifies the flat file to synchronize
against. Email addresses must appear one per line. If filename is
`-' then stdin is used.
--help
-h
Print this message.
listname
Required. This specifies the list to synchronize.
System error, bad content: %(content)s Tend to pending moderator requests Text appended to the bottom of every immediately-delivery
message. Text attached (as a final message) to the bottom of digests. Text attached (as an initial message, before the table of contents) to the top of digests. Text prepended to the top of every immediately-delivery
message. Text sent to people leaving the list. If empty, no special
text will be added to the unsubscribe message. Text to include in any
<a href="?VARHELP/privacy/sender/member_moderation_action"
>rejection notice</a> to
be sent to moderated members who post to this list. Text to include in any rejection notice to be sent to
non-members who post to this list. This notice can include
the list's owner address by %%(listowner)s and replaces the
internally crafted default message. Text%(sz)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. 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 set a separate moderator password in the fields below,
and also provide the email addresses of the list moderators in the
<a href="%(adminurl)s/general">general options section</a>. 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.) The Mailman Replybot The `join' command is synonymous with `subscribe'.
The `leave' command is synonymous with `unsubscribe'.
The `remove' command is synonymous with `unsubscribe'.
The address requesting to be changed has
been subsequently unsubscribed. This request has been
cancelled. The address requesting unsubscription is not
a member of the mailing list. Perhaps you have already been
unsubscribed, e.g. by the list administrator? The attached message has been automatically discarded. The attached message matched the %(listname)s mailing list's content filtering
rules and was prevented from being forwarded on to the list membership. You
are receiving the only remaining copy of the discarded message.
The attached message was received as a bounce, but either the bounce format
was not recognized, or no member addresses could be extracted from it. This
mailing list has been configured to send all unrecognized bounce messages to
the list administrator(s).
For more information see:
%(adminurl)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 :-) The current archive The email address you supplied is banned from this
mailing list. If you think this restriction is erroneous, please
contact the list owners at %(listowner)s. The email address you supplied is banned from this mailing list.
If you think this restriction is erroneous, please contact the list
owners at %(listowner)s. The email address you supplied is not valid. (E.g. it must contain an
`@'.) The following illegal substitution variables were
found in the <code>%(property)s</code> string:
<code>%(bad)s</code>
<p>Your list may not operate properly until you correct this
problem. The header filter rule pattern
'%(safepattern)s' is not a legal regular expression. This
rule will be ignored. The held message with the Subject:
header <em>%(subject)s</em> could not be found. The most likely
reason for this is that the list moderator has already approved or
rejected the message. You were not able to cancel it in
time. The held message you were referred to has
already been handled by the list administrator. The hostname of the machine your news server is running on. The list administrator email addresses. Multiple
administrator addresses, each on separate line is okay. The list administrator has disabled digest delivery for
this list, so your delivery option has not been set. However your
other options have been set successfully. The list administrator has disabled non-digest delivery
for this list, so your delivery option has not been set. However
your other options have been set successfully. The list moderator email addresses. Multiple
moderator addresses, each on separate line is okay. The list password cannot be empty The list password cannot be empty<!-- ignore --> The mailing list `%(listname)s' has been created via the through-the-web
interface. In order to complete the activation of this mailing list, the
proper /etc/aliases (or equivalent) file must be updated. The program
`newaliases' may also have to be run.
Here are the entries for the /etc/aliases file:
The mailing list `%(listname)s' has been removed via the through-the-web
interface. In order to complete the de-activation of this mailing list, the
appropriate /etc/aliases (or equivalent) file must be updated. The program
`newaliases' may also have to be run.
Here are the entries in the /etc/aliases file that should be removed:
The master qrunner lock could not be acquired because it appears as if another
master qrunner is already running.
The master qrunner lock could not be acquired, because it appears as if some
process on some other host may have acquired it. We can't test for stale
locks across host boundaries, so you'll have to do this manually. Or, if you
know the lock is stale, re-run mailmanctl with the -s flag.
Lock file: %(LOCKFILE)s
Lock host: %(status)s
Exiting. The master qrunner lock could not be acquired. It appears as though there is
a stale master qrunner lock. Try re-running mailmanctl with the -s flag.
The maximum member bounce score before the member's
subscription is disabled. This value can be a floating point
number. The message's content type was explicitly disallowed The message's content type was not explicitly allowed The message's file extension was explicitly disallowed The message's file extension was not explicitly allowed The moderation policy of the newsgroup. The name of the Usenet group to gateway to and/or from. The new address is already a member: %(newaddr)s The new address you requested %(newaddr)s is already a member of the
%(listname)s mailing list, however you have also requested a global change of
address. Upon confirmation, any other mailing list containing the address
%(safeuser)s will be changed. The next digest will be sent as volume
%(volume)s, number %(number)s 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. The number of days between sending the <em>Your Membership
Is Disabled</em> warnings. This value must be an integer. The public name of this list (make case-changes only). The results of your email command are provided below.
Attached is your original message.
The results of your email commands The site administrator at %(hostname)s has changed the password for your
mailing list %(listname)s. It is now
%(notifypassword)s
Please be sure to use this for all future list administration. You may want
to log in now to your list and change the password to something more to your
liking. Visit your list admin page at
%(adminurl)s
The subscribers list 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. The topic filter categorizes each incoming email message
according to <a
href="https://docs.python.org/2/library/re.html">regular
expression filters</a> you specify below. If the message's
<code>Subject:</code> or <code>Keywords:</code> header contains a
match against a topic filter, the message is logically placed
into a topic <em>bucket</em>. Each user can then choose to only
receive messages from the mailing list for a particular topic
bucket (or buckets). Any message not categorized in a topic
bucket registered with the user is not delivered to the list.
<p>Note that this feature only works with regular delivery, not
digest delivery.
<p>The body of the message can also be optionally scanned for
<code>Subject:</code> and <code>Keywords:</code> headers, as
specified by the <a
href="?VARHELP=topics/topics_bodylines_limit">topics_bodylines_limit</a>
configuration variable. The topic matcher will scan this many lines of the message
body looking for topic keyword matches. Body scanning stops when
either this many lines have been looked at, or a non-header-like
body line is encountered. By setting this value to zero, no body
lines will be scanned (i.e. only the <code>Keywords:</code> and
<code>Subject:</code> headers will be scanned). By setting this
value to a negative number, then all body lines will be scanned
until a non-header-like line is encountered.
The topic pattern '%(safepattern)s' is not a
legal regular expression. It will be discarded. The variable `m' is the %(listname)s MailList instance There are no pending requests. 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. 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. There was no digest to send. There were some problems deleting the mailing list
<b>%(listname)s</b>. Contact your site administrator at %(sitelist)s
for details. These are all the natural languages supported by this list.
Note that the
<a href="?VARHELP=language/preferred_language">default
language</a> must be included. 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. Third 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. This is %(also)sa hidden list, which means that the
list of members is available only to the list administrator. This is %(also)sa private list, which means that the
list of members is not available to non-members. This is %(also)sa public list, which means that the
list of members list is available to everyone. This is a closed list, which means your subscription
will be held for approval. You will be notified of the list
moderator's decision by email. 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://marc.merlins.org/netrants/reply-to-harmful.html">`Reply-To'
Munging Considered Harmful</a> for a general discussion of this
issue. See <a
href="http://marc.merlins.org/netrants/reply-to-useful.html">
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. This is the default natural language for this mailing list.
If <a href="?VARHELP=language/available_languages">more than one
language</a> is supported then users will be able to select their
own preferences for when they interact with the list. All other
interactions will be conducted in the default language. This
applies to both web-based and email-based messages, but not to
email posted by list members. This list This list does not support digest delivery. This list has no members. This list is restricted; your message was not approved. This list only supports digest delivery. This list only supports digest subscriptions! 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://marc.merlins.org/netrants/reply-to-harmful.html">`Reply-To'
Munging Considered Harmful</a> for a general discussion of this
issue. See <a
href="http://marc.merlins.org/netrants/reply-to-useful.html">
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. This page allows you as the list owner, to permanently
remove this mailing list from the system. <strong>This action is not
undoable</strong> so you should undertake it only if you are absolutely
sure this mailing list has served its purpose and is no longer necessary.
<p>Note that no warning will be sent to your list members and after this
action, any subsequent messages sent to the mailing list, or any of its
administrative addreses will bounce.
<p>You also have the option of removing the archives for this mailing list
at this time. It is almost always recommended that you do
<strong>not</strong> remove the archives, since they serve as the
historical record of your mailing list.
<p>For your safety, you will be asked to reconfirm the list password.
This section allows you to configure subscription and
membership exposure policy. You can also control whether this
list is public or not. See also the
<a href="%(admin)s/archive">Archival Options</a> section for
separate archive-related privacy settings. This section allows you to configure various anti-spam
filters posting filters, which can help reduce the amount of spam
your list members end up receiving.
This section allows you to configure various filters based on
the recipient of the message. This setting determines the moderation policy of the
newsgroup and its interaction with the moderation policy of the
mailing list. This only applies to the newsgroup that you are
gatewaying <em>to</em>, so if you are only gatewaying from
Usenet, or the newsgroup you are gatewaying to is not moderated,
set this option to <em>None</em>.
<p>If the newsgroup is moderated, you can set this mailing list
up to be the moderation address for the newsgroup. By selecting
<em>Moderated</em>, an additional posting hold will be placed in
the approval process. All messages posted to the mailing list
will have to be approved before being sent on to the newsgroup,
or to the mailing list membership.
<p><em>Note that if the message has an <tt>Approved</tt> header
with the list's administrative password in it, this hold test
will be bypassed, allowing privileged posters to send messages
directly to the list and the newsgroup.</em>
<p>Finally, if the newsgroup is moderated, but you want to have
an open posting policy anyway, you should select <em>Open list,
moderated group</em>. The effect of this is to use the normal
Mailman moderation facilities, but to add an <tt>Approved</tt>
header to all messages that are gatewayed to Usenet. 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)
This value may be either the name of your news server, or
optionally of the format name:port, where port is a port number.
The news server is not part of Mailman proper. You have to
already have access to an NNTP server, and that NNTP server must
recognize the machine this mailing list runs on as a machine
capable of reading and posting news. 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> Thu To finish creating your mailing list, you must edit your /etc/aliases (or
equivalent) file by adding the following lines, and possibly running the
`newaliases' program:
To unsubscribe from %(realname)s, get a password reminder,
or change your subscription options %(either)senter your subscription
email address:
<p><center> To visit the administrators configuration page for an
unadvertised list, open a URL similar to this one, but with a '/' and
the %(extra)slist name appended. If you have the proper authority,
you can also <a href="%(creatorurl)s">create a new mailing list</a>.
<p>General list information can be found at Today's Topics (%(msgcount)d messages) Today's Topics:
Too many recipients to the message Topic %(i)d Topic filter details Topic keywords, one per line, to match against each message. Topic name: Topic specifications require both a name and
a pattern. Incomplete topics will be ignored. Topics Tue Turkish 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. 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. U Ukrainian Umbrella list settings Uncaught bounce notification Unix-From line changed: %(lineno)d Unknown language: %(lang)s Unknown list: %(listname)s Unknown virtual host: %(safehostname)s Unlock a locked list, but do not implicitly Save() it.
This does not get run if the interpreter exits because of a signal, or if
os._exit() is called. It will get called if an exception occurs though.
Unlocking (but not saving) list: %(listname)s Unsubscribe Unsubscribe or edit options Unsubscription Requests Unsubscription request Unsubscription request confirmed Unsubscription request succeeded. Unsubscription results Updating HTML for article %(seq)s Updating Mailman 2.0 pending_subscriptions.db database Updating Mailman 2.1.4 pending.pck database Updating Usenet watermarks Updating index files for archive [%(archive)s] Updating mailing list: %(listname)s Updating the held requests database. Upgrading from version %(hexlversion)s to %(hextversion)s Usage: 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. Use this option to remove each message attachment that
matches one of these content types. Each line should contain a
string naming a MIME <tt>type/subtype</tt>,
e.g. <tt>image/gif</tt>. Leave off the subtype to remove all
parts with a matching major content type, e.g. <tt>image</tt>.
<p>Blank lines are ignored.
<p>See also <a href="?VARHELP=contentfilter/pass_mime_types"
>pass_mime_types</a> for a content type whitelist. Use this option to remove each message attachment that does
not have a matching content type. Requirements and formats are
exactly like <a href="?VARHELP=contentfilter/filter_mime_types"
>filter_mime_types</a>.
<p><b>Note:</b> if you add entries to this list but don't add
<tt>multipart</tt> to this list, any messages with attachments
will be rejected by the pass filter. User `%(addr)s' removed from list: %(listname)s. User address/name User specific options page Using Mailman version: Value View or edit the list configuration information. View this page in Visit Subscriber List Visit Subscriber list Visit the list's admin page Visit the list's info page WARNING: Ignoring duplicate pending ID: %(id)s. WARNING: could not acquire lock for list: %(listname)s WARNING: directory does not exist: %(d)s Warning! You may encounter permission problems. Warning: Warning: couldn't remove %(src)s -- %(rest)s We're sorry, but you have already been unsubscribed
from this mailing list. To re-subscribe, please visit the
<a href="%(listinfourl)s">list information page</a>. Wed Weekly Welcome email text file Welcome to the "%(realname)s" mailing list%(digmode)s Welcome! What steps are required for subscription?<br> 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". 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>
When a message is posted to the list, a series of
moderation steps are taken to decide whether 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=
"https://docs.python.org/2/library/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. When a new digest volume is started, the volume number is
incremented and the issue number is reset to 1. When a new member is subscribed to this list, their initial
set of options is taken from this variable's setting. When a post from a non-member is received, the message's
sender is matched against the list of explicitly
<a href="?VARHELP=privacy/sender/accept_these_nonmembers"
>accepted</a>,
<a href="?VARHELP=privacy/sender/hold_these_nonmembers">held</a>,
<a href="?VARHELP=privacy/sender/reject_these_nonmembers"
>rejected</a> (bounced), and
<a href="?VARHELP=privacy/sender/discard_these_nonmembers"
>discarded</a> addresses. If no match is found, then this action
is taken. 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. When receiving digests, which format is default? When set, the list of subscribers is protected by member or
admin password authentication. 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. When you are done making changes... When you scrub attachments, they are stored in the archive
area and links are made in the message so that the member can
access them via a web browser. If you want the attachments to
totally disappear, you can use content filtering options. When you tell Mailman to perform a catchup on the newsgroup,
this means that you want to start gating messages to the mailing
list with the next new message found. All earlier messages on
the newsgroup will be ignored. This is as if you were reading
the newsgroup yourself, and you marked all current messages as
<em>read</em>. By catching up, your mailing list members will
not see any of the earlier messages. Where are replies to list messages directed?
<tt>Poster</tt> is <em>strongly</em> recommended for most mailing
lists. Which delivery mode is the default for new users? 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. Who can view subscription list? Yearly Yes Yes, w/discard Yes, w/forward You are already a member of this mailing list! You are already subscribed! You are already subscribed. You are already using that email address You are forbidden from posting messages to this list. You are not a member of the %(listname)s mailing list You are not allowed to retrieve the list membership. You are not authorized to create new mailing lists You are not authorized to delete this mailing list You are not currently a member. Have you already unsubscribed or changed
your email address? You can access your personal options via the following url: You can create a new mailing list by entering the
relevant information into the form below. The name of the mailing list
will be used as the primary address for posting messages to the list, so
it should be lowercased. You will not be able to change this once the
list is created.
<p>You also need to enter the email address of the initial list owner.
Once the list is created, the list owner will be given notification, along
with the initial list password. The list owner will then be able to
modify the password and add or remove additional list owners.
<p>If you want Mailman to automatically generate the initial list admin
password, click on `Yes' in the autogenerate field below, and leave the
initial list password fields empty.
<p>You must have the proper authorization to create new mailing lists.
Each site should have a <em>list creator's</em> password, which you can
enter in the field at the bottom. Note that the site administrator's
password can also be used for authentication.
You cannot add a Reply-To: to an explicit
address if that address is blank. Resetting these values. You cannot enable gatewaying unless both the
<a href="?VARHELP=gateway/nntp_host">news server field</a> and
the <a href="?VARHELP=gateway/linked_newsgroup">linked
newsgroup</a> fields are filled in. You did not give the correct old password, so your password has not been
changed. Use the no argument version of the password command to retrieve your
current password, then try again. You did not give the correct password You forgot to enter the list name You forgot to specify the list owner You gave the wrong password You have been successfully subscribed to the %(realname)s mailing list. You have been successfully unsubscribed from the
mailing list %(fqdn_listname)s. If you were receiving digest
deliveries you may get one more digest. If you have any questions
about your unsubscription, please contact the list owners at
%(owneraddr)s. You have been unsubscribed from the %(realname)s mailing list You have canceled the re-enabling of your membership. If
we continue to receive bounces from your address, it could be deleted from
this mailing list. You have canceled your change of address request. You have canceled your subscription request. You have canceled your unsubscription request. You have digest members, but digests are turned
off. Those people will not receive mail.
Affected member(s) %(dm)r. You have regular list members but non-digestified mail is
turned off. They will receive non-digestified mail until you
fix this problem. Affected member(s) %(rm)r. You have successfully created the mailing list
<b>%(listname)s</b> and notification has been sent to the list owner
<b>%(owner)s</b>. You can now: You have successfully deleted the mailing list
<b>%(listname)s</b>. You have successfully set your options. You have turned off delivery of both digest and
non-digest messages. This is an incompatible state of
affairs. You must turn on either digest delivery or
non-digest delivery or your mailing list will basically be
unusable. You invited %(address)s to your list, but in a
deliberate malicious attempt, they tried to confirm the invitation to a
different list. We just thought you'd like to know. No further action by you
is required. You may get one last digest. You may not subscribe a list to itself! You must confirm your unsubscription request by turning
on the checkbox below the <em>Unsubscribe</em> button. You
have not been unsubscribed! You must fix the preceding invalid addresses first. You must specify a list name. Here is the %(link)s You must specify a list. You must supply a valid email address. You were not invited to this mailing list. The invitation has been discarded,
and both list administrators have been alerted. You will be sent email requesting confirmation, to
prevent others from gratuitously subscribing you. You will be sent email requesting confirmation, to
prevent others from gratuitously subscribing you. Once
confirmation is received, your request will be held for approval
by the list moderator. You will be notified of the moderator's
decision by email. You're being a sneaky list owner! Your <code>%(property)s</code> string appeared to
have some correctable problems in its new value.
The fixed value will be used instead. Please
double check that this is what you intended.
Your confirmation is required in order to cancel the
posting of your message to the mailing list <em>%(listname)s</em>:
<ul><li><b>Sender:</b> %(sender)s
<li><b>Subject:</b> %(subject)s
<li><b>Reason:</b> %(reason)s
</ul>
Hit the <em>Cancel posting</em> button to discard the posting.
<p>Or hit the <em>Continue awaiting approval</em> button to continue to
allow the list moderator to approve or reject the message. Your confirmation is required in order to complete the
change of address request for the mailing list <em>%(listname)s</em>. You
are currently subscribed with
<ul><li><b>Real name:</b> %(fullname)s
<li><b>Old email address:</b> %(oldaddr)s
</ul>
and you have requested to %(globallys)s change your email address to
<ul><li><b>New email address:</b> %(newaddr)s
</ul>
Hit the <em>Change address</em> button below to complete the confirmation
process.
<p>Or hit <em>Cancel and discard</em> to cancel this change of address
request. Your confirmation is required in order to complete the
subscription request to the mailing list <em>%(listname)s</em>. Your
subscription settings are shown below; make any necessary changes and hit
<em>Subscribe</em> to complete the confirmation process. Once you've
confirmed your subscription request, you will be shown your account
options page which you can use to further customize your membership
options.
<p>Note: your password will be emailed to you once your subscription is
confirmed. You can change it by visiting your personal options page.
<p>Or hit <em>Cancel my subscription request</em> if you no longer want to
subscribe to this list. Your confirmation is required in order to complete the
unsubscription request from the mailing list <em>%(listname)s</em>. You
are currently subscribed with
<ul><li><b>Real name:</b> %(fullname)s
<li><b>Email address:</b> %(addr)s
</ul>
Hit the <em>Unsubscribe</em> button below to complete the confirmation
process.
<p>Or hit <em>Cancel and discard</em> to cancel this unsubscription
request. Your confirmation is required in order to continue with
the subscription request to the mailing list <em>%(listname)s</em>.
Your subscription settings are shown below; make any necessary changes
and hit <em>Subscribe to list ...</em> to complete the confirmation
process. Once you've confirmed your subscription request, the
moderator must approve or reject your membership request. You will
receive notice of their decision.
<p>Note: your password will be emailed to you once your subscription
is confirmed. You can change it by visiting your personal options
page.
<p>Or, if you've changed your mind and do not want to subscribe to
this mailing list, you can hit <em>Cancel my subscription
request</em>. Your confirmation is required to join the %(listname)s mailing list Your confirmation is required to leave the %(listname)s mailing list Your current option settings: Your decision Your email address: Your membership in the %(realname)s mailing list is
currently disabled due to excessive bounces. Your confirmation is
required in order to re-enable delivery to your address. We have the
following information on file:
<ul><li><b>Member address:</b> %(member)s
<li><b>Member name:</b> %(username)s
<li><b>Last bounce received on:</b> %(date)s
<li><b>Approximate number of days before you are permanently removed
from this list:</b> %(daysleft)s
</ul>
Hit the <em>Re-enable membership</em> button to resume receiving postings
from the mailing list. Or hit the <em>Cancel</em> button to defer
re-enabling your membership.
Your message had a suspicious header. Your message to %(listname)s awaits moderator approval Your message was deemed inappropriate by the moderator. Your message was rejected Your message was too big; please trim it to less than
%(kb)d KB in size. Your new %(listname)s list password Your new mailing list: %(listname)s Your password is: %(password)s Your passwords did not match. Your real name: Your request has been forwarded to the list moderator for approval. Your subscription is not allowed because
the email address you gave is insecure. Your subscription is not allowed because the email address you gave is
insecure. Your subscription request has been forwarded to the list administrator
at %(listowner)s for review. Your subscription request has been received, and will soon be acted upon.
Depending on the configuration of this mailing list, your subscription request
may have to be first confirmed by you via email, or approved by the list
moderator. If confirmation is required, you will soon get a confirmation
email which contains further instructions. Your subscription request was deferred because %(x)s. Your request has been
forwarded to the list moderator. You will receive email informing you of the
moderator's decision when they get to your request. Your unsubscription request has been forwarded to the list administrator for
approval. Your unsubscription request has been received and
forwarded on to the list moderators for approval. You will
receive notification once the list moderators have made their
decision. Your urgent message to the %(realname)s mailing list was not authorized for
delivery. The original message as received by Mailman is attached.
[Message discarded by content filter] [No bounce details are available] [No explanation given] [No reason given] [no description available] a single held message. ack administrative list overview all held messages. all of %(esender)s's held messages. also article db files must be %(octperms)s: %(path)s article file %(filename)s is missing! attribute "%(k)s" changed attribute "%(k)s" ignored author by the admin by the list administrator by you by yourself check a translated template against the original one
search also <MM-*> tags if html is not zero check a translation comparing with the original string check for differences between checked in and checked out checking cgi-bin permissions checking mode for %(prefix)s checking ownership of %(dbfile)s checking permissions on %(file)s checking permissions on %(pwfile)s checking permissions on list data checking perms on %(private)s checking set-gid for %(wrapper)s couldn't remove old file %(pyc)s -- %(rest)s date day days delivery disabled by user delivery enabled delivery off delivery on digest digest footer digest header directory must be at least 02775: %(d)s directory permissions must be %(octperms)s: %(path)s disabled done due to bounces due to excessive bounces email address and figuring article archives
file permissions must be at least 660: %(path)s fixing all the perms on your old html archives to work with b6
If your archives are big, this could take a minute or two... for unknown reasons found in: from %(start)s to %(end)s general list overview getting rid of old source files globally hide language legal values are: list creator list info list of available mailing lists. listname is required matching mailing lists found: mbox file must be at least 0660: member address<br>member name members message is unparsable: %(filebase)s mod n/a no date no lists == nothing to do, exiting no subject nodupes nomail nomail<br>[reason] not available not metoo notmetoo off on options parse a .po file extracting msgids and msgstrs password plain private private archives processing mailing list: public public archives removing %(src)s removing directory %(src)s and everything underneath return to the %(categoryname)s options page. right right scan a string from the original file scan a translated string scan the po file comparing msgids with msgstrs site size not available source perms must be %(octperms)s: %(path)s stale lock file stop is synonymous with the end command.
subject subscriptions to %(name)s require administrator approval subscriptions to %(realname)s require moderator approval the list admin overview page the list administrator the mailing list overview page thread unknown sender unsub unsubscriptions require moderator approval updating old qfiles view all messages from %(esender)s Project-Id-Version: mailman
POT-Creation-Date: Fri Jun 26 17:05:40 2020
PO-Revision-Date: 2005-05-14 12:07+0800
Last-Translator: Dai Xiaoguang <leona@cs.hit.edu.cn>
Language-Team: <mailman-cn@mail.cs.hit.edu.cn>
Language:
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Generated-By: pygettext.py 1.4
注意 注意 注意 注意 注意
您正在升级一项已存在的Mailman安装, 但我无法得知
您之前运行的是什么版本.
如果您从 Mailman 1.0b9 或更早版本升级, 您需要
手动升级您的邮件列表. 对于每一张邮件列表,您需要
复制文件 templates/options.html lists/<listname>/options.html.
不管怎样, 如果您经由 Web 接口编辑了这个文件, 您必须
将您的修改加入这个文件, 否则您将失去您的
修改.
注意 注意 注意 注意 注意
confirm <confirmation-string>
确认某个动作。confirmation-string会在在此之前邮寄给你的相应的确认通知中提供。
echo [args]
简单地回复一个应答。args被原封不动的返回。
end
停止处理命令。如果您的邮件程序自动的在您的邮件后面添加签名文件，就可以使
用此命令。
help
打印此帮助信息。
info
获取此邮件列表的相关信息。
lists
查看这个GNU Mailman邮件列表服务器上所有公共邮件列表的清单。
password [<oldpassword> <newpassword>] [address=<address>]
取回或者更改您的密码. 当您不使用参数时，此命令返回您的当前密码。
当您提供 <oldpassword> 和 <newpassword>时，就能修改您的密码。
如果您当前发信的地址不是您的成员地址，请指定您的成员地址：
"address=<address>" (注意在email地址前后不用括号和引号。)
此时回信将会发送到您订阅时注册的地址。
set ...
重设或者查看您的成员设置.
使用 "set help" (不用引号) 可以取得您可以修改的更多的设置。
使用 "set show" (不用引号) 可以查看您当前的设置。
set help
显示详细的帮助信息.
set show [address=<address>]
查看您的当前设置. 如果您现在加入使用的不是您的成员地址，
请指定您的成员地址: "address=<address>"
(注意在email地址前后不用括号和引号。)
set authenticate <password> [address=<address>]
在进行任何设置前，您都得先使用这条命令，输入您的成员密码。
如果您现在加入使用的不是您的成员地址，请指定您的成员地址:
"address=<address>"(注意在email地址前后不用括号和引号。)
set ack on
set ack off
当"ack" 操作开启后，在您向列表发邮件后，您将收到一个确认信息。
set digest plain
set digest mime
set digest off
当操作"digest"关闭后，, 如果有人发信，您将能立即收到.
使用命令 "set digest plain" 后，信件将已纯文本(plain
text)(i.e. RFC 1153 digest)形式的摘要发给您。
使用命令 "set digest mime" 后，信件将以MIME(多用途的网际邮件
扩充协议)形式的摘要发给您。
set delivery on
set delivery off
能开启或者关闭接受信件. 这并不阻止您发信，只是告诉Mailman不要再收信了
当您度假或者外出时，这个命令可能很有用，但是，当您回来后，记住一定要再使用
"set delivery on"开启服务.
set myposts on
set myposts off
使用 "set myposts off" 后，您将不会再收到您发出去的信件的复制件
但是当您设置了接收摘要时，这个命令将不起作用.
set hide on
set hide off
使用 "set hide on" 后，当有人索取成员列表时，您能隐藏您的邮件地址
set duplicates on
set duplicates off
使用 "set duplicates off"后，当您的地址在邮件的 To:(收件人)或者 Cc:(抄送) 区域中时
您将不会收到邮件的复制件。这样能大量的减少您的信件量
set reminders on
set reminders off
使用 "set reminders off" 后，邮件列表的每月密码提示就会停止工作
subscribe [password] [digest|nodigest] [address=<address>]
订阅此邮件列表. 如果您要取消订阅或者更改您的设置，您必须提供密码，
但如果您忽略密码，我们将为您生成一个。我们将会周期性的提醒您您的密码
下一个参数是: `nodigest' or `digest' (不用引号!).
如果您想订阅的地址不是您现在发信的地址您可以指定
`address=<address>' (注意在email地址前后不用括号和引号。)
unsubscribe [password] [address=<address>]
从邮件列表中取消订阅. 使用此命令时，您必须提供一个正确的密码
如果不使用密码，必须提供一个正确的邮件地址。
如果您想取消的邮件地址不是您当前发信的地址，请指定新的地址
`address=<address>' (注意在email地址前后不用括号和引号。)
who password
查看所有在邮件列表中的人. 此命令仅限于列表管理员和仲裁员使用，您必须提供
管理员和仲裁员密码才能使用此命令
%(listname)s 既有公有邮箱存档又有私有邮箱存档. 因为这个列表
正在使用私有存档, 我将安装私有邮箱存档
-- %(o_pri_mbox_file)s -- 为活动存档, 并将
%(o_pub_mbox_file)s
更名为
%(o_pub_mbox_file)s.preb6
如果您想将它们合并,您可以使用'arch'
脚本.
- 完成。
- 忽略:
- 未处理：
检查给定的Mailman翻译, 确定翻译中涉及到的变量与
和原始模板与目录中的相同.
用法:
cd $MAILMAN_DIR
%(program)s [-q] <lang>
这里 <lang> 是您的国家代码 (例如 'it' 是意大利) , -q 用来
请求简明的摘要.
错误:
某些列表的锁无法获得. 这意味着
当您升级时, Mailman仍然运行, 或者有无效的锁定在
%(lockdir)s 目录内.
您必须将Mailman 停止并移除所有失效的锁,
然后手动重新运行 "make update" . 参见 INSTALL 和 UPGRADE 文件来获得更多信息.
阻塞的信件：
为了删除您的该邮件列表，需要删除/etc/aliases 中的以下列。
同时需要运行程序newaliases
## %(listname)s 邮件列表
用法:
您使用大小写相关的地址订阅了此列表
<em>%(cpuser)s</em>. 您已经成功地取消了发送标题头部为 <em>%(subject)s</em>
的信息到 %(listname)s 这个邮件列表. 在邮件列表 %(listname)s 中,您已经成功地将邮件地址从
<b>%(oldaddr)s</b> 修改为 <b>%(newaddr)s</b>.
现在您可以 <a href="%(optionsurl)s">进入您的成员登陆页面了</a>. 您已经成功地确认对邮件列表 %(listname)s 发出订阅请求的地址
"%(addr)s" . 一个单独的验证信息将发送到您的电子邮箱里,
同时还有您的密码和其他一些有用的信息和链接.
<p>现在,您就可以
<a href="%(optionsurl)s">进入您的成员登陆页面</a>. 您已经成功地确认了%(listname)s 你的订阅请求,
但是在您能收到订阅之前,还需要列表主持者的最终批准.
您的请求已经发给列表主持者了, 您将收到列表主持者的决定的通知. 您已经成功的在邮件列表 %(listname)s 中重新设置您的成员资格有效.
现在您可以 <a href="%(optionsurl)s">访问您的成员选项页</a>.
您已经成功地取消了对邮件列表 %(listname)s 的订阅.
现在您就可以 <a href="%(listinfourl)s">访问列表的主要信息页面</a>. 这个邮件列表还没有邀请您.
邀请函已经被丢弃, 而且列表管理员已经收到了警告. 描述： %(description)s 请求发送到地址: %(requestaddr)s 确认 %(onoff)s 未找到的地址： 为 %(path)s 检查gid和许可权 检查 %(path)s的许可权 检查 %(path)s 的set-gid许可权 添加的复制地址： 复制地址已经是列表成员： MIME摘要 取消摘要 纯文本摘要 复制 %(onoff)s 隐藏 %(onoff)s 我的信件 %(onoff)s 新列表属主： 源地址被移除： 提示函 %(onoff)s 扫描列表属主： 不明的文件,移动
%(o_pri_mbox_file)s
至
%(newname)s 未知文件,移动
%(o_pub_mbox_file)s
至
%(newname)s %(file)s: 完好 线索 %(size)i 字节 ( %(total)d 的 %(count)d (摘要模式) (但是我们将地址模糊化，这样它们将不会轻易被垃圾信息收集器识别)。 (需要授权) (请求确认)<br> <br> <p>输入你的 如果您将该字段设为空白，您将被提示输入您的邮件地址。 您最后的退信日期为 %(date)s 要访问没有发布的列表的通用信息,
打开类似的 URL , 但是在列表名后附加上 '/' 和 %(adj)s .
<p>如果你是列表管理员,您可以访问 和口令以便访问订阅者列表：<p><center> 在 字节 来自 %(remote)s 已经是成员了 订阅者： 以找到您的列表管理接口.
<p>如果您在使用列表时碰到的麻烦,请与我们联系 ## %(listname)s 邮件列表 %%% %(address)s 不是邮件列表 %(listname)s 中的地址 %(address)s 被邀请加入另一个邮件列表, 但却恶意地
将其对邀请的回复发送给您，我们估计您乐意了解这个情况但您不必采取任何行动。 成员总数 %(allcnt)s 成员总数 %(allcnt)s, 显示了 %(membercnt)s %(day)i 日 %(month)s 月 %(year)i 年 %(days)d %(units)s %(dbdir)s的"其它"许可权必须为000 %(dbfile)s 为 %(owner)s 所有(必须为 %(user)s 所有 %(dbfile)s 的权限必须是 0664 （获得 %(octmode)s） %(file)s 的权限必须是 0664 （获得 %(octmode)s） %(host)s邮件列表成员身份提示 %(hostname)s 邮件列表 %(hostname)s 的邮件列表 - 管理链接 %(i)3d. 列表名： %(realname)s %(listfullname)s 邮件列表提示函 由 %(owner_link)s 运行的 %(listinfo_link)s 邮件列表 没有找到叫 %(filename)s的 %(listname)s %(msg)s %(listname)s 的邮件列表探测消息 %(listname)s 中来自 %(sender)s 的信件需要审批 查找到 %(messages)d 封信件 %(month)s 月 %(year)i 年 %(name)s 运行 %(runnername)s qrunner %(newaddr)s 已经是列表的成员. %(year)i 的第 %(ord)s 季度 %(path)s所属组错误(当前组: %(groupname)s, 期望值为 %(MAILMAN_GROUP)s) %(path)s必须是set-gid的 %(private)s不能是其他人可读(other-readable) %(pwfile)s 的许可权必须是0640(现在是 %(octmode)s) %(realname)s -- 为 %(template_info)s 编辑html %(realname)s -- HTML 页面编辑 %(realname)s 管理员 (%(label)s) %(realname)s 管理数据库 %(realname)s 管理数据库结果 %(realname)s 摘要, 卷 %(volume)d, 发布 %(issue)d %(realname)s 邮件列表配置帮助
<br><em>%(varname)s</em> 选项 %(realname)s 的管理接口 %(realname)s 列表： 用户 %(safeuser)s 的成员选项信息 %(realname)s 列表： 成员选项登录页 %(realname)s 邮件列表管理员n<br>%(label)s 部分 %(realname)s发送确认 %(realname)s身份验证失败 %(realname)s 订阅通知 %(realname)s 退订通知 %(safetemplatename)s: 无效的模版 %(wday)s %(mon)s %(day)2i %(hh)02i:%(mm)02i:%(ss)02i %(tzname)s %(year)04i %(wrapper)s必须是set-gid的 %s 既有公有邮箱存档又有私有邮箱存档. 因为这个列表
正在使用公有存档, 我将安装公有邮箱存档
存档文件 (%s) 为活动者, 并将
%s
更名为
%s.preb6
如果您想将它们合并,您可以使用'arch'
脚本.
<空行> (<i>%(which)s只对列表成员有效</i>) (<i>%(which)s只对列表管理员有效</i>) (邮件过滤器) 检查邮件和那些看起来像是管理请求但被中途拦截的邮件吗？ (注意 - 您正在订阅一个邮件列表，所以 %(type)s 通知将被发送到管理员以告知您用来订阅的地址 %(addr)s。)<p> (列表属主) (固定) (帮助) (已加锁) (无更改) (无主题) (已解锁) - %(o_tmpl)s 不存在, 不做修改 - 结果： - 看来可能有<=b4列表模板 - %(o_tmpl)s 和 %(n_tmpl)s 均存在, 将不做任何修改 - 移动 %(o_tmpl)s 至 %(n_tmpl)s - 没有需要升级的 - 正在升级旧的私有邮箱文件 - 正在升级旧有公有邮箱文件 - 新闻组水印升级,gate_watermarks 移除 -------------- 下一部分 --------------
--all需要--run ...在这个之后 在这个之前 ...指定一个上传的文件: ；列表管理员禁止了该选项 ；您禁止了该选项 ；由于退信过多，它被禁止了。最后一封退信在 %(date)s 收到。 ；由于不明原因，它被禁止了 <----- start object %(cnt)s -----> <P>目前没有归档文件 </P> <b><i>任一的</i></b> <b>取消</b>并返回到列表管理页 <b>确认</b> -- 用户收到对他们邮件的确认信了吗? <b>摘要</b> -- 用户是否要以摘要的形式接受信件?
(否则, 单个的信件) <b>隐藏</b> -- 用户的地址在订阅者列表中是隐藏的吗? <b>语言</b> -- 用户偏好的语言 <b>mod</b> -- 用户的个人节制标志. 如果设置该值,
用户发出的信件将被缓存, 否则将被发送。 <b>无副本</b> -- 用户是否想避免收到同一信件的副本? <b>没有邮件</b> -- 向用户的投递失效了么? 如果是这样,
将给出一个简短的信息描述投递失效的原因:
<ul><li><b>U</b> -- 用户在个人选项页面中禁止了投递.
<li><b>A</b> -- 列表管理员禁止了投递.
<li><b>B</b> -- 由于该用户地址过多的退信,系统禁止了投递.
<li><b>?</b> -- 投递失效的原因未知.
在Mailman的早些版本中这是对所有被禁止成员投递信息时出现的情况.
</ul> <b>除了我</b> -- 用户是否想避免收到自己信件的副本? <b>纯文本</b> -- 如果接收摘要,是纯文本形式的摘要么?
(否则, 使用多用途的网际邮件扩充协议MIME) <b>real_name</b>属性没有被修改!它必须与邮件列表有大小写上的不同 <b>取消订阅</b> -- 点击此处退出成员列表. <br>(<b>%(varname)s</b>的细节) <br>(编辑 <b>%(varname)s</b>) <br><em>...指定一个上传的文件</em><br> <br><em><strong>注释:</strong>
设置此值会在当前环境立刻生效，但此值不会被保存。</em> <br>返回到 <em>(%(num_concealed)d个私有成员没有显示)</em> <em>(1个私有成员没有显示)</em> <em><strong>警告:</strong> 更改此选项
可能引起其他窗口的不同步。确保重新载入邮件列表中所有使用该选项的页。
您也可以
<em>输入以下文本, 或者...</em><br> <em>ID号为 #%(id)d 的消息损坏了. <em>ID号为 #%(id)d 的消息丢失了. <em>没有已定义的主题</em> <em>不可用</em> <em>这个发送者现在是这个列表的成员了</em> <em>是的，我确实想要退订</em> <em>不可用</em> <li>设置每位成员的节制位，包括
目前不可见的用户 <丢失> <p>%(note)s
<p>你可能故意禁止了列表投递，或者被来自你的电子邮件地址的
退信触发而禁止了。无论是哪一种情况，改变以下的 %(link)s 选
项以便重新启动投递。如果您有任何问题，或者需要帮助，请联系
%(mailto)s。 <p>(注意：这是一个掩护列表，用来将其他的邮件列表作为
成员。在其他事务中，这意味着对您的地址，您的确认请求将被发送
到`%(sfx)s'。) <p>(发送问题和评论到 <p>... <b><i>or</i></b>从订阅者列表(参考上文)中选择您的
入口条目。 <p><em>想要查看更多的成员, 点击下面列出来的合适的区间:
</em> <p>下面是 %(hostname)s 上所有公开的列表地址.
点击列表名称以获得关于该列表更多的信息,或者订阅,取消订阅,更改您订阅的偏好设置. <p>下面是 %(hostname)s 上公开的
%(mailmanlink)s 邮件列表。 点击一个列表
名称可以访问此列表的配置页面 <p>目前在 %(hostname)s 上没有公开的 %(mailmanlink)s 邮件列表. <p>目前在 %(hostname)s 上无公开的 %(mailmanlink)s
邮件列表。 <p>我们已经接收到一些来自您的地址的新近的退信。
您当前的<em>退信数</em>已经比最大限制 %(total)s 超过了 %(score)s。
请仔细检查你用来订阅的地址是否正确并且可以正常使用。问题被纠正后，你
的退信数将很快被自动重设。 <tt>Reply-To:</tt> header munging <ul><li><b>暂存</b> -- 这将暂存信件以待列表管理员审核。
<p><li><b>退回</b> -- 这将把信件自动退回发信者，并发送一封退信通知。
退信通知的内容可以由您
<a href="?VARHELP=privacy/sender/member_moderation_notice">配置</a>。
<p><li><b>丢弃</b> -- 这将简单的丢弃此信件，而不会向发信者发送任何的
通知。
</ul> ? A 确认信息已经发送到了 %(newaddr)s . 发送了一则摘要。 需要指定一个列表名 您的密码提示已经发送到您的电子信箱了 一个唯一标识该列表的简洁的短语。 接受 接受 应答成员的邮件 当一个没有被显式指定处理方法的非成员向列表发信时应执行的动作。 对所有这些滞留的信息的动作: 当消息内容与内容过滤规则相符时过滤. 当一个被节制的成员发信到列表时应该执行的动作。 动作 把<b>%(esender)s</b> 加到这些发送过滤器中: 向字典中加入一个准确的翻译。 增加新选项 加入 : %(s)s 额外的成员任务 其他设定 另外，发送这条消息给: 地址/姓名/时间 地址： 地址不匹配! 此清单中的地址被禁止订阅此邮件列表，而无须审核。每行添加一
个地址；以 ^ 开头的行是一个正则表达式匹配。 地址不能为空 管理员地址： 对邮件列表的管理请求 管理员 管理员密码不匹配 邮件检查会检查邮件看它是否真的是一个管理请求(像订阅，取消订阅，等)，
并把它加入到管理请求的队列中，通报管理员这一在进行之中的新的请求。 在有人询问此主机上运行着哪些邮件列表时，显示此列表吗？ 经过内容过滤后，该信件为空 确认口令 明确指明此列表的to或者cc地址的别名(正则表达式)。 All 运行上面的所有qrunners 已经是成员了 已经是成员：%(member)s 同时删除邮件归档？ `require_explicit_destination'选项打开时的
其他可接受地址。可以在每行指定一个正则表达式，用来匹配信件中的
所有目的地址。正则表达式匹配是用Python的re.match()函数实现的，
这意味着匹配是从字符串的开头开始进行的。
<p>为了与Mailman 1.1保持向后兼容，如果正则表达式中不包括字符'@'，
那么它将仅与收件地址的本地部分进行匹配。如果匹配失败，或者此
正则表达式中含有字符'@'的话，它将会与整个收件地址进行匹配。
<p>不赞成与本地部分进行匹配；在未来的版本中，这里指定的正则表达式
模式将总是与完整的收件地址进行匹配。 始终 一个HTML附件被移除...
URL: %(url)s
有人尝试用您的地址订阅邮件列表 %(listaddr)s。您已经订阅了此列表。
注意，列表成员不是公开的，所以可能是有些不怀好意的人在试探列表的成员地址。
我们不会让他们得逞，因为这样他们将侵犯您的隐私。
如果您忘记了您已经订阅了此列表，所以又提交了此订阅请求的话，您可以忽略此信息。
如果您认为这是对判断您是否是此列表成员的一次秘密试探，并且担心这将暴露您的隐私，
请不要拘束，发送一封邮件到 %(listowner)s 告诉列表管理员。
关于列表的介绍性的描述 - 几个段落。
它将作为html片段包含在列表信息页面的顶部
回车将结束一个段落 - 更多信息看细节。 任何人 批准 四月 四月 存档消息吗? 存档选项 根据需要 八月 八月 认证失败 认证失败 自动丢弃通知 自动生成列表初始密码吗? 自动回复器 自动回复器特征.<p>
在下面的文字域内将执行如下的键/值替换:
<p><ul>
<li><b>listname</b> - <em>得到邮件列表的名字</em>
<li><b>listurl</b> - <em>得到列表的信息页URL</em>
<li><b>requestemail</b> - <em>得到列表的请求地址</em>
<li><b>owneremail</b> - <em>得到列表的主人地址</em>
</ul>
<p>在每个文字域内,您可以直接向文本框中键入文本也可以指定一个本地文件, 上传后
作为相应的文本. 对您发送至 "%(realname)s" 邮件列表信件的自动答复 向列表所有者发送的自动回复文本. 向请求邮件发送的自动回复文本. 向邮件列表发言者发送的自动回复文本. 等待列表主持者的批准 B 错误的 --digest 选项： %(kind)s 错误的 --nomail 选项： %(why)s 被忽略的错误的MIME类型：%(spectype)s 错误的URL细则 错误的核准口令。保存的信息仍然被保存着。 -a/--admin-notify选项的错误参数: %(arg)s -w/--welcome-msg选项的错误参数: %(arg)s 错误的参数: %(arg)s 参数错误: %(pargs)s 错误的参数： %(strargs)s 错误的选择: %(yesno)s 错误命令: %(command)s 错误的验证字符串 指定了错误的分类: %(arg)s 选项 %(k)s 的email地址错误： %(v)s 错误的邮件地址选项%(property)s: %(error)s 提供了错误的邮件地址 错误的节制标记变量 错误的拥有者邮件地址: %(s)s 队列目录错误： %(qdir)s 错误的正则表达式 错误的设置命令: %(subcmd)s 错误的状态号： %(arg)s 以下变量被赋予非法值:<a href="?VARHELP=bounce/%(property)s"
>%(property)s</a>: %(val)s 错误/无效的邮件地址 错误/不合法的邮件地址： %(member)s 错误/不合法的邮件地址: 空行 错误形式选项入口:
%(record)s 禁止 <b>%(esender)s</b> 订阅这个列表 黑名单 打包投递摘要的特性 下面, 在您的邀请或者订阅通知的头部中添加附加文字.
结尾至少包含一个空白行... 不允许收信人的地址空白或者不清晰
请尝试在To:和Cc:字段写明地址后重新发送 退信行为通告 退信检测灵敏度 退信处理 通过点击<em>提示</em>按钮，您的口令将被邮寄给您。 通过点击<em>退订</em>按钮，一封确认函将被投递给您。
您需要点击确认函中的一个链接来完成整个退订过程(您也可以通过邮件来确认，
请参考确认函中的具体信息)。 默认情况下，列表新成员的信件是否被暂存？ 把这个值设置为<em>,否则设为</em>, 你就禁止了这个列表所有的
自动退信处, 然而为了使列表管理员免于被退信消息淹没, 它们
仍然会被忽略 把这个值设置成<em>否</em>, 你就关闭了当一个用户由于
过多的退信而被退订时,通常发向列表所有者的通知消息的服务. 但系统总是尝
试通知将被禁止的用户. 把这个值设置成<em>否</em>, 你就关闭了一个通知服务，该服务用于在某一个用户
因为过多的退信而将被暂时禁止时通知列表属主. 但系统总是尝试通知将被禁止的用户. CGI脚本错误 列表成员可以选择接收打包成摘要的列表通讯吗？ 订阅者可否选择即时收信而不是收取摘要？ 不能有空的html页面. 取消 取消并且删除 取消对滞留信件的发送 取消我的订阅请求 取消发送 无法打开mbox文件 %(mbox)s: %(msg)s 无法读出地址文件: %(filename)s: %(msg)s 无法从标准输入既读取摘要用户又读取正常用户 不能恢复消息 %(filebase)s, 忽略:
%(e)s 不能取消非成员的订阅: (西班牙)加泰罗尼亚语 信件收件人的最大数目。 修改我的地址和姓名 修改我的口令 修改列表的口令。
在Mailman 2.1以前，列表的口令一般以加密格式保存。一些Python安装并没有附带加
密模块，这样的话将会退而使用md5。如果这些Python安装突然添加了加密模块的话，
所有的列表口令都将被破坏。
在Mailman 2.1中，所有的列表和站点口令都是以SHA1 hexdigest形式存储的。这破坏
了所有Mailman 2.1之前建立的列表的口令，同时，由于这些口令并不是以明文形式存
放的，它们也将不能被取回或更新。
此脚本用来为列表生成新的口令，并且可以选择将新口令发送给列表的所有管理员。
用法： change_pw [options]
选项:
--all / -a
修改所有列表的口令。
--domain=domain
-d domain
在虚拟域'domain'中修改所有列表的口令。可以指定多个-d选项。
--listname=listname
-l listname
为指定的列表修改口令。可以指定多个-l选项。
--password=newpassword
-p newpassword
使用指定的明文口令'newpassword'作为需要修改口令的列表(由-a,-d和-l指定
)的新口令。如果不给出此选项的话，列表将被指派一个随即产生的新口令。
--quiet / -q
不通知列表管理员列表的新口令。您需要有其他的方法来让列表管理员知道新口令
--help / -h
打印此帮助信息然后退出。
更改地址 更改列表拥有者的密码 对地址请求的修改已经确认 为列表 %(listname)s改变密码 检查列表配置数据库的完整性。
下面的所有文件都将被检查：
config.pck
config.pck.last
config.db
config.db.last
config.safety
这些文件中的任意一个都可以缺失。config.pck和config.pck.last是2.1a3及之后版本
配置文件的备份。config.db和config.db.last是所有之前版本使用的配置文件，它们是
Python的配置(marshals)。config.safety是当2.1a3及之后版本的主配置文件config.pck
读取时使用的备份文件(pickle)。
用法: %(PROGRAM)s [options] [listname [listname ...]]
选项：
--all / -a
检查所有列表的数据库。否则只有在命令行上指定的列表才会被检查。
--verbose / -v
冗余输出。每一个被检查的文件的状态都将被打印。否则只有损坏的文件的状态
才会被打印。
--help / -h
打印此帮助信息然后退出。
查看阻塞的管理请求，在必要时向列表主人发送邮件。
用法： %(PROGRAM)s [options]
选项：
-h/--help
打印此帮助信息然后退出。
检查Mailman安装的文件许可权。
用法： %(PROGRAM)s [-f] [-v] [-h]
不指定参数时，仅检查和报告有虚假许可权或者所属组不正确的文件。
指定-f选项(以root身份运行)时，修复所有被发现的许可权问题。
指定-v选项将导致冗余输出。
中文（中国） 中文（台湾） 清除.mbox存档文件。
存档器搜寻用来在mbox存档文件中分隔信件(messages)的Unix-From行。为兼容起见，
它明确地寻找以"From "开头的行 -- 即，大写字母F，小写字母r，o，m，空格，忽略此行中
其他的所有字符。
一般来说，信件正文中以"From "开头的行都应该在行首使用字符'>'来转义。但是
也有可能正文中的那些行并没有被转义。此脚本试图通过对Unix-From行做严格的测试
以解决这些问题，任何以"From "开头但是没有通过此严格测试的行都将被用一个'>'
字符转义。
用法： cleanarch [options] < inputfile > outputfile
选项：
-s n
--status=n
每处理完n行打印一个#字符
-q / --quiet
不向标准错误打印已修改行的信息
-n / --dry-run
不输出任何信息
-h / --help
打印此帮助信息并退出
清除表格 清除这个用户的 <em>节制</em> 标记 点击这里获取列表 点击这里隐藏图表的图例. 点击这里包含图表的图例. 点击此处以重新加载页面. 点击连接以访问您请求的邮件列表的选项页面 点击信息序号来查看分别的信息，或者您可以 复制一个成员。
复制成员意味着把一个新成员加入到列表，这个新成员有着和源成员完全相同的选
项和口令。注意，此操作完全信任它的执行者 -- 它不对新成员作任何的确认，也不发
送任何欢迎信息，等等。
现有成员的订阅一般来说不会以任何方式发生修改。如果您想要移除老成员的话，可以
使用-r选项。如果您也想修改任何列表管理员的地址，可以使用-a选项。
用法：
clone_member [options] fromoldaddr tonewaddr
其中：
--listname=listname
-l listname
仅检查和修改指定的邮件列表。如果没有指定-l选项，所有的邮件列表都将被
扫描。可以指定多个-l选项。
--remove
-r
复制并删除成员。
--admin
-a
在列表管理员中查找、复制或修改老成员。
--quiet
-q
修改时不产生任何输出。
--nomodify
-n
打印将要做的修改，但不做任何实际的操作。不能同时使用--quiet选项。
--help
-h
打印此帮助信息并退出。
fromoldaddr ('from old address') 是成员的旧地址。tonewaddr
('to new address') 是成员的新地址。
计算索引
隐藏成员地址 配置目录 从描述文本中配置邮件列表。
用法： config_list [options] listname
选项：
--inputfile filename
-i filename
把文件中的每个模块全局变量(module-global variable)赋值给列表对象的
相应属性，然后保存列表。指定的文件由execfile()加载，并且必须是合法
的Python代码。不对应于列表对象任何属性的变量将被忽略(会打印一个警告
信息)。参见-c选项。
一个名为'mlist'的特殊变量在execfile时被设置为全局变量，被绑定到真实
的邮件列表对象上。这样您就可以对列表对象做任意的操作，但是小心！这样
做可能会对您的邮件列表造成严重的(同时也可能是不可挽回的)伤害！
--outputfile filename
-o filename
以此脚本的输入格式输出列表的当前配置参数，而不是配置列表。这样您就可
以方便地获取特定列表的配置并让其他列表使用相同配置。配置参数将被输出
到以filename命名的文件中。如果文件名为'-'，数据将被写到标准输出。
--checkonly
-c
指定此选项后，要修改的列表不会作任何实际的改动。只有与-i选项一起指定
时才起作用。
--verbose
-v
打印每一个被改变的属性的名字。只有与-i选项一起指定时才起作用。
--help
-h
打印此帮助信息并退出
选项-o和-i不能同时使用。
确认 确认 (*) - 需要邮件确认<br>
Require approvel - 需要列表管理员审核订阅请求<br>
Confirm and approve - 即需要邮件确认也需要管理员审核
<p>(*) 当有人请求订阅时，Mailman会给他们发送一封通知，
附带一个唯一的订阅请求号。要想订阅，必须回复此通知。
<br>这用来防止恶意用户不经他人同意而为其订阅列表。 确认管理员密码: 确认并核准 确认修改地址的请求 确认初始密码: 确认主持者密码: 确认订阅请求 确认取消订阅请求 为了防止其他人在未经您允许的情况下替您订阅列表，需要从您的邮件地址发送的确
认函。将会有一些指导信息被投递到您的信箱 %(email)s 中。请注意，除非您确认了
您的订阅请求，否则您的订阅将不会生效。 验证字符串为空. 验证字符串: 确认成功 对内容被过滤信件的通知 内容过滤 继续等待批准 把列表中内插的字符串从 %-strings 转化为 $-strings。
此脚本应该被作为bin/withlist脚本来运行，也就是
% bin/withlist -l -r convert <mylist>
不能读取文件: %(filename)s。 无法以写方式打开文件： 创建列表 创建一个 %(hostname)s 邮件列表 创建另一个列表 创建归档目录 克罗地亚语 捷克语 每日 丹麦语 数据库升级中... 十二月 十二月 列表默认语言。 新加入列表成员的默认选项设定是：<input
type="hidden" name="new_member_options" value="ignore"> 延期 删除 删除此列表 删除邮件列表 由 Mailman<br> %(version)s 投递 描述 描述 描述： %(description)s 详细的管理数据库的指南 摘要 摘要尾部 摘要头部 订阅了摘要的成员: 摘要选项 禁用 丢弃 丢弃所有标记有 <em>推迟</em>的信息 丢弃此日数前被延缓的邮件。0 表示不自动丢弃 丢弃保存的信件。
用法：
discard [options] file ...
选项：
--help / -h
打印此帮助信息然后退出。
--quiet / -q
不打印状态信息。
丢弃列表 %(listname)s 中保存的信件 #%(id)s 放弃 不发送成员自己邮件拷贝 发现降级安装, 从版本 %(hexlversion)s 到版本 %(hextversion)s
这很可能不安全.
正在退出. 演示模式 导出所有Mailman 'database'文件的内容。
用法: %(PROGRAM)s [options] filename
选项：
--marshal/-m
如果文件包含Python marshal，则覆盖任何自动猜测。
--pickle/-p
如果文件包含Python pickle，覆盖任何自动猜测。
--noprint/-n
不试图美化打印对象。这在对象有一些问题，并且您只是想获得一个unpickled
表示时十分有用。以'python -i bin/dumpdb <file>'的形式使用非常有用。这
样的话，the root of the tree will be left in a global called "msg"。
--help/-h
打印此帮助信息然后退出
如果文件名以'.db'结束，将假定文件中包含Python marshal。如果文件名以'.pck'结束，
将假定文件中包含Python pickle。无论是哪种情况，如果您想要覆盖默认的假定 -- 或者
文件名不以这两种后缀结束 -- 使用 -p 或者 -m 选项。
荷兰语 每一个列表成员都有一个<em>节制标志</em>来控制此成员的信件是
直接发送到列表中还是必须先经列表主持者审查。当节制标志被打开时
列表成员的信件就必须先通过审查。作为列表管理员，您可以决定某个人
的信件是否必须通过审查。
<p>新加入成员的初始节制标志将从此选项中获得。关闭此选项将默认直接
接受成员的信件。打开此选项将默认使得成员信件必须首先经过审查。您
总是可以在<a href="%(adminurl)s/members">成员管理页</a>单独地设
置某个成员的节制标志。 每个订阅者都被赋予一个退信值, 这是一个浮点数. 每当Mailman从
某列表用户那里收到一封退信, 该用户的分值就被增加. 严重退信 (致命
错误) 使分数加1, 而轻微退信 (暂时错误) 使分数增加0.5. 每个用户每
天只被计算一封退信, 故而即使在一天内收到10封来自同一用户的退信,
他的分数也仅会增1
这个变量描述了用户退信值的上限, 退信值高于此值的用户自动被禁止,
但并非永久从列表中除名. 每个主题关键字事实上都是一个正则表达式，他们将与邮件的指定部分，
特别是<code>Keywords:</code>头和<code>Subject:</code>头，进行匹配。
注意，邮件正文的前面几行也可以包含<code>Keywords:</code>"头"和
<code>Subject:</code>"头"，也将对他们进行匹配。 编辑HTML : 错误 编辑选项 编辑公开的HTML页和文本文件 把我的口令邮寄给我 邮件地址： 紧急暂缓所有列表信件 所有列表通讯的紧急缓存被设置 紧急延缓列表中所有邮件。 列表口令不得为空 启用 即使<a href="?VARHELP=general/subject_prefix">标题前缀</a>仅由ASCII码组成，
也对它编码。 结束 英语(美式) 输入验证cookie 输入新的管理员密码: 输入新的列表主持者密码: 在下面的每一行填写地址... 输入运行列表的人的email： 输入列表的名字： 错误 错误取消订阅: 错误邀请: 打开列表"%(listname)s"时发生错误，忽略。
%(e)s 打开列表 %(listname)s 时出错... 正在跳过。 错误订阅: 错误: 爱沙尼亚语 喀拉海语 显式的<tt>Reply-To:</tt>头部。 显式地址 二月 二月 过滤发送给成员的重复消息(如果可能的话) 匹配邮件头部的过滤器规则 完成 查找包含指定成员地址的所有列表。
用法：
find_member [options] regex [regex [...]]
其中：
--listname=listname
-l listname
仅搜索指定的列表。
--exclude=listname
-x listname
不搜索指定的列表。
--owners
-w
搜索列表属主和成员。
--help
-h
打印此帮助信息并退出。
regex
将要匹配的一个Python正则表达式。
-l和-x的相互影响如下。如果给出了-l选项，则仅搜索指定的列表。如果
指定了-x选项，但没有指定-l选项，那么除了指定的列表外，所有的列表都将被搜索。
正则表达式语法类似于Perl5，使用了Python的re模块。完整的定义参见:
https://docs.python.org/2/library/re.html
地址匹配是大小写无关的，但是显示的地址将保留原有形式。
查找 %(link)s 的成员 芬兰语 第一 修复MM2.1b4归档。
用法: %(PROGRAM)s [options] file ...
可用的选项有:
-h / --help
打印此帮助信息然后退出。
仅用来'修复'在Mailman 2.1b4中生成的带有虚假数据(bogus data)的邮件存档文件。
在您的$PREFIX目录里像这样来使用它:
%% %(PROGRAM)s `grep -l _mlist archives/private/*/database/*-article`
(注意，反引号是必须的)
在运行此脚本后您需要运行'bin/check_perms -f'。
修正语言模板: %(listname)s 加在每个摘要上的尾部信息 添加到发给常规列表成员邮件尾部的文本 因为某些原因, %(mbox_dir)s 作为一个文件存在. 它不能和
b6一同工作, 所以我将它更名为%(mbox_dir)s.tmp 并继续. 由于未知原因 发送信息(分别)给: 被暂存信件的转发 向前到列表所有者 转发选项 第四 法语 星期五 来自: 完全个性化 基本的列表特征，包括描述信息
和基本行为。 一般选项 与mailing list对象交互的通用框架。
可以用两种方式使用此脚本：交互式或者程序式。
交互式的使用允许您在Python交互式解释器中调整、检查和修改一个MailList
对象。此时，在全局命名空间中会有一个名为'm'的MailList对象可用，同时
也会把类MailList加载入全局命名空间。
程序式的使用，您可以写一个函数来操纵MailList对象，而此脚本会负责所有
的内务处理(请查看下面的例子)。如果是那样的话，一般的使用语法是：
%% bin/withlist [options] listname [args ...]
选项：
-l / --lock
打开列表列表时将其加锁。一般来说打开列表是不加锁的(例如为只读操作而打
开)。您总是可以通过输入'm.Lock()‘来给文件加锁。
注意，如果是用了此选项，您需要在退出前显式地调用m.Save()，因为解释器
的清理过程不会自动保存对MailList对象所作的修改(但是会给列表解锁)。
-i / --interactive
在所有其他处理过程结束后给您提供一个交互式的提示。这是默认行为，除非
提供了 -r 选项。
--run [module.]callable
-r [module.]callable
用于在一个打开的MailList对象上运行一个脚本，这是通过试图导入
'module'(它必须在保存列表的目录下，或者可以通过您的sys.path来访问),
然后从模块中调用'callable'来实现的。callable可以是一个类或者一个函
数；它被作为MailList对象的第一个参数来调用。如果在命令行上给出了其
的参数，他们会被作为后续的位置参数而传递给callable。
注意，'module.'是可选的；如果被省略的话，一个名为'callable'的模块将
被导入。
全局变量'r'将被设置为此调用的返回值。
--all / -a
此选项仅与 -r 选项一起工作。在您想要在所有的邮件列表上运行脚本时使用
此选项。在使用 -a 时，不能在命令行上包含列表名参数。变量'r'将是包含所
有返回值的列表。
--quiet / -q
去除所有的状态消息。
--help / -h
打印此帮助信息然后退出。
下面是一个如何使用 -r 选项的例子。假设您在Mailman的安装目录下有一个叫做
'listaddr.py'的文件，其中有下面的两个函数：
def listaddr(mlist):
print mlist.GetListEmail()
def requestaddr(mlist):
print mlist.GetRequestEmail()
现在，您可以通过在命令行上运行下面的命令来打印出列表的post地址：
%% bin/withlist -r listaddr mylist
Loading list: mylist (unlocked)
Importing listaddr ...
Running listaddr.listaddr() ...
mylist@myhost.com
您可以通过运行：
%% bin/withlist -r listaddr.requestaddr mylist
Loading list: mylist (unlocked)
Importing listaddr ...
Running listaddr.requestaddr() ...
mylist-request@myhost.com
来打印出列表的request地址。
另外一个例子，假设您希望改变一指定列表中特定用户的口令，您可以把下面的函数
放到一个名为'changepw.py'的文件中：
from Mailman.Errors import NotAMemberError
def changepw(mlist, addr, newpasswd):
try:
mlist.setMemberPassword(addr, newpasswd)
mlist.Save()
except NotAMemberError:
print 'No address matched:', addr
从命令行中运行：
%% bin/withlist -l -r changepw mylist somebody@somewhere.org foobar
通用列表信息页面 一般的列表属性 从文本翻译描述中产生二进制信息目录。
本程序将原始的统一字符编码的信息目录(.po文件)转换成二进制的GNU目录(.mo文件)。
它本质上和GNU的msgfmt程序是一样的，但是，它只是一个简单的操作。
用法: msgfmt.py [OPTIONS] filename.po
选项:
-o file
--output-file=file
指定信息写入的文件。如果忽略，将会输出到名为filename.mo（取决于输入文件名）的文件中。
-h
--help
输出此信息并退出。
-V
--version
显示版本信息并退出。
德语 Gnu's Not Unix 前往列表归档 前往列表常规信息页 Gzip压缩文本大小为 %(sz)s HTML 没有改变. HTML附件被移除 HTML更新成功. 加在每个摘要上的头部 添加到发给常规列表成员邮件头部的文本 头部过滤器规则需要一个模式。
不完整的过滤器规则将被忽略。 头部过滤器 隐藏消息的发送者，用列表地址替代它。
(将From,Sender,Reply-TO等域的信息删除掉) 单击回车来通知 %(listname)s的所有者... 滞留 暂存头部匹配指定正则表达式的信件。 滞留 列表发送邮件时使用的主机名。 不合法的地址(含有非法的字符) 恶意地址(非法字符)： %(member)s 检测到敌意的订阅尝试 一个被禁止成员的地址被移出邮件列表前, 收到<em>你的成员
资格被禁止</em> 警告的次数. 如果设置成0, 则一旦某成员的退信值超过
阈值, 他的地址便立即被移出列表。 主题匹配器应该扫描多少行正文内容？ 每隔多久启动一个新的存档卷? 多长时间开始新的一册摘要？ 匈牙利语 如果某封信件的收件人数目大于或等于这个数字，就将被暂存以待
管理员核准。0表示无上限。 如果您拒绝了这个邮件,<br>请给出原因 (可选l): 如果您回复该信件，请保持Subject:邮件头不变,
Mailman 将会丢弃被暂存的信件。如果该信息是垃圾邮件，采用以上处理方式。
如果您回复该信件并包含带有邮件列表密码的Approved:头部
该信件将被批准发送至列表。该Approved:头部将会
同时出现在回复信件正文的第一行 如果您提供一个口令，您必须对它进行确认。 如果你的邮件列表默认语言使用非ASCII码集，并且前缀中有非ASCII码，
将使用相关标准对前缀编码。但是，如果前缀仅包含ASCII码，或许你想
设置该选项为<em>从不</em>以禁止对前缀编码。对使用不支持非ASCII译
码邮件阅读器的用户来说，这将使得头部标题变得易读一些。
<p>注意，如果你的邮件列表同时接收编码和未编码的头部标题，你应该
选择<em>根据需要</em>。使用这个设定，如果头部其余部分仅含ASCII
码，Mailman将不编码前缀， 反之，如果原始头部中含有非ASCII码字符，
则将编码前缀。对于可能导致邮件阅读器显示额外信息或是遗失前缀和
头部之间空格的标准，这样做避免了译码时可能出现的模糊。 忽略 : %(addr)30s 忽略错误的未处理数据: %(key)s: %(val)s 忽略对已删除用户的更改: %(user)s 忽略保存的信件w/bad id: %(f)s 忽略未被保存的信件： %(f)s 忽略 non-text/plain MIME 部分 非法的邮件地址 提供了非法的邮件地址 非法的列表名称: %(s)s 无效的选项: %(opt)s 导入 %(module)s... 为了修改您的选项，您必须首先在下面的部分中使用您的 %(extra)s 成员口令进行登录。
如果您忘记了您的口令，您可以通过点击下面的按钮来把它邮寄给您。如果您只是想
退订此列表，请点击<em>退订</em>按钮，然后一封确认函将投递给您。
<p><strong><em>重要：</em></strong>从此处起，您必须在您的浏览器中启用cookies，
否则您做的所有修改都将不起作用。
增加摘要卷序号并把摘要序号复位至1。
用法： %(PROGRAM)s [options] [listname ...]
选项：
--help/-h
打印此帮助信息然后退出。
命令行上给出的列表将被处理。如果没有给出任何列表的话，所有的列表都将被处理。
初始的 %(listname)s的密码： 支持语言的初始列表. <p>请注意:如果您
没有选择初始语言, 邮件列表将采用服务器
默认的语言 %(deflang)s 初始的列表拥有者地址: 初始列表密码: 初始列表密码不匹配 把文件中的信件插入到Mailman的incoming队列中。
用法: inject [options] [filename]
选项：
-h / --help
打印此帮助信息并退出。
-l listname
--listname=listname
将插入信件的列表名。必须指定此选项。
-q queuename
--queue=queuename
将要插入信件的队列名。queuename必须是qfiles目录的一个子目录名。如果省略
的话，将使用incoming队列。
filename是要插入的文本信息文件。如果省略的话，将使用标准输入。
被中断... 无效的: %(addr)30s 无效的验证字符串.
可能你在尝试为已经取消订阅的地址确认请求. 无效的CGI脚本参数 无效的CGI脚本选项 属性值非法: %(k)s 该变量的值非法：%(property)s 邀请 存档文件是公开的还是私人的? 队列管理器正在运行吗？ 退订请求需要经过列表主持者的核准吗？(推荐选<em>否</em>) 意大利语 一月 一月 日语 七月 七月 六月 六月 韩国语 语言选项 列表支持的语言。 本日最后一条自动回复通知 如果您想让 Mailman 自动生成列表密码,请将初始密码域(和验证域)置空. 传统的垃圾邮件过滤器 列表 列表特性 列表帮助机器人： %(requestaddr)s 列表身份 列表属主： %(owneraddr)s 仅列表管理员 列出一个邮件列表的所有属主。
用法： %(program)s [options] listname ...
其中：
--all-vhost=vhost
-v=vhost
列出指定虚拟主机上所有邮件列表的属主。
--all
-a
列出此系统中所有邮件列表的属主。
--help
-h
打印此帮助信息并退出。
'listname'是要列出属主的邮件列表名。可以在命令行上指定多个列表。
列表已经存在: %(listname)s 列表已经存在: %(safelistname)s 列出创建者的(认证)密码: 列表成员 像对一个延缓列表的订阅，或因某种原因而被延缓的邮件所做的那样，给列表管理员
发送关于未批准请求的每日提醒。设定这个选项同样会导致新请求一到达
就立刻发通知给列表管理员。 列出我的所有订阅 需要列表名 列表名称是必需的. 列表名称不能包含 "@": %(safelistname)s 列表名： %(listname)s 被禁止加入列表的地址清单。 其信件应当被自动接受的非成员地址清单。 所发信件会被自动丢弃的非成员地址清单。 所发信件会被自动拒绝的非成员地址清单。 所发信件会被立即暂存以待审查的非成员地址清单 列表管理口令： 为 %(safeuser)s 列出在 %(hostname)s 上的订阅 列出一个或所有邮件列表的属主。
用法： %(PROGRAM)s [options] [listname ...]
选项：
-w / --with-listnames
把属主按列表名分组，并且在输出中包含列表名。否则，属主将按
邮件地址排序，并且重复的地址将被删去。
-m / --moderators
在输出中包括列表管理员。
-h / --help
打印此帮助信息然后退出。
listname
打印指定列表的属主。可以在选项后指定多个列表。如果未指定列表，所有
列表的属主都将被打印。
列表主题关键字 列表通讯存档策略 添加到新订阅者欢迎消息前的列表说明文本 列表: 列表： %(listname)s, 属主： %(owners)s 立陶宛语 加载列表 %(listname)s 登录 退出登录 注销 MIME 邮件投递 邮件<-->新闻网关 Mail-to-News和News-to-Mail网关服务 邮件列表 %(listname)s 创建请求 创建邮件列表的结果 邮件列表删除结果 对邮件列表 %(listname)s 的删除请求 Mailman Mailman %(varname)s 列表选项帮助 Mailman 管理数据库 错误 Mailman以<a href="?VARHELP=general/subject_prefix">
您可以定制的文本</a>作为内容添加<tt>Subject:</tt>头部。并且在正
常情况下，这个前缀显示在经网关
路由到新闻组的信件中。你可以把此选项设定为<em>否</em>以禁止在被路由
信件中添加前缀。当然，如果你关闭正常的<tt>Subject:</tt>前缀，
它们也将不会出现为被路由信件的前缀。 Mailman内部警告 您输入的地址不是Mailman的有效地址(如:地址中必须有@)。 修改以下部分, 然后用
<em>提交您的修改</em>按钮提交它们。 很多(事实上是绝大多数)垃圾邮件都不是把它们那无数的目的地
直接的放到目的地址中 - 事实上To:字段经常只有伪造的虚假地址。
此限制仅仅应用到目的地址中'@'前面的部分，但是这样也能捕获
所有的这种垃圾邮件。
<p>这样做的代价是，列表将不再接受从其他地址中继过来的正常信件，
除非
<ol>
<li>中继地址有着同样的名字，或者
<li>可接受的别名清单中包含此中继地址。
</ol> 三月 三月 批量删除 批量订阅 批量移除 批量订阅 邮件正文最大长度(以千字节为单位的)。0表示无限制。 五月 成员过滤器 成员姓名修改成功 成员列表 成员身份公布 成员重新有效 成员列表 成员管理... 消息摘要: 消息头部: 信件内容过大：%(size)d 字节 (上限为 %(limit)d KB) 信件带有可疑的邮件头 信息中含有隐式的目的地 消息中包含管理指令 由于匹配过滤规则而被拒绝的信件 节制的 主持人 主持者密码不匹配 星期一 每月 更多信息： %(listurl)s 下移规则 上移规则 必须有一个列表名和文件名 信件的目的地址(to,cc)必须包含此列表的地址(或在下面指定的
可接受的别名)吗？ 列表名称: 名字： 自然语言(国际化)选项。 从不 %(listname)s的新口令： %(notifypassword)s 新 %(pwdesc)s 口令 成员 %(member)40s的新密码： %(randompw)s 来自 %(addr)s 的对 %(realname)s 列表的订阅请求 来自 %(addr)s 的对 %(realname)s 列表的退订请求 新闻服务器设置 不 没有给出地址 没有给出-f的参数 进程: %(pid)s 没有子进程 没有提供命令。 该邮件中没有发现指令。
发送内容为 "help" 的信件以获得所有命令.
没有给出文件名 没有给出列表的名字 没有指定列表: 没给出列表名 没有要搜索的列表 没有找到匹配的邮件列表 此列表不支持订阅摘要! 没有发现问题 没有给出原因 没提供管理器的名字。 无主题 列表"%(listname)s"不存在
%(e)s 没有这个列表(或者列表已经被删除了): %(listname)s 没有类似的列表 <em>%(safelistname)s</em> 没有此列表： %(listname)s 没有这个列表: %(listname)s。正在删除它的残留的文件。 没有这个成员: %(addr)s 不存在 %(safeuser)s 这个成员. 不需要升级 订阅的地址无效 找不到有效的变量名。 没订阅摘要(普通的)的成员: 非摘要(Non-digest)选项 非成员过滤器 不允许非成员往该列表发送信息。 非标准属性复位： %(k)s 无 无 - 无认证步骤(<em> 不推荐使用 </em>)<br>
确认 (*) - 要求有邮件确认步骤 <br>
要求核准 - 需要列表管理员核准订阅<br>
确认并核准 - 即要求确认,也需要管理员核准
<p>(*) 当有人请求订阅时，Mailman给他发送带有唯一订阅请
求号的的通知，如果他要订阅，必须回信。
这用来防止恶意用户不经他人同意而为其订阅。 一般来说,Mailman把普通投递信息批量的送给邮件服务器.这样
做更有效率,因为它减少了Mailman和邮件服务器之间的通讯量.
<p>但是,更个性化的设置对一些列表可能会很有帮助.在这种情况下
Mailman为普通投递列表中的每一个成员均提交一份新的信息.打开
此特性可能会降低您站点的性能,所以您应该好好考虑一下,这个交易
是否合算,或者是否有其它的方式来完成您想要的效果.您应该小心的
监视您的系统负载,以确保您所花的代价是可承受的.
<p>选择<em>否</em>来禁止个性化设置,批量向成员投递信息.选择
<em>是</em>来个性化您的投递,并且允许在消息头和消息尾施用额外
的替换变量(参考下面的内容).此外,通过选择<em>完全的个性化</em>,
所发信息的<code>To</code>头部会被修改以包含成员的地址而非列表
的发信地址.
当个性化启用时,可以在<a href="?VARHELP=nondigest/msg_header">
信息头和<a href="?VARHELP=nondigest/msg_footer">信息尾使用少量
的额外替换变量.
<p>当此特性开启时,如下的额外的替换变量可以在信息的头部或者尾
部使用:
<ul><li><b>user_address</b> - 用户的地址,被修改为小写.
<li><b>user_delivered_to</b> - 用户订阅列表时使用的大小写
相关的地址.
<li><b>user_password</b> - 用户的口令.
<li><b>user_name</b> - 用户的全名.
<li><b>user_optionsurl</b> - 用户选项页的URL地址.
</ul> 挪威语 非法email地址： %(toaddr)s 无法鉴别 没有删除文件。带上 -a再调用一遍命令来删除它们。 没有订阅 注意: 由于这是一个邮件列表的清单, 口令提示函等管理通知会被发
送到您的成员管理地址, %(addr)s. 注意：你在列表中的发信权现在被禁止了，因为 %(reason)s。 什么也不需要做. 注意： %(discarded)d 旧请求自动过期。
通告 十一月 十一月 向邮件列表或向相同发言者的请求或所有者地址发送自动回复
间隔的天数. 设置成零(或负数)则没有宽限期 (也就是说向每条消息
发送自动回复). 十月 十月 关 OK, 列表主持者仍然有机会批准或者拒绝这条信息. 开 你的口令将每月一次以提示函的形式发送给你。 -i和-o至少需要一个 当消息与内容过滤规则之一匹配, 将采取下列动作之一:
, 也就是说顶级内容类型与 <a
href="?VARHELP=contentfilter/filter_mime_types" >过滤MIME类型</a>之一匹配, 或者顶级内容类型
<strong>不</strong>匹配 <a href="?VARHELP=contentfilter/pass_mime_types" >允许通过MIME类型</a>中的任何一个,或者子部分被过滤后
该消息已经变成了一个空消息.
<p>请注意如果过滤后的消息仍然还有内容, 则次动作不会被采取. 在那
种情况下消息总会被发送给列表成员.
<p>当消息被放弃时, 会写入一个包含被放弃消息ID的消息项. 当消息被
拒绝或者发向了列表所有者时, 原作者将收到包含被拒原因的退信. 当
消息被滞留, 它被存储在磁盘上一个特殊的队列目录以便管理员查看
(也可能恢复这个消息), 但除此情况消息会被放弃. 最后这种选项只
有当站点管理员允许时才有效. 只允许一个-f开关 -i和-o中只能选择一个 开放的列表，节制的组 原文 其他管理事件 %(hostname)s 上的所有邮件列表 在: %(pidfile)s 中找不到PID 口令 // URL 更改口令失败 口令以更改 口令提示函 密码修改成功 口令： 口令： 口令 密码不匹配! 口令不相同，未做改变 密码不能为空 模式(正则表达式) 阻塞的订阅： 执行所有需要的升级.
用法: %(PROGRAM)s [options]
选项:
-f/--force
强迫运行升级过程. 正常情况下,如果
已安装的版本号与正安装的版本号相同 (或者
一次`降级'安装被发现), 什么安装也不会执行.
-h/--help
显示这段文本并退出.
使用这段脚本从之前的某个版本升级到最新的发行版.
它可以识别到1.0b4 (?)版本.
永久拒绝这个列表 永久删除邮件列表<em>%(realname)s</em> 普通 请不要发送管理请求到邮件列表，如果希望订阅，
请访问 %(listurl)s 或者 以｀help｀为内容发送信息至
请求地址， %(request)s，以获得进一步的指示信息。 请输入您的验证字符串
(也就是说在下面的方框中您以邮件信息的方式收到的<em>cookie</em>)
然后点击 <em>提交</em> 按钮，以进行下一步的验证. 请指定 -p 或者 -m 请整理收件人列表；该列表太长。 即时投递传输的策略 波兰语 向NNTP服务器查询需要转发到邮件列表的消息。
用法： gate_news [options]
这里的选项为
--help
-h
打印此帮助信息然后退出。
葡萄牙语 葡萄牙语(巴西) 由非成员发送到一个仅成员列表(members-only list) 发送到受限列表 发送的信件已经取消 发布者 待批准邮件 您以标题 "%(subject)s" 发布的信件 发送信息至受节制的新闻组 需要被审核的用户向一个受限列表发送信息 这些非成员的信件将被自动丢弃。也就是说，这些信件将被直接丢
弃，而不会再做进一步的处理，也不会发送任何的通知。发信人将不会收到
邮件通知或者退信，但是列表管理员可以选择
<a href="?VARHELP=privacy/sender/forward_auto_discards">接收一份
被自动丢弃信件的拷贝</a>。
<p>每行添加一个地址；行首的字符^说明后面的是正则表达式。 这些非成员的信件将被自动拒绝。也就是说，他们的信件将被连同一
份退信通知一起被退回。这个选项不适用于已知的垃圾邮件发送者；他们
发送的信件应该被
<a href="?VARHELP=privacy/sender/discard_these_nonmembers"
>自动丢弃</a>。
<p>每行添加一个地址；行首的字符^说明后面的是正则表达式。 这些非成员的信件将会被立即暂存以待列表管理员审查。发送者将
收到邮件通知，以允许他们自己撤销被暂存的信件。每行添加一个地址；
行首的字符^说明后面的是正则表达式。 投递到： %(postaddr)s 喜欢的语言 在经网关发送到新闻组的邮件中添加<tt>Subject:</tt>头部？ 列表邮件的主题前缀。 滞留 为站点管理员保留信息 为站点管理员保存信息 关闭、开启Mailman qrunner守护进程的主脚本程序。
此脚本可以开启，关闭，和重启Mailman queue runners，确保各种长期运行的qrunner仍
在正常运行。此脚本通过fork和exec这些qrunners并且获取他们的pid来做到这些。当它发
现有子进程退出时，就会重新启动它。
qrunners会对SIGINT， SIGTERM和SIGHUP信号作出响应。SIGINT和SIGTERM信号可以使qrunners
完全地退出，但是master只会对由SIGINT信号造成的退出进行重启。SIGHUP会导致master
和qrunners关闭它们的日志文件，直到产生新的输出信息时才重新打开它。
master也会响应SIGINT, SIGTERM和SIGHUP，但只是把它们传递给qurnners(注意，当接收到
SIGHUP时master会关闭并重新打开它的日志文件)。master也会在data/master-qrunner.pid
这个文件中记录它自己的进程号，但是一般来说您不需要直接使用它。'start', 'stop',
'restart'和'reopen'这几个命令为您处理了全部的事情。
用法： %(PROGRAM)s [options] [ start | stop | restart | reopen ]
选项：
-n/--no-restart
在qurnners因错误或者SIGINT而退出后不被重启。如果它们是因为SIGTERM而
退出的话，将从不会被重启。仅调试时使用此选项。仅在使用'start‘
命令时有效。
-u/--run-as-user
一般来说，当用户id和组id没有被设置为'mailman'(在您编译配置Mailman时定
义)时，此脚本会拒绝执行。如果以root身份运行的话，此脚本将会在检查之前
切换到此用户和组。
这可能会对测试或者调试造成不便，设置-u选项会导致设置和检查
uid/gid的步骤被忽略，并且程序将会以当前用户和组的身份运行。不推荐在实
际环境(normal production environments)中使用此选项。
但是请注意，如果使用了-u选项，并且不属于mailman组，则可能会遇到权
限问题，例如无法从web上删除一个列表的存档。厄运！
-s/--stale-lock-cleanup
如果mailmanctl发现一个已存在的master锁文件，它一般会打印一段错误信息，
然后退出。指定此选项会使mailmanctl做进一步的检查。如果发现一个正在运行
的进程，它的host/pid与锁文件中描述的一致，mailmanctl仍然会退出。但是如
果没有找到这样的进程，mailmanctl会删除这个错误的锁文件，然后尝试建立正确
的master锁文件。
-q/--quiet
不显示状态信息。错误信息仍然会被打印到标准错误。
-h/--help
打印此帮助信息然后退出。
命令：
start - 启动master守护进程和所有的qrunners。如果master守护进程已经在运行
的话，打印一条信息然后退出。
stop - 停止master守护进程和所有的qrunners。停止后，不会再有信件被处理。
restart - 重启qrunners，但是不重启master进程。当您升级Mailman后使用此
命令，这样qrunners将会使用新安装的代码。
reopen - 这将会关闭所有的日志文件，在产生新的日志信息时再重新打开它们。
显示Mailman版本.
隐私选项... 内部存档错误 内部存档错误 - %(msg)s 没有找到内部存档文件 发现问题: 处理被禁止的成员，建议每天一次。
此脚本在所有的邮件列表中查找禁止投递的成员。如果他们是因为退信而被禁止，他们将
收到另一封通知，或者在他们收到的通知超过了最大数量时将他们从列表中移除。
使用 --byadmin, --byuser, 和 --unknown 选项将会向因相应原因而被禁止的成员发送通
知。使用 --all 将向所有被禁止的成员发送通知。
用法： %(PROGRAM)s [options]
选项：
-h / --help
打印此帮助信息然后退出。
-o / --byadmin
也向被列表主人/管理员禁止的成员发送通知。
-m / --byuser
也向自己禁止的成员发送通知。
-u / --unknown
也向因未知原因而被禁止的成员发送通知(一般是一个继承的被禁止的地址)。
-b / --notbybounce
不向因退信而被禁止的成员发送通知(默认是向他们发送通知)。
-a / --all
向所有被禁止的成员发送通知。
-f / --force
向被禁止的成员发送通知，即使他们还不应该现在就接到新的通知。
-l listname
--listname=listname
仅处理指定的列表，否则将处理所有的列表。
%(hostname)s 上的公共邮件列表： Python Powered 每季度 RFC 2369 定义了一个 List-*的头部集，这个头部集通常会添加在发给列表成员的每封邮件中
这极大的帮助了使用标准(standards compliant)邮件阅读器的终端用户。
通常应该使用这些头部。
<p>然而，并不是所有的阅读器都是符合标准的，如果你有很多成员使用非标准
(non-compliant)邮件阅读器，他们会对此头部很生气。你应该首先告诉你的成员
这些头部存在的原因，并告诉他们怎样在邮件客户端隐藏头部。实在不行的话可以
禁用头部。但并不建议这样做(事实上，你最终会失去禁止头部的能力)。 重新设置邮件列表成员有效 重新设置成员资格为有效 重新生成gzip压缩的Pipermail存档文件。
此脚本应该在每晚由cron运行。从命令行运行时，可以识别下面的用法：
用法： %(program)s [-v] [-h] [listnames]
这里：
--verbose
-v
打印正在被gzip压缩的文件名。
--help
-h
打印此帮助信息然后退出。
listnames
可选，仅压缩指定列表的 .txt 文件。不指定的话所有可存档的列表都将被处理。
正在打开所有的日志文件 以 %(MAILMAN_USER)s(或root)身份使用-f标记(flag)重新运行此脚本
来修复发现的问题 拒绝的原因 原因: 重建列表归档
使用这个命令重新为一个邮件列表创建归档。如果您需要编辑或者
删除归档中的信件，可能需要做此操作。
用法: %(PROGRAM)s [options] <listname> [<mbox>]
这里选项为
-h / --help
打印此帮助信息然后退出.
-q / --quiet
关闭冗余输出.
--wipe
在重新生成归档前删除原有归档.一般来说,除非您成块地生成归档,您会指定此
选项.
-s N
--start=N
从第N篇文章开始索引,mbox中的文章从0开始计数.默认为0.
-e M
--end=M
到第M篇文章处结束索引.这个脚本在内存管理和处理大的归档方面并不高效,
可能无法完全索引mobx中的所有条目.由此,您可以提供开始和结束索引的文
章编号.
<mbox>是列表mbox归档的路径.一般来说是archives/private目录下的某个路径.例如:
%% bin/arch mylist archinves/private/mylist.mbox/mylist.mbox
<mbox>是可选的.如果没有提供,它将被计算出来.
接收文摘吗? 接收: 收信人过滤器 接收端过滤器 降低磁盘空间。
用法: %(PROGRAM)s [options] file ...
选项是:
-h / --help
输出此帮助信息然后退出。
此命令仅用来整理用Mailman 2.1.3O或更早的版本生成的数据库归档文件，这些文件都是html格式的。
而html格式会造成大量的内存浪费并严重影响高速列表的性能，特别是会产生大量文本纪录的列表。
例子:
%% ls -1 archives/private/*/database/*-article | xargs %(PROGRAM)s
在运行此脚本后，您应该运行‘bin/check_perms -f’。
当您对结果满意后，您可能会想要删除由此脚本产生的-article.bak文件。
此脚本仅是用来提升性能的。并不是必需使用的。
从头开始重新生成Mailman specific aliases。
实际的输出依赖于mm_cfg.py文件中'MTA'的值。
用法： genaliases [options]
选项：
-q/--quiet
一些MTA的输出会包括更多冗余的帮助信息。使用此选项来关闭冗于。
-h/--help
打印此帮助信息并退出。
正则表达式 一般 拒绝 拒绝 提示 移除内容类型不匹配的附件.
若想跳过过滤器测试则请将此项留空. 移除没有匹配的扩展名的消息附件. 如果您想跳过过滤器，请留空此项. 移除类型匹配的附件. 移除有匹配的扩展名的附件. 安全的删除邮件列表的所有组件!
能删除邮件列表的（几乎）所有的痕迹。默认情况下，对不用的旧列表很有用的列表存档不会被删除。
用法:
rmlist [-a] [-h] listname
其中:
--archives
-a
将列表存档也删除，如果列表已经被删除，则删除所有残留的存档。
--help
-h
输出该帮助信息然后退出。
移除 : %(s)s 正在删除 %(msg)s 对于 %(realname)s 邮件列表的请求被拒绝 请求的主题不存在: %(topicname)s 要求核准 把列表的web_page_url属性恢复为默认设置。
此脚本应该被作为一个bin/withlist脚本来运行，也就是
% bin/withlist -l -r fix_url listname [options]
选项：
-u urlhost
--urlhost=urlhost
在虚拟主机列表中搜索urlhost，并把web_page_url和host_name属性设置为找到的值。
在本质上，这把一个列表从一个虚拟域移到了另一个。
不指定此选项，将使用web_page_url和host_name的默认值。
-v / --verbose
打印脚本正在做什么。
如果独立运行的话，将打印此帮助信息并退出。
为邮件列表成员重设密码。
此脚本为一个邮件列表的所有成员重设密码。它也能为所有邮件列表的所有成员重设密码，
但是您有必要让所有得用户知道他们的密码被改变了。
该脚本必须作为bin/withlist脚本来运行，即
% bin/withlist -l -r reset_pw listname [options]
选项:
-v / --verbose
输出脚本正在干什么
重设 %(n)s BYBOUNCEs 使没有退订信息的地址失效 正在重启Mailman的主队列管理器 返回产生的输出。 返回到 罗马尼亚语 用root用户，或 %(name)s用户身份来运行此程序，或者使用-u。 运行 %(module)s.%(callable)s()... 俄语 星期六 保存列表 去除常规投递邮件的附件？ 需指定搜索正则表达式 搜索... 第二 选择您要编辑的页面: 向列表拥有者发送"列表已创建"的信件吗? 当成员退订时，是否发送再见消息？ 当邮件被延缓等待批准时给发件人发邮件吗？ 是否每月发送密码提示？ 向列表管理员发送出现新订阅的通知? 向列表拥有者发送通知 向所有列表中的所有成员发送口令提示函。
此程序扫描所有的邮件列表，搜集用户和他们的口令，如果mm_cfg.VIRTUAL_HOST_OVERVIEW
为真的话还将他们按照列表的host_name进行分组。然后给每一个唯一的用户(每一个虚拟主机)
发送一封电子邮件，包含列表的口令以及可选的url。口令提示函从mm_cfg.MAILMAN_SITE_LIST
发出，mm_cfg.MAILMAN_SITE_LIST一定要存在。
用法： %(PROGRAM)s [options]
选项：
-l listname
--listname=listname
仅为指定的列表发送口令提示函。如果省略的话，将会给所有的列表发送。可以使用
多个 -l/--listname 选项。
-h/--help
打印此帮助信息然后退出。
将密码提示发送给，例如，"-owner"地址，而不是
直接发送给用户。 向用户发送取消订阅的确认 是否向新订阅者发送欢迎消息？ 向新的订阅者发送欢迎信件么? 寄件人通过web删除了信件 发送人被明确禁止 发送端过滤器 九月 九月 塞尔维亚语 服务器本地时间 设置 从终端提示来设置口令。
在管理员口令有效的大部分地方（但不是全部），站点口令都有效。在用户口令有效的大部分地方，
站点口令也有效。
用法: %(PROGRAM)s [options] [password]
选项:
-c/--列表创建者（listcreator）
设置列表创建者的口令，而不是站点口令。列表创建者有权创建和删除列表，但是
没有站点管理员的全部权限。
-h/--帮助
显示此帮助信息并退出
如果没有在命令行中输入口令，则会提醒您。
设置host_name为： %(mailhost)s 设置此项将导致在网页中显示经过变形后的成员邮件地址(文本
和链接都经过变形)，变形后的邮件地址将不再是标准格式。这样作的目
的是为了防止一些垃圾邮件制造者利用网络爬虫自动收集这些邮件地址。 设置这个选项用于指示Mailman在下一册发
送出去时开始新一册摘要。 设置web_page_url为： %(web_page_url)s Mailman是否将<tt>text/html</tt>部分转化成纯文本?
此种转换在MIME附件被剥离时发生. Mainman是否安下列设置过滤列表中的消息内容? 当用户由于退信而被退订时, Mailman是否通知您(列表所有者)? 当用户的订阅由于退信而被禁止, Mailman是否通知你? Mailman是否执行自动退信处理? Mailman是否为每一个非摘要投递进行个性化设置？这对仅作发布通知用途的列表很有
用，但应该<a href="?VARHELP=nondigest/personalize">读取详细
信息</a>部分讨论列表系统性能的重要性。 Mailman是否就发向列表所有者地址的邮件发送自动回复? Mailman是否就发向请求地址的邮件发送自动回复?
如果您选择发送,请决定Mailman放弃原始邮件,还是继续把该邮件当做
正常的邮件发送到系统中. Mailman是否向邮件列表的发言者发送自动回复? 如果摘要不为空，Mailman应该现在就发送下一册摘要吗
？ Mainman是否向您(列表所有者)发送退信处理器检测失败的退信消息?
建议选择<em>是</em>。 Mailman应该开始新一册摘要吗？ 当没有达到摘要大小的上限时，摘要需要每天投递吗？ 管理员是否应该得到订阅和取消订阅的通知？ 所有在原消息中找到的<tt>Reply-To:</tt>头部都应该被删除吗？
如果是，不管是否是Mailman显式添加的
<tt>Reply-To:</tt>头部都将被删除。 被自动丢弃的非成员信件是否应该被转发给列表管理员？ 来自这个邮件列表的邮件是否要包括
<a href="http://www.faqs.org/rfcs/rfc2369.html">RFC 2369</a>
(也就是，<tt>List-*</tt>) 的头部？强烈推荐<em>包括</em> 新加入的成员在允许向这个列表发送没有经过缓冲的信息前需要被隔离吗?
回答 <em>是</em> 会将
新成员发送的信息滞留起来,等待主持者的批准(默认). 要把投递到列表的新邮件发送给新闻组吗？ 要把投递到新闻组的新邮件发送给列表吗？ 邮件是否应该包括<tt>List-Post:</tt>的头部？ 列表管理员是否应该得到新请求的即时通知，像得到关于收集到的请求的每日通知一样？ 启用主题过滤器吗？ 不以标准格式显示成员的邮件地址？ 显示一个或多个Mailman队列文件的内容.
用法: show_qfiles [options] qfile ...
-q / --quiet
不打印`有用的'消息分界符.
-h / --help
打印这份文本并退出.
示例: show_qfiles qfiles/shunt/*.pck
正在关闭Mailman的主队列管理器 缺少站点列表: %(sitelistname)s 大小: 跳过的 %(partctype)s 类型的内容
斯洛文尼亚语 在创建列表的时候发生了未知的错误.
请联系站点管理员以获得帮助. 垃圾邮件过滤正则表达式 垃圾邮件过滤规则 %(i)d 垃圾邮件过滤器 西班牙语(西班牙) 过期的进程号文件已删除。 正在启动Mailman的主队列管理器 有限状态机解析器的状态表:
0 空闲
1 文件名或注释
2 消息标识
3 消息串
4 结束
主题: 提交 提交所有的数据 提交更改 提交我的修改 提交您的修改 订阅 订阅结果页面 替这些用户订阅或者邀请他们 订阅邮件列表 %(listname)s 已订阅: %(member)s 订阅 订阅请求 订阅请求 订阅请求已经确认 订阅请求成功。 订阅规则 成功删除: 成功取消订阅: 成功邀请: 成功订阅: 根据前面"umbrella_list"的设置，当这个列表是其它列表的保护列表时
使用的前缀。 星期日 瑞典语 使用一个普通的文件来同步一个邮件列表的全体成员.
这个脚本将很有用,如果您有一份Mailman邮件列表和一份sendmail
:include:式样的地址列表(Majordomo也如此使用). 对于每一个
没有出现在邮件列表里却包含在文件里的地址,它们将被添加.
对于每一个没有出现在文件里的邮件列表内地址,它们将被
删除.其他的选项用来控制当一个地址被添加或删除时将会
发生什么.
用法: %(PROGRAM)s [options] -f file listname
这里 `options' 有:
--no-change
-n
不真正作成改变. 相应的,显示
列表将有何改变.
--welcome-msg[=<yes|no>]
-w[=<yes|no>]
设置是否向新加入成员发送欢迎信息,
而不论列表的 `send_welcome_msg' 设置究竟是什么.
使用 -w=yes 或 -w, 欢迎信息将被发送. 使用 -w=no,
将不会发送欢迎信息.
--goodbye-msg[=<yes|no>]
-g[=<yes|no>]
设置是否向移除成员发送告别信息,
不论列表的`send_goodbye_msg' 的设置.
使用-g=yes 或 -g, 告别信息将被发送. 使用 -g=no,
将不会发送告别信息.
--digest[=<yes|no>]
-d[=<yes|no>]
选择是否使新加入的成员接收文摘中的信息.
使用 -d=yes 或 -d, 他们将成为文摘成员. 使用 -d=no
(或者没有给出 -d ) 他们将被添加为普通成员.
--notifyadmin[=<yes|no>]
-a[=<yes|no>]
指定在每一次订阅或退订时,管理员是否被通知.
如果您加入大量的地址, 您绝对会将这个选项关闭!
使用 -a=yes 或 -a, 管理员将被通知.
使用 -a=no, 管理员不会被通知. 不给出 -a 选项,
将使用列表的默认选项.
--file <filename | ->
-f <filename | ->
这个选项是必需的. 它指定了用来同步的文件.
Email地址必须每行一个. 如果文件名是
`-' 那么将使用标准输入.
--help
-h
显示这段信息.
listname
必需.指定了同步的列表.
系统错误, 错误的内容: %(content)s 处理待裁决请求 添加到每一封即时投递的邮件末尾的文本 加在摘要尾部的文本(作为结束消息)。 加在摘要顶部的文本(在内容表格之前作为开始消息)。 添加到每一封即时投递的邮件中的文本 发送给离开列表的成员的文本。如果空，不会有指定的文本
添加到退订消息上。 应当被包含在<a href="?VARHELP/privacy/sender/member_moderation_action"
>退信通知</a>中的文本。 应当被包含到寄给发信到本列表的非成员的退信通知中的文本。
此通知可以包含列表属主地址 %%(listowner)s, 并且替换掉Mailman
内定的默认信息。 文本大小为 %(sz)s 当此主机给mailman相关地址发送邮件时使用此主机名，通常主机名应该是邮件交换机的地址。
当主机有多个地址时，可通过设定此选项为主机选择一个名字。 <em>列表管理员</em>拥有所有邮件列表参数的最终控制权.
他们可以更改在管理员页面上列出的所有配置变量.
<p><em>列表主持者</em> 有受限的权限;
他们不能改变任何列表的参数, 但是他们可以挂起管理请求.
包括批准或者拒绝滞留订阅请求,清理滞留邮件.当然
<em>l列表管理员</em> 也可以挂起请求.
<p>为了在列表管理员和列表主持者之间分配管理员职责
您必须在下面的域中设置单独的列表主持者密码,
并在<a href="%(adminurl)s/general">常规选项部分</a>中提供列表主持者的邮件地址. <tt>List-Post:</tt>头部是<a href="http://www.faqs.org/rfcs/rfc2369.html">RFC 2369</a>.
推荐的头部之一。然而，对一些<em>只限通知</em>的邮件列表，仅有一些人有向列表
发送邮件的权利；不允许普通成员发送邮件。对这种类型的列表，<tt>List-Post:</tt>
头部容易让人误解。选择<em>否</em>来禁止此头部。(这不影响可包含其他
<tt>List-*:</tt>头部。 Mailman 自动回复机器人 `join'命令和`subscribe'命令是相同的。
`leave'命令和`unsubscribe'命令是相同的。
命令 "remove" 和命令 "unsubscribe"是相同的.
要求更改的地址后来取消了订阅.
这次请求被撤销了. 要求取消订阅的地址不是邮件列表中的成员.
可能您已经取消了订阅,比如说被邮件列表的管理员取消? 附带的消息被自动丢弃 附带的信件匹配 %(listname)s 邮件列表的内容过滤规则
而被禁止发送至列表用户
您所收到的内容为被丢弃信息的拷贝。
附带的信件是接收到的退信，但是退信格式不可识别，或者无法从其中提取出成员地
址。本邮件列表设置将所有不可辨识的退信发送至列表管理员。
要获取更多信息，请浏览：
%(adminurl)s
该名字的大写或者首字母的缩写可能被某些公司里作为专用名词
。但是，如果该名字被申请作为邮件地址(
如：在订阅确认中可以注明)，所以<em>不</em>应该
以其他方式改变名字。(邮件地址不是大小写敏感的，
但是在其他地方一般是非常敏感的:-) 当前归档 您提供的邮件地址被此邮件列表禁止了。若您认为这是错误的，请联系列表管理员
%(listowner)s。 您提供的邮件地址被禁止。如果您觉得这些限制是错误的，
请联系列表管理员 %(listowner)s 您提供的邮件地址是无效的。(例如，它必须包含一个`@'。) 在<code>%(property)s</code>中发现下列非法的订阅变量值：
<code>%(bad)s</code>
<p>不更正这些问题，你的列表可能无法正常运作 头部过滤器规则模式
'%(safepattern)s' 不是合法的正则表达式。这条规则将被忽略。 找不到主题头部为 <em>%(subject)s</em> 的滞留信件。
最有可能的原因是
列表主持者已经批准或者拒绝了这条信件.
你不能及时地取消这条信件. 提交给你的滞留信件已经由列表管理员处理了. 您的新闻服务器所在主机的主机名。 列表管理员邮件地址。如果有多个地址，
每个地址填写在单独的一行即可。 列表管理员已经禁止了此列表的摘要投递功能，所以您的
投递选项没有被设置，但是您的其他选项都已成功地设置。 列表管理员已经禁止了此列表的非摘要投递功能，所以您的
投递选项没有被设置，但是您的其他选项都已成功地设置。 列表主持人邮件地址。如果有多个地址，
每个地址填写在单独的一行即可。 列表密码不能为空 列表密码不能为空<!-- ignore --> `%(listname)s' 邮件列表通过Web界面被创建。
为了激活该邮件列表，需要对/etc/aliases给予适当的更新。
同时需要运行程序newaliases
以下为需要添加的/etc/aliases相关项
`%(listname)s' 邮件列表通过Web界面被移除。
为了完全删除该邮件列表，需要对/etc/aliases给予适当的更新。
同时需要运行程序newaliases
以下为需要删除的/etc/aliases 相关项:
队列管理器的主锁无法获得，可能另一个主队列管理器正在运行。
队列管理器的主锁无法获得，可能其他主机上的某些进程正在使用它。
我们不能越过主机来测试过期的主锁，所以您必须手动测试。
或者，如果您知道主锁已过期，用 -s flag 来重启mailmanctl。
主锁文件: %(LOCKFILE)s
主锁主机: %(status)s
正在退出。 队列管理器的主锁无法获得。可能存在一个过期的队列管理器主锁。
可以尝试使用 -s flag 来重启mailmanctl。
用户退信数的阈值（超过此值您的服务将被关闭）, 该值可设为浮点数。 该信件的内容类型(content type)被明确禁止 该信件的内容类型(content type)没有被明确禁止 该信件的文件扩展名被明确禁止 该信件的文件扩展名没有被明确禁止 新闻组的节制策略 要链接的Usenet新闻组名 新的地址 %(newaddr)s 已经是成员了 您请求的新地址 %(newaddr)s 已经是邮件列表 %(listname)s 的成员了,
但是您仍然请求对这个地址进行全局的修改.
确认后, 其他包含 %(safeuser)s 这个地址的邮件列表将被修改. 下一则摘要将作为第
%(volume)s册，%(number)s号发送。 取消某成员退信信息所需天数，在此天数内若系统未收到新的退信，则丢弃以前保留的退信信息。
该值应为一个整数。 发出<em>你的成员资格被禁止</em>警告的间隔天数. 此值必须是整数。 该列表的公共名字(仅能做大小写改变)。 您的邮件命令的执行结果提供如下。
附件中是您的原始信件。
您的邮件命令执行结果 %(hostname)s的站点管理员为您的邮件列表 %(listname)s 修改了口令。新口令为：
%(notifypassword)s
在以后的管理工作中请务必使用新口令。您现在可以登录到您的列表中，把口令修改
得更合乎您的口味。访问您的列表管理页：
%(adminurl)s
订阅者列表 文本将作为html片段对待，<em>除了</em>
换行会被转换成<br> - 所以你能使用链接，
预定格式文本等等，但是不要使用回车，除非你打算
新建段落。预览你的改变 -
错误的html(像一些没有结束的html结构)
能影响整个列表信息页面的显示。 主题过滤器根据您在下面指定的<a
href="https://docs.python.org/2/library/re.html">
正则表达式</a>来对收到的邮件进行分类。如果某邮件的<code>Subject:</code>
头或<code>Keywords:</code>头匹配一个主题过滤器，那么此邮件将在逻辑上
被放进一个主题<em>桶</em>。每个列表成员都可以选择只从邮件列表中接收属于
某个或某几个主题桶的邮件。不属于用户注册的任何主题桶的信件将不会被投递
到列表中。
<p>注意，此特性只工作在普通投递模式，而不工作于摘要投递模式。
<p>您也可以在<a
href="?VARHELP=topics/topics_bodylines_limit">topics_bodylines_limit</a>
指定配置选项以在信件正文中寻找<code>Subject:</code>头和<code>Keywords:
</code>头。 主题匹配器将在信件正文中扫描这么多行以寻找要匹配的主题关键字。
当这么多行都已经扫描完或者遇到一个不象头部的行时，扫描终止。
若这个值设定为0，则将不会对正文进行扫描(也就是说，只有<code>Keywords:
</code>头和<code>Subject:</code>头会被扫描)。把这个值设为负数，则所有
的行都将被扫描，直至遇到一个不象头部的行。
主题模式 '%(safepattern)s' 不是一个合法的正则
表达式。它将被丢弃。 变量'm'是 %(listname)s 的MailList实例 没有挂起的请求. 每个邮件列表有两个管理者，他们扮演着不一样的角色。
<em>列表管理员</em>拥有最大的权力。
他们可以通过这些管理页面
改变任何列表配置变量。
<p><em>列表主持人</em>的权力受到一定的限制，
他们不能改变列表配置变量，但他们允许管理一些
待处理的管理请求，包括同意或拒绝保存的订阅请求、
丢弃邮件等。当然<em>列表管理员</em>也能够管理
未处理的请求。
<p>为了将列表所有者的职责分给管理员
和主持人，你必须
<a href="passwords">设置一个单独的主持人密码</a>，
和提供<a href="?VARHELP=general/moderator">列表主持人的邮件
地址</a>。注意，你在这里改变的区域定义的是列表管理员。 每个邮件列表有两个所有者角色。
<em>列表管理员</em>是控
制该列表所有参数的成员。
他们可以通过这些管理页面
改变任何可变的列表配置变量。
<p><em>列表主持人</em>有其他一些限制的许可；
他们不能改变列表配置变量，但他们允许管理一些
待处理的管理请求，包括同意或拒绝保存的订阅请求，
和丢弃邮件。当然<em>列表管理员</em>也能够处理
未处理的请求。
<p>为了将列表所有者的职责分给管理员
和主持人，你必须
<a href="passwords">设置一个单独的主持人密码</a>，
和提供<a href="?VARHELP=general/moderator">列表主持人的邮件
地址</a>。注意，你在这里改变的区域定义的是列表支持人。 没有要发送的摘要。 在删除邮件列表<b>%(listname)s</b>时出现了一些问题。
联系您的站点管理员 %(sitelist)s 以获取详情。 这些是列表支持的自然语言，注意：必须包括
<a href="?VARHELP=language/preferred_language">
默认语言</a>。 这些策略控制Mailman中的自动退信处理系统。下面是对其工作方式的
简要说明.
<p>一旦收到一封退信, Mailman尝试从中抽取两条信息: 消息的目的成员
的邮件地址, 以及导致退信的问题的严重性. 严重性可能是 <em>严重</em> 或
<em>轻微</em> 这分别意味着致命错误, 或仅是传送错误. 不能决定时就认为是
"严重".
<p>如果退信中得不到成员地址, 那么这封退信通常被忽略掉. 另外, 每
个成员都被赋予一个<em>退信值</em> 且每当遇到一个来自某成员的退信,
我们就增加该成员的退信值. 严重的退信增加1, 而轻微的退信增加0.5.
每天我们只增加一次退信值, 因此急事我们一天内从一个成员处收到10
退信, 他的退信值当天也仅增加1.
<p>若一个成员的退信值大于 <a href="?VARHELP=bounce/bounce_score_threshold">退信值
阈值</a>, 那么他的订阅就被禁止了, 一旦被禁止,
这个成员就不在收到列表里的任何消息, 除非他被列表管理员或该用户
自己显式地重新开禁然而,他会收到相应的提示函,告知他已被禁止,
, 提示函里同时会包含关于用户如何开禁的信息.
<p>你既可控制该成员收到的 <a href="?VARHELP=bounce/bounce_you_are_disabled_warnings">提示函 数量</a>也可控制提示函发送的
<a href="?VARHELP=bounce/bounce_you_are_disabled_warnings_interval"
>频率</a>.
<p>有几个重要的配置变量; 若一段时间不再从该用户处收到退信
,退信信息就被 <a href="?VARHELP=bounce/bounce_info_stale_after">认为 过期</a> 而被取消. 因此通过调整这个时长, 和刚才提到
的分数阈值, 你就能控制退信的用户多快被禁止. 您应该根据您的列表的
发信频度和通信量同时调节这两个值. 第三 当该邮件列表和其他邮件列表一起被列出、一起出现
在标题中等，在这些情况下，使用这个短语。
该短语要简洁，这样你才容易理解，同时它
还要能标识出列表。 这是一个 %(also)s 隐藏列表，这意味着成员列表仅对列表管理员可见。 这是一个 %(also)s 私有列表，这意味着非成员无法访问成员列表。 这是一个 %(also)s 公共列表，这意味着成员列表对任何人都可见。 这是一个关闭的列表，这意味着你的订阅请求将被暂缓以待
批准。列表管理员作出决定后将通过电子邮件通知你。 这是当<a
href="?VARHELP=general/reply_goes_to_list">reply_goes_to_list</a>
选项被设置为<em>显式地址</em>时，被设置在<tt>Reply-To:</tt>中的地址。
<p>有很多原因不建议覆盖<tt>Reply-To:</tt>头部
其中一个原因是很多发布者依赖他们自己的
<tt>Reply-To:</tt>设置来携带有效的回复地址。
另一个原因是修改<tt>Reply-To:</tt>会使得发送
单独回复变得困难。对这个问题的综合讨论见<a
href="http://marc.merlins.org/netrants/reply-to-harmful.html">`Reply-To'
Munging Considered Harmful</a>。不同意的观点见<a
href="http://marc.merlins.org/netrants/reply-to-useful.html">Reply-To
Munging Considered Useful</a>。
<p>一些邮件列表限制邮递权限，与之相关的有一个专用于讨
论的列表。`patches'或`checkin'都是这样的列表，
在这些列表里，版本控制系统会发送软件的修改信息，
但关于这些修改的讨论在开发者列表中进行。
为了支持这样的邮件列表，这里指定显式的<tt>Reply-To:</tt>地址。
你还必须将<tt>reply_goes_to_list</tt>变量指定为
<tt>显式地址</tt>
<p>注意，如果原消息中包含
<tt>Reply-To:</tt>头部，它将被改变。 这是此邮件列表使用的默认自然语言，如果邮件列表
<a href="?VARHELP=language/available_languages">支持的语言多于一种
</a>，用户可以选择选择他们与列表交互时使用的语言。此后其他所有的交互
都将使用用户选择的语言。这项规则适用于基于网页和电子邮件的信息，但不
适用于列表成员所发送的邮件。 该列表 此列表不支持定期投递摘要。 次列表没有成员。 该列表受限制；您的信息没有经过批准。 此列表仅支持投递定期摘要。 此列表仅能订阅摘要！ 这个选项控制Mailman对流经该邮件列表的消息的
<tt>Reply-To:</tt>头部的处理方法。
当设置为<em>发布者</em>时，Mailman不会添加
<tt>Reply-To:</tt>头部，即使原消息中已
经有一个头部了，它不会被删除。将这个值设置
为<em>该列表</em>或<em>显式地址</em>时，会
导致Mailman在所有的消息中插入一个指定的<tt>Reply-To:</tt>
头部，如果必要的话，还会覆盖原消息的头部
(<em>显式地址</em>插入<a
href="?VARHELP=general/reply_to_address">reply_to_address</a>的值)。
<p>有很多原因不建议覆盖<tt>Reply-To:</tt>头部
其中一个原因是很多发布者依赖他们自己的
<tt>Reply-To:</tt>设置来携带有效的回复地址。
另一个原因是修改<tt>Reply-To:</tt>会使得发送
单独回复变得困难。对这个问题的综合讨论见<a
href="http://marc.merlins.org/netrants/reply-to-harmful.html">`Reply-To'
Munging Considered Harmful</a>。不赞成的观点见<a
href="http://marc.merlins.org/netrants/reply-to-useful.html">Reply-To
Munging Considered Useful</a>。
<p>一些邮件列表限制邮递权限，与之相关的有一个专用于讨
论的列表。`patches'或`checkin'都是这样的列表，
在这些列表里，版本控制系统会发送软件的修改信息，
但关于这些修改的讨论在开发者列表中进行。
为了支持这样的邮件列表，选择<tt>显式地址</tt>，
将下面的<tt>Reply-To:</tt>值设置为相应的用于
讨论的列表地址。 这个页面允许列表属主从系统中永久性地删除此邮件列表。
<strong>此动作是不可撤销的</strong>，所以在确认删除之前请您三思。
<p>注意，将不会向列表成员发送任何的警告信息，并且在删除列表后，所有发送给
此列表或者列表管理员的信件都将被退回。
<p>您可以在删除列表的同时也删除列表的邮件存档。但是我们强烈建议您<strong>
不要</strong>删除这些存档，因为它们是您的邮件列表的历史记录。
<p>为安全起见，您将被要求再次确认列表管理口令。
您可以在本小节中配置订阅及成员身份公开策略。您也可以
控制此列表是否是公开的。参考<a href="%(admin)s/archive">归档选
项</a>小节以获取归档相关的隐私策略。 您可以在本小节配置一些垃圾邮件过滤器，这将有助于减少
列表成员收到的垃圾邮件数量。
您可以在本小节配置一些基于收信人地址的过滤器。 这个设置检测新闻组的节制策略以及它和邮件列表节制策略的相互作用。该设置仅应用于
您正通过网关连接<em>至</em>的新闻组，所以如果您只是从Usenet
向外连接，或者你正通过网关连接的新闻组不受节制，
请将该选项设为<em>不</em>。
<p>如果新闻组受节制，您可以将该邮件列表设为新闻组的缓冲地址。通过
选定<em>节制</em>，一份额外的消息会放置到审核程序中。所有发
送到邮件列表的信息将在被发送到新闻组或者邮件列表成员之前经过审核。
<p><em>注意如果信息中包含一个<tt>Approved</tt>头部，同时头部里还有
列表的管理口令，则这个暂存测试将被绕开，将允许有特权的发送者直接
往列表和新闻组发送信息。</em>
<p>最后，如果新闻组受节制，但是您又想要使用开放的发信策略,
您可以选定<em>开放的列表，节制的组</em>。这将使用标准的
Mailman节制设施，但是在所有通过网关发送到Usenet的信息中
加上了一个<tt>Approved</tt>头部。 这些文本将被加在向列表发送的消息的主题行前，
用来在收件箱中区分列表消息。
这里简洁才是受欢迎的，将长长
的邮件列表名缩写更简洁的形式就
行，只要它仍能唯一标识邮件列表。
你也可以用%%d替代符添加序列号。
例如：[listname %%d] -> [listname 123]
(listname %%05d) -> (listname 00123)
这个值可以是您新闻服务器的名字，或者是 name:port 的形式，
port是一个端口号。
新闻服务器不是Mailman的组成部分。您必须已经可以访问一个NNTP服务器，
并且此NNTP服务器必须已把此邮件列表所在的主机认作是可以阅读和发布新
闻的主机。 这个值，将被加到新订阅者的欢迎消息的前面。欢迎消息
的其余部分已经描述了邮件列表的地址和URL，
所以你不必在这里包含任何的这类信息。
这应该仅仅包含使命性的，像方针，团
队方向这类的说明。
<p>注意这些文本将根据一下规则被封装：
<ul><li>填充段落，使得每行不超过70个字符。
<li>任何以空白符开始的行不被填充。
<li>空白行分割段落。
</ul> 星期四 为了完成邮件列表的创建，您需要编辑/etc/aliases或者相关文件，
并添加如下行内容，然后运行newaliases程序：
为了从 %(realname)s 退订，获得口令提示函，或者改变你的订阅选项 %(either)s输入你
用来订阅的电子邮件地址:
<p><center> 要访问未公开列表的管理员配置页面
, 打开一个与此相似的链接, 但是附加一个 '/' 和
%(extra)s列表名。 如果您有权限,
你还可以 <a href="%(creatorurl)s">创建一个新的邮件列表</a>.
<p>列表常规信息可在这里找到 本日主题 (%(msgcount)d 封信件) 本日主题:
该信息的收件人太多 主题 %(i)d 主题过滤器详情 与每封邮件进行匹配的主题关键字，每行写一个。 主题名 主题的说明需要包含一个名字和一个模式。不完整
的主题将被忽略。 主题 星期二 土耳其语 如果你打算手工添加订阅者，但不想让他们知道时，关掉这个功能。
当你想将成员从一个其他类型的列表透明地移一个Mailman列表时，
这个选项特别有用。 如果你想向你的成员每月发送一次密码提示，启动这项功能。
注意成员可能仅用他们各自的密码提示功能。 U 乌克兰语 保护列表设置 未捕获的退信通知 Unix-From行被改变： %(lineno)d 未知的语言: %(lang)s 未知的列表： %(listname)s 未知的虚拟主机: %(safehostname)s 解锁一个被锁住的列表，但是并不对其执行Save()。
如果解释器因为接收到一个信号而退出，或者os._exit()被调用，这将不会被执行。
但是当发生异常时，将会被调用。
解锁(但不保存)列表： %(listname)s 取消订阅 退订或编辑选项 取消订阅的请求 退订请求 取消订阅通过了验证 取消订阅成功 退订结果 为文章 %(seq)s 更新HTML 正在升级 Mailman 2.0 pending_subscriptions.db 数据库 正在升级 Mailman 2.1.4 pending.pck 数据库 正在升级新闻组水印 为归档 [%(archive)s] 更新索引文件 正在升级邮件列表: %(listname)s 升级持有请求的数据库 正在升级,从版本%(hexlversion)s 到 %(hextversion)s 用法： 使用此选现来根据特定的头部值禁止垃圾邮件。目标值是一个
用来与指定头部进行匹配的正则表达式。匹配以大小写无关的形式进行。
以'#'开头的行将被作为注释而忽略。
<p>例如：<pre>to: .*@public.com </pre>是说要延缓邮件头<em>To:</em>
中包含'@public.com'的所有信件。
<p>注意，开头的空格将被从正则表达式中清除。可以通过许多方法绕开此
限制，例如转义或者用括号把空白括起来。 使用这个选项来移除以下类型的附件. 每行应包含一个MIME
<tt>类型/子类型</tt>的名字, 例如 <tt>image/gif</tt>. 若省略子
类型, 则将移除所有匹配主类型的附件, 比如 <tt>image</tt>.
<p>空行会被忽略.
<p>参见 <a href="?VARHELP=contentfilter/pass_mime_types" >pass_mime_types</a>, 那里有安全附件类型的列表. 使用此项来移除内容类型不匹配的附件. 要求和格式跟 <a href="?VARHELP=contentfilter/filter_mime_types"
>过滤MIME类型</a>.
<p><b>注意:</b> 如果你向此清单增加了项目但没有同时增加
<tt>multipart</tt>, 所有带附件的消息都将被过滤掉 用户 %(addr)s 已从列表: %(listname)s中删除。 用户 地址/姓名 用户定制的选项页面 正在使用的Mailman版本: 值 查看或编辑列表的配置信息. 选择本页所用的语言： 访问订阅者列表 访问订阅者列表 访问列表管理页面 访问列表信息页面 警告: 忽略多重的未处理ID: %(id)s 警告: 不能获得列表 %(listname)s 的锁 警告：目录不存在： %(d)s 警告！您可能会遇到权限问题。 警告： 警告: 无法删除 %(src)s -- %(rest)s 非常抱歉, 但是您已经取消了订阅这个邮件列表.
如果您想要重新订阅，请访问
<a href="%(listinfourl)s">列表信息页面</a>. 星期三 每周 邮件的欢迎文本信息 欢迎加入"%(realname)s"的邮件列表 %(digmode)s 欢迎！ 订阅需要那些步骤？<br> 当"umbrella_list"被的设置指示该列表有其它邮件列表作为成员时，
像确认和管理通知这样的管理通知不被发送到成员地址，
而是发送到这些成员列表的拥有者。这种情况下，这个
设置的值被添加到成员账户明后来作为接收这些通知的
地址。`-owner'是典型的选择。当"umbrella_list"
被设置为"无"时，该设置无效。 当列表启用<a href="?VARHELP=nondigest/personalize">个性化设置(personalization)</a>时，
在邮件头部和尾部以下额外替换变量可用：
<ul><li><b>user_address</b> - 用户地址，转化为小写字母。
<li><b>user_delivered_to</b> - 用户订阅列表时使用的大小写相关的地址.
<li><b>user_password</b> - 用户口令。
<li><b>user_name</b> - 用户全名。
<li><b>user_optionsurl</b> - 用户选项页的URL地址.
</ul>
当一封邮件被发送到列表时，要执行一系列的步骤以确定列
表主持者是否必须首先对此信件进行审查。本小节包含对成员或非成员信
件的控制选项。
<p>如果列表成员的<b>节制</b>标志被打开，那么他的信件都将被暂存以待
审核。您可以控制成员信件默认情况下是否被暂存。
<p>非成员的信件可以单独的或成组的被自动
<a href="?VARHELP=privacy/sender/accept_these_nonmembers"
>接受</a>，
<a href="?VARHELP=privacy/sender/hold_these_nonmembers">暂存以
待审核</a>，
<a href="?VARHELP=privacy/sender/reject_these_nonmembers"
>拒绝</a>(被退回)，或者
<a href="?VARHELP=privacy/sender/discard_these_nonmembers"
>丢弃</a>。
任何没有明确指明接受，退回，或者丢弃的非成员信件都将被
<a href="?VARHELP=privacy/sender/generic_nonmember_action">非成
员通用规则</a>所过滤。
<p>下面的文本框中，每行只能添加一个地址。行首的字符 ^ 说明后面的是
一个<a href="https://docs.python.org/2/library/re.html"
>Python正则表达式</a>。反斜线请按照Python原始字符串的形式输入(也就是
说您只需要输入一个反斜线就可以了)。
<p>请注意，总是先做非正则表达式匹配。 当一册新的摘要开始时，册号增加
发行号被重置为1。 当新成员订阅此列表时，他们选项的初始设定从这个变量的设定获得。 当接收到非成员发送的信件时，发信者地址将与被显式指定为
<a href="?VARHELP=privacy/sender/accept_these_nonmembers"
>接受</a>，
<a href="?VARHELP=privacy/sender/hold_these_nonmembers">暂存</a>，
<a href="?VARHELP=privacy/sender/reject_these_nonmembers"
>拒绝</a>(退信)，或者
<a href="?VARHELP=privacy/sender/discard_these_nonmembers"
>丢弃</a>的地址进行比较。如果没有匹配，那么将执行此动作。 当成员想要离开列表时，他们会通过web或者email发送一个
退订请求。一般来说，您最好允许列表成员能够自由的退订列表，这样他
们就能够容易地把自己从邮件列表中移除(如果他们不能离开列表的话，会
觉得很烦)
<p>但是对某些列表，您可能希望在一个退订请求被执行之前需要经过列表
主持人核准。这种列表的例子包括公司的邮件列表，所有的雇员都要求是
列表的成员。 当受到摘要时，默认的格式是什么？ 若设置此项，则已订阅成员清单将受成员口令或管理员口令的保护。 当打开此选项时，列表中所有邮件都被紧急延缓。也就是都被暂时保存起来而不立即发送。
当你的列表邮件量不正常增多而你想要让此增长趋于缓和时打开此选项。 当您正要完成更改时... 当你使用附件时，附件被放在归档区，邮件中设置链接，这样成员可以通过网页浏览器来访问附件。
如果你想使附件完全不出现，可以使用内容过滤选项。 当你告知Mailman执行一个运行在新闻组上的catchup时，这意味着你
想开始向邮件列表连接找到的下一条新信息。所有在新闻组上的之前的
信息都将被忽略。这就好像你自己正在阅读新闻组，并且你给所有当前
信息标志了<em>读取</em>。通过catchup，你的邮件列表成员将看不到
任何之前的信息。 列表消息的回复被发送到哪里？
对大多数邮件列表来说，<em>强烈</em>推荐使用<tt>发布者</tt>。 向用户邮递时的默认方式是什么？ 虽然Mainman的退信检测器相当强大, 它仍不可能检测世界上
所有的退信格式. 鉴于如下两点理由, 你应该将这个变量设为<em>是</em>:
1) 如果这真的是来自某成员的永久性退信, 你应该手工移除这个成员, 而且
2)你可能想要向Mailman的开发者发一封邮件, 以便这种新的格式被添加到
已知格式集合中去.
<p>如果您真的不希望被打扰, 那么把这个变量设置成<em>否</em>, 这样这
样没有被正确检测的退信就直接被忽略, 而不会进行任何进一步的处理.
<p><b>注意:</b> 这个设置同样会影响发向您的列表的管理地址的消息.
这个地址是不被推荐的而且不应该收到任何消息但仍然可能有人给这个地址
发信一旦这种情况发生了, 同时这个变量被设置成<em>否</em>, 那么那些消息就被
忽略. 你可可能希望给列表的所有者地址和管理地址设置一个 <a href="?VARHELP=autoreply/autoresponse_admin_text">自动 回复消息</a>. 谁可以查看已订阅成员清单？ 每年 是 是的,放弃 是的,继续 您已经是这个邮件列表的成员了! 您已经订阅了! 您已经订阅过了。 您已经使用了那个邮件地址 您被禁止往该列表发送信息。 您不是邮件列表 %(listname)s 的成员 您没资格查看邮件列表的成员。 您没有创建新邮件列表的权限 您没有删除此邮件列表的授权 您还不是列表的成员。您是否已经退订了列表，或者修改了您的邮件地址？ 您可以通过下面的url访问您的个人选项： 在下面的表格中填入相关的信息,您就可以创建新的邮件列表了.
邮件列表的名称将用作向这个列表发送信息的主要地址,
它应该小写.
但列表创建之后,您不能对其进行修改.
<p>您还需要输入初始的列表拥有者的邮件地址.
当列表被创建后,列表的拥有者将收到通知和初始的列表密码.
列表的拥有者能够修改密码,以及添加或删除附加的列表拥有者.
<p>如果您想要让 Mailman 自动生成初始的列表管理密码,在下面的自动生成域点击'是',
并将初始列表密码置为空.
<p>为了创建新的邮件列表,您需要适当的权限.
每个站点应该有一个 <em>列表创建者</em> 的密码,
您可以在下面的域中输入这个密码.请注意站点管理员的密码
同样可以作为认证信息.
如果一个地址是空的话你不能为它设置Reply-To:头部。 重设这些值。 除非<a href="?VARHELP=gateway/nntp_host">
新闻服务器字段</a>和<a href="?VARHELP=gateway/linked_newsgroup">
链接的新闻组</a>域已经被填写，你不能启动网关。 您没有提供正确的密码, 所以您的密码没有被改变
您可以先取回您的密码(不使用参数)，然后再试一次。 您没有输入正确的密码 您忘记了输入列表名称 您忘记了确定列表拥有者 您的密码错误 您已经成功地订阅了 %(realname)s 邮件列表。 您已经成功地退订了邮件列表 %(fqdn_listname)s。如果
您接收摘要投递的话，您还将收到一封摘要信息。如果您对于退订有任何的
问题，请联系列表管理员： %(owneraddr)s。 您已经退订了 %(realname)s 的邮件列表 您已经取消重新设置您的成员资格有效.
如果我们持续从你的地址收到退信,你地址将被从列表中删除. 您已经取消了对地址请求的修改. 您已经取消了您的订阅请求. 您已经撤消了您取消订阅的请求. 您有开启摘要模式的会员, 但是摘要模式被关闭。
这些人将接不到信件%(dm)r 您有开启非摘要模式会员，但是非摘要模式被关闭。
直到您修正上述问题前，非摘要模式会员将持续收到信件。%(rm)r 您已经成功地创建了邮件列表 <b>%(listname)s</b>
同时,通知已经发送到给了列表拥有者 <b>%(owner)s</b>.
现在您可以: 您成功地删除了邮件列表
<b>%(listname)s</b>. 您已经成功设置您的选项。 您关闭了摘要与非摘要信息的发送
这是不兼容状态。您必须从两者之中选择其一，
不然你的邮件列表基本是无法使用的。 您邀请了 %(address)s 加入您的列表, 但他们恶意
尝试确认一个加入别的列表的邀请, 我们估计您乐意了解这个情况. 但您不必采取任何行动。 您可能会收到最后一封摘要。 您不能让一个邮件列表订阅它自身！ 为了确认您取消订阅的请求,您必须选中复选框中 <em>取消订阅</em>
这一项. 您还没有取消订阅! 您必须先修正上述的无效地址. 您必须给出一个列表名称. 这里是 %(link)s 您必须指定一个列表。 您必须提供一个有效的电子邮件地址。 您没有被邀请加入此邮件列表。邀请已被废弃，列表的所有管理员都将收到此警告。 为防止有人无意替您订阅，将有确认函发送给您。 为防止有人无意替您订阅，将有确认函发送给您。一旦经
您确认，您的请求将被暂缓以待列表主持者审核。主持者的决定将通
过电子邮件告知你。 您将成为一个隐蔽的列表属主！ 你的<code>%(property)s</code>的新值中好像有一些
可以更正的问题。
将用预备的值代替。请
仔细检查这是你想要的结果。
为了取消向邮件列表<em>%(listname)s</em>发送信件,您需要通过验证.
<ul><li><b>发送者:</b> %(sender)s
<li><b>主题:</b> %(subject)s
<li><b>原因:</b> %(reason)s
</ul>
点击 <em>取消发送</em>按钮来取消发送.
<p>或者点击 <em>继续等待批准</em> 按钮,继续允许列表主持者批准或者拒绝信件. 为了完成对邮件列表<em> %(listname)s </em>的地址请求的修改,
您必须通过验证. 您的订阅身份是:
<ul><li><b>真实姓名:</b> %(fullname)s
<li><b>旧的邮件地址:</b> %(oldaddr)s
</ul>
您已经请求 %(globallys)s 更改您的邮件地址为
<ul><li><b>新的邮件地址:</b> %(newaddr)s
</ul>
点击下面的 <em>更改地址</em>来完成验证过程
<p>或者点击 <em>取消并且删除</em> 来取消对地址的更改请求. 为了完成对邮件列表<em>%(listname)s</em>的订阅请求,您必须完成验证.您的订阅设置如下;
可以做任何任何必要的修改,然后点击<em>订阅</em>完成验证.
一旦您完成了订阅请求的验证,您将看到您的帐户的选项页,您可以通过它进一步
定制您的成员选项.
<p>注意: 如果您的订阅完成了验证,您的密码会发送到您的邮箱里.您可以
通过访问您的个人选项页修改它.
<p>或者,如果您不想订阅这个列表，可以点击<em>取消我的订阅请求</em> 为了完成对 <em>%(listname)s</em> 的取消订阅请求,您必须确认.
当前,您订阅的身份是:
<ul><li><b>真实姓名:</b> %(fullname)s
<li><b>邮件地址:</b> %(addr)s
</ul>
点击下面的 <em>取消订阅</em> 按钮，来完成确认.
<p>或者点击 <em>取消并且删除</em> 来撤销您的取消订阅请求. 为了继续对邮件列表<em>%(listname)s</em>的订阅请求,您必须完成验证.您的订阅设置如下;
你可以做任何必要的修改,然后点击<em>订阅这个列表...</em>完成验证.
一旦您完成了订阅请求的验证,列表主持者会批准或者拒绝您的成员请求,您将收到他(们)
决定结果。
<p>注意: 如果您的订阅完成了验证,您的密码会发送到您的邮箱里.您可以
通过访问您的个人选项页修改它.
<p>或者,如果您改变了主意，不想订阅这个邮件列表,
您可以点击 <em>取消我的订阅请求</em>. 您需要对加入 %(listname)s 邮件列表进行确认 您需要对退出 %(listname)s 邮件列表进行确认 您的当前操作设置: 您的决定 您的邮件地址: 您在邮件列表 %(realname)s 当中的成员资格由于您过多的退信被禁止了.
如果您希望能够重新向您的地址发送消息,您必须通过验证.
下面是我们的文本信息:
<ul><li><b>成员地址:</b> %(member)s
<li><b>成员姓名:</b> %(username)s
<li><b>收到最后一次退信的时间</b> %(date)s
<li><b>在您被永久的从这个邮件列表中删除之前还剩下大约的天数:</b> %(daysleft)s
</ul>
点击 <em>重新设置您的成员资格有效</em> 按钮以继续接收来自这个邮件列表的信件.
或者点击<em>取消</em> 按钮 推迟重新设置有效您的成员资格.
您的信件带有可疑的邮件头 您发送到 %(listname)s 的信件已经交由列表主持者审批 列表主持人认为您的信息不合适。 您的消息被拒绝了 您的信件过大，请修改信件内容至小于 %(kb)d KB 您的 %(listname)s列表的新口令 您新建的邮件列表: %(listname)s 您的密码是: %(password)s 您的口令不匹配。 您的真实姓名: 您的请求已经被转发给列表管理员以待核准。 由于您提供的邮件地址不可靠，所以您的订阅请求没有被批准。 您的订阅请求被拒绝了，因为您提供的邮件地址是不可靠的。 您的订阅要求已经转发给了列表管理员 %(listowner)s 。 您的订阅请求已经被收到，并将很快被处理。依赖于此列表的配置，您的注册请求
可能需要您通过邮件进行确认，或者需要由列表管理员批准。如果需要进行确认的
话，很快您就将收到一封确认函，确认函里将包含更进一步的指导信息。 因为 %(x)s ，您的订阅请求被搁置了。您的请求已经被转发给列表管理员。在列表管理
对您的请求作出决定后，您将会收到邮件通知。 您的取消订阅的请求已经发送给列表管理员去审查。 您的退订请求已被收到并转发给列表管理员以待其核准。
管理员作出决定后您将受到一封邮件通知。 您发送到 %(realname)s 邮件列表的加急信息没有投递授权。附上Mailman收讫的原始信息。
[被内容过滤程序删除的信件] [无退信的细节信息] [没有给出原因] [没有给出原因] [没有描述] 仅一个滞留信息. 承认 管理列表概览 全部滞留信息. 所有的 %(esender)s's 滞留信息. 同样 文章数据库文件必须是 %(octperms)s: %(path)s 文章文件 %(filename)s 丢失 属性"%(k)s"被修改 属性"%(k)s"被忽略 作者 由管理员 (由)列表管理员 由您 (由)您自己 对比原始模板检查翻译后的模板
如果html长不为零,则搜索<MM-*>标签 和原始字符串比较,检查翻译 检查读入和输出的不同 检查cgi-bin许可权 检查 %(prefix)s 的许可权 查看 %(dbfile)s 的所有者 查看 %(file)s 的权限 检查 %(pwfile)s 的许可权 检查列表数据的许可权 检查 %(private)s 的许可权 检查 %(wrapper)s 的set-gid许可权 无法删除旧文件 %(pyc)s -- %(rest)s 日期 天 天 用户已经禁止投递 启用投递 接收关闭 接收开启 摘要 摘要尾部 摘要头部 目录许可权必须至少为02775: %(d)s 目录许可权必须是 %(octperms)s: %(path)s 禁止 完成 由于退信 因为过多的退信 邮件地址和 处理文章存档
文件许可权至少是660： %(path)s 正在修复您旧的html存档上所有的错误来使b6工作
如果您的存档很大, 可能需要花费一两分钟时间... 因为未知原因 在这里找到： 从 %(start)s 到 %(end)s 通用列表概览 去除旧的源文件 全局地 隐藏 语言 合法的值： 列表创建者 列表信息 可用的邮件列表的清单 需要列表名 匹配的邮件列表： mbox文件许可权必须至少为0660: 成员地址<br>成员姓名 成员 消息无法解析: %(filebase)s 修改 n/a 没有日期 没有列表文件 == 无事可做, 退出 没有主题 无副本 没有邮件 没有邮件<br>[原因] 不可用 除了我 除了我 关闭 开启 选项 解析一个 .po文件, 读出消息标识和消息串 口令 纯文本 私人的 私人邮件存档 正处理邮件列表： 公开的 公有邮件存档 删除%(src)s 删除目录%(src)s 及其目录内所有文件 返回 %(categoryname)s 选项页面. 正确 正确 从原始文件扫描一串字符串 扫描翻译后的字符串 对比消息标识和消息串扫描po文件 站点 不被允许的大小 源许可权必须是 %(octperms)s: %(path)s 失效的被锁文件 stop 和end 命令相同
主题 %(name)s 的订阅需要管理员批准 对 %(realname)s 的订阅请求需要列表主持者批准 列表管理概览页面 列表管理员 邮件列表简介页 线索 未知的发送者 取消订阅 退订需要列表主持人批准 升级旧的qfiles 查看来自 %(esender)s 所有的信息