Viewing File: /usr/local/cpanel/3rdparty/mailman/messages/ja/LC_MESSAGES/mailman.mo

l.\.\^Z_w_+e`;`V`'$aLcT	RdNmoq|r	aseku
vvv9vR2xyy_zUgzzl{h|_~b0!!$Ձ&#%J!p&҂.DYwZZ_qz`&/_VRƅ5O:"]bizw}ʈWΈ&&<Md-}3ߊ#
815j3*ԋ(!C$e&,.ތ'
35i(,q!C:~&=/!,'N$v,4ȑP(N%w7,Ւ=+@!l*&%& F(g",.JZ+vIKnK
NYbir~
-
Ę@Ϙ9 Jk 7ř(&;Nb+aӚ%5"[)~B/1J\beTȡW1uWBWfצr>8$,-Z6%-S(-)V%0ت*	4\K	L#fVۮӯhhd!9Kd^`b57Ozg4%= "bC*OF!qh6.H/?Nf'z2
(AGbq)
%7P".sf%EVsT0[YAr
0	BLUY`w$BA,`.3,#Im?*).Gbx)4&A[z_H%b%'U,$5(Z#Te9
C`w'/?O4g9TY%#E)i%
*)-E0sRSukM1		Vv!
7
)H]%t.z "
&,/,\}[ahy+5+ 
2 
@ N ^ n }  * d !0!	"")$o/$$$((-,/2<4N4)[4444/434)'5$Q5v5~56
6&6!@6b66#6066
77(7287,k777	777#77/8	38=8A8;J878
88<<<<'>>1>??#????@@@#@C)@m@]@@@@OOORRYRhR'|RRRR$RRS1)S_[SS"SS
SxT){TT9TT&T$U06U%gUUUFU2*W1]W0W	WWeZ^\x=^^K_ZdLNe=e}e6Wfmf.g+hlNl*#m,Nm!{m m"mmmn/nGn__n?oqs6sst#tQAtvvvviwxxx"x!y("yKycyjy6~yyqy@zHzLzTz]zazfzjzozvz!z(zzj{{{{
{{{;{1~	!%)-WZdۈ09TXBUZYLXaa3p^6Kɏ'
CNhu|
/3"@2^$%`Óy$w{

ǗٗURF"Ϙ#8VgDx6 !5%W}	,	6!@bfn.=
J#Uy
0?-Es2;85Jdgxp.AXgy0ݠ
! B4`&<ס-K#eŢݢ:%+QbV6		% 82kz9"\#k=&ͱ$
'+4"ó˳_ϳ/2ANK.3b}:ɺSU*Լ+=O	n
x	(Ͻ/,55bYD
/O7>
) 'F,` 87{9y;)',?l
/BX4xw%o	j!;P58N	5\`hpw/JPa-<M! -B+p:<#Pt<$*26.B"q	(;<$ a:%Z01E)w!	"r"*BumgK)[--U0.._#/g/u/ra0;031"D1Wg22J3O
4Z4)5J-5Mx55:6u6h7P8K9KT9799|u:/:c";[;; <&=
3=&A=h=&n==	=z=!>5>L>^>n>?"?A???@@!@3@	G@Q@)h@@@@@'@A'AFAfA~AAAAApBtB|BBB&xK"KPK=L[QLNLwLtM:N9O
1P:<PwQ\RyTVX-X3Y6EY7|YYGZ6Z6[*\?]_0__L}``*a6a(bbac30d;dd{dfvfTghRh%iijVbknk!(l0Jl{l1mO7nroYoTqq`r4r5s6Ms7s's7s0tMtPJuuUv
vw6zyYy"z[.z{{C>}Vmك6G~EЍA/Ŏ-
|֚qSnś4pݜN	7+Am7(-.ʭ1+gU/O46 W[Rm&"'<<yk	"6Q&l-k !3!J6l+.#$=9bOX0N!` 
0J\r/6(&/O&0	,5!-*Xtv;~G1by0g
u#z13eDdqx|4.(6_
554(2]2];!*]p%!$G3-{=1,.nG
'R zsn'+'S3073h&~p[.!	
,KC&CDb
%^67H#f#CP?PcVEVk  !#-"%Q"%w"!""";"$#?#V#Z#i#x######/#%$9$S$m$t$$$$$g$6/%8f%%% % %"&!>&`& ~&,&&&&&&'''
%'
3'A''S'4{'''['&(+(:(S(i(|((/({(V)	j)t)>)))***#*3*<*N*	[* e*** ***+#+4+8+K+O+"W+
z++++
+	+++++.+,,,,.,G,N,.^,(,,,4,,-=-C-$J-o-.-
----+-.)%.O.8W.8..../#/2/A/*G/r/////"/00#13ZE445$5=Z5O5578ACWEFFYH	JJJ+JYK
qL|LWMV`MkM#NNOsXPPMQ!Q!Q$R>RWR&uR'R"RRS"#SFS#bSSS"SSS"T2TjPTjT&U
6UAUSUmUIUUUWV[V4hV0VV<aWWWWWWeWmDXXXXDX)1Y6[YY(Z:;Z.vZZZ-ZE[TI[Q[)[\*8\!c\\)\-\5\02]3c]']])]w] u^^E__O_*G`7r`S`0`!/aQaoa#a4aVa=b[b/ub1b3bc)c"Ccfc|cc2c%cd'd5Ed9{dPd-e4eNf=]f:fMf$ggggg
ggg+h-h:5h7ph!hh$h#i8*i(ciiii4ii"i jW?j*j(j#jkm!mRm86opoo~oC_pbpq&qOqrFsttTxt5tu"u@Au}u	v:
v*Evpv#3w'Ww)w!ww5wx1xCExxxySzSpzIz{{[c|[|,}"H~Tk~N^#щӉՉ*^"f"qv{4%ύ4(*FS4/Վ(:B}	Ŗܖ ϗ :2NZ^#ݙ1OٜO)yy
ˠ!*!7Yb=3'q*(ģ'
&24Y<-,Bbxʥ'7
BE(!Ц2%*@%kU*&1%XC~
¨%ͨ"m0ELT7{s]ѬSCh7)(?P+]3DCF^Hk,4:Gb5FNBO\
))(<,e,L.;)AX	ak[p
$<TcrLamz
*Q|#
l@! .OT&YU/4:X
w
7R2*Lw<|"yVe
k}, ""Cf v $u{())(0@ q:74HQ^kt)	6
2=
 /3$5"Z(})'<d{
J(
:E
V(
=
C\


(-
V
r
$
W
7
S
^\i748&=d)m1-3#9W^5u>6T! 4v + 0!"%M%.d%$%$%% %&$7&\&%x&&&Z("*"+kB++++F,I.`.h.Y{..#///.060P0k0|00900E0
61A1E1I1P1T1X1\1`1g1v1 1r1!2>2E2R2p222.24m; S=$t==
==>>>3>?5?2@84@*m@(@&@2@A7.AEfAmCD1D(HDqD)yDDDDD
D
DE
E!E(2E'[EEE'EE,EFZ3FGnGWH?sHJJJJJJJKG!K/iKKKKK
KKK
LLL
.LN<L8L L&LM*)MTMNN $NENHNMNpgNOOOP!P
PPPP/PQ-+Q3YQ3QQQQQR$$RIRk`R RRSS/S$LS1qSSSSS,S)TD=T1T%TET# U'DUlU0UU
UUU(V.VHVMVGW%] 2]S]8\]]]y]9&^`^}^:^&^%^ _%_*_/__l`q`v`[{```/`))aSad0d5'e ]e
~e6eetewBfcf%g!Dgfgggggggh
hh*6hah~hhhhj*j3j

k$k:k=?k}kGlll<
m.GmvmmQr^r
ss.sMsds{s ss#s(s&t,tuvtx
z{'{B3{v{{${${{{!w ̈B&0Wv#;JR
*TG
˘јޘYKE	,ۜ'aYn0ȡ*$ۣ5Ҥ'0w52)
k%!GPS+b"ò1)3?#s
%ȳ=-ٶ!!)%K q
Ƿ.η =MbC'T|AqASdC'>If?4-%S$!F-?j\-=&3Z7'C_P996JvQJ_fc$*%O'u
,0O(x}!K'mm	

"-<K;\+4DSchr/2."a62P{?a_OCP(i*-&CoV(tjqMe*7+sc:j;.nHLC{mCqH..-\XG@e$1&V&}(*-E8UXN5V	W	Dl	
:
UxKZ5U*p$8r
6n Y a Sa!e!S"oo'
(*()]4))%))/2cy3A34H8A9*;$;=`=c=2>>T?U@r@@
@@0@@Q@;A@ACALAwAiBkBxBBBBBB&C-C3C#D(DCDLDUDlDDD:D<D$E5AE%wEE5EEEG[oI)JJ	K"K1KDKQKlKK
KKKKKKK+
L29LlL+L-L0LMM*"NMNNNN6O	:O'DOlO%QjRUDX2XX:pZ?[L[8\@]^^I^8`5``dddd
d
d:d-*eXeje(eeBf.f9gAg0Dh0uh.hNh:$i_ieRlllmn2nMnln+nn+oo$>pcp~pp3qgq;ar$rr_sFt*Lt9wt6t}t(fu2u8uu(v?vcv-w*w"xx7z|S~qC`E*H72*j6%$"6Yt8z_`QtƇ2Ka~'g'."	"0;
lwË؋ H"'kŒی
=Y*v"č!&%+&Q&x!10D
Wbs#4Jݏ(1pHѐ!
0>Di ;<xƒϒ	"9%N-tΓ$ӓ$"'.0_dmv
+
ڔ %82/k#$ԕ+%,&4[0t
ƖLՖ"%5[+`/їޗ
!&EWj&Ә

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
        See the non-hidden members of this mailing list.
    who password
        See everyone who is on this mailing list. The password is the
        list's admin or moderator password.

    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.

    who password [address=<address>]
        See the non-hidden members of this mailing list.  The roster is
        limited to list members only, and you must supply your membership
        password to retrieve it.  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!). If you provide the list's admin or moderator password,
        hidden members will be included.

%(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    %(status)s (%(how)s on %(date)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>&nbsp;<br> - owner addresses need to be fully-qualified names like "owner@example.com", not just "owner". <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 # -*- python -*-
# -*- coding: %(charset)s -*-
## "%(listname)s" mailing list configuration settings
## captured on %(when)s
## %(listname)s mailing list#%(counter)05d %(msgid)s%%%%%prog [options]

Export the configuration and members of a mailing list in XML format.%(addr)s is banned (matched: %(patt)s)%(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%(count)d %(realname)s moderator request(s) waiting%(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%(list_name)s address change notice.%(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 %(realname)s list.  It is possible that you are attempting
            to confirm a request for an address that has already been
            subscribed.%(newaddr)s is already a member of the list.%(newaddr)s is banned from subscribing to the
            %(realname)s list.  If you think this restriction is erroneous,
            please contact the list owners at %(owneraddr)s.%(newaddr)s is banned from this list.  If you
                      think this restriction is erroneous, please contact
                      the list owners at %(owneraddr)s.%(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 address change notification%(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 moderator request check result%(realname)s post acknowledgement%(realname)s roster authentication failed.%(realname)s subscription notification%(realname)s unsubscribe notification%(realname)s via %(lrn)s%(safetemplatename)s: Invalid template%(schange_from)s is not a member%(schange_to)s is already a list member.%(schange_to)s is already a member%(schange_to)s is not a valid email address.%(schange_to)s matches banned pattern %(spat)s%(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.
&lt;blank line&gt;(<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:/Quarantine; 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><a href="http://www.faqs.org/rfcs/rfc2822.html">RFC
                 2822</a> defines the <tt>Sender</tt> header and defines it
                 as "the mailbox of the agent responsible for the actual
                 transmission of the message."  Mailman replaces this header
                 by default with the list's bounce address.
                 
                 <p>While it is debatable if Mailman is such an agent, setting
                 this header helps directing bounces from some broken MTAs to
                 the right destination.  On the other hand, some mail
                 readers show unexpected behaviour if this header is set (like
                 missing addresses in forwarded mails and copies sent to the
                 bounce address on reply-to-all), so it can be disabled 
                 here.<b><i>either</i></b> <b>Cancel</b> and return to list administration<b>Invalid confirmation string:</b>
    %(safecookie)s.

    <p>Note that confirmation strings expire approximately
    %(days)s days after the initial request.  They also expire if the
    request has already been handled in some way.  If your confirmation
    has expired, please try to re-submit your request.
    Otherwise, <a href="%(confirmurl)s">re-enter</a> your confirmation
    string.<b>ack</b> -- Does the member get acknowledgements of their
        posts?<b>admin_member_chunksize</b> attribute not
            changed!  It must be an integer > 0.<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>host_name</b> attribute not changed!
                It must be a valid domain name.<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><ul><li><b>Munge From</b> -- applies the <a
             href="?VARHELP=general/from_is_list">from_is_list Munge From</a>
             transformation to these messages.

             <p><li><b>Wrap Message</b> -- applies the <a
             href="?VARHELP=general/from_is_list">from_is_list Wrap
             Message</a> transformation to these messages.

             <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/dmarc_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>

             <p>This setting takes precedence over the <a
             href="?VARHELP=general/from_is_list"> from_is_list</a> setting
             if the message is From: an affected domain and the setting is
             other than Accept.<ul><li><b>No</b> -- this applies dmarc_moderation_action to
               only those posts From: a domain with DMARC p=reject and
               possibly p=quarantine depending on the setting of
               dmarc_quarantine_moderation_action.
               <p><li><b>Yes</b> -- this applies dmarc_moderation_action to
               posts From: a domain with DMARC p=none if
               dmarc_moderation_action is Munge From or Wrap Message and
               dmarc_quarantine_moderation_action is Yes.
               <p>The intent of this setting is to eliminate failure reports
               to the owner of a domain that publishes DMARC p=none by applying
               the message transformations that would be applied if the
               domain's DMARC policy were stronger.<ul><li><b>No</b> -- this applies dmarc_moderation_action to
               only those posts From: a domain with DMARC p=reject.  This is
               appropriate if you are concerned about bounced messages, but
               want to apply dmarc_moderation_action to as few messages as
               possible.
               <p><li><b>Yes</b> -- this applies dmarc_moderation_action to
               posts From: a domain with DMARC p=reject or p=quarantine.
               </ul><p>If a message is From: a domain with DMARC p=quarantine
               and dmarc_moderation_action is not applied (this set to No)
               the message will likely not bounce, but will be delivered to
               recipients' spam folders or other hard to find places.?AA 'two dimensional' list of email address domains which are
               considered equivalent when checking if a post is from a list
               member.A confirmation message has been sent to %(newaddr)s. A digest has been sent.A list name is requiredA non-text attachment was scrubbed...
Name: %(filename)s
Type: %(ctype)s
Size: %(size)d bytes
Desc: %(desc)s
URL: %(url)s
A reminder of your password has been emailed to you.A terse phrase identifying this list.A wrapped message will either be a multipart/mixed message
             with up to four sub-parts; a text/plain part containing
             msg_header, a text/plain part containing 
             dmarc_wrapped_message_text, a message/rfc822 part containing the
             original message and a text/plain part containing msg_footer, or
             a message/rfc822 message containing only the original message if
             none of the other parts are applicable.AcceptAcceptsAcknowledge the member's postingAction 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 to take when anyone posts to the
             list from a domain with a DMARC Reject%(quarantine)s Policy.Action:Add <b>%(esender)s</b> to one of these sender filters:Add a non-fuzzy translation to the dictionary.Add members to a list from the command line.

Usage:
    add_members [options] listname

Options:

    --regular-members-file=file
    -r file
        A file containing addresses of the members to be added, one
        address per line.  This list of people become non-digest
        members.  If file is `-', read addresses from stdin.

    --digest-members-file=file
    -d file
        Similar to above, but these people become digest members.

    --invite
    -i
        Specify this if you only want to invite the users to a list
        instead of subscribing them.

    --invite-msg-file=file
    -m file
        This will prepend the message in the file to the invite email that
        gets generated when --invite is set.

    --welcome-msg=<y|n>
    -w <y|n>
        Set whether or not to send the list members a welcome message,
        overriding whatever the list's `send_welcome_msg' setting is.  This
        is ignored and the list's setting at the time of acceptance is used
        if --invite is set.

    --admin-notify=<y|n>
    -a <y|n>
        Set whether or not to send the list administrators a notification on
        the success/failure of these subscriptions, overriding whatever the
        list's `admin_notify_mchanges' setting is.  This is ignored and the
        list's setting at the time of acceptance is used if --invite is set.

    --nomail
    -n
        Set the newly added members mail delivery to disabled by admin.  This
        is ignored if --invite is set.

    --help
    -h
        Print this help message and exit.

    listname
        The name of the Mailman list you are adding members to.  It must
        already exist.

You must supply at least one of -r and -d options.  At most one of the
files can be `-'.
Add new item...Added  : %(s)sAdditional Member TasksAdditional settingsAdditionally, forward this message to: Address %(schange_from)s changed to %(schange_to)sAddress ChangeAddress to change toAddress&nbsp;ChangeAddress/name/timeAddress: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 blankAdmin address:Admin/moderator login pageAdministrative requests for mailing list:AdministratorAdministrator passwords did not matchAdministrivia 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 emptyAgain to confirm password: Alias names (regexps) which qualify as explicit to or cc
             destination names for this list.All runs all the above qrunnersAlready a memberAlready a member: %(member)sAlso 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.AlwaysAn 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 embedded and charset-unspecified text was scrubbed...
Name: %(filename)s
URL: %(url)s
An embedded message was scrubbed...
From: %(who)s
Subject: %(subject)s
Date: %(date)s
Size: %(size)s
URL: %(url)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.AnyoneApproveAprAprilArabicArchive messages?Archiving OptionsAs neededAsturianAugAugustAuthentication failed.Authorization failed.Auto-discard notificationAuto-generate initial list password?Auto-responderAuto-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 listAuto-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 approvalBBad --digest option: %(kind)sBad --nomail option: %(why)sBad MIME type ignored: %(spectype)sBad URL specificationBad approval password given.  Held message is still being held.Bad argument to -a/--admin-notify: %(arg)sBad argument to -w/--welcome-msg: %(arg)sBad argument: %(arg)sBad arguments: %(pargs)sBad arguments: %(strargs)sBad choice: %(yesno)sBad command: %(command)sBad confirmation stringBad digest specifier: %(arg)sBad email address for option %(k)s: %(v)sBad email address for option %(property)s: %(error)sBad email address providedBad moderation flag valueBad owner email address: %(s)sBad queue directory: %(qdir)sBad regular expression: Bad set command: %(subcmd)sBad status number: %(arg)sBad value for <a href="?VARHELP=bounce/%(property)s"
                >%(property)s</a>: %(val)sBad/Invalid email addressBad/Invalid email address: %(member)sBad/Invalid email address: blank lineBadly formed options entry:
 %(record)sBan <b>%(esender)s</b> from ever subscribing to this
                    mailing listBan listBanned address (matched %(pattern)s)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 notificationBounce detection sensitivityBounce processingBy 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 errorCan 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.CancelCancel and discardCancel held message postingCancel my subscription requestCancel postingCannot open mbox file %(mbox)s: %(msg)sCannot read address file: %(filename)s: %(msg)sCannot read both digest and normal members from standard input.Cannot unshunt message %(filebase)s, skipping:
%(e)sCannot unsubscribe non-members:CatalanCeiling on acceptable number of member posts, per interval,
               before automatic moderation.Ceiling on acceptable number of recipients for a posting.Change My Address and NameChange My PasswordChange 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 addressChange list ownership passwordsChange of address request confirmedChanging passwords for list: %(listname)sCheck 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 FormClear this member's <em>moderate</em> flagClick 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 addressConfiguration CategoriesConfigure 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.

ConfirmConfirm (*) - 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 approveConfirm change of address requestConfirm initial password:Confirm moderator password:Confirm poster password:Confirm subscription requestConfirm unsubscription requestConfirmation 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 succeededContent filtered message notificationContent&nbsp;filteringContinue awaiting approvalConvert 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 ListCreate a %(hostname)s Mailing ListCreate a new, unpopulated mailing list.

Usage: %(PROGRAM)s [options] [listname [listadmin-addr [admin-password]]]

Options:

    -l language
    --language=language
        Make the list's preferred language `language', which must be a two
        letter language code.

    -u urlhost
    --urlhost=urlhost
        Gives the list's web interface host name.

    -e emailhost
    --emailhost=emailhost
        Gives the list's email domain name.

    -q/--quiet
        Normally the administrator is notified by email (after a prompt) that
        their list has been created.  This option suppresses the prompt and
        notification.

    -a/--automate
        This option suppresses the prompt prior to administrator notification
        but still sends the notification.  It can be used to make newlist
        totally non-interactive but still send the notification, assuming
        listname, listadmin-addr and admin-password are all specified on the
        command line.

    -h/--help
        Print this help text and exit.

You can specify as many of the arguments as you want on the command line:
you will be prompted for the missing ones.

Every Mailman list has two parameters which define the default host name for
outgoing email, and the default URL for all web interfaces.  When you
configured Mailman, certain defaults were calculated, but if you are running
multiple virtual Mailman sites, then the defaults may not be appropriate for
the list you are creating.

You also specify the domain to create your new list in by typing the command
like so:

    newlist --urlhost=www.mydom.ain mylist

where `www.mydom.ain' should be the base hostname for the URL to this virtual
hosts's lists.  E.g. with this setting people will view the general list
overviews at http://www.mydom.ain/mailman/listinfo.  Also, www.mydom.ain
should be a key in the VIRTUAL_HOSTS mapping in mm_cfg.py/Defaults.py if
the email hostname to be automatically determined.

If you want the email hostname to be different from the one looked up by the
VIRTUAL_HOSTS or if urlhost is not registered in VIRTUAL_HOSTS, you can specify
`emailhost' like so:

    newlist --urlhost=www.mydom.ain --emailhost=mydom.ain mylist

where `mydom.ain' is the mail domain name. If you don't specify emailhost but
urlhost is not in the virtual host list, then mm_cfg.DEFAULT_EMAIL_HOST will
be used for the email interface.

For backward compatibility, you can also specify the domain to create your
new list in by spelling the listname like so:

    mylist@www.mydom.ain

where www.mydom.ain is used for `urlhost' but it will also be used for
`emailhost' if it is not found in the virtual host table. Note that
'--urlhost' and '--emailhost' have precedence to this notation.

If you spell the list name as just `mylist', then the email hostname will be
taken from DEFAULT_EMAIL_HOST and the url will be taken from DEFAULT_URL_HOST
interpolated into DEFAULT_URL_PATTERN (as defined in your Defaults.py file or
overridden by settings in mm_cfg.py).

Note that listnames are forced to lowercase.
Create another listCreating archive directory CroatianCull bad and shunt queues, recommended once per day.

This script goes through the 'bad' and 'shunt' queue directories and,
if mm_cfg.BAD_SHUNT_STALE_AFTER is > 0, it removes all files more than
that many seconds old.

If mm_cfg.BAD_SHUNT_ARCHIVE_DIRECTORY is a writable directory, the old
files are moved there. Otherwise they are deleted.

Only regular files immediately subordinate to the 'bad' and 'shunt'
directories are processed. Anything else is skipped.

Usage: %(PROGRAM)s [options]

Options:
    -h / --help
        Print this message and exit.
Current and new addresses must be different.CzechDailyDanishDatabase Updated...DecDecemberDefault language for this list.Default options for new members joining this list.<input
             type="hidden" name="new_member_options" value="ignore">DeferDeleteDelete this listDelete this mailing listDelivered by Mailman<br>version %(version)sDescriptionDescription:Description:  %(description)sDetailed instructions for the administrative databaseDigestDigest FooterDigest HeaderDigest mastheadDigest members:Digest optionsDisabledDiscardDiscard 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)sDiscardsDispatch digests for lists w/pending messages and digest_send_periodic set.

Usage: %(PROGRAM)s [options]

Options:
    -h / --help
        Print this message and exit.

    -l listname
    --listname=listname
        Send the digest for the given list only, otherwise the digests for all
        lists are sent out.  May be repeated to do multiple lists.

    -e listname
    --exceptlist listname
        Don't send the digest for the given list.  May be repeated to skip
        multiple lists.
Do not send a copy of a member's own postDowngrade detected, from version %(hexlversion)s to version %(hextversion)s
This is probably not safe.
Exiting.Dry run modeDump 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.
DutchEach header filter rule has two parts, a list of regular
             expressions, one per line, and an action to take.  Mailman
             matches the message's headers against every regular expression in
             the rule and if any match, the message is rejected, held, or
             discarded based on the action you specify.  Use <em>Defer</em> to
             temporarily disable a rule.

             You can have more than one filter rule for your list.  In that
             case, each rule is matched in turn, with processing stopped after
             the first match.

             Note that headers are collected from all the attachments
             (except for the mailman administrivia message) and
             matched against the regular expressions. With this feature,
             you can effectively sort out messages with dangerous file
             types or file name extensions.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 : ErrorEdit OptionsEdit the public HTML pages and text filesEdit this template forEmail My Password To MeEmail address:Emergency hold on all list traffic is in effectEmergency moderation of all list traffic is enabledEmergency moderation of all list traffic.Empty list passwords are not allowedEnabledEncode the
             <a href="?VARHELP=general/subject_prefix">subject
             prefix</a> even when it consists of only ASCII characters?End of English (USA)Enter confirmation cookieEnter new administrator password:Enter new moderator password:Enter new poster password:Enter one address per line below...Enter the email of the person running the list: Enter the name of the list: ErrorError Unsubscribing:Error inviting:Error opening list "%(listname)s", skipping.
%(e)sError opening list %(listname)s... skipping.Error subscribing:Error: EsperantoEstonianEuskaraExplicit <tt>Reply-To:</tt> header.Explicit addressExport an XML representation of a mailing list.FAQ 4.48.FebFebruaryFilter out duplicate messages to list members (if possible)Filter rules to match against the headers of a message.FinalizingFind 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:FinnishFirstFix 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)sFooter added to every digestFooter added to mail sent to regular list membersFor 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 reasonForward messages (individually) to:Forward of moderated messageForward to List OwnerForwarding optionsFourthFrenchFriFrom:From: %(sender)s on %(date)s
Subject: %(subject)s
Cause: %(reason)sFull PersonalizationFundamental list characteristics, including descriptive
            info and basic behaviors.GalicianGeneral OptionsGeneral 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 pageGeneral list personalityGenerate 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.
GermanGnu's Not UnixGo to list archivesGo to the general list information pageGreekGzip'd Text%(sz)sHTML Unchanged.HTML attachment scrubbed and removedHTML successfully updated.Header added to every digestHeader added to mail sent to regular list membersHeader filter rules require a pattern.
                Incomplete filter rules will be ignored.Header filtersHeader matched regexp: %(pattern)sHebrewHeld MessagesHide 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...HoldHold posts with header value matching a specified regexp.HoldsHost name this list prefers for email.Hostile address (illegal characters)Hostile address (illegal characters): %(member)sHostile subscription attempt detectedHow big in Kb should a digest be before it gets sent out?  0 implies no maximum size.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?HungarianIf a member posts this many times, within a period of time
               the member is automatically moderated.  Use 0 to disable.  See
               <a href="?VARHELP=privacy/sender/member_verbosity_interval"
               >member_verbosity_interval</a> for details on the time period.

               <p>This is intended to stop people who join a list or lists and
               then use a bot to send many spam messages in a short interval.

               <p>Be careful when using this setting.  If it is set too low,
               this can be triggered by a single post cross-posted to
               multiple lists or by a single post to an umbrella list.If a member's total posts to all lists in this installation
               with member_verbosity_threshold enabled reaches this list's
               member_verbosity_threshold, the member is automatically
               moderated on this list.

               <p>Posts which are counted towards this list's
               member_verbosity_threshold are all posts to any list with
               member_verbosity_threshold enabled that arrived within that
               list's member_verbosity_interval.If a post is addressed to this list and to one or more of
             the exclude lists, regular members of those lists will not be
             sent the post from this list, but if the poster is not a member
             of an excluded list, the post may not be accepted by that list
             which leaves the members of that list with no copy of the post.
             Setting this to Yes ignores any of the exclude lists of which the
             poster is not a member.If a posting has this number, or more, of recipients, it is
             held for admin approval.  Use 0 for no ceiling.If dmarc_moderation_action applies and is Wrap Message,
             and this text is provided, the text will be placed in a
             separate text/plain MIME part preceding the original message
             part in the wrapped message.If two poster addresses with the same local part but
               different domains are to be considered equivalents for list
               membership tests, the domains are put here.  The format is
               one or more groups of equivalent domains.  Within a group,
               the domains are separated by commas and multiple groups are
               separated by semicolons. White space is ignored.
               <p>For example:<pre>
               example.com,mail.example.com;mac.com,me.com,icloud.com
               </pre>
               <p>In this example, if user@example.com is a list member,
               a post from user@mail.example.com will be treated as if it is
               from user@example.com for list membership/moderation purposes,
               and likewise, if user@me.com is a list member, posts from
               user@mac.com or user@icloud.com will be treated as if from
               user@me.com.
               <p>Note that the poster's address is first tested for list
               membership, and the equivalent domain addresses are only tested
               if the poster's address is not that of a member.
               <p>Also note that moderation of the equivalent domain address
               will apply to the post, but other options such as 'ack' or
               'not&nbsp;metoo' will not.If you are a list member,
                          your password has been emailed to you.If you are a list member,
            your password has been emailed to you.If you are a list member, a confirmation email has been sent.If you are a list member, your unsubscription request has been
             forwarded to the list administrator for approval.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)30sIgnore regular_exclude_lists of which the poster is not a
             member.Ignoring bad pended data: %(key)s: %(val)sIgnoring changes to deleted member: %(user)sIgnoring held msg w/bad id: %(f)sIgnoring non-held message: %(f)sIgnoring non-text/plain MIME partsIllegal Email AddressIllegal email address providedIllegal list name: %(s)sIllegal option: %(opt)sImporting %(module)s...In addition to the above passwords you may specify a password for
pre-approving posts to the list. Either of the above two passwords can
be used in an Approved: header or first body line pseudo-header to
pre-approve a post that would otherwise be held for moderation. In
addition, the password below, if set, can be used for that purpose and
no other.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)sInitial list owner address:Initial list password:Initial list passwords do not matchInject 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.
InterlinguaInterrupted...Invalid :  %(addr)30sInvalid confirmation string.  It is
            possible that you are attempting to confirm a request for an
            address that has already been unsubscribed.Invalid confirmation string.  Note that confirmation strings expire
approximately %(days)s days after the initial request.  They also expire if
the request has already been handled in some way.  If your confirmation has
expired, please try to re-submit your original request or message.Invalid options to CGI scriptInvalid options to CGI script.Invalid password schemeInvalid request method: %(method)sInvalid value for property: %(k)sInvalid value for variable: %(property)sInvitation to join listInviteInvited: %(member)sIs 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)ItalianJanJanuaryJapaneseJulJulyJunJuneKoreanLanguage&nbsp;optionsLanguages supported by this list.Last autoresponse notification for todayLeave the initial password (and confirmation) fields
                blank if you want Mailman to autogenerate the list
                passwords.Legacy anti-spam filtersListList CharacteristicsList Helpbot: %(requestaddr)sList IdentityList Owners:  %(owneraddr)sList admin onlyList all mailing lists.

Usage: %(program)s [options]

Where:

    -a / --advertised
        List only those mailing lists that are publically advertised

    -p / --public-archive
        List only those lists with public archives.

    --virtual-host-overview=domain
    -V domain
        List only those mailing lists that are homed to the given virtual
        domain.  This only works if the VIRTUAL_HOST_OVERVIEW variable is
        set.

    -b / --bare
        Displays only the list name, with no description.

    -h / --help
        Print this text and exit.

List all the members of a mailing list.

Usage: %(PROGRAM)s [options] listname

Where:

    --output file
    -o file
        Write output to specified file instead of standard out.

    --regular / -r
        Print just the regular (non-digest) members.

    --digest[=kind] / -d [kind]
        Print just the digest members.  Optional argument can be "mime" or
        "plain" which prints just the digest members receiving that kind of
        digest.

    --nomail[=why] / -n [why]
        Print the members that have delivery disabled.  Optional argument can
        be "byadmin", "byuser", "bybounce", or "unknown" which prints just the
        users who have delivery disabled for that reason.  It can also be
        "enabled" which prints just those member for whom delivery is
        enabled.

    --fullnames / -f
        Include the full names in the output.

    --preserve / -p
        Output member addresses case preserved the way they were added to the
        list.  Otherwise, addresses are printed in all lowercase.

    --moderated / -m
        Print just the moderated members.  Ignores -r, -d, -n.

    --non-moderated / -M
        Print just the non-moderated members.  Ignores -r, -d, -n.

    --invalid / -i
        Print only the addresses in the membership list that are invalid.
        Ignores -r, -d, -n.

    --unicode / -u
        Print addresses which are stored as Unicode objects instead of normal
        string objects.  Ignores -r, -d, -n.

    --help
    -h
        Print this help message and exit.

    listname is the name of the mailing list to use.

Note that if neither -r or -d is supplied, regular members are printed first,
followed by digest members, but no indication is given as to address status.
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)sList already exists: %(safelistname)sList creator's (authentication) password:List membersList 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 subscriptionsList name is requiredList name is required.List name must not include "@": %(safelistname)sList name:    %(listname)sList of addresses (or regexps) whose posts should always apply
             <a href="?VARHELP=privacy/sender/dmarc_moderation_action"
             >dmarc_moderation_action</a> 
             regardless of any domain specific DMARC Policy.List of addresses (or regexps) whose subscriptions do not
             require approval.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)sList 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 the supported password hashing schemes and exit.  The scheme labels are
case-insensitive.List topic keywordsList traffic archival policies.List-specific text prepended to new-subscriber welcome
             messageList:List: %(listname)s, 	Owners: %(owners)sLithuanianLoading list %(listname)sLocking listLog inLog outLogoutMIMEMail deliveryMail&lt;-&gt;News&nbsp;gatewaysMail-to-News and News-to-Mail gateway services.Mailing list creation request for list %(listname)sMailing list creation resultsMailing list deletion resultsMailing list removal request for list %(listname)sMailmanMailman %(varname)s List Option HelpMailman Administrative Database ErrorMailman 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 alertMailman 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>MarMarchMass RemovalsMass SubscriptionsMass catch upMass catchup completedMass&nbsp;RemovalMass&nbsp;SubscriptionMaximum length in kilobytes (KB) of a message body.  Use 0
             for no limit.Maximum number of members to show on one page of the
             Membership List.MayMember filtersMember name successfully changed. Member's current addressMembership ListMembership exposureMembership re-enabled.Membership&nbsp;ListMembership&nbsp;Management...Message Excerpt:Message Headers:Message body is too big: %(size)d bytes with a limit of
%(limit)d KBMessage body suppressed by Mailman site configuration
Message has a suspicious headerMessage has implicit destinationMessage may contain administriviaMessage rejected by filter rule matchMessage rejected.
It appears that this message contains an HTML part with the
Approved: password line, but due to the way it is coded in the
HTML it can't be safely removed.
ModeratedModeratorModerator passwords did not matchMonMonthlyMore information: %(listurl)sMove a message from the shunt queue to the original queue.

Usage: %(PROGRAM)s [options] [directory]

Where:

    -h / --help
        Print help and exit.

Optional `directory' specifies a directory to dequeue from other than
qfiles/shunt.  *** Warning ***  Do not unshunt messages that weren't
shunted to begin with.  For example, running unshunt on qfiles/out/
will result in losing all the messages in that queue.
Move rule downMove rule upMunge FromMust have a listname and a filenameMust 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.NeverNew %(listname)s password: %(notifypassword)sNew %(pwdesc)s password: New password for member %(member)40s: %(randompw)sNew subscription request to list %(realname)s from %(addr)sNew unsubscription request from %(realname)s by %(addr)sNews server settingsNext message (by thread):NoNo address givenNo argument to -f givenNo child with pid: %(pid)sNo 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 givenNo lists to searchNo matching mailing lists foundNo one can subscribe to the digest of this list!No problems foundNo reason givenNo runner name given.No subjectNo such list "%(listname)s"
%(e)sNo such list %(safelistname)sNo such list (or list already deleted): %(listname)sNo such list <em>%(safelistname)s</em>No such list: %(listname)sNo such list: %(listname)s.  Removing its residual archives.No such member: %(addr)sNo such member: %(safeuser)s.No updates are necessary.No valid address found to subscribeNo valid variable name found.Non-digest (regular) members:Non-digest&nbsp;optionsNon-member filtersNon-members are not allowed to post messages to this list.Non-standard property restored: %(k)sNoneNone - 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>
                 NorwegianNot a valid email address: %(toaddr)sNot authenticatedNot removing archives.  Reinvoke with -a to remove them.Not subscribedNote: 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 of post refused by moderatorNotice: %(discarded)d old request(s) automatically expired.

Notification sent to %(schange_from)s.Notification sent to %(schange_to)s.NotificationsNovNovemberNumber 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).Number of seconds to remember posts to this list to determine
               member_verbosity_threshold for automatic moderation of a
               member.OctOctoberOffOkay, the list moderator will still have the
    opportunity to approve or reject this message.OnOn demand password reminderOnce a month, your password will be emailed to you as a reminder.One of -i or -o is requiredOne 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 allowedOnly one of -i or -o is allowedOnly one of -m, -M, -i or -u may be specified.Open list, moderated groupOriginal MessageOriginal message suppressed by Mailman site configuration
Other Administrative ActivitiesOther mailing lists on this site whose members are
             excluded from the regular (non-digest) delivery if those
             list addresses appear in a To: or Cc: header.Other mailing lists on this site whose members are
             included in the regular (non-digest) delivery if those
             list addresses don't appear in a To: or Cc: header.Output XML to FILENAME.  If not given, or if FILENAME is '-', standard out is
used.Overview of all %(hostname)s mailing listsPID unreadable in: %(pidfile)sPage Unchanged.Password // URLPassword change failed.Password changed.Password reminderPassword successfully changed.Password:Password: PasswordsPasswords did not match!Passwords do not match; no changes made.Passwords may not be blankPattern (as regexp):Pending subscriptions:Pending unsubscriptions: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 listPermanently remove mailing list %(realname)sPermanently remove mailing list <em>%(realname)s</em>PersianPickling archive state into PlainPlease answer the following question to prove that
                    you are not a bot: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 enter your email addressPlease specify either -p or -m.Please take a few seconds to fill out the form before submitting it.Please trim the recipient list; it is too long.Policies concerning immediately delivered list traffic.Policies concerning the content of list traffic.

            <p>Content filtering works like this: when a message is
            received by the list and you have enabled content filtering, the
            individual attachments are first compared to the
            <a href="?VARHELP=contentfilter/filter_mime_types">filter
            types</a>.  If the attachment type matches an entry in the filter
            types, it is discarded.

            <p>Then, if there are <a
            href="?VARHELP=contentfilter/pass_mime_types">pass types</a>
            defined, any attachment type that does <em>not</em> match a
            pass type is also discarded.  If there are no pass types defined,
            this check is skipped.

            <p>After this initial filtering, any <tt>multipart</tt>
            attachments that are empty are removed.  If the outer message is
            left empty after this filtering, then the whole message is
            discarded.

            <p> Then, each <tt>multipart/alternative</tt> section will
            be replaced by just the first alternative that is non-empty after
            filtering if
            <a href="?VARHELP=contentfilter/collapse_alternatives"
            >collapse_alternatives</a> is enabled.

            <p>Finally, any <tt>text/html</tt> parts that are left in the
            message may be converted to <tt>text/plain</tt> if
            <a href="?VARHELP=contentfilter/convert_html_to_plaintext"
            >convert_html_to_plaintext</a> is enabled and the site is
            configured to allow these conversions.PolishPoll 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.

PortuguesePortuguese (Brazil)Post by non-member to a members-only listPost to moderated listPosted message canceledPosterPoster passwords did not matchPosting Held for ApprovalPosting of your message titled "%(subject)s"Posting to a moderated newsgroupPosting to a restricted list by sender requires approvalPostings from any of these addresses will automatically
             apply any DMARC action mitigation.  This can be utilized to
             automatically wrap or munge postings from known addresses or
             domains that might have policies rejecting external mail From:
             themselves.

             <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
             accepted with no further moderation applied.  Add member
             addresses one per line; start the line with a ^ character to
             designate a regular expression match.  A line consisting of
             the @ character followed by a list name specifies another
             Mailman list in this installation, all of whose member
             addresses will be accepted for this list.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)sPreferred language:Prefix <tt>Subject:</tt> headers on postings gated to news?Prefix for subject line of list postings.PreservePreserve message for site administratorPreserve messages for the site administratorPrevious message (by thread):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 ErrorPrivate Archive Error - %(msg)sPrivate archive - "./" and "../" not allowed in URL.Private archive file not foundPrivate archive login pageProblems 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 PoweredQuarterlyRFC 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 membershipRe-enable membershipRe-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 filesRe-run as %(MAILMAN_USER)s (or root) with -f flag to fixReason for refusalReason: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 filtersRecipient&nbsp;filtersReduce 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:RegularRejectRejectsReloading pickled archive stateRemindRemove members from a list.

Usage:
    remove_members [options] [listname] [addr1 ...]

Options:

    --file=file
    -f file
        Remove member addresses found in the given file.  If file is
        `-', read stdin.

    --all
    -a
        Remove all members of the mailing list.
        (mutually exclusive with --fromall)

    --fromall
        Removes the given addresses from all the lists on this system
        regardless of virtual domains if you have any.  This option cannot be
        used -a/--all.  Also, you should not specify a listname when using
        this option.

    --nouserack
    -n
        Don't send the user acknowledgements.  If not specified, the list
        default value is used.

    --noadminack
    -N
        Don't send the admin acknowledgements.  If not specified, the list
        default value is used.

    --help
    -h
        Print this help message and exit.

    listname is the name of the mailing list to use.

    addr1 ... are additional addresses to remove.
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)sRemoving %(msg)sReplace the From: header address with the list's posting
             address to mitigate issues stemming from the original From:
             domain's DMARC or similar policies.Request to confirm subscriptionRequest to confirm unsubscriptionRequest to mailing list %(realname)s rejectedRequested topic is not valid: %(topicname)sRequire approvalReset 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 infoRestarting Mailman's master qrunnerReturn the generated output.Return to the RomanianRun one or more qrunners, once or repeatedly.

Each named runner class is run in round-robin fashion.  In other words, the
first named runner is run to consume all the files currently in its
directory.  When that qrunner is done, the next one is run to consume all the
files in /its/ directory, and so on.  The number of total iterations can be
given on the command line.

Usage: %(PROGRAM)s [options]

Options:

    -r runner[:slice:range]
    --runner=runner[:slice:range]
        Run the named qrunner, which must be one of the strings returned by
        the -l option.  Optional slice:range if given, is used to assign
        multiple qrunner processes to a queue.  range is the total number of
        qrunners for this queue while slice is the number of this qrunner from
        [0..range).

        If using the slice:range form, you better make sure that each qrunner
        for the queue is given the same range value.  If slice:runner is not
        given, then 1:1 is used.

        Multiple -r options may be given, in which case each qrunner will run
        once in round-robin fashion.  The special runner `All' is shorthand
        for a qrunner for each listed by the -l option.

    --once
    -o
        Run each named qrunner exactly once through its main loop.  Otherwise,
        each qrunner runs indefinitely, until the process receives a SIGTERM
        or SIGINT.

    -l/--list
        Shows the available qrunner names and exit.

    -v/--verbose
        Spit out more debugging information to the logs/qrunner log file.

    -s/--subproc
        This should only be used when running qrunner as a subprocess of the
        mailmanctl startup script.  It changes some of the exit-on-error
        behavior to work better with that framework.

    -h/--help
        Print this message and exit.

runner is required unless -l or -h is given, and it must be one of the names
displayed by the -l switch.

Note also that this script should be started up from mailmanctl as a normal
operation.  It is only useful for debugging if it is run separately.
Run this program as root or as the %(name)s user, or use -u.Running %(module)s.%(callable)s()...RussianSatSaving listScrub attachments of regular delivery message?Search regular expression requiredSearch...SecondSee 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 noticeSend 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 forbiddenSender&nbsp;filtersSepSeptemberSerbianServer Local TimeSetSet 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.
Set this to yes when this list is intended to cascade only
             to other mailing lists.  When set, meta notices like
             confirmations and password reminders will be directed to an
             address derived from the member's address - it will have the
             value of "umbrella_member_suffix" appended to the member's
             account name.Setting host_name to: %(mailhost)sSetting invite-msg-file requires --invite.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 this value to <em>Yes</em> will cause Mailman to
             send a notice including a copy of the bounce message to the list
             owners whenever a bounce increments a member's bounce score but
             doesn't cause a disable or a probe to be sent.Setting web_page_url to: %(web_page_url)sSeveral protocols now in wide use attempt to ensure that use
             of the domain in the author's address (ie, in the From: header
             field) is authorized by that domain.  These protocols may be
             incompatible with common list features such as footers, causing
             participating email services to bounce list traffic merely
             because of the address in the From: field.  <b>This has resulted
             in members being unsubscribed despite being perfectly able to
             receive mail.</b>
             <p>
             The following actions are applied to all list messages when
             selected here.  To apply these actions only to messages where the
             domain in the From: header is determined to use such a protocol,
             see the <a
             href="?VARHELP=privacy/sender/dmarc_moderation_action">
             dmarc_moderation_action</a> settings under Privacy options...
             -&gt; Sender filters.
             <p>Settings:<p>
             <dl>
             <dt>No</dt>
             <dd>Do nothing special.  This is appropriate for anonymous lists.
             It is appropriate for dedicated announcement lists, unless the
             From: address of authorized posters might be in a domain with a
             DMARC or similar policy. It is also appropriate if you choose to
             use dmarc_moderation_action other than Accept for this list.</dd>
             <dt>Munge From</dt>
             <dd>This action replaces the poster's address in the From: header
             with the list's posting address and adds the poster's address to
             the addresses in the original Reply-To: header.</dd>
             <dt>Wrap Message</dt>
             <dd>Just wrap the message in an outer message with the From:
             header containing the list's posting address and with the original
             From: address added to the addresses in the original Reply-To:
             header and with Content-Type: message/rfc822.  This is effectively
             a one message MIME format digest.</dd>
             </dl>
             <p>The transformations for anonymous_list are applied before
             any of these actions. It is not useful to apply actions other
             than No to an anonymous list, and if you do so, the result may
             be surprising.
             <p>The Reply-To: header munging actions below interact with these
             actions as follows:
             <p> first_strip_reply_to = Yes will remove all the incoming
             Reply-To: addresses but will still add the poster's address to
             Reply-To: for all three settings of reply_goes_to_list which
             respectively will result in just the poster's address, the
             poster's address and the list posting address or the poster's
             address and the explicit reply_to_address in the outgoing
             Reply-To: header. If first_strip_reply_to = No the poster's
             address in the original From: header, if not already included in
             the Reply-To:, will be added to any existing Reply-To:
             address(es).
             <p>These actions, whether selected here or via <a
             href="?VARHELP=privacy/sender/dmarc_moderation_action">
             dmarc_moderation_action</a>, do not apply to messages in digests
             or archives or sent to usenet via the Mail&lt;-&gt;News gateways.
             <p>If <a
             href="?VARHELP=privacy/sender/dmarc_moderation_action">
             dmarc_moderation_action</a> applies to this message with an
             action other than Accept, that action rather than this is
             appliedShall the above dmarc_moderation_action apply to messages
               From: domains with DMARC p=none as well as p=quarantine and
               p=rejectShall the above dmarc_moderation_action apply to messages
               From: domains with DMARC p=quarantine as well as p=rejectShould Mailman collapse multipart/alternative to its
             first part content?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 bounce score to be incremented?Should Mailman notify you, the list owner, when bounces
             cause a member's subscription to be disabled?Should Mailman perform a <em>catchup</em> on the newsgroup?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 duplicate avoidance drop addresses from Cc: headersShould 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 <tt>Sender</tt> header be rewritten for this
                 mailing list to avoid stray bounces?  <em>Yes</em> is
                 recommended.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 basic statistics about, and build options for this
installation of Mailman. Requires python 2.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
Show this list grouped/sorted byShutting down Mailman's master qrunnerSibling listsSite list is missing: %(sitelistname)sSize:Skipped content of type %(partctype)s
SlovakSlovenianSome unknown error occurred while creating the list.
                Please contact the site administrator for assistance.Spam Filter Regexp:Spam Filter Rule %(i)dSpam&nbsp;filtersSpanish (Spain)Specify the RFC 2307 style hashing scheme for passwords included in the
output.  Use -P to get a list of supported schemes, which are
case-insensitive.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:SubmitSubmit All DataSubmit ChangesSubmit My ChangesSubmit Your ChangesSubscribeSubscribe results pageSubscribe these users now or invite them?Subscribe to list %(listname)sSubscribed: %(member)sSubscribingSubscription RequestsSubscription disabled by bounce warningSubscription requestSubscription request confirmedSubscription request succeeded.Subscription&nbsp;rulesSuccessfully 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.SunSwedishSync Membership ListSync&nbsp;Membership&nbsp;ListSynchronize 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)sTend to pending moderator requestsText 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
             <a href="?VARHELP=privacy/sender/dmarc_moderation_action"
             >rejection notice</a> to
             be sent to anyone who posts to this list from a domain
             with a DMARC Reject%(quarantine)s Policy.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)sThe "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 <b>info</b> attribute you saved
contains suspicious HTML that could potentially expose your users to cross-site
scripting attacks.  This change has therefore been rejected.  If you still want
to make these changes, you must have shell access to your Mailman server.
This change can be made with bin/withlist or with bin/config_list by setting
mlist.info.
                        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 ReplybotThe Week Of Monday %(day)i %(month)s %(year)iThe `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 archiveThe 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 form is too old.  Please GET it again.The form lifetime has expired. (request forgery check)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 hidden token didn't match.  Did your IP change?The hostname of the machine your news server is running on.The list addresses should be written in full mail address
             format (e.g. mailman@example.com). Do not specify this list
             address mutually in the exclude list configuration page of the
             other list, or members of both lists won't get any message.
             Note also that the site administrator may prohibit cross domain
             siblings.The list addresses should be written in full mail address
             format (e.g. mailman@example.com). Note also that the site
             administrator may prohibit cross domain siblings.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 administrator may not change the
                    password for a user.The list administrator may not change the
                options for this user's other subscriptions.  However the
                options for this mailing list subscription has been
                changed.The list administrator may not change the
            password for this user's other subscriptions.  However, the
            password for this mailing list has been changed.The list administrator may not change the names
            or addresses for this user's other subscriptions.  However, the
            subscription for this mailing list has been changed.The list administrator may not view the other
            subscriptions for this user.The list moderator email addresses.  Multiple
             moderator addresses, each on separate line is okay.The list password cannot be emptyThe list password cannot be empty<!-- ignore -->The list to include in the output.  If not given, then all mailing lists are
included in the XML output.  Multiple -l flags may be given.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 member address %(change_from)s on the
%(list_name)s list has been changed to %(change_to)s.
The message's content type was explicitly disallowedThe message's content type was not explicitly allowedThe message's file extension was explicitly disallowedThe message's file extension was not explicitly allowedThe 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)sThe 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)sThe 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 page you saved contains suspicious HTML that could
potentially expose your users to cross-site scripting attacks.  This change
has therefore been rejected.  If you still want to make these changes, you
must have shell access to your Mailman server.
             The process which avoids sending a list copy of a message to
               a member who is also directly addressed in To: or Cc: can drop
               the address from Cc: to avoid growing a long Cc: list in long
               threads.  This can be undesirable as it can break DKIM
               signatures and possibly cause confusion.  To avoid changes to
               Cc: headers, set this to No.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 commandsThe 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 listThe text will be treated as html <em>except</em> that
             newlines will be translated to &lt;br&gt; - 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 instanceThere 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 was no hidden token in your submission or it was corrupted.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.ThirdThis 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 form requires JavaScript.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 listThis 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>This was not the right answer to the CAPTCHA question.ThuTo change a list member's address, enter the
    member's current and new addresses below. Use the check boxes to send
    notice of the change to the old and/or new address(es).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 messageTopic %(i)dTopic filter detailsTopic 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.TopicsTueTurkishTurn 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.UUkrainianUmbrella list settingsUncaught bounce notificationUnexpected argumentsUnix-From line changed: %(lineno)dUnknown language: %(lang)sUnknown list: %(listname)sUnknown virtual host: %(safehostname)sUnlock 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)sUnsubscribeUnsubscribe or edit optionsUnsubscription RequestsUnsubscription requestUnsubscription request confirmedUnsubscription request succeeded.Unsubscription resultsUpdating HTML for article %(seq)sUpdating Mailman 2.0 pending_subscriptions.db databaseUpdating Mailman 2.1.4 pending.pck databaseUpdating Usenet watermarksUpdating index files for archive [%(archive)s]Updating mailing list: %(listname)sUpdating the held requests database.Upgrading from version %(hexlversion)s to %(hextversion)sUsage: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/nameUser notice of autoresponse limitUser notice of held postUser notice of held subscriptionUser post acknowledgementUser specific options pageUsing Mailman version:ValueVietnameseView or edit the list configuration information.View this page inVisit Subscriber ListVisit Subscriber listVisit the list's admin pageVisit the list's info pageWARNING: Ignoring duplicate pending ID: %(id)s.WARNING: could not acquire lock for list: %(listname)sWARNING: directory does not exist: %(d)sWarning!  Deleting empty .pck file: %(pckfile)sWarning!  Not a directory: %(dirpath)sWarning!  You may encounter permission problems.Warning: Warning: Private archive directory is other-executable (o+x).
         This could allow other users on your system to read private archives.
         If you're on a shared multiuser system, you should consult the
         installation manual on how to fix this.Warning: couldn't remove %(src)s -- %(rest)sWe'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>.WedWeeklyWelcome email text fileWelcome to the "%(realname)s" mailing list%(digmode)sWelcome!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 subscription requires approval, addresses in this list
             are allowed to subscribe without administrator approval. Add
             addresses one per line. You may begin a line with a ^ character
             to designate a (case insensitive) regular expression match.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?Wrap MessageYearlyYesYes, w/discardYes, w/forwardYou already have a subscription pending confirmationYou are already a member of this mailing list!You are already subscribed!You are already subscribed.You are already using that email addressYou are currently banned from subscribing to
            this list.  If you think this restriction is erroneous, please
            contact the list owners at %(owneraddr)s.You are currently banned from subscribing to this list.  If you think this
restriction is erroneous, please contact the list owners at
%(owneraddr)s.You are forbidden from posting messages to this list.You are not a member of the %(listname)s mailing listYou are not allowed to post to this mailing list From: a domain which
publishes a DMARC policy of reject or quarantine, and your message has been
automatically rejected.  If you think that your messages are being rejected in
error, contact the mailing list owner at %(listowner)s.You are not allowed to retrieve the list membership.You are not authorized to create new mailing listsYou are not authorized to delete this mailing listYou 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 passwordYou forgot to enter the list nameYou forgot to specify the list ownerYou gave the wrong passwordYou 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 listYou 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 also use the @listname notation to designate the
             members of another list in this installation.You may get one last digest.You may not subscribe a list to itself!You must GET the form before submitting it.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 provide both current and new addresses.You must specify a list name.  Here is the %(link)sYou 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 listYour confirmation is required to leave the %(listname)s mailing listYour current option settings:Your decisionYour 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 has been rejected, probably because you are not subscribed to the
mailing list and the list's policy is to prohibit non-members from posting to
it.  If you think that your messages are being rejected in error, contact the
mailing list owner at %(listowner)s.Your message to %(listname)s awaits moderator approvalYour message was deemed inappropriate by the moderator.Your message was rejectedYour message was too big; please trim it to less than
%(kb)d KB in size.Your new %(listname)s list passwordYour new mailing list: %(listname)sYour password is: %(password)sYour 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.
[----- end %(typename)s file -----][----- start %(typename)s file -----][Message discarded by content filter][No bounce details are available][No explanation given][No reason given][disabled by periodic sweep and cull, no message available][no description available]a single held message.ackack option setadmin mass subadmin mass unsubadministrative list overviewall held messages.all of %(esender)s's held messages.also article db files must be %(octperms)s: %(path)sarticle file %(filename)s is missing!attribute "%(k)s" changedattribute "%(k)s" ignoredauthorbounce score incrementedby the adminby the list administratorby youby yourselfcheck a translated template against the original one
       search also <MM-*> tags if html is not zerocheck a translation comparing with the original stringcheck for differences between checked in and checked outchecking cgi-bin permissionschecking mode for %(prefix)schecking ownership of %(dbfile)schecking permissions on %(file)schecking permissions on %(pwfile)schecking permissions on list datachecking perms on %(private)schecking set-gid for %(wrapper)scouldn't remove old file %(pyc)s -- %(rest)sdatedaydaysdelivery disabled by userdelivery enableddelivery offdelivery ondigestdigest footerdigest headerdigest option setdirectory must be at least 02775: %(d)sdirectory permissions must be %(octperms)s: %(path)sdisableddisabled addressdmarc_moderation_action must be >= the configured
                           default value.donedue to bouncesdue to excessive bouncesduplicates option setemail address and email confirmationfiguring article archives
file permissions must be at least 660: %(path)sfixing 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 reasonsfound in:from %(start)s to %(end)sgenaliases can't do anything useful with mm_cfg.MTA = %(mta)s.general list overviewgetting rid of old source filesgloballyheld message filehidehide option setlanguagelegal values are:list creatorlist infolist of available mailing lists.listname is requiredmatching mailing lists found:mbox file must be at least 0660:member address<br>member namemember mgt pagemembersmessage is unparsable: %(filebase)smodmyposts option setn/ano dateno lists == nothing to do, exitingno subjectnodupesnomailnomail<br>[reason]not availablenot metoonotmetoooffonoptionsparse a .po file extracting msgids and msgstrspasswordplainprivateprivate archivesprocessing mailing list:publicpublic archivesreCAPTCHA could not be validated: %(e_reason)sreCAPTCHA validation failed: %(e_codes)sreminder option setremoving %(src)sremoving directory %(src)s and everything underneathreturn to the %(categoryname)s options page.rightright scan a string from the original filescan a translated stringscan the po file comparing msgids with msgstrssender/sendersender/timesitesize not availablesource perms must be %(octperms)s: %(path)sstale lock filestop is synonymous with the end command.
subjectsubscriptions to %(name)s require administrator approvalsubscriptions to %(realname)s require moderator approvalthe list admin overview pagethe list administratorthe mailing list overview pagethreadungrouped/timeunknown senderunsubunsubscriptions require moderator approvalupdating old qfilesvia admin approvalvia email confirmationvia the member options pagevia web confirmationview all messages from %(esender)sweb confirmationProject-Id-Version: Mailman 2.1.30rc1
POT-Creation-Date: Fri Jun 26 17:05:40 2020
PO-Revision-Date: 2020-01-13 09:16+09:00
Last-Translator: Yasuhito FUTATSUKI at POEM <futatuki@poem.co.jp>
Language-Team: Japanese <mailman-users-jp@googlegroups.com>
Language: ja
MIME-Version: 1.0
Content-Type: text/plain; charset=EUC-JP
Content-Transfer-Encoding: 8bit
Generated-By: pygettext.py 1.4


    

    ¸ Mailman 򥢥åץ졼ɤ褦ȤƤޤ
    ΥС󤬤狼ޤ

    Mailman 1.0b9 ΥС󤫤Υåץ졼ɤϡ
    ȤǥꥹȤ򹹿ɬפޤ
    줾Υ᡼󥰥ꥹȤˤĤơtemplate/options.html 
    lists/<ꥹ̾>/options.html ˥ԡɬפޤ

    Υե򥦥֥󥿥եԽ硢
    ѹƤ򤳤ΥեȿǤʤФʤޤ
    ȿǤʤѹϼޤ

    


    confirm <ǧʸ>
        ǧޤǧʸɬܤǡǧ׵Υ᡼
        񤫤ƤΤǤʤФʤޤ

    echo []
        ǧΤ򤽤Τޤɽޤ줿ʸ֤äƤޤ

    end
        ޥɽߤޤưŪ˽̾ɲä
        ᡼륽եȤѤƤȤϡȤäƤ

    help
        Υإץåɽޤ

    info
        Υ᡼󥰥ꥹȤΰ󤻤ޤ

    lists
         GNU Mailman Фθ᡼󥰥ꥹȤΰ򸫤롣

    password [<ѥ> <ѥ>] [address=<ɥ쥹>]
        ѥɤ󤻤ѹޤդ˼¹Ԥȡ
        ߤΥѥɤ󤻤ޤ
        <ѥ><ѥ>դȡѥɤ
        ѹޤ
        Ͽ줿ɥ쥹ʳ᡼ϡ
        `address=<ɥ쥹>' (̤դʤ) 
        Ͽ륢ɥ쥹ꤷƤξ硢ֿϿ
        줿ɥ쥹ޤΤǤդ

    set ...
        ץ, ǧ򤷤ޤ

        `set help' (դʤ) ѹǽʥץΰ
        뤳ȤǤޤ

        `set show' (դʤ) ǸߤΥץ򸫤뤳Ȥ
        Ǥޤ

    set help
        󤻤롣

    set show [address=<ɥ쥹>]
        ߤΥץ򸫤롣Ͽɥ쥹ʳ᡼
        ϡϿɥ쥹 `address=<ɥ쥹>' η
        ꤷƤ(᡼륢ɥ쥹ˤϡ<ס>פդʤȡ
        ޤޥɤ'פǰϤޤʤ)

    set authenticate <ѥ> [address=<ɥ쥹>]
        ץꤹϡޤΥޥɤ¹Ԥɬפ
        ޤ<ѥ>ϼʬβѥɤǤϿ
        ɥ쥹ʳ᡼, Ͽɥ쥹
        `address=<ɥ쥹>' ηǻꤷƤ(᡼륢ɥ쥹
        ˤϡ<ס>פդʤȡޤޥɤ'פǰϤޤʤ)

    set ack on
    set ack off
        `ack' ץ on ˤȡ᡼󥰥ꥹȤ˥᡼
        Ƥ뤿ӤˡǧΤΥ᡼뤬褦ˤʤޤ

    set digest plain
    set digest mime
    set digest off
        `digest' ץ off ˤȡƤ줿᡼뤬ľ
        ޤ̤Υ᡼ޤȤʿʸ(RFC 1153 
        )Ǽꤿ `set digest plain' ȤäƤ
        MIMEǼꤿˤ `set digest mime' Ȥޤ

    set delivery on
    set delivery off
         on/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 [ѥ] [digest|nodigest] [address=<ɥ쥹>]
        Υ᡼󥰥ꥹȤ񤹤롣ѥɤ䥪ץ
        ѹɬפǤ⤷άˤϼưŪޤ
        Ū˥ѥɤ˺Τޤ

        ΰ `nondigest' ޤ `digest' (ʤ!)
        ⤷᡼ȯΤȤϰ㤦ɥ쥹ˤΤ
        С`address=<ɥ쥹>' ηǻǤޤ
        (åդʤ!)

    unsubscribe [ѥ] [address=<ɥ쥹>]
        ᡼󥰥ꥹȤ񤷤ޤѥɤդ硢
        Ͽ줿ѥɤ˰פʤȤޤ󡣥ѥ
        ά줿ϡ񤹤륢ɥ쥹˳ǧΥ᡼
        ޤ񤹤륢ɥ쥹ʳΥɥ쥹Ȥäƿ᡼
        Ȥϡ`address=<ɥ쥹>' ꤷƤ 
        (ξΥ᡼륢ɥ쥹ˤ <>  " դʤǤ!)

    who
        Υ᡼󥰥ꥹȤαǤʤ򸫤롣
    who password
        Υ᡼󥰥ꥹȤ򸫤롣password ϥꥹȴ
        ޤϻʲԤΥѥɡ

    who ѥ
        Υ᡼󥰥ꥹȤβ̾򸫤롣̾αϥꥹȴ
        ԤȻʲԤ¤ƤޤꥹȴԤΥѥɤ
        ʲԤΥѥɤդƤ

    who ѥ [address=<ɥ쥹>]
        Υ᡼󥰥ꥹȤβ̾򸫤롣̾ϥꥹȲ
        ¤ƤޤΤ, ˤϲѥɤɬפǤϿ
        ɥ쥹ʳ饳ޥɥ᡼ `address=<ɥ쥹>'
        Dzɥ쥹ꤷƤ(᡼륢ɥ쥹 <> ǰϤ
        ʤȡ줫饯ơޡޤޤʤ!)
        ꥹȴϻʲԤΥѥɤȡޤޤ
        ޤ

%(listname)s  public  private  mbox ե뤬ޤΥꥹ
 private ¸ˤȤޤΤǡprivate  mbox ե --
 %(o_pri_mbox_file)s -- ͭʥեȰޤ
        %(o_pub_mbox_file)s

        %(o_pub_mbox_file)s.pre6
ѹޤ

Υե `arch' ޥɤȤä¸ˤȤ߹ळȤǤޤ

- λ


- ̵:
- ǽ:
Mailmanå롣ѿȥܤѿ
˰פ뤫ɤĴ٤롣

ˡ:

cd $MAILMAN_DIR
%(program)s [-q] <>

, <>ϸ쥳(Ȥ 'it' ϥꥢ) -q û
Ϥ׵᤹롣

顼:

åǤʤꥹȤޤåץ졼MailmanưƤ
%(lockdir)s ǥ쥯ȥ˻ȤƤʤåե뤬ĤäƤ
Τɤ餫Ǥ

Mailman ߤƸŤå򤹤٤ƺ줫 "make update" 
ȤǼ¹ԤƤܤ INSTALL  UPGRADE Υե˽
ƤޤΤǡɤߤ

α:
᡼󥰥ꥹȺλˤϡ/etc/aliases (ޤƱ
ե) 顢ιԤɬפޤ
ޤ餯ϡ`newaliases' ץ¹ԤʤФʤʤǤ礦

## %(listname)s mailing list
ˡ:
<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    %(status)s (%(date)s  %(how)s)    ack (ǧ) %(onoff)s    ɥ쥹Ĥޤ:    %(path)s  gid ȥ⡼ɤå    %(path)s Υѡߥåå    %(path)s  set-gid å    󥢥ɥ쥹ɲ: 󥢥ɥ쥹ϴ˲Ǥ    digest mime (MIMEǤޤȤɤ)    digest (ޤȤɤ) off    digest plain (ʿʸǤޤȤɤ)    duplicates (ʣ) %(onoff)s    hide () %(onoff)s    myposts (ʬ) %(onoff)s    ꥹȴ:    Υɥ쥹:    reminders (˺) %(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>&nbsp;<br>- ꥹȴԤΥɥ쥹ϡowner@example.comפΤ褦˴ʷǤɬפޤ <p>ʤ̤ξ硢β̤ǥ᡼륢ɥ쥹ϤޤǸ˥顼᡼դ %(date)s ǤɽƤʤꥹȤΥڡؤΰưϡΥڡ URL 
'/' ȥꥹȤ̾ %(adj)s դURL򳫤Ƥ
<p>ꥹȴԤȥѥɤϤƲ̾ؿʤǤ: <p><center>    Х %(remote)s  ϴ˲Ǥβ̾򸫤: ǼʬδڡõƤ
<p>ꥹȤѤ˴ؤȥ֥ϡΰϢƤ: # -*- python -*-
# -*- coding: %(charset)s -*-
## "%(listname)s" ᡼󥰥ꥹ
## %(when)s ɤ߽Ф
## %(listname)s mailing list#%(counter)05d %(msgid)s%%%%%prog [options]

XML ǥ᡼󥰥ꥹȤȲ¸롣%(addr)s ػߤǤ (%(patt)s ˰)%(address)s  %(listname)s ΥꥹȲǤϤޤ¾Υ᡼󥰥ꥹȤ˾Ԥ줿 %(address)s 
Υ᡼󥰥ꥹȤ񤷤褦Ȥޤ. 
⤹ɬפϤޤ󤬡ǰΤˤΤ餻ޤ %(allcnt)s ̾ %(allcnt)s ̾,  %(membercnt)s ̾ ɽޤ%(count)d  %(realname)s Ʒ郎ޤ%(year)iǯ%(month)s%(day)i%(days)d %(units)s%(dbdir)s  other ˵ĤͿƤϤޤ%(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%(list_name)s ɥ쥹ѹ%(listfullname)s ᡼󥰥ꥹ˺%(listinfo_link)s ꥹȴ %(owner_link)s%(listname)s %(msg)s  %(filename)s ˸Ĥޤ%(listname)s ᡼󥰥ꥹ ɥ쥹õΥ᡼%(listname)s ؤ %(sender)s ƤϾǧɬפǤ%(messages)d ĤΥ᡼뤬Ĥޤ%(year)iǯ%(month)s%(name)s  %(runnername)s qrunner ¹%(newaddr)s ϡ %(realname)s ꥹȤβǤ
񤷤ɥ쥹οǧ褦ȤƤǽޤ%(newaddr)s ϴѤߤǤ%(newaddr)s Ȥ᡼륢ɥ쥹 %(realname)s ؤ
϶ػߤƤޤ
¤ϿˤΤȻפ
Υꥹȴ԰ˤϢ: %(owneraddr)s%(newaddr)s Υ᡼륢ɥ쥹Ǥ϶ػߤƤޤ
¤ϿˤΤȻפ
Υꥹȴ԰ˤϢ: %(owneraddr)s%(year)iǯ%(ord)sȾ%(path)s 롼פθ (%(groupname)s Ǥ %(MAILMAN_GROUP)s ˤƤ)%(path)s  set-gid ƤʤȤޤ%(private)s  other ɤ߼ǽǤʤФޤ%(pwfile)s Υѡߥå %(octmode)s ˤʤäƤޤ0640 ǤʤȤޤ%(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 Mailman᡼󥰥ꥹإ
    <br><em>%(varname)s</em> ץ%(realname)s ɥ쥹ѹ%(realname)s ѥڡ%(realname)sꥹ: %(safeuser)s ץ%(realname)s ꥹ: ץڡ%(realname)s ᡼󥰥ꥹȴ<br>%(label)s %(realname)s Ʒ︡%(realname)s Ƴǧ%(realname)s ̾ ǧڤ˼ԡ%(realname)s %(realname)s %(realname)s (%(lrn)s ͳ)%(safetemplatename)s: (ƥץ졼)̵Ǥ%(schange_from)s ϲǤϤޤ%(schange_to)s ϴ˲Ǥ%(schange_to)s ϴ˲Ǥ%(schange_to)s ͭʥ᡼륢ɥ쥹ǤϤޤ%(schange_to)s ػߥѥ %(spat)s ˥ޥåޤ%(year)04iǯ %(mon)s %(day)2i (%(wday)s) %(hh)02i:%(mm)02i:%(ss)02i %(tzname)s%(wrapper)s  set-gid ƤʤȤޤ%s  public  private  mbox ե뤬ޤΥꥹ
 public ¸ˤȤޤΤǡpublic  mbox ե --
 %s -- ͭʥեȰޤ
        %s

        %s.pre6
ѹޤ

Υե `arch' ޥɤȤä¸ˤȤ߹ळȤǤޤ
&lt;&gt;(<i>%(which)s ϥ᡼󥰥ꥹȲѤǤޤ</i>)(<i>%(which)s ϥꥹȴԤ뤳ȤǤޤ</i>(ޥɥե륿) 
ޥɤޤޤƤ᡼αޤ?( - ʤϥ᡼󥰥ꥹȤΥꥹȤϿ褦ȤƤޤΤ %(type)s ΤΤ餻ϴѥ᡼륢ɥ쥹 %(addr)s ޤ)()()(إ)(åλ)(ѹʤ)(̵)(å)- %(o_tmpl)s Ϥޤ󡣤Τޤޤˤޤ- :- ΥꥹȤˤ b4 Υƥץ졼ȤĤäƤ褦Ǥ- %(o_tmpl)s  %(n_tmpl)s ޤΤޤޤˤޤ- %(o_tmpl)s  %(n_tmpl)s ˰ư- ɬפޤ- Ť private mbox ե򹹿- Ť public mbox ե򹹿- ͥåȥ˥塼οɼλgate_watermark-------------- next part --------------
--all ˤ --run ɬפǤ...θ......ޤϥåץɤեꤷƤ:/Υ; ꥹȴԤߤޤ; Ȥߤޤ; 顼᡼¿ȯˤߤޤ
            ǸΥ顼 %(date)s ˼; ߤƤޤͳǤ<----- %(cnt)s ܤΥ֥ -----><P>ߡ¸ˤϤޤ</P><a href="http://www.faqs.org/rfcs/rfc5322.html">RFC 5322</a>
ǡ<tt>Sender ()</tt>إå졢"ºݤΥ᡼
Ǥ (agent) Υ᡼ܥå" ȤʤäƤޤ
Mailman ϤΥإåꥹȤΥ顼 (bounce) ɥ쥹֤
Ƥޤ
<p>
Mailman Τ褦ͤǤ뤫ɤˤĤƤϵ;Ϥޤ
Ƥʤ MTA 顼Τɥ쥹˰ƤΤΩäƤޤ
ǡΥإåꤵƤȻפʤư򤹤᡼륽եȤ⤢ޤ
(㤨СžȤ˥ɥ쥹ˤʤäꡢֿפȤ
Υ顼Υɥ쥹ˤ) äơ̵ˤǤ褦ˤޤ<b><i>...</i></b><b>ä</b>ƥꥹȴ<b>ǧʸ̵Ǥ:</b>
    %(safecookie)s

<p>ǧʸϺǽ餪褽 %(days)s
¤ڤ뤳ȤդƤ
Ǥ˲餫μǽѤߤξ̵ˤʤޤ
⤷ǧڤǤС⤦ľƤ
뤤ϡǧʸ<a href="%(confirmurl)s">Ǻ</a>Ƥ<b></b> -- βƤ˳ǧΤޤ?<b>admin_member_chunksize</b>°ѹǤޤ!
<b>admin_member_chunksize</b>ǤʤФʤޤ<b>ޤȤɤ</b> -- βؤϡ֤ޤȤɤߡפޤ?
    (ʤΤǤС1̤ˤʤޤ)<b></b> -- βΥɥ쥹
    ̾Ǥϱޤ?<b>host_name</b>°ѹǤޤ!
<b>host_name</b>°ˤʥɥᥤ̾ꤷƤ<b></b> -- <b></b> -- Ŀñ̤Dz(ǥ졼)򤫤ե饰
Υե饰򥻥åȤȡβƤ¤ޤ
åȤʤмͳƤǤޤ<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></div><br>:<em>(%(num_concealed)d ̾α ɽޤ)</em><em>(1 ̾α ɽޤ)</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>뤤</i></b> ̾餢ʤιܤǤ (򻲾)<p>¾β򸫤ˤϡΥꥹȤŬϰϤ򥯥åƤ:</em><p> %(hostname)s ǸƤ᡼󥰥ꥹȤϰʲ̤Ǥ
ꥹ̾򥯥åȡܤˡ
ץѹˡʤɤܤ줿ڡ˰ưޤ<p>ʲ %(hostname)s ǸƤ 
%(mailmanlink)s ᡼󥰥ꥹȤǤꥹȤ̾򥯥åȡ
ΥꥹȤڡ˰ưޤ<p> %(hostname)s dz˸Ƥ %(mailmanlink)s 
᡼󥰥ꥹȤϤޤ<p> %(hostname)s dz˸Ƥ %(mailmanlink)s 
᡼󥰥ꥹȤϤޤ<p>ʤΥ᡼륢ɥ쥹顢Ƕ顼ΤƤޤ
 ʤθߤ <em>顼</em>Ϻ %(total)s Фơ
 %(score)s ˤʤäƤޤϿɥ쥹ʬå
 Υɥ쥹ؤ̵꤬褦դƤ
 ꤬褹Ф顼ϥꥻåȤޤ<tt>Reply-To:</tt>إåν񤭴<ul><li><b>α</b> -- ꥹȻʲԤξǧ뤿ᡢ᡼αޤ
<p><li><b></b> -- ưŪ˥᡼ݤơΤȤ
   ƼԤ˥᡼Τ餻ޤΤʸ <a href="?VARHELP=privacy/sender/member_moderation_notice">
   ꤹ뤳ȤǤޤ</a>

<p><li><b>˴</b> -- ƼԤΤ˥᡼˴ޤ
</ul><ul><li><b>From 񤭴</b> -- <a
             href="?VARHELP=general/from_is_list">from_is_list 
            From 񤭴</a>
             ᡼ŬѤޤ

             <p><li><b>᡼ź</b> -- <a
             href="?VARHELP=general/from_is_list">from_is_list 
             ᡼ź</a>
             ᡼ŬѤޤ

             <p><li><b></b> -- ưŪ˥᡼ݤơ
             ƼԤ˥᡼Τ餻ޤΤʸ<a
             href="?VARHELP=privacy/sender/dmarc_moderation_notice"
             >ꤹ뤳ȤǤޤ</a>

             <p><li><b>˴</b> -- ƼԤΤ˥᡼˴ޤ
             </ul>

             <p>ֵġװʳꤹȡ
             ᡼ From: Υɥᥤ DMARC ݥꥷľ硢
             <a href="?VARHELP=general/from_is_list">from_is_list</a>
             ͥ褷Ƽ¹Ԥޤ<ul><li><b></b> -- Ƥ From: ɥᥤ DMARC  p=reject ޤ
               dmarc_quarantine_moderation_action ˱
               p=quarantine Ǥ褦Ƥˤ
               dmarc_moderation_action ŬѤޤ
               <p><li><b>Ϥ</b> -- dmarc_moderation_action 
               From 񤭴פޤϡ֥᡼źաפξǡ
               dmarc_quarantine_moderation_action ֤Ϥפξ
               Ƥ From: ɥᥤ DMARC  p=none ƤФ
               dmarc_moderation_action ŬѤޤ
               <p>ΰտޤ DMARC  p=none ɽƤ
               ɥᥤĤơDMARCΥݥꥷ궯礫ä
               ŬѤƥåν񤭴ԤȤԤ
               ݡȤɥᥤͭԤΤ򤱤뤳ȤǤ<ul><li><b></b> -- Ƥ From: ɥᥤ DMARC  p=reject 
               Ȥ dmarc_moderation_action ŬѤޤ
               顼᡼˴ؿ뤬ǤΥ᡼Ф
                dmarc_moderation_action ŬѤȤŬ
               ޤ
               <p><li><b>Ϥ</b> -- Ƥ From: ɥᥤ DMARC 
               p=reject ޤ p=quarantine Ȥ dmarc_moderation_action
               ŬѤޤ
               </ul><p>꤬֤פΤȤ᡼
               From: ɥᥤ DMARC  p=quarantine 
               dmarc_moderation_action ŬѤ줺᡼ϥ顼
               ʤޤ󡣤Υ᡼륵С spam 졢
               ΥѤΥեʤɤǽޤ?AƤΤΤǤ뤫åȤˡ᡼륢ɥ쥹
ɥᥤˤƱΤΤǤȤưɥᥤΡ2Ρץꥹ%(newaddr)s ˳ǧ᡼ޤޤȤɤߤȯޤꥹ̾ꤷƤƥȷʳźեեݴɤޤ...
ե̾: %(filename)s
:         %(ctype)s
:     %(size)d Х
:       %(desc)s
URL:        %(url)s
ѥ˺Τޤ᡼󥰥ꥹȤƤɽ硣źդå4ĤޤǤΥ֥ѡ(msg_headerǼ᤿
             text/plain ѡȡdmarc_wrapped_message_textǼ᤿
             text/plain ѡȡΥåǼ᤿ message/rfc822 
             ѡȡmsg_footerǼ᤿ text/plain ѡ)鹽
             multi-part/mixed ΥåΥåʳ
             ѡȤɤ⳺ʤˤ message/rfc822 å
             줫ηˤʤޤǧǧƤФǧΤޤưƤʤƤФư餹٤Ƥα᡼Ф:᡼뤬źեե§˥ޥåȤưդƤäȤưDMARC %(quarantine)sݥꥷĥɥᥤ󤫤ƤФư:<b>%(esender)s</b>ɤ줫ԥե륿ɲäfuzzyޡĤƤʤʸ򼭽ɲáޥɥ饤DzϿ롣

ˡ:
    add_members [ץ] ꥹ̾

ץ:

    --regular-members-file=ե
    -r ե
        ϿΥɥ쥹äե롣 1 Ԥ 1 ɥ쥹
        β̾ˤʤޤե `-' ꤵȡ
        ɸϤ᡼륢ɥ쥹ɤ߹ߤޤ

    --digest-members-file=ե
    -d=ե
        Ʊ͡βϤޤȤɤ߲ˤʤޤ

    --invite
    -i
        ϿΤǤϤʤԤΤ߹ԤˤΥץ
        ꤷޤ

    --invite-msg-file=file
    -m file
        --invite ꤷݤ뾷ԥ᡼ƬˤΥץ
        ꤷեƤΥåޤ

    --welcome-msg=<y|n>
    -w <y|n>
        ꥹȲˡޥ᡼Фɤϥꥹ
        `send_welcome_msg' ͥ褷ޤ
        Υץ --invite ꤷˤ̵ˤʤꡢ
        ǤΥꥹȤ˽ޤ

    --admin-notify=<y|n>
    -a <y|n>
        ꥹȴԤϿ/ԤΤ뤫ɤϥꥹ
        `admin_notify_mchanges' ͥ褷ޤ
        Υץ --invite ꤷˤ̵ˤʤꡢ
        ǤΥꥹȤ˽ޤ

    --nomail
    -n
        ϿΥ᡼ץ̵ꤷޤ
        Υץ --invite ꤷˤ̵ˤʤꡢ
        ǤΥꥹȤ˽ޤ

    --help
    -h
        ΥإץåϤƽλޤ

    listname
        Ͽ褦Ȥ Mailmanꥹ̾˺Ƥʤ
        ʤޤ

ʤȤ -r  -d Τɤ餫1Ĥλ꤬ɬפǤ
ξꤹ硢`-' ȤΤϤɤ餫1ĤǤ
ܤɲ...ɲ   : %(s)sϢΤ¾¾ˡΥ᡼ž:ɥ쥹 %(schange_from)s  %(schange_to)s ѹޤɥ쥹ѹѹΥɥ쥹ɥ쥹ѹɥ쥹/̾/ɥ쥹:ɥ쥹פޤΥɥ쥹ˤϡԤκȤά̵˵ݤޤ
1ԤˤĤ1IJɥ쥹ޤ
ɽȤȤϡԤκǽ ^ ǻϤƤɥ쥹Ƥԥɥ쥹:/ʲԤΥڡ᡼󥰥ꥹȤФԤΥѥɤפޤޥɸǤƤåơ줬
 οǤ뤫Ĵ٤ޤ(Ȥ
 subscribe, unsubscribe, )ƴԤ˲ä
 Ԥ˿Ƥ뤳Ȥ
 Τ餻ޤ ΥۥȤˤɤʥꥹȤ뤫ʹ줿
ɽޤ?źեե̡᡼뤬ˤʤޤѥɳǧ:Ū To: ޤ Cc: äƤ Υꥹ
    ȤؤԤ褦̾(ɽ)All Ͼ qrunner ¹Ԥ˲ǤѤ: %(member)s¸ˤޤ?`require_explicit_destination' ꤵƤȤ
 ꥹȤ̾ȸʤɥ쥹Ǥ, ٤Ƥΰ襢ɥ쥹
 бӤɽΥꥹȤǤ1Ԥ1ɥ쥹򵭽Ҥޤ
 Ӥˤ Python  re.match() ؿȤ뤿ᡢ
 ɬʸƬбĴ٤ޤ

<p>Mailman 1.1 Ȥθߴݻ뤿ˡɽ `@'
 ޤޤƤʤС襢ɥ쥹ΥѡȤȤбĴ٤ޤ
 Ӥη̡бĤʤäꡢѥ `@'
 ޤޤƤϡ襢ɥ쥹ΤȥѥȤӤޤ

<p>Υ꡼ǤϥѡȤȤӤϹԤ鷺
襢ɥ쥹ΤȤбӤͽǤĤHTMLźեեݴɤޤ...
URL: %(url)s
%(listaddr)s Υ᡼󥰥ꥹȤˤʤΥɥ쥹Ͽ褦Ȥ
ߤޤʤϴˤΥ᡼󥰥ꥹȤ񤷤Ƥޤ

ΥꥹȤϲˤƤ뤿ᡢԤ褦
ȤƤΤ⤷ޤ󡣥ץ饤Хɤˡ
󶡤ϤޤǤ

⤷ѤߤǤ뤳Ȥ˺򤷤ΤǤСΥ᡼
̵뤷Ƥ⤷ʤΥꥹȤ˲Ƥ뤫ɤ
Ūï᡼󥰥ꥹȲߤȻפˡץ饤
ˤĤƤηǰ
%(listowner)s Υ᡼ǥꥹȴԤˤ̤
ʸɻ̵źʸݴɤޤ...
̾: %(filename)s
URL:  %(url)s
źե᡼ݴɤޤ...
: %(who)s
̾:   %(subject)s
:   %(date)s
: %(size)s Х
URL:    %(url)s
Υ᡼󥰥ꥹȤξҲʸ ()
ξҲʸϡΥڡ HTMLȤưѤޤ
ʤԤϲԥѴޤ
ܤ infoξܺ٤򻲾ȤƤïǤǧ44ӥ¸ˤޤ?¸˥ץɬפʤȥꥢ88ǧڼǧڼư˴ѥɤưޤ?ưư<p>

ʲΥƥȥեɤǤϡ
ʲִѿȤޤ:
<p><ul>
   <li><b>listname</b> - <em>ΥꥹȤ̾</em>
   <li><b>listurl</b> - <em>ΥꥹȤ listinfo URL</em>
   <li><b>requestemail</b> - <em>ΥꥹȤ -request ɥ쥹</em>
   <li><b>owneremail</b> - <em>ΥꥹȤ -owner ɥ쥹</em>
</ul>
<p>ƥƥȥեɤˡľʸ̤뤳ȤǤޤ
ޤʬΥԥ塼Υե򥢥åץɤ뤳ȤǤޤ"%(realname)s" ᡼󥰥ꥹȰ줿᡼ؤμư-owner Υ᡼Ф뼫ưʸ(-request)᡼Ф뼫ưʸ᡼󥰥ꥹƼԤؤμưʸʲԤξǧԤäƤޤB--digest ץ󤬰㤤ޤ: %(kind)s--nomail ץ󤬰㤤ޤ: %(why)sMIMEפ˸꤬ޤ̵뤷ޤ: %(spectype)sURLεҤְäƤޤǧѥɤְäƤޤα᡼α³ޤ-a/--admin-notify ؤΰ㤤ޤ: %(arg)s-w/--welcome-msg ؤΰ㤤ޤ: %(arg)s˴ְ㤤ޤ: %(arg)sθ: %(pargs)s㤤ޤ: %(strargs)s̵: %(yesno)sޥɤ㤤ޤ: %(command)sǧʸ󤬴ְäƤޤ֤ޤȤɤߡפλؼ㤤ޤ: %(arg)s%(k)s ץΥ᡼륢ɥ쥹ְäƤޤ: %(v)s%(property)s ץΥ᡼륢ɥ쥹ְäƤޤ: %(error)sʤ᡼륢ɥ쥹Ϥޤ¥ե饰ְͤäƤޤԥ᡼륢ɥ쥹θ: %(s)s塼ǥ쥯ȥλְ꤬äƤޤ: %(qdir)sɽ˸꤬ޤ: set ޥɤ˴ְ㤤ޤ: %(subcmd)sstatusλְ꤬äƤޤ: %(arg)s<a href="?VARHELP=bounce/%(property)s">%(property)s
</a>ְͤäƤޤ: %(val)sޤ̵ʥ᡼륢ɥ쥹ޤ̵ʥ᡼륢ɥ쥹: %(member)sޤ̵ʥ᡼륢ɥ쥹: ץιܤ:
 %(record)s<b>%(esender)s</b>򤳤Υ᡼󥰥ꥹȤ
ʵפӽޤӽꥹػߥɥ쥹 (%(pattern)s ˰)ޤȤɤ()ԤޤΤƬդʸϤʲϤƤ
ǽԤθ, Ԥ1԰ʾƤ...Bcc:(Ʊ)䰸ʤ᡼ϼդƤޤ
To:()Cc:(Ʊ)ˤΥ᡼󥰥ꥹȤΥɥ쥹
ƤƤ顼顼Τδ顼<em>˺</em>ܥ򥯥åȡ
ѥɤ᡼ޤ<em></em>ܥ򥯥åȡǧΥ᡼뤬ܿͰޤ
Υ᡼˽񤫤Ƥ󥯤򥯥åλޤ
(᡼dzǧ뤳ȤǤޤ; ܤϡ᡼λؼɤߤ)ϿΥǥեȤդˤޤ?ͤ<em></em>ꤹȡΥꥹȤǤϼư顼
ʤʤޤξϤꥨ顼᡼˴ޤ顢
ԤѤ蘆뤳ȤϤޤ<em></em>ꤹȡ顼ˤ
ꥹȴͤΤޤ
ؤΤ³ޤ<em></em>ꤹȡ顼ˤ
ؤߤꥹȴͤΤޤ
ؤΤ³ޤCGI ץȥ顼ꥹȲϥȤǤޤȤɤߤ륪ץǤޤ?ޤȤɤβˡؤѹĤޤ?HTML ڡˤ뤳ȤϤǤޤä󥻥롦˴αƤääƼämboxե %(mbox)s 򳫤ޤ: %(msg)sɥ쥹ե %(filename)s ɤޤ: %(msg)sޤȤɤߤ̤ξβɸϤɤ߹ळȤϤǤޤ%(filebase)s ᡼ե unshunt ǤޤФޤ:
%(e)sǤޤ:˥ư(ǥ졼)򤫤ޤǤΰΰƿξ¡Ƥǧ᡼˴ޤޤԿξ¡ɥ쥹̾ѹѥѹꥹȤΥѥɤѹ롣

Mailman 2.1 ˤʤޤǡꥹȤΥѥɤϰŹ沽Ƥޤ(̤)
Python μˤäƤ crypt ⥸塼뤬̵ơMD5 ǰŹ沽Ƥ
Ȥ, Python С󥢥åפ crypt ⥸塼뤬
ȡ뤵褦ˤʤꡢΤѥɤƤޤȤ
ޤ

Mailman 2.1 Ǥϡ٤ƤΥȥѥɤ SHA1 16ʿη¸
褦ˤʤޤΤᡢMailman 2.1 Τ٤ƤΥѥɤϲ
ƤޤΥѥɤʿʸǤϤɤˤ¸Ƥʤᡢ
᤹ȤǤޤ

ΤᡢΥץȤϿꥹȥѥɤץ
٤ƤΥꥹȴԤ뤳ȤǤޤ

ˡ: change_pw [ץ]

ץ:

    --all / -a
        ΥꥹȤˤĤƥѥɤѹ롣

    --domain=ɥᥤ̾
    -d ɥᥤ̾
        ֥ɥᥤ̾פβۥɥᥤΥꥹˤĤƥѥɤ
        롣ʣ -d ץդ뤳Ȥǽ

    --listname=ꥹ̾
    -l ꥹ̾
        ΥꥹȤˤĤƤѥɤѹ롣ʣ -l ץ
        դ뤳Ȥǽ

    --password=ѥ
    -p ѥ
        ʿʸǽ񤤤ֿѥɡפѹꥹȤοѥ
        ɤˤ롣(-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 ʹߤƳ줿pickleǡ١Ǥ
config.db  config.db.last ϤΥСǻȤƤ
ǡPython marshalեǤconfig.safety ϡ2.13aʹߤ config.pck
ɤʤȤ˺pickleեǤ

ˡ: %(PROGRAM)s [ץ] [ꥹ̾ [ꥹ̾ ...]]

ץ:

    --all / -a
        ΥꥹȤˤĤƥå롣ǤʤХꥹ̾λ
        줿ΤˤĤƤΤߥå

    --verbose / -v
        Ͼ¿ФåեΤ٤ƤˤĤơ
        Ϥ롣ǤʤС줿եɽ롣

    --help / -h
        Υإץåɽƽλ롣
αδåɬפʤꥹȴԤ˥᡼뤹롣

ˡ: %(PROGRAM)s [ץ]

ץ:

    -h / --help
        Υåɽƽλ롣
Mailman 󥹥ȡΤΥѡߥåå롣

ˡ: %(PROGRAM)s [-f] [-v] [-h]

̵ˤϡåƥѡߥå䥰롼׽ͭ
äƤե𤷤ޤ-f ץդ(root¤
¹Ԥ)ˤϡΥѡߥåޤ
-v ץǤ¿ξϤޤ
()().mbox β᡼ե򤭤줤ˤ롣

¸ˤκˤϡmbox β᡼ե뤫 Unix-From Ԥ
õФޤߴΤ, ä "From " ǻϤޤ -- Ĥޤꡢ
ʸ F ǻϤޤäơʸ r, o, m ȶõιԤλĤ
̵뤷ޤ

̾᡼ʸ "From " ǻϤޤԤ > ʸǥ
ƤϤǤˤäƤʸιԤפ
ʤ⤷ޤ󡣤ΥץȤϡUnix-From Ԥ̩˸
ȤˤꡢνߤΤǤ"From " ǻϤޤäƤ뤬
θ̩ʸ̤ʤԤϡ> ʸȤäƥפޤ

ˡ: cleanarch [ץ] < ϥե > ϥե
ץ:
    -s n
    -status=n
        n Խ뤴Ȥ # 1ĤĽϤ롣

    -q / --quiet
        ѹ줿Ԥξɸ२顼˽Ϥʤ

    -n / --dry-run
        ºݤˤϤʤˤϤʤ

    -h / --help
        Υإפɽƽλ롣
Ϥõβ<em></em>ե饰򥯥ꥢ򥯥åɽ򱣤ˤϡ򥯥åɽɽˤϡ򥯥åΥڡɽˤϡ򥯥å󥯤򥯥åȡΥ᡼󥰥ꥹȤΥץڡ˰ưޤ᡼ֹ򥯥åƸġΥ᡼򸫤뤫ɥ쥹Υ

ɥ쥹ΥȤ, βɥ쥹Ʊץ
ѥɤǿϿ뤳Ȥ̣ޤȤƤϡ
ϼ¹ԼԤѤƤ뤳ȤǤĤޤꡢɥ쥹γǧ䡢
褦᡼ȯʤɤԤʤȤȤǤ

¸ϿˤѹϤޤ󡣤⤷Ťɥ쥹
ΤǤС-r ե饰ȤäƤޤꥹȴɥ쥹ѹ
ΤǤС-a ե饰ȤäƤ

ˡ:
    clone_member [ץ] 쥢ɥ쥹 ɥ쥹

:

    --listname=ꥹ̾
    -l ꥹ̾
        ꥹ̾Υ᡼󥰥ꥹȤˤĤƤѹ롣⤷-l 
        ̵С٤ƤΥ᡼󥰥ꥹȤ롣-l ץ
        ʣꤹ뤳Ȥǽ

    --remove
    -r
        塢쥢ɥ쥹ꥹȤ롣

    --admin
    -a
        ꥹȤδԥɥ쥹쥢ɥ쥹õ⥯
        ޤѹ롣

    --quiet
    -q
        ѹŤ˹Ԥ

    --nomodify
    -n
        ɤѹ뤫ɽ뤬ºݤˤѹʤ--quietե饰
        Ȥ϶ѤǤʤ

    --help
    -h
        Υإץåɽƽλ롣

쥢ɥ쥹ϲѹΥɥ쥹ǡɥ쥹ѹΥɥ쥹
åɲ
ɥ쥹򱣤ޤʬƥȥեεҤꥹȤԤ

ˡ: config_list [ץ] ꥹ̾

ץ:
    --inputfile ե̾
    -i ե̾
        ꥹȥ֥Ȥ°˥⥸塼ѿƤ
        ȤǥꥹȤԤꥹȤ¸롣ե̾
        ꤵ줿ե execfile() Ȥäɤ߹Τǡ
        Python ΥɤǤʤФʤʤ˥ꥹȤ°Ȥ
        Ƥʤѿ̵뤵롣(ٹåФ)
        -c ץ⻲ȤΤȡ

        ̤ѿ̾ mlist ѿդΤǡºݤ MailList
        ֥Ȥ°Ȥʤ롣ΤȤϥꥹȥ֥Ȥ
        ؤƲǤǤ뤳Ȥˤʤ뤬դʤ! 
        Ȥȥ᡼󥰥ꥹȤ˿»Ϳ(Բǽˤʤ)ǽ
        롣

    --outputfile ե̾
    -o filename
        ꥹȤԤΤǤʤΥץȤϤ˹礦ͤˡ
        ߤѿϤ롣ˤäơΥꥹȤ
        Фơ̤ΥꥹȤ˰ܤѤ뤳ȤǤ롣
        ե̾ϤϤ񤭹ޤե̾Ǥ롣
         - ˤƤȡɸϤ˽񤭽Ф

    --checkonly
    -c
        ΥץǤϡºݤѹϹԤʤ-i ץ
        ȤäȤͭ

    --verbose
    -v
        °ѹäȤ̾ɽ롣-i ץ
        ȤäȤͭ

    --help
    -h
        Υإץåɽƽλ롣

-o ץ -i ץƱ˻ȤȤǤʤ

ǧǧ (*) - ᡼ˤܿͤγǧɬ<br>
ǧ - ꥹȴԤξǧɬ<br>
ǧ+ǧ - ǧȾǧξɬ

<p>(*) ïФ Mailman ֹ
 դֿޤԤϤֹȤäֿʤ
 Ǥޤ<br>
 ˤ¾ͤλ񤵤Ȥͭ
 (뤤ϰդ) ԰٤ɤȤǤޤԥѥɤγǧ:ǧܾǧɥ쥹ѹǧޤѥɤγǧ:ʲԥѥɤγǧ:Ƽԥѥɤγǧ:ǧǧ¾̵ͤǤϿ뤳Ȥɤˡ
ܿͤΥ᡼륢ɥ쥹ǤγǧɬפǤ
%(email)s ᡼λؼ˽äƤ
ܿͤˤγǧʤǤޤΤǤդǧʸ󤬶Ǥǧʸ:ǧޤźեեźեեǧԤꥹȤʸ %ʸ  $ʸѹ롣

ΥץȤ bin/withlist ΥץȤȤƼΤ褦˼¹Ԥ롣

% bin/withlist -l -r convert <ꥹ̾>
ɤ߹ߥե뤬ޤ: %(filename)s񤭹ե뤬ޤ:ꥹȤ%(hostname)s ᡼󥰥ꥹȤ̤ϿΥ᡼󥰥ꥹȤ롣

ˡ: %(PROGRAM)s [ץ] [ꥹ̾ [ԥɥ쥹 [ѥ]]]

ץ:
    -l 
    --language=
        ꥹȤθ `' ꤹ롣2ʸθ쥳
        ( _ μ2ʸι񥳡) ɽ롣

    -u urlhost
    --urlhost=urlhost
        ꥹȤΥ֥󥿥եΥۥ̾ꡣ

    -e emailhost
    --emailhost=emailhost
        ꥹȤΥ᡼ɥᥤꤹ롣

    -q/--quiet
        ̾Ԥˤ(ǧθ)᡼ǥꥹȺΤ롣
        ץդȳǧȥ᡼ΤԤʤ

    -a/--automate
        ԤؤγǧԤ򤻤Τ롣 newlist 
        ޥɥ饤ˤΥץȥꥹ̾ԥɥ쥹
        ԥѥɤΤ٤Ƥꤹ뤳Ȥǡnewlist ÷
        ¹ԡĴԤؤΤԤʤȤǤ롣

    -h/--help
        Υإץåɽƽλ롣

ޥɹԤˤϤĤǤ¤٤뤳ȤǤ롣⤷̵ȡץץ
ФϤ׵᤹롣

Mailman ΥꥹȤϤ줾2ĤΥѥ᡼Ĥޤ᡼뤬ФƹԤȤ
ۥ̾ȡ֥󥿥ե URL äƤ롣Mailman ν
ԤȤˡǥեȤꤵ롣ʣβ Mailman 
ȤäƤȤˤϡΥǥեȤϺꥹȤ˹ʤ
⤷ʤ

ɥᥤꤹ뤿ˡꥹ̾ʲΤ褦˻ꤷơޥɤ񤯤ȤǤ:

    newlist --urlhost=www.mydom.ain mylist

, `www.mydom.ain' ϤβۥꥹȤδܥۥ̾Ǥ롣
ĤޤꡢꥹȰΥڡ
    http://www.mydom.ain/mailman/listinfo
Ǹ뤳ȤǤΤȤ롣ޤwww.mydom.ain  mm_cfg.py/
Defaults.py  VIRTUAL_HOSTS 򻲾ȤΤ˻Ѥ롣
᡼Υۥ̾ФȤˤʤ롣

⤷᡼Υۥ̾ VIRTUAL_HOSTS ǼФΤȰ㤨ꡢ
urlhost  VIRTUAL_HOSTS ϿƤʤˤϡΤ褦ˤ
`emailhost' ꤹ뤳ȤǤ:

    newlist --urlhost=www.mydom.ain --emailhost=mydom.ain mylist

ǡ`mydom.ain' ϥ᡼Υɥᥤ̾Ǥ롣⤷emailhost ꤻ
ۥۥȥơ֥ urlhost ̵Сmm_cfg.DEFAULT_EMAIL_HOST 
᡼륤󥿥ե˻Ȥ

ߴΤᡢꥹ̾ʲΤ褦ˤƿꥹȤ뤳ȤǤ:

    mylist@www.mydom.ain

ǡwww.mydom.ain  `urlhost' ˻Ѥ졢ޤۥۥȥơ֥
줬ʤС`emailhost' ˤѤ롣 `--urlhost'  `--emailhost'
꤬ͥ褵뤳Ȥա

⤷ꥹ̾ `mylist' ä顢᡼ۥ̾URLϤ줾
Defaults.py ޤ mm_cfg.py  DEFAULT_EMAIL_HOST  DEFAULT_URL
(DEFAULT_URL_PATTERN ؤߤ) Ȥ롣

ꥹ̾ϾʸѴ롣
̤Υ᡼󥰥ꥹȤ¸˥ǥ쥯ȥbad  shunt 塼ǥ쥯ȥݽ1¹Ԥ侩

ΥץȤ 'bad'  'shunt' Υǥ쥯ȥ󤷡
⤷mm_cfg.BAD_SHUNT_STALE_AFTER > 0 ǤСÿŤ
եޤ

⤷mm_cfg.BAD_SHUNT_ARCHIVE_DIRECTORY 񤭹߲ǽǥ쥯ȥ
ǤСΥեϤذưޤǤʤСޤ

'bad'  'shunt' ľ̾եޤʳ
åפޤ

ˡ: %(PROGRAM)s [ץ]

ץ:
    -h / --help
        ΥåϤƽλ롣
ߤΥɥ쥹ѹΥɥ쥹ϰۤʤäƤʤФʤޤǥޡǡ١ιλޤ1212Υ᡼󥰥ꥹȤΥǥեȸ졣ν͡
<input type="hidden" name="new_member_options" value="ignore">ΥꥹȤΥ᡼󥰥ꥹȤMailman %(version)s ˤ::         %(description)sǡ١ξܤˡޤȤɤޤȤɤߥեåޤȤɤߤإåޤȤɤߤΥإåƥޤȤɤ߲:֤ޤȤɤߡץץѤʤ˴<em></em>˥åƤ᡼˴ޤŤα᡼˴ޤ
ư˴򤷤ʤ 0 ˤƤα᡼˴롣

ˡ:
    discard [ץ] ե ...

ץ:

    --help / -h
        Υإץåɽƽλ롣

    --quiet / -q
        ȾϤʤ
%(listname)s ꥹȤΥ᡼ #%(id)s ˴˴digest_send_periodic åȤƤƥ᡼뤬ίޤäƤꥹȤ
ĤơޤȤɤߤȯ

ˡ: %(PROGRAM)s [ץ]

ץ:
    -h / --help
        Υåɽƽλ

    -l ꥹ̾
    --listname=ꥹ̾
        ꥹ̾ǻꤷꥹȤˤĤƤޤȤɤߤ롣
        줬̵硢٤ƤΥꥹȤν򤹤롣

    -e ꥹ̾
    --exceptlist=ꥹ̾
        ꥹ̾ǻꤷꥹȤˤĤƤϡޤȤɤߤʤ
        ʣΥꥹȤޤȤɤоݤ鳰˷֤
        ꤹ뤳ȤǤ롣
Ƥܿͤˤޤ%(hexlversion)s  %(hextversion)s ؤΥ󥰥졼ɤ򸡽Фޤ
˼¹ԤǤʤǽޤ
λޤ帡⡼Mailman Υǡ١եƤɽ롣

ˡ: %(PROGRAM)s [ץ] ե̾

ץ:

    --marshal/-m
        ե Python  marshal Ȳꤹ롣ư̵
        ʤ롣

    --pickle/-p
        ե Python  pickle Ȳꤹ롣ư̵
        ʤ롣

    --noprint/-n
        ֥ȤɽԤʤϥ֥Ȥˤʤ餫
        ꤬äơpickle βɽԤͭǤ롣
        `python -i bin/dumpdb ե̾' ηǻȤȤ褤ξ硢
        Хѿ "msg" ĥ꡼¤Υ롼ȤȤʤ롣

    --help/-h
        Υإץåɽƽλ롣

ե̾ `.db' ǽȤ, Python  marshal ꤷ`.pck' 
Ȥˤ Python  pickle ꤹ롣ɤξ⤳β
̵ˤ䡢ɤγĥҤǤ⽪äƤʤȤˤϡ-p ޤ -m
ե饰Ȥȡ
Ƥإåե륿§ˤϡ1Ԥ1ĤɽҤ줿ꥹȤȡ
Фưꤷޤ᡼Τإå
ε§˵Ҥ줿ɽȥޥåɤ줫ȥޥå
ꤵ줿ư˽äƵݡαޤ˴ޤ
Ū˵§̵ˤϡ<em></em>פꤷޤ

줾Υ᡼󥰥ꥹȤʣΥե륿§ꤹ뤳ȤǤޤ
Ƶ§Ͻ֤˸졢ޥåإåФ줿ǽλޤ

: إåϤ٤ƤźեեʬޤƥޥåоݤȤʤޤ( Mailman δѤΥ᡼Ͻ)
뤳Ȥǡʥե륿פĥҤĥ᡼Ȥ
ǤޤġβϡľܥꥹȤƤǤ뤫ʲԤξǧɬפȤ뤫
ꤹ<em>¥ե饰</em>äƤޤ
¥ե饰åȤƤˤƤϡǧ³
ɬפˤʤޤꥹȴԤϡβˤƤ
¤뤫ɤ뤳ȤǤޤ

<p>񤷤¥ե饰ϡꤷͤ˥åȤޤ
ƤǧǥեȤˤ
Υץ򥪥 ()ˤޤǥեȤDzˤƤ
ϡ򥪥 (Ϥ) ˤޤġβ¥ե饰ϡ
<a href="%(adminurl)s/members"></a>餤ĤǤ
ꤷľȤǤޤˤϤ줾ưΥ顼դޤMailman ꥹ
饨顼᡼ȡβΥ顼ûޤ
顼(̿Ū顼)1, 夤顼(Ū顼)0.5
ûޤ顼11ûޤäƤ1
10󥨥顼֤Ƥ⡢1ޤ

ѿϲΥ顼ξͤꤷޤͤۤ
ؤϼưŪߤޤ᡼󥰥ꥹȤ񤵤
櫓ǤϤޤꥭɤɽǡ᡼ʬ
Ūˤ <code>Keywords:</code>  <code>Subject:</code>
إåƤȰפ뤫ɤθ˻Ȥޤ᡼ʸƬ
񤫤줿 <code>Keywords:</code>  <code>Subject:</code> "إå"
ФƤ⸡ԤʤޤHTMLԽ : 顼ץԽ HTML ڡȥƥȥեԽԽƥץ졼Ȥθѥɤ᡼äƤ᡼륢ɥ쥹:۵αͭˤʤäƤޤ۵αꤵƤޤ٤ƤƤ۵αˤޤꥹȤΥѥɤ϶ˤǤޤѤ<a href="?VARHELP=general/subject_prefix">֤̾</a>
ASCIIʸȤƤʤǤ沽ޤ?ʾ: Ѹ (ƹ)ǧʸϤƤԥѥɤϤƤʲԥѥɤϤƤ:ƼԥѥɤϤƤ:1Ԥ1ɥ쥹...ꥹȴԤΥ᡼륢ɥ쥹ϤƤ: ꥹȤ̾ϤƤ: 顼³Υ顼:Լ³Υ顼:%(listname)s ꥹȤ顼dzޤФޤ: %(e)s%(listname)s ꥹȤ顼dzޤ... Фޤ³Υ顼:顼: ڥȥ˥Х̤<tt>Reply-To:</tt>ɥ쥹̤Υɥ쥹᡼󥰥ꥹȤ XML ¸롣FAQ 4.48.22ꥹȲƤʣ᡼ޤ(ǽʤ)إåŬѤե륿§ǽ°ꥹȤ򸡺롣

ˡ:
    find_member [ץ] ɽ [ɽ [...]]

:
    --listname=ꥹ̾
    -l ꥹ̾
        ꤷꥹȤ鸡

    --exclude=ꥹ̾
    -x ꥹ̾
        ꤷꥹȤ򸡺оݤϤ

    --owners
    -w
        ǤʤꥹȴԤ⸡

    --help
    -h
        Υإץåɽƽλ

    ɽ
        Ŭ򸡺 Python ɽ

-l  -x ץδطϰʲΤ褦ˤʤ롣⤷ -l ץ
ꤵƤ顢ΥꥹȤ򸡺˴ޤ롣⤷ -x ץ
ä -l ץ̵ϡꤵƤʤ٤ƤΥꥹȤ
оݤȤʤ롣

ɽ Perl5 ˻Ƥ뤬, Python  re ⥸塼Ȥ re
⥸塼λͤϰʲΥڡˤ:

https://docs.python.org/2/library/re.html
(ܸǤ https://docs.python.org/ja/2.7/library/re.html)

᡼륢ɥ쥹ʸʸζ̤򤻤˸뤬̤ɽ
ʸޤǹԤ롣

 %(link)s:եɸ1MM2.1b4 ¸ˤ롣

ˡ: %(PROGRAM)s [ץ] ե ...

, ץ:
    -h / --help
        ΥإץåϤƽλ롣

Mailman 2.1b4 Ǻ;פʥǡ񤭹ޤ줿¸ˤ
ˤȤޤ$PREFIX ǥ쥯ȥ꤫顢Τ褦˻ȤäƤ

%% %(PROGRAM)s `grep -l _mlist archives/private/*/database/*-article`

(ХåȤɬפǤ뤳ȤդƤ)

ΥץȤ¹Ԥǡbin/check_perms -f ¹Ԥɬפޤ
ƥץ졼Ȥ: %(listname)sơ֤ޤȤɤߡפդեåؤΥ᡼ղäեåʤ餫ͳ %(mbox_dir)s եȤ¸ߤޤ b6 ǤϤ
ȤޤΤǡ%(mbox_dir)s.tmp ѹ˿ʤߤޤ餫ͳˤ᡼(̤)Υɥ쥹ž:α줿᡼žꥹȴԤžžץ4ե󥹸ȯ:ȯ: %(sender)s
:   %(date)s
̾:   %(subject)s
:   %(reason)sĿŪʥꥹȤ󡢴ưꥷŪץMailingList֥Ȥ뤿ΰŪȤߡ

ΥץȤλȤ2̤ꤢ: 󥿥饯ƥ֤ȥץŪǤ롣
󥿥饯ƥ֤˻Ȥ, Pyhton Υ󥿥饯ƥ֥󥿥ץ꥿Ѥ
MailList ֥Ȥ򸡺ꡢѹꡢͷ֤ȤǤ롣
󥿥饯ƥ֤˼¹ԤȤˤϡХ֤̾ `m' 
 MailList ֥Ȥ¸ߤ롣ޤMailList 饹򥰥Х
֤̾ɤ߹ࡣ

ץŪˤ MailList ֥Ȥ褦ʴؿ񤯤Ȥ
ǽǡΥץȤϲȻڤä򤹤(ʲ򻲾)
ξΰŪʸ:

%% bin/withlist [ץ] ꥹ̾ [ ...]

ץ:
    -l / --lock
        ꥹȤ򳫤Ȥ˥å롣̾ꥹȤϥå˳
        (Ĥޤ, ɤ߹Ѥ)夫 `m.Lock()' Ϥ
        Ȥǥå뤳ȤǤ롣

        ΥץȤȤɬ m.Save() λ˸ƤӽФ
        դʤʤʤ顢󥿥ץ꥿Υ꡼󥢥å׽Ǥ
        MailList ֥ȤѹưŪ¸ʤǤ롣
        (ưŪ˥åϹԤ)

    -i / --interactive
        ¾νλ饤󥿥饯ƥ֥⡼ɤΥץץȤ
         -r ץ󤬻ꤵƤʤȤΥǥեȤǤ롣

    --run [module.]callable
    -r [module.]callable
         MailList ֥ȤˤĤƥץȤ¹ԤȤ
        ȤȤǤ롣 `module' ( withlist Τ
        ǥ쥯ȥ֤Ƥ뤫sys.path ǥ
        ǽǤ뤳)  import `callable' ƤӽФcallable
        ϥ饹ޤϴؿǤ롣ޤMailList ֥Ȥ1
        ȤƸƤӽФ⤷ޥɹԤɲäΰ callable
        ΰ³ȤϤ롣

        module ϥץǡ⤷ά callable ̾
        ⥸塼뤬 import 롣

       Хѿ `r' ˸ƤӽФη̤롣

    --all / -a
        Υץ -r ץꤷȤͭǤ롣⤷
        ٤ƤΥ᡼󥰥ꥹȤ˥ץȤŬѤȤˤϡ
        Ȥ-a ꤷȤˤϡޥɹԤ˥ꥹ̾ƤϤʤ
        ѿ `r' Ϥ٤Ƥη̤ΥꥹȤȤʤ롣

    --quiet / -q
        ֥å򤹤٤롣

    --help / -h
        ΥåϤƽλ


-r ץλȤ򤢤롣ȤСMailman Υ󥹥ȡ
ǥ쥯ȥˡ`listaddr.py' Ȥ̾Υե뤬ꡢʲ2Ĥ
ؿäƤȤ롣

def listaddr(mlist):
    print mlist.GetListEmail()

def requestaddr(mlist):
    print mlist.GetRequestEmail()

ȡޥɥ饤󤫤鼡Τ褦ˤơꥹȤƥɥ쥹ɽ
ȤǤ:

%% bin/withlist -r listaddr mylist
mylist ΥꥹȤɤ߹ (å)
listaddr  import ...
listaddr.listaddr() ¹ ...
mylist@myhost.com

ޤꥹȤοɥ쥹ϰʲΤ褦ˤɽǤ:

%% bin/withlist -r listaddr.requestaddr mylist
mylist ΥꥹȤɤ߹ (å)
listaddr  import ...
listaddr.requestaddr() ¹ ...
mylist-request@myhost.com

⤦ĤȤơꥹȤΤΥѥɤѹȤ褦
Τ褦ʴؿ `changepw.py' Ƥ:

from Mailman.Errors import NotAMemberError

def changepw(mlist, addr, newpasswd):
    try:
        mlist.setMemberPassword(addr, newpasswd)
        mlist.Save()
    except NotAMember:
        print 'ɥ쥹ޤ:', addr

ơޥɥ饤󤫤鼡Τ褦˼¹Ԥ:
%% bin/withlist -l -r changepw mylist somebody@somewhere.org foobar
ꥹڡ᡼󥰥ꥹȤŪʿʸʸХʥΥå롣

Υץʿʸ Uniforum Υå (.po ե)
顢Хʥ GNU  (.mo ե) Ѵ롣Υץ
ǽϴŪ GNU  msgfmt ץƱǤ뤬ñƤ롣

ץ:
    -o ե
    --output-file=ե
        񤭹ϥեꤹ. ά filename.mo 
        (ϥե̾򸵤ˤ) ˤʤ롣

    -h
    --help
        Υإץåɽƽλ롣

    -V
    --version
        СϤƽλ롣
ɥĸGnu's Not UnixꥹȤ¸ˤ˰ưꥹΥڡꥷGzip̥ƥ %(sz)sHTML ѹޤǤHTMLźեե, ƤޤHTML ѹλޤ֤ޤȤɤߡפդإåؤΥ᡼դإåإåե륿§ˤɬѥꤷƤ
Դʥե륿̵뤵ޤإåե륿᡼إåɽ˹פޤ: %(pattern)sإ֥饤α᡼᡼Ԥ򱣤ơꥹȤΥɥ쥹֤
(From, Sender  Reply-To ޤ)Enter 򲡤 %(listname)s δԤ˥᡼Τ...αꤷɽ˥ޥåإåƤα롣α᡼˻Ȥۥ̾(ɥᥤ̾)ʥɥ쥹 (§ʸ)ʥɥ쥹 (§ʸ): %(member)sλߤ򸡽ƥ᡼뤬Kb ʾˤʤä֤ޤȤɤߡפȯޤ? 0 ꤹȥäˤȯϤޤ<em></em>ηٹ᡼򲿲äƤ顢ºݤ
 β᡼󥰥ꥹȤޤ? 0 ꤹȡ
 顼ͤ㨤ޤ
 ͤǤ᡼ʸβܤޤ򥹥󤷤ޤ?¸ˤοϤ٤ϤɤΤ褦ˤޤ?֤ޤȤɤߡפοϤ٤ϤɤΤ褦ˤޤ?ϥ󥬥꡼˰ƿοãȡβưŪ
               (ǥ졼)ޤεǽ̵ˤˤ0ꤷޤ
               Ρְ֡פˤĤƤ
               <a href="?VARHELP=privacy/sender/member_verbosity_interval"
               >member_verbosity_interval</a>򻲾ȤƤ

               <p>εǽñޤʣΥꥹȤϿƥܥåȤ
               Ѥû֤Τ¿ spam Ĥ褦ʿͤ
               ޻ߤ뤿ΤΤǤ

               <p>εǽꤹȤˤϽʬդƤ
               ⤷ͤ򾮤ꤷȡ̤ƤʣΥꥹȤ
               ޤäƹԤäꡢ̤οƥꥹȤؤƤǤ¤
               äޤ Mailman ƥ member_verbosity_threshold ͭˤʤäƤ
               ꥹȤ٤ƤǤΰˤƿιפ
               ΥꥹȤ member_verbosity_threshold ͤãȡ
               βϼưŪ(ǥ졼)ޤ

               <p>ΥꥹȤ member_verbosity_threshold Ӥ
               ƿϡ member_verbosity_threshold ͭˤʤäƤ
               줾Υꥹ member_verbosity_interval 
               ϤƤ٤ƤǤΥꥹȤӽꥹȤ˴ޤޤ1İʾΥꥹȤƱ˸줿
             ƤϽꥹȤβˤϤΥꥹȤ
             ޤ󤬡ƼԤνꥹȤβǤʤˤ
             ꥹȤβˤƤʤޤޡƤ
             νꥹȤǤ뤳Ȥޤ
             ֤ϤפꤹȡƼԤνꥹȤ
             Ǥʤ褦ʤνꥹȤˤĤƤ⡢
             νꥹȤ̵뤷ޤͰʾμԿꤵ줿᡼ϡ
ǧΤαޤ0̵¤ΰ̣ˤʤޤdmarc_moderation_action ŬѤ졢줬֥᡼źաפǤȤˡ
ΥƥʸꤵƤˤϡƥå
ΥƥʸΩMIMEѡȤȤޤꥹȤβǤ뤫γǧΤȤƱѡȤǥɥᥤ
               ĤƼԥɥ쥹ƱȴȤΥɥᥤ
               ˽񤭤ޤƱȴɥᥤΥ롼פ
               뤤ʣ񤯤ȤǤޤ줾Υ롼פ
               ߥ:פǻڤꡢ롼פΥɥᥤ
               ޡ,פ¤٤ƽ񤭤ޤ̵뤵ޤ
               <p>:<pre>
               example.com,mail.example.com;mac.com,me.com,icloud.com
               </pre>
               <p>Ǥ user@example.com ꥹȤβäȤ
               Ƥ user@mail.example.com ΤΤä硢
               ꥹȤβǤ뤳Ȥγǧ(ǥ졼)
               ǧκݤˤϤƤ user@example.com ΤƱͤ
               ޤƱͤ user@me.com ꥹȤβä
               Ƥ user@mac.com 뤤 user@icloud.com ΤΤ
               äˤ user@me.com ΤƱͤ˰ޤ
               <p>դȤƤϡǤ뤫γǧˤƤƼԤ
               ɥ쥹ϤϤ˻졢ƱȴɥᥤΥɥ쥹
               ƼԤΥɥ쥹ǤʤäΤߤ˻ޤ
               <p>ޤ(ǥ졼)ˤĤƥɥ쥹
               Ʊɥᥤ󥢥ɥ쥹ŬѤޤּΡפ
               ̵ֹפȤä¾ΥץˤŬѤʤȤˤ
               դɬפǤʤʤ顢
ѥɤ᡼ޤʤꥹȲǤСѥ˺ΤޤʤꥹȲǤСǧ᡼ޤʤꥹȲǤСǧ³ΤꥹȴԤžޤƤݤ硢<br>ͳ (ץʥ):αƤ᡼˴ˤϡSubject: (̾) إå˼ä
ֿƤǥ᡼ʤ顢˴ƤꥹȤؤ
ǧϡApproved:إåˤΥ᡼󥰥ꥹȤΥѥ
դֿƤApproved: إåֿ᡼ʸƬ
뤳ȤǤޤѥɤϤϡǧϤɬפǤܸʤɡASCIIʳʸȤ줬Υ᡼󥰥ꥹȤ
ǥեȤθꤵƤơ
Ƥ줿᡼η֤̾ASCIIʳʸޤޤ硢
֤ɸŪˡ沽ޤ֤ASCIIʸ
ȤäƤʤС<em>ʤ</em>沽ʤ褦ˤǤޤ
粽ʤȤǡASCII沽бƤʤ᡼륽եȤǤ⡢
̾ɤߤ䤹ʤޤ
<p>Ƥ᡼η̾粽Ƥꡢ
粽Ƥʤäꤹϡ
<em>ɬפ˱</em>Ӥޤ
<em>ɬפ˱</em>֤ȡ
֤ʳη̾ASCIIʸʤ֤沽
ASCIIʸޤǤ֤沽ޤˤ
Υ᡼륽եȤ֤ȸΥإåδ֤ζäꤹ
Ǥޤ̵:   %(addr)30sƼԤ regular_exclude_lists βǤϤʤ褦ʤȤˤϤ̵뤷ޤαǡ˸ꡣ̵뤷ޤ: %(key)s: %(val)s줿ѹ̵: %(user)sְä Idĥ᡼̵: %(f)sαʳΥ᡼̵: %(f)stext/plainǤʤMIMEѡȤ̵ѤǤʤ᡼륢ɥ쥹ʥ᡼륢ɥ쥹ϤޤѤǤʤꥹ̾: %(s)sץޤ: %(opt)s%(module)s  import ...2ĤΥѥɤ˲äơΥꥹȤƤ뤿Υѥɤ
ꤹ뤳ȤǤޤΤɤΥѥɤƥ᡼Υإå
ʸκǽιԤǤ뵼إåˡإå̾ Approved: Ȥ
ѥɤ񤤤ƤȤǡα줺ˤΤޤ褦
Ǥޤ˲äƲΥѥɤƱ褦˻ȤȤǤޤ
¾ (admin  admindb ؤΥ) ˻ȤȤϤǤޤץѹˤϡޤΥե
%(extra)sѥɤƥ󤷤Ƥѥ
狼ʤȤϡΥܥ򥯥åȥ᡼ǥѥɤ
ޤޤΥꥹȤ񤷤Ȥϡ<em></em>
ܥ򥯥åƤǧΥ᡼ޤ

<p><strong><em>:</em></strong> λϡ֥饦
åͭˤƤƤå̵ˤȡ
ѹǤޤ
   ޤȤɤߤδä1˥ꥻåȤ

ˡ: %(PROGRAM)s [ץ] [ꥹ̾ ...]

ץ:

    --help/-h
        Υåɽƽλ

ޥɹԤΥꥹȤˤĤ bump 롣ꥹ̵̾ˤ
٤ƤΥꥹȤ bump 롣
%(listname)s νѥ: Ѥνꡣ<p>
άȥФꤵƤǥեȤθ%(deflang)sˤŬѤޤꥹȴԥɥ쥹ν: ꥹȥѥ:ѥɤפޤMailman  incoming 塼˥ե뤫᡼롣

ˡ: inject [ץ] [ե̾]

ץ:

    -h / --help
        ΥƥȤɽƽλ롣

    -l ꥹ̾
    --listname=ꥹ̾
        ᡼ꥹȤ̾ɬܡ

    -q 塼̾
    -queue=塼̾
        ᡼륭塼̾塼̾ qfiles ǥ쥯ȥ
        ֥ǥ쥯ȥ̾Ǥ롣άξϡincoming 塼
        Ȥ롣(塼Ԥ뤳Ȥ)

ե̾ϥ塼ʿʸΥ᡼ե̾Ǥ롣ά
ɸϤȤ롣
󥿡(ݸ)...̵:   %(addr)30sǧʸ̵Ǥ񤷤ɥ쥹οǧ褦
Ƥǽޤǧʸ̵Ǥǧʸ %(days)s
ڤˤʤޤΤǤդǤ˲餫μ
Ѥߤξ̵ˤʤޤǧ¤ڤƤ
⤦򤪴ꤤޤCGIץȤΥץ̵ǤCGI Υץ̵Ǥ ѥɷ̵ǤHTTPꥯȤΥ᥽åɤǤ: %(method)sץѥƥ̵ͤ: %(k)sѿ̵ͤ: %(property)sꥹξԤޤ: %(member)s¸ˤϳ˸ޤȤ˸ꤷޤ?qrunner ޤäƤޤ?ˤϡꥹȻʲԤξǧɬפǤ? (<em></em>侩)ꥢ11ܸ7766ڹ쥪ץΥꥹȤǻȤǸ줿ưꥹȤΥѥɤưŪ Mailman Ȥϡ
ѥ(ȳǧ)ˤƤƤǥ᡼кե륿ꥹꥹȤꥹȥإ: %(requestaddr)sꥹȼ̾ꥹȴ: %(owneraddr)sꥹȴԤΤ٤ƤΥ᡼󥰥ꥹȤɽ롣

ˡ: %(program)s [ץ]

:

    -a / --advertised
        줿ꥹȤɽ롣

    -p / --public-archive
        ¸ˤΥꥹȤɽ롣

    --virtual-host-overview=ɥᥤ
    -V ɥᥤ
        ɥᥤǻꤷۥɥᥤ°᡼󥰥ꥹȤΤߤ
        ɽ롣VIRTUAL_HOST_OVERVIEW ѿꤵƤɬ
        롣

    -b / --bare
        ꥹȤû̵ꥹȤΤߤɽ롣

    -h / --help
        ΥƥȤɽƽλ롣

᡼󥰥ꥹȤβɽ롣

ˡ: %(PROGRAM)s [ץ] ꥹ̾

:

    --output ե
    -o ե
        ϤɸϤǤʤꤷե˽񤭹ࡣ

    --regular / -r
        ̾(ޤȤɤߤǤʤ)Τߤɽ롣

    --digest[=] / -d []
        ޤȤɤ߲ΤߤϤ롣ץǻꤹ[]
        "mime" ޤ "plain" Τɤ餫ǡηǤΤޤȤ
        ɤߤꤷƤɽ롣

    --nomail[=ͳ] / -n [ͳ]
        ᡼ߤƤɽ롣ץǻꤹ
        [ͳ]  "byadmin""byuser""bybounce""unknown" 
        ɤ줫ǡͳߤƤɽ롣ޤ
        "enabaled" ꤹȡͭˤʤäƤɽ
        롣

    --fullnames / -f
        ̾ɽ롣

    --preserve / -p
        ᡼륢ɥ쥹ɽȤˡϤȤʸ/ʸ
        򤽤Τޤ޻ȤꤷʤȾʸѴ롣

    --moderated / -m
        (ǥ졼)줿Τߤɽ롣 -r, -d, -n ̵뤹롣

    --non-moderated / -M
        (ǥ졼)ƤʤΤߤɽ롣
        -r, -d, -n ̵뤹롣

    --invalid / -i
        ̵ʥ᡼륢ɥ쥹ϿƤϤ롣
        -r, -d, -n ̵뤹롣

    --unicode / -u
        ʸǤʤ˥ɥ֥ȤȤ¸Ƥ륢ɥ쥹
        Ϥ롣-r, -d, -n ̵뤹롣

    --help / -h
        Υإץåɽƽλ롣

    ꥹ̾ϻѤ᡼󥰥ꥹȤ̾

: -r  -d ꤷʤȡǽ̾ˤޤȤɤ߲ɽ
뤬ξ֤ˤĤƤɽʤ
᡼󥰥ꥹȤδԤɽ롣

ˡ: %(program)s [ץ] ꥹ̾ ...

:

    --all-vhost=ۥۥ
    -v=ۥۥ
        ۥۥȤ°뤹٤ƤΥ᡼󥰥ꥹȤδԤɽ롣

    --all
    -a
        ΥƥΤ٤ƤΥ᡼󥰥ꥹȤδԤɽ롣

    --help
    -h
        Υإץåɽƽλ롣

ꥹ̾ϴԤɽ褦Ȥ᡼󥰥ꥹȤ̾Ǥ롣2
ʾΥꥹ̾򥳥ޥɹԤǻꤹ뤳ȤǤ롣
ϿѤߥꥹȤǤ: %(listname)sϿѤߥꥹȤǤ: %(safelistname)sꥹȺԤǧڥѥ:ꥹȲʲ(ȴ)αδ˴ؤ˺Τޤ
 ȤΥꥹȤؤβ䡢餫ͳ
 αƤƤʤɤǤΥץꤹ
 뤿ӤľΤޤ¾ΥꥹȤؤꥹ̾ɬפǤꥹȤ̾ɬפǤꥹ̾ "@" ʸϻȤޤ: %(safelistname)sꥹ̾:     %(listname)s᡼륢ɥ쥹ΥɥᥤФƤDMARCݥꥷˤ餺
<a href="?VARHELP/privacy/sender/dmarc_moderation_action"
>dmarc_moderation_action</a>
ŬѤ᡼륢ɥ쥹(ޤɽ)Υꥹȡ˾ǧפʥɥ쥹(ޤɽ)ΥꥹΥ᡼󥰥ꥹȤؤݤ륢ɥ쥹ΥꥹȡưŪƤǧ٤Υɥ쥹ưŪƤ˴Υɥ쥹ưŪƤݤΥɥ쥹ʲǧΤľƤαΥɥ쥹ꥹȤΥѥ%(hostname)s Ǥ %(safeuser)s ΥꥹȲϿޤϰΥ᡼󥰥ꥹȤδԤɽ롣

ˡ: %(PROGRAM)s [ץ] [ꥹ̾ ...]

    -w /--with-listnames
        Ԥꥹ̾ǥ롼ײꥹ̾Ϥ˴ޤ롣
        ꤷʤȴԤϥ᡼륢ɥ쥹򸵤¤ؤñ첽
        Ԥ롣

    -m / --moderators
        ꥹȤλʲԤϤ˴ޤ롣

    -h / --help
        ΥإץåϤƽλ롣

    ꥹ̾
        ꤷꥹȤδԤϤ롣2İʾΥꥹ̾񤯤Ȥ
        Ǥ롣ꥹ̾Ĥ̵ˤϡΥꥹȤδԤɽ
        롣
ݡȤѥɡϥåꥹȤƽλ롣
âϥåλ羮ʸζ̤ϤʤꥹȤꥭ¸˺δ᡼Ƭʸꥹ:ꥹ: %(listname)s, 	: %(owners)sȥ˥%(listname)s ΥꥹȤɤ߹ꥹȤåMIME᡼᡼ &lt;-&gt; ˥塼᡼롦˥塼ӥꡣ%(listname)s ᡼󥰥ꥹȺο᡼󥰥ꥹȺ᡼󥰥ꥹȺη%(listname)s ᡼󥰥ꥹȺοMailmanMailman %(varname)s ꥹȥץ󡦥إMailman ǡ١顼Mailman ϡ<tt>Subject:</tt>إå(̾)<a 
href="?VARHELP=general/subject_prefix">ԤǤ֤</a>
դޤϡ̾Usenet ˥塼ž뵭ˤ⸽ޤ
Υץ<em></em>ˤžˤ֤Ĥʤ
褦ˤʤޤ̤Υ᡼˷֤̾դʤС
˥塼ˤդޤMailmanΥץ饤Хٹꤵ줿᡼륢ɥ쥹ηޤ
(ȤХɥ쥹ˤɬ @ ޤޤƤʤФʤޤ)ʲιܤѹơ<em>ѹ</em>Υܥ
 åƤ¿(ºݤˤϤۤȤɤ) ǥ᡼ʰ
Ū˰襢ɥ쥹˽Ϣͤ뤳ȤϤޤ
ºݤˤϡޤǤǤΥɥ쥹 To: ˽񤫤Ƥ뤳Ȥ
褯ޤꤹ¤ '@' κ¦ŬѤޤ
Ǥμǥ᡼򤹤٤ƿߤ뤳ȤǤޤ

<p>ˡ¾Υɥ쥹餽Τޤž줿᡼뤬
դʤʤޤ
<ol>
    <li>ѸΥɥ쥹 '@'κ¦Ʊ̾Ǥ롢ޤ
    <li>ѸΥɥ쥹Ƥդ̾ΥꥹȤ˴ޤޤƤ
</ol>
ȡդ褦ˤʤޤ33ޤȤޤȤϿåååå״λޤȤޤȤϿƥ᡼ʸκ祵(KB)̵¤ˤˤ 0 ꤷƤꥹȤ 1 ڡɽβ5ե륿̾ѹޤθߤΥɥ쥹ꥹ̾θ褷ޤꥹ...᡼ȴ:᡼إå:᡼ʸĹޤ: %(size)d ХȤޤ
¤ %(limit)d KB Ǥ᡼ʸ Mailman Ȥˤޤ
᡼ԿʥإåޤΥ᡼褬ɽƤޤޥɤޤޤƤޤե륿§˹פ᡼ݤޤåϵѲޤ
Υåˤ Approved: ѥɤιԤޤޤ줿 HTML ѡȤ
ޤޤ褦ǤHTMLؤΥɲΤ
˼ФȤǤޤ
դʲʲԤΥѥɤפޤۡڡ: %(listurl)s᡼ shunt 塼鸵Υ塼˰ư롣

ˡ: %(PROGRAM)s [ץ] [ǥ쥯ȥ]

:

    -h / --help
        إפɽƽλ

ǥ쥯ȥꤹ qfiles/shunt ʳΥǥ쥯ȥ꤫ư롣
*** ٹ *** shunt 줿ΤǤϤʤ᡼ unshunt ƤϤޤ
㤨Сqfiles/out Υ᡼ unshunt ȥ᡼뤬äƤޤޤ
§򲼤§夲From 񤭴ꥹ̾ȥե̾ɬפǤƤˤϥꥹ̾(to, cc) ˴ޤޤƤ
ʤФʤʤǤ礦? (ޤϰʲ˻
̾äƤʤФ
ʤ)?ꥹȤ̾:̾:(ݲ)ץʤ%(listname)s οѥ: %(notifypassword)s %(pwdesc)s Υѥ:οѥ %(member)40s: %(randompw)s%(realname)s ꥹȤ %(addr)s 鿷񿽤%(realname)s ꥹȤ %(addr)s 鿷񿽤˥塼Фε (å)ɥ쥹ϤƤޤ-f ΰޤPIDλҥץޤ: %(pid)sޥɤޤ᡼˥ޥɤޤޤƤޤ
ˡ󤻤ˤ, "help" Ȥ񤤤᡼äƤ
ե̾ꤵƤޤꥹȤ̾ɬפǤꥹȤޤ:ꥹ̾ޤоݤΥꥹȤޤŬ礹᡼󥰥ꥹȤޤΥꥹȤǤϡ֤ޤȤɤߡפǤϤǤޤ!ꤢޤͳϼƤޤrunner ̾ޤ̵%(listname)s ȤꥹȤϤޤ: %(e)s%(safelistname)s ȤꥹȤϤޤ%(listname)s ȤꥹȤϤޤ (, ˺Ƥޤ)<em>%(safelistname)s</em>ȤꥹȤϤޤ%(listname)s ȤꥹȤϤޤ%(listname)s ȤꥹȤϤޤ󡣻Ĥ줿¸ˤޤΤ褦ʲϤޤ: %(addr)s.Τ褦ʲϤޤ: %(safeuser)s.ɬפϤޤϿΤɥ쥹ĤޤǤͭѿ̾Ĥޤ:ץե륿ʳϤΥꥹȤƤǤޤɸǤʤͤ: %(k)s̵̵ - ǧ̵ (<em> ᤷޤ </em>)<br>
ǧ (*) - ᡼ˤܿͤγǧɬ <br>
ǧ - ꥹȴԤξǧɬ <br>
ǧ+ǧ - ǧȾǧξɬ

<p> (*) ïФMailman ֹդֿޤ
 ԤϤֹȤäֿʤǤޤ<br> 
 ˤ¾ͤλ񤵤Ȥͭ(뤤ϰդ)
 ԰٤ɤȤǤޤ̾MailmanϡΥ᡼ޤȤƥ᡼륵Фޤ
ˡ Mailman ȥ᡼륵д֤̤̿򸺤餻Τ
Ψ⤤ˡǤ
<p>
ĿͤȤ˥᡼뤳Ȥ˰̣᡼󥰥ꥹȤ⤢ޤ
ξ硢Mailman̾ꥹȤβȤˡ
᡼ʸޤϥΤǽǽ
ޤβͤ뤫ɤ¾ˡϤʤΤ
ʬ˸ƤƤ
ޤƥ٤ʬƻ뤷ơ˥ƥबѤ뤳Ȥ
ǧƤ

<p><em></em>֤ȡ᡼Ŀ̤ޤȤޤ
<em>Ϥ</em>֤ȸĿ̤إåȥեå
ִѿȤ褦ˤʤޤ<em>ĿͲ</em>֤
<code>To:</code>إåΥɥ쥹ꥹȤΥɥ쥹ǤϤʤ
ƲΥɥ쥹ˤʤޤ

<p>ĿǤϡ㴳ִѿ<a href="?VARHELP=nondigest/msg_header">
إå</a><a href="?VARHELP=nondigest/msg_footer">եå</a>
褦ˤʤޤ

<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>
    Υ륦̵ʥ᡼륢ɥ쥹: %(toaddr)sǧڼ¸ˤϺޤ󡣺ˤ -a ĤƤ⤦񤷤Ƥޤ:: ϥ᡼󥰥ꥹѤΥꥹȤǤѥ˺Τʤɤ
Τϡɥ쥹 %(addr)s ޤ: ᡼ϰŪߤƤޤ %(reason)sʤˤ⤹뤳ȤϤޤʲԤˤƵ: %(discarded)d οƷ郎ڤȤʤޤ

Τ %(schange_from)s ޤΤ %(schange_to)s. ޤ1111᡼󥰥ꥹȤ -request/-owner , ƱȯԤ
᡼˼ưֳ֤(ޤο)Ϥȡ
᡼뤬뤿Ӥ˱뤳Ȥˤʤޤμư(ǥ졼)Τ member_verbosity_threshold ˤ
               ΥꥹȤ˲ƤΤäȤϿƤÿ1010λ򡣥ꥹȻʲԤˤϡΥ᡼ǧ뤫ݤ뤫
ꤹ󥹤ޤޤ׵ˤѥ˺1᡼ǥѥɤ˺Τޤ-i ޤ -o Τɤ餫ꤷƤ᡼뤬źեե§˹פȤưꤷޤ
Ĥޤꡢֳ¦Content-Type
<a href="?VARHELP=contentfilter/filter_mime_types"></a>
Τɤ줫˥ޥå뤫
<a href="?VARHELP=contentfilter/pass_mime_types">̲᥿</a>
˥ޥå<b>ʤ</b>
̤ΥѡȤ̡᡼뤬ˤʤäưǤ

<p>ѡȤ줿˻ĤäźեեФƤ
ǤŬѤ줺˥᡼뤬ޤΤǤդ

<p>˴֤ȥ᡼˴졢Υ᡼ Message-ID
˵ϿޤݡޤϥꥹȴԤž줿ϡ
᡼ƼԤؤΥ顼Τ˵ݤͳܤޤ
ݴɤ֤ȡ᡼ϥۥȥԥ塼̤ʥǥ쥯ȥݴɤޤ
Ȥδ(ꥹȤδԤǤϤޤ)ϡݴɤ줿᡼
褵뤫뤤˴ޤ
ݴɥץϡȴԤͭˤˤΤǤޤ-f å1ĤǤ-i ޤ -o Τɤ餫1ĤꤷƤ-m, -M, -i, ޤ -u Τ1ĤǤޤꥹȤϸ롼פդΥ᡼Υ᡼ Mailman Ȥˤޤ
¾δΥȤΥꥹȤǡΥꥹȥɥ쥹 To:  Cc: إå
Ƥ顢ΥꥹȲ.ΥȤΥꥹȤǡΥꥹȥɥ쥹 To:  Cc: إå
Ƥʤä顢ΥꥹȲ˴ޤΡXML  FILENAME ˽ϡΥץ̵ȤFILENAME  '-' 
ȤϡɸϤѤ롣%(hostname)s ᡼󥰥ꥹȰPID ãǤޤ: %(pidfile)sڡѹޤǤѥ // URLѥɤѹ˼ԡѥɤѹޤѥ˺ѥɤѹޤѥ:ѥ: ѥѥɤפޤѥɤפޤ; ѹǤޤѥɤϤƤѥ(ɽǻ):αβϿ:α:ɬפʥåץ졼ɤԤ

ˡ: %(PROGRAM)s [ץ]

ץ:
    -f/--force
        Ū˥åץ졼ɤνԤ̾ϡ⤷󥹥ȡ
        줿 Mailman ΥС󤬸ߤΤΤѤʤС(
        󥰥졼ɤΤ줿) Ԥʤ

    -h/--help
        ΥƥȤɽƽλ롣

ΥС󤫤ǿMailman꡼˹ȤϡΥץ
¹Ԥ롣 1.0b4 ޤǤΥСΤäƤ롣
ΥꥹȤʵӽ˥᡼󥰥ꥹ %(realname)s ˥᡼󥰥ꥹ <em>%(realname)s</em> ڥ륷¸ˤξpickleƤޤ: ʿʸʤܥåȤǤϤʤȤ򼨤ᡢμƲ:᡼᡼󥰥ꥹȰʤǤ
 %(listurl)s ΥڡǼ³򤹤뤫
ɥ쥹 %(request)s  `help' Ƚ񤤤
᡼äƥޥɤλȤ󤻤Ƥˡ᡼Ǽäǧʸ(<em>å</em>)
ϤƤˡ<em></em>ܥ򲡤ơ
ǧ³˿ʤǤ᡼륢ɥ쥹:-p ޤ -m ꤷƤ⤦֤򤫤ƥեϤƤƤ襢ɥ쥹ĹޤûƤ˴ؤˡۿ᡼źեե˴ؤˡ

<p>źեեե륿ưϼ̤Ǥ: 
źեեꤵƤСꥹȤ夷᡼˴ޤޤ
ġźեեϤޤ
<a href="?VARHELP=contentfilter/filter_mime_types"></a>
ӤޤźեեΥե륿פ
ꤵ줿פΤɤ줫פСΥե˴ޤ

<p>ˡ<a href="?VARHELP=contentfilter/pass_mime_types">̲᥿</a>
ƤСꤵ줿̲᥿פ˰פʤźեե
˴ޤ̲᥿פƤʤСåάޤ

<p>νƤˤʤä<tt>ޥѡ</tt>
źեե뤬Сźեեޤֳ¦
ΥåˤʤäϡΥ᡼Τ˴ޤ

<p>ơ⤷<a href="?VARHELP=contentfilter/collapse_alternatives"
>collapse_alternatives</a>ꤵƤС줾
<tt>multipart/alternative</tt>ΤƬ
ǤʤalternativeƤ֤ޤ

<p>Ǹˡ<a href="?VARHELP=contentfilter/convert_html_to_plaintext">
convert_html_to_plaintext</a>ꤵƤơ
ȤʿʸؤѴƤС
Ĥ<tt>text/html</tt><tt>text/plain</tt>ѴޤݡɸNNTPФ䤤碌Ԥ᡼󥰥ꥹȤѤ뵭롣

ˡ: gate_news [ץ]

ץ:

    --help
    -h
        ΥƥȤɽƽλ

ݥȥݥȥ(֥饸)ꥹȤؤդꥹȤؤƤäޤƼƼԤΥѥɤפޤƤϾǧΤα̾ %(subject)s Ƥ줿᡼ǥ졼ƥåɡ˥塼롼פؤդꥹȤؤƤϾǧɬפǤΥ᡼륢ɥ쥹ƤϼưŪ DMARC ˤδ¤
ŬѤޤFrom: ɥ쥹ȤΥɥᥤǤ褦ʳΥ᡼
˴褦ʥݥꥷäƤȻפȤ狼äƤ᡼륢ɥ쥹
뤤ϥɥᥤФưŪˡ֥᡼źաפ뤤
From 񤭴פԤΤѤ뤳ȤǤޤ<p>1ԤˤĤ1ĤβΥ᡼륢ɥ쥹
Ƥ; ɽȤˤϹԤκǽ ^ ǻϤƤƤϡưŪ˾ǧ
ʲץɬפȤޤ1ԤˤĤ1ĤΥɥ쥹
Ƥ; ɽȤˤϹԤκǽ ^ ǻϤƤ.
Ԥκǽ @ ʸˤơˤ Mailman ƥΥꥹ̾³ȡ
ΥꥹȲǧޤƤ, ưŪ˴ޤ
Ĥޤꡢ᡼ϼΤƤ졢ΤϤޤԤˤΤ
⤢ޤ󤬡ץǥꥹȻʲԤ
<a href="?VARHELP=privacy/sender/forward_auto_discards">
˴᡼Υԡ</a>ȤǤޤ
<p>1ԤˤĤ1ĤβΥ᡼륢ɥ쥹
Ƥ; ɽȤˤϹԤκǽ ^ ǻϤƤƤϡưŪ˵ݤޤ
ĤޤꡢưݤȤΤȰ˥᡼ޤ
Τǥ᡼ԤˤΥץꤹ٤ǤϤޤ
Τ褦ʥ᡼
<a href="?VARHELP=privacy/sender/discard_these_nonmembers"> ưŪ
˴</a>٤Ǥ

<p>1ԤˤĤ1ĤβΥ᡼륢ɥ쥹
Ƥ; ɽȤˤϹԤκǽ ^ ǻϤƤƤϡʲԤξǧ뤿
ưŪľαޤ᡼ƼԤˤαȤΤ졢
᡼ʬǼäȤǤޤ1ԤˤĤ1ĤβΥ᡼륢ɥ쥹
Ƥ; ɽȤˤϹԤκǽ ^ ǻϤƤư:     %(postaddr)s:˥塼ؤƵ<tt>Subject:</tt>(̾)֤դޤ?̾Ƭդ硣ݴȴԤΤ˥᡼ݴɤȴԤΤ˥᡼ݴɤε (å)Mailman  qrunner ǡ򥹥/ߤ륹ץ.

ΥץȤ Mailman Υ塼ʡ (Ԥ) ץ
ưߡƵưΤǡĹˤ錄äƼ¹Ԥ qrunner 
ưƤ뤳Ȥǧɬפ˱ƺƵư롣 qrunner 
fork  exec  pid ˤĤԵ뤳ȤǹԤ롣֥ץ
λȤΤȡƵưߤ롣

qrunner  SIGINT, SIGTERM, SIGHUP ˱롣SIGINT  SIGTERM 
qrunner 줤˽λ褦ˤ뤬ޥ SIGINT ǽλ
ȤƵưԤSIGHUP ϥޥ qrunner եĤ
ΥåȯΤȤ˺Ƥӳ褦ˤ롣

ޥޤ SIGINT, SIGTERM, SIGHUP ˱롣Υʥ۲
qrunner Ǥ롣(ޥ SIGHUP ȼʬѤ
եĤƺٳȤ) ޥϤޤʬΥץ
ID  data/master-qrunner.pid ե˻Ĥ̾盧ľܻȤɬ
̵`start', `stop', `restart', `reopen' ΥޥɤǽʬѤ­
ϤǤ롣

ˡ: %(PROGRAM)s [ץ] [ start | stop | restart | reopen ]

ץ:

    -n/--no-restart
        顼 SIGINT ǽλȤ qrunner Ƶưʤ
        SIGTERM ǽλȤϺƵưϤʤΥץ
        ǥХåͭ`start' ޥɤȤ줿ȤΤͭ

    -u/--run-as-user
        ̾ΥץȤϥ桼IDȥ롼ID mailman 
        ʤäƤʤȵưǤʤ(Mailman configure λ
        )root ǵưȡΥץȤϥå
        Υ桼ȥ롼פѹ롣

        ΤȤϡƥȤǥХåκݤؤˤʤ뤳Ȥ롣
        -u ե饰 uid/gid ΥåФƥץ򸽺ߤ
        桼/롼פǼ¹Ԥ롣Υե饰̾μ¹ԴĶˤ
        ʤ

        -u ե饰Ȥä mailmanʳΥ롼פǼ¹Ԥȡ
        ѡߥå꤬ȯǽΤա
        ȤХꥹȤ¸ˤWebǤʤʤ뤫⤷ʤ
        ޥ!

    -s/--stale-lock-cleanup
        ⤷mailmanctl ޥΥåե򸫤Ĥ顢̾
        顼åФƽλ롣Υץդȡ
        ̤ΥåԤ⤷åե˽񤫤줿
        host/pid ˥ޥåץʤ顢mailmanctl Ͻλ
        ץ̵ˤϡŤʤäåե
        ơޥå褦Ȼߤ롣

    -q/--quiet
        ֥åϤʤ顼åɸ२顼˽
        롣

    -h/--help
        ΥåϤƽλ

ޥ:

    start   - ޥΥǡ qrunner ư롣⤷
              ޥưƤСΤȤ𤷽λ롣

    stop    - ޥǡ qrunner ߤ롣߸ϥ᡼
              νϹԤʤ

    restart - qrunner Ƶư뤬ޥϤΤޤޤˤ롣
              ޥɤ Mailman 򹹿С󥢥åפ˼¹
              롣qrunner ϿɤȤ褦ˤʤ롣

    reopen  - ΥեĤơΥåȯ
              Ȥˡ٥ץ󤵤롣
Mailman Сɽޤ
ץ饤Хץ...¸˥顼¸˥顼 - %(msg)s¸ - "./"  "../"  URL 뤳ȤϤǤޤ¸ե뤬Ĥޤ¸˥ڡ꤬ޤ:߲롣11¹ԤȤ褤

ΥץȤΥ᡼󥰥ꥹȤ󤷡ߤƤ
õФ⤷ߤͳ顼ˤΤǤ, 
βϺΤ롣ơΤۤ顢ꥹ
롣

--byadmin, --byuser,  --unknown Υե饰ȤȤͳ
ˤΤԤ롣٤Ƥ߲Τˤϡ --all 
Ȥ

ˡ: %(PROGRAM)s [ץ]

ץ:
    -h / --help
        Υåɽƽλ

    -o / --byadmin
        ꥹȴԤˤäߤ줿ˤΤ

    -m / --byuser
        ȤˤäߤƤˤΤ

    -u / --unknown
        ͳߤ줿ˤΤ
        (ۤȤɤξϸŤС󤫤Ѥ줿߲)

    -b / --notbybounce
        顼ߤƤˤΤʤ
        (ǥեȤϥ顼߲)

    -a / --all
        ٤Ƥ߲Τ

    -f / --force
        ΤˤʤäƤʤƤ⡢߲Τ

    -l ꥹ̾
    --listname=ꥹ̾
        ꥹ̾ΥꥹȤ롣ǤʤСΥꥹȤ
%(hostname)s θ᡼󥰥ꥹPython Powered4ȾRFC 2369ǡ᡼󥰥ꥹȤβ᡼ɲä List-* إå
ƤޤΤإåϡɸ˽򤷤᡼륽եȤѼ
ˤϤȤƤΩޤ̾ϾͿ٤Ǥ
<p>ɬ⤹٤ƤΥ᡼륽եȤޤɸ˽򤷤Ƥ櫓Ǥ
ʤޤ¿ɸ˽򤷤Ƥʤ᡼륽եȤȤäƤ
硢ΥإåԲ˻פ⤷ޤ󡣤ξϡޤ
Υإåͳ򤷤Ƥǡ᡼륽եȤɽ鱣
ˡ򶵤뤳ȤϤ٤ǤǸȤơΥإå
դʤǤޤᤷޤ(Υ꡼Ǥϡ
إå˴ؤ꤬Ǥʤ褦ˤ뤫⤷ޤ)᡼󥰥ꥹȲgzipǰ̤ Pipermail¸ѥƥȥե롣

ΥץȤ cron Ǽ¹Ԥ뤳ȡޥɥ饤󤫤
¹ԤȤϰʲΥץǧ롣

ˡ: %(program)s [-v] [-h] [ꥹ̾]

:
    --verbose
    -v
        gzip Ȥ˥ե̾ɽ롣

    --help
    -h
        Υåɽƽλ

    ꥹ̾
        ꥹ̾ǻꤷꥹȤ .txt ե򰵽̤롣
        ꥹ̾λ꤬άȡ¸ˤĤ٤Ƥ
        ꥹȤˤĤƽ롣

ե򳫤ʤޤˤ -f ץĤ %(MAILMAN_USER)s  root θ¤Ǽ¹ԤƤݤͳͳ:ꥹȤ¸ˤƹۤ.

Υޥɤǥ᡼󥰥ꥹȤ¸ˤƹۤޤ¸
᡼ԽȤˡΥޥɤ¹ԤȤ褤Ǥ礦

ˡ: %(PROGRAM)s [ץ] <ꥹ̾> [<mbox ե>]

ǥץ:
    -h / --help
        ΥإץåϤƽλ롣

    -q / -quiet
        ¸˺Υå롣

    --wipe
        ƹ˸¸ˤä롣¸ˤʬ䤷ƺƹۤ
        ʳǤϡΥץꤷۤ褤Ǥ礦

    -s N
    --start=N
        Nܤε롣0ܤ mbox κǽε
        Ǥꡢά 0 ˤʤޤ

    -e M
    --end=M
        MܤεǺ򽪤롣ΥץȤϥ
        ΨΤǡ礭¸ˤ褦Ȥȡmbox ե
        Τ٤˺Ϻʤ⤷ޤ󡣤ͳ
        ǽȺǸεֹǤ褦ˤʤäƤޤ

<mbox ե̾>  mbox ˤʤäꥹȤβؤΥѥǡ
ϡƤ archives/private ǥ쥯ȥβˤޤȤ: 

%% bin/arch mylist archives/private/mylist.mbox/mylist.mbox

<mbox ե̾> ϥץǡ⤷̵С嵭Τ褦ɸ
mbox եؤΥѥȤޤ
ޤȤɤߤˤޤ?:ե륿ե륿Pipermail ¸ˤΥǥ̤򸺤餹

ˡ: %(PROGRAM)s [ץ] ե ...

ץ:
    -h / --help
        ΥåϤƽλ

Mailman 2.1.3  -article ǡ١ե, html_body
°¸ˤ. °ϥ꡼̤˾
椨ȯʥꥹȤǤǽ˱ƶǽ롣

:
%% ls -1 archives/private/*/database/*-article | xargs %(PROGRAM)s

ΥץȤ¹Ԥ `bin/check_perms -f' ¹Ԥ뤳

ޤ̤褱 -article.bak եȤ褤

ΥץȤصΤ󶡤ƤꡢݡȤϤʤ
Mailman  aliases 롣

ºݤνϤϡmm_cfg.py ե `MTA' ѿͤˤäѤޤ

ˡ: genaliases [ץ]
ץ:

    -q/--quiet
        MTAˤäƽϤϾĹʥإʸդޤΥץ
        Ĺ٤򲼤뤳ȤǤޤ

    -h/--help
        ΥåϤƽλ롣
ɽ:pickle¸ˤξ֤ɹƤޤ˺ꥹȤ롣

ˡ:
    remove_members [ץ] [ꥹ̾] [ɥ쥹1 ...]

ץ:

    --file=ե
    -f ե
        ե˽񤫤Ƥɥ쥹롣ե̾
        `-' ꤹȡɸϤɤ߹ޤ롣

    --all
    -a
        ᡼󥰥ꥹȤβ򤹤٤ƺ롣
        (--fromall ȤƱ˻ѤǤʤ)

    --fromall
        ɥ쥹β򤳤ΥƥΤ٤ƤΥꥹȤ롣
        ۥɥᥤоݤȤʤ롣Υץ -a/--all
        Ʊ˻ꤹ뤳ȤϤǤʤޤΥץ
        Ȥϡꥹ̾ꤷƤϤʤ

    --nouserack
    -n
        ˳ǧΥ᡼ʤΥץάȡ
        ꥹȤδͤȤ롣

    --noadminack
    -N
        Ԥ˳ǧΥ᡼ʤΥץάȡ
        ꥹȤδͤȤ롣

    --help
    -h
        Υإץåɽƽλ롣

    ꥹ̾ϻѤ᡼󥰥ꥹȤ̾

    ɥ쥹1 ... Ϻ᡼륢ɥ쥹

ꤵ줿ե륿װʳźեեޤ
ˤƤȡθάޤꤵ줿ĥҰʳźեեޤ
ˤƤȡθάޤʲΥפƤϤޤźեե롣ʲγĥҤźեե롣᡼󥰥ꥹȤ () - !

ϥ᡼󥰥ꥹȤκפ(ۤ)õ롣ǥեȤǤϡ
ꥹȤ¸ˤϺʤŤꥹȤѻߤΤˤϽʬꤴǤ롣

ˡ:
    rmlist [-a] [-h] ꥹ̾

:
    --archives
    -a
        ꥹȤ¸ˤ롢ޤϴ˥ꥹȤƤ
        ĤäƤ¸ˤ롣

    --help
    -h
        ΥإץåϤƽλ롣

   : %(s)s%(msg)s From: إåΥ᡼륢ɥ쥹ꥹȤƥɥ쥹֤
              From: ɥᥤ DMARC 뤤Υݥꥷˤ
             ¤ޤγǧΰγǧΰ%(realname)s ᡼󥰥ꥹȤؤοϵѲޤ׵ᤵ줿̵Ǥ: %(topicname)sǧweb_page_url °ǥեȤꤹ

ΥץȤ bin/withlist ȤȤ˻ѤޤĤޤ

% bin/withlist -l -r fix_url ꥹ̾ [ץ]

ץ:
    -u ۥ̾
    -urlhost=ۥ̾
        ۥۥɽ򻲾ȤꥹȤ web_page_url  host_name °
        ɽ˽äƥۥ̾ǻꤷͤꤹ롣ϡܼŪˤ
        ꥹȤ򤢤벾ۥɥᥤ󤫤̤Υɥᥤ˰ܹԤ뤳ȤǤ롣

        Υץ̵, ǥեȤ web_page_url  host_name
        Ȥ롣

    -v / --verbose
        ץȤ򤷤Ƥ뤫ɽ롣

⤷ñȤǼ¹Ԥȥإץåɽƽλ롣
᡼󥰥ꥹȤΥѥɤꤷޤ

ΥץȤϻꤷ᡼󥰥ꥹȤΥѥɤ
ޤꥹȤΥѥѹˤѤǤޤѥ
ѹ줿ȤΤΤϡʤܤȤʤޤ

ΥץȤ bin/withlist βǼ¹Ԥ뤳ȤꤷƤޤĤޤꡢ

% bin/withlist -l -r reset_pw ꥹ̾ [ץ]

ץ:
    -v / --verbose
        ץȤ򤷤Ƥ뤫Ϥ롣
ߤ %(n)s BYBOUNCE  [ʤ] ˥ꥻåMailman Υޥ qrunner ƵưޤϤ֤:롼ޥ˥ҤȤĤޤϤʾ qrunner 򡢰٤ޤϷ֤¹Ԥ롣

ꤵ줿 runner Υ饹饦ɥӥǼ¹Ԥ롣
Ĥޤꡢǽ˻ꤵ줿 runner Υǥ쥯ȥˤե򤹤٤
롣 qrunner 򽪤ȡ qrunner Υǥ쥯ȥ
ˤե˼¹Ԥ롣֤βϡޥ
ɹԤǻǤ롣

ˡ: %(PROGRAM)s [ץ]

ץ:

    -r runner[:饤:ϰ]
    --runner=runner[:饤:ϰ]
        ꤵ줿 qrunner ư롣˻Ȥ̾ -l ץ
        ɽ롣ץ 饤:ϰ ϰĤΥ塼(Ԥ)
        ʣ qrunner ץƤ˻Ѥ롣ϰϤϤΥ塼
        ˳Ƥ qrunner ι׿ǡ饤 [0..ϰ] δ֤
         qrunner ֹǤ롣

        饤:ϰϤꤹϡư뤽줾 qrunner 
        ƱϰͤĤ褦դ뤳ȡ饤:ϰϤꤵ
         1:1 Ȥ롣

        -r ץʣꤹ뤳ȤǤ롣ξ硢 qrunner 
        饦ɥӥǼ¹Ԥ롣`All' Ȥ̤̾ runner ϡ
        -l ץɽ뤹٤Ƥrunnerư뤳Ȥ̣롣

    -once
    -o
        qrunner 1¹Ԥ롣Υץάȡץ
        SIGTERM ޤ SIGINT ޤ̵¤˼¹Ԥ롣

    -l/--list
        ¸ߤ qrunner ̾ɽƽλ롣

    -v/--verbose
        logs/qrunner ե˥ǥХå񤭽Ф

    -s/--subproc
        mailmanctl εưץȤ qrunner ¹ԤȤ˻Ȥ
        顼λư򤳤Ȥߤ˹碌롣

    -h/--help
        ΥåϤƽλ롣

-l ޤ -h ꤹrunner ɬܤǤ롣ޤ -l 
åɽ̾Τɤ줫ǤʤФʤʤ

ΥץȤ̾ mailmanctl 鵯ư٤ΤǤ뤳Ȥյ
Ƥ̤˼¹Ԥ뤳ȤͭפʤΤϥǥХåԤǤ롣
Υץ root  %(name)s 桼Ǽ¹ԤƤ
Ǥʤ -u ץȤäƤ%(module)s.%(callable)s() ¹...ꥹȤ¸᡼źեեݴɤޤ?ѤɽꤷƤ...2:ԽڡǤ:֥ꥹȺλפ᡼ǴԤΤ餻ޤ?񤹤ˤ̤Υ᡼Фޤ?ƤǧΤα줿ƼԤ˥᡼뤷ޤ?ѥ˺Τޤ?ΤꥹȴԤ˿Τޤ?ꥹȴԤΤޤ?ꥹȤ˥ѥ˺Τ

ΥץϤ٤ƤΥ᡼󥰥ꥹȤȤΥѥɤ
롣mm_cfg.VIRTUAL_HOST_OVERVIEW ǤСꥹȤΥۥ̾
롼ײ롣ˡ(ƲۥۥȤ) 줾β˥ꥹȤΥѥ
ɤȲץڡ URL ޤ᡼롣ѥ˺
 mm_cfg.MAILMAN_SITE_LIST ʤΤǡɬꤷƤȡ

ˡ: %(PROGRAM)s [ץ]

ץ:
    -l ꥹ̾
    --listname=ꥹ̾
        ꤵ줿ꥹȤˤĤƥѥ˺Τ롣ά
        ȡ٤ƤΥꥹȤˤĤ롣ʣ -l/--listname Ǥ롣

    -h/--help
        Υåɽƽλ롣
ѥ˺Τľܲ餺"-owner" ޤ³γǧΤޤ?˴ޥ᡼Фޤ?˴ޥ᡼Фޤ?Ԥ Web ǥ᡼˴ޤƼԤ϶ػߥꥹȤäƤޤԥե륿99ӥСθϻåüϤ뤳ȤǡȤΥѥɤꤹ

ȥѥɤϥꥹȤδԥѥɤꥹȲΥѥɤ
ˡۤȤɤξǻȤȤǤ롣

ˡ: %(PROGRAM)s [ץ] [ѥ]

    -c/--listcreator
        ȥѥɤǤʤꥹȺԤΥѥɤꤹ롣
        ꥹȺԤϥꥹȤ븢¤Ĥ
        ԤλǽϤĤ櫓ǤϤʤ

    -h/--help
        Υإץåɽƽλ롣

ѥɤޥɥ饤̵ˤϡϤ¥ץץȤФ롣
¾Υ᡼󥰥ꥹ(ҥꥹ)뤿Υ᡼󥰥ꥹ(ƥꥹ)Ǥ
֤ϤפǤ
֤Ϥפ֤ȳǧѥ˺Τʤɤϡ
Υɥ쥹˰ʲǻꤹ "umbrella_member_suffix" 
դɥ쥹ޤhost_name  %(mailhost)s invite-msg-fileλˤ --invite ץ꤬ɬפǤΥץꤹȲΥ᡼륢ɥ쥹
 (ʸǤ󥯤Ǥ)ñˤϥ᡼륢ɥ쥹Ǥ뤳
ʬʤ褦Ѵޤϡǥ᡼Ԥ
ư Web ʤ Ȥäƥ᡼륢ɥ쥹
ʤ褦ˤ뤿ΤΤǤΥץ򥻥åȤ Mailman ϼΡ֤ޤȤɤߡפ
ȯλ鿷򥹥Ȥޤͤ<em>Ϥ</em>פꤹȡ顼᡼ˤΥ顼û줿Ȥ˥顼᡼ޤΤꥹȴԤޤ(ߤȥɥ쥹õΤξϽ)web_page_url  %(web_page_url)s ᡼񤤤ͤΥɥ쥹(ĤޤꡢFrom: إåե)
             ɥᥤλѤˤĤƤǧ뤿ˤĤ
             ץȥ뤬ǤϹȤƤޤץȥ
             ˤϥեåǽΤ褦˥᡼󥰥ꥹȤˤ褯褦
             ǽƤʤȤ⤢ꡢꥹȻäΤΥӥ
             From: եɤΤͳ顼
             ޤ<b>η̲ϥ᡼ʤ뤳Ȥ
             Ǥˤ⤫餺񤵤뤳Ȥˤʤޤ</b>
             <p>
             ʲν򤳤򤷤硢ϥꥹȤƤ
             åŬѤޤ From: إåΥɥᥤ󤬤
             ץȥѤ褦ʥɥᥤǤåФ
             ΤߤνŬѤˤϡ
             ֥ץ饤Хץ... -&gt; ԥե륿פ<a
             href="?VARHELP=privacy/sender/dmarc_moderation_action">
             dmarc_moderation_action</a> 򻲾ȤƤ
             <p>:<p>
             <dl>
             <dt></dt>
             <dd>̤ʤȤϤޤ󡣤ƿ̾ꥹȤ˸Ƥޤ
             Ƹ¤ƼԤ From: Υɥ쥹Υɥᥤ
             DMARC 䤽ΥݥꥷȤäƤʤ褦ʾˤϡ
             ʥѤΥꥹȤˤƤޤޤΥꥹȤ
             Ф dmarc_moderation_action ־ǧװʳꤷ
             ˤƤޤ</dd>
             <dt>From 񤭴</dt>
             <dd>εǽ From: إåƼԤΥɥ쥹ꥹȤ
             ѥɥ쥹֤ƼԤΥɥ쥹򸵤 Reply-To: 
             إåΥɥ쥹ɲäޤ</dd>
             <dt>᡼ź</dt>
             <dd>From: إåꥹȤѥɥ쥹ȤƤ From: 
             ɥ쥹򸵤 Reply-To: إå˲ä¦Υå
             Ƥ줿å Content-Type: message/rfc822 Ȥ
             ƥåźդޤ ϼ¼ŪˤñΥå
             ʤMIMEΥ(ޤȤɤ)Ǥ</dd>
             </dl>
             <p>anonymous_list Ф񤭴ϤΤν
             ŬѤޤƿ̾ꥹȤФƤϡ֤װʳν
             ŬѤΤ̵פǤ⤷򤷤顢η̤
             äȤˤʤǤ礦
             <p>ʲReply-To: إåν񤭴νϼΤ褦
             ߤ˺Ѥޤ:
             <p> first_strip_reply_to = Yes (Ϥ)ξϤ
             å Reply-To: Υɥ쥹򤹤٤Ƽޤ
             reply_goes_to_list ꤬3ĤΤΤɤǤ⡢
             ƼԤΥɥ쥹ΤߡƼԤΥɥ쥹ȥꥹȤ
             ѥɥ쥹뤤ƼԤΥɥ쥹Ū
             reply_to_address ȤǤƼԤΥɥ쥹
             å Reply-To: ˲äޤ
             first_strip_reply_to = No ()ξ Reply-To: 
             إåƼԤ From: إåΥɥ쥹Ǥ
             ޤޤƤʤˤ Reply-To: إåˤäƤ
             ɥ쥹˲äƼԤΥɥ쥹򤽤˲äޤ
             <p>(ޤȤɤ)¸ˡ
             ᡼ &lt;-&gt; ˥塼ΥåФƤ
             Ǥꡢ<a
             href="?VARHELP=privacy/sender/dmarc_moderation_action">
             dmarc_moderation_action</a>
             ǤˤŬѤޤ
             <p><a
             href="?VARHELP=privacy/sender/dmarc_moderation_action">
             dmarc_moderation_action</a>־ǧװʳŬѤ
             ƥåˤĤƤϡνǤϤʤ餬
             ŬѤޤFrom: ɥᥤ DMARC  p=none ΤȤ p=quarantine ΤȤ
               p=reject ΤȤƱ dmarc_moderation_action 
               ᡼ŬѤFrom: ɥᥤ DMARC  p=quarantine ΤȤ p=reject ΤȤƱͤdmarc_moderation_action ᡼ŬѤmultipart/alternative Τ򤽤κǽΥѡȤ֤ޤ?<tt>text/html</tt>ʬʿʸѴޤ?
Ѵźեե뤬줿˼¹ԤޤʲǥꥹȤۿ᡼뤫źեեޤ?顼ˤΤޤ?顼ˤΥ顼äȤ˥ꥹȴԤΤޤ?顼ΤΤߤ硢ꥹȴԤΤޤ?˥塼롼פ <em>åå</em> ޤ?Mailman ˥顼᡼μư򤵤ޤ?᡼Ŀ̤˥ޥޤ?
ʥѤΥꥹȤǤʤȤޤ
θΨ˴ؤ꤬ޤΤ
<a href="?VARHELP=nondigest/personalize">ܺ</a>⤪ɤߤ-owner Υ᡼˼ưޤ?-request ɥ쥹ؤΥ᡼˼ưޤ? 
֤Ϥפ־硢Υ᡼˴뤫Ȥ̾Υ᡼륳ޥ
Ʊͤ˥ƥž뤫Ǥ᡼󥰥ꥹȤؤƼԤ˼ưޤ?Ǥ᡼뤬Сˡ֤ޤȤɤߡפȯޤ?顼ưФǸΤǤʤä顼᡼ꥹȴ
ޤ? <em>Ϥ</em>侩ޤ֤ޤȤɤߡפο򥹥Ȥޤ?ꤵ줿̤ʤƤ֤ޤȤɤߡפȯԤޤ?/η̤ԤΤޤ?⤷<tt>Reply-To:</tt>إå᡼դƤ顢
ޤ? ⤷ʤ顢<tt>Reply-To:</tt>إå
 Mailman ˤäդ줿ϤᤫդƤ
餺ޤνʣ򤱤ݤCc:إå饢ɥ쥹ޤǼưŪ˴ȷ᤿᡼ϥꥹȻʲԤžޤ?Υ᡼󥰥ꥹȤΥ᡼
<a href="http://www.faqs.org/rfcs/rfc2369.html">RFC 2369</a> إå
(<tt>List-*</tt>) դޤ? <em>Ϥ</em>ˤ뤳Ȥ侩ޤ̵ǧǤƤĤޤǿΥޤ? 
<em>Ϥ</em>֤ȡƤ˾ǧɬפ
դȤϿޤ᡼󥰥ꥹȤؤƤ˥塼롼פžޤ?˥塼롼פؤƤ᡼󥰥ꥹȤžޤ?Ƶ <tt>List-Post:</tt> إåɬפȤޤ?<tt>Sender ()</tt> إåѤơ顼᡼뤬»Ҥ
 ʤʤ褦ˤޤ? <em>Ϥ</em>侩ޤ褿顢11ޤȤΤ餻Ǥʤ˻ʲԤΤ餻ޤ?ե륿Ѥޤ?ܥ󥹥ȡĶ Mailman ˤĤƤδܾ󤪤
ӥɥץɽ롣 Python 2Υɥ쥹ɽȤˡ
 Żҥ᡼Υɥ쥹Ǥ뤳Ȥ狼ʤ褦ɽޤ?Mailman  qfiles ˤ᡼Ƥɽ롣

ˡ: show_qfiles [ץ] 塼ե ...

ץ:

    -q / --quiet
        ᡼ζڤ򼨤åϤʤ

    -h / --help
        ΥإץåϤƽλ롣

: show_qfiles qfiles/shunt/*.pck
ΥꥹȤ򥰥롼ײ/¤ؤɽMailman Υޥ qrunner ߤޤꥹȥꥹ̾ޤ: %(sitelistname)s:źեեΥ %(partctype)s ̵뤷ޤ
Х٥˥ꥹȺͳΥ顼ȯޤ
ȴԤϢƤSpamե륿ɽSpamե륿§ %(i)dǥ᡼ե륿ڥ (ڥ)RFC 2307 Υѥɡϥåꡣ
-P ץǥݡȤƤϤ롣â羮ʸζ̵Ť PID եޤMailman Υޥ qrunner ưޤͭ¾ֲϵξɽ:
    0 ɥ
    1 ե̾ޤϥ
    2 msgid
    3 msgstr
    4 end
    ̾:ѹѹѹ򿽤η̥ڡΥɥ쥹򤹤Ͽޤ? Ȥ⾷Ԥޤ?%(listname)s ꥹȤ񤷤ޤ: %(member)sԤˤߤǧλޤ§³λ:³λԼ³λ:³λ "umbrella_list" ꤷƤΥ᡼󥰥ꥹȤƥꥹ
ˤΥ᡼˻ȤեåǥꥹȤƱꥹȤƱꥹȤβʿʸΥեƱ롣

ΥץȤ, sendmail  :include: Υɥ쥹ꥹ(
Majordomo ǤѤƤ) ȤͭǤ롣᡼
ꥹȤϿƤʤեΥɥ쥹ɲä졢ե
äƤʤꥹȲϺ롣¾Υץǥɥ쥹ɲ
ޤϺȤ˲뤫椹롣

ˡ: %(PROGRAM)s [ץ] -f ե ꥹ̾

ץ:

    --no-change
    -n
        ºݤˤѹԤʤˡɤΤ褦ѹ뤫
        ɽ롣

    --welcome-msg[=<yes|no>]
    -w[=<yes|no>
        Ͽ줿˴ޥ᡼Фɤꤹ롣
        ꥹȤ `send_welcome_msg' ꤬ɤΤ褦ˤʤäƤƤ
        Υץͥ褷-w=yes ޤ -w Ǵޥ᡼
        Ф-w=no
 Ǥϴޥ᡼ϽФʤ

    --goodby-msg[=<yes|no>]
    -g[=<yes|no>
        줿ˤ̤Υ᡼Фɤꤹ롣
        ꥹȤ `send_goodbye_msg' ꤬ɤΤ褦ˤʤäƤƤ
        Υץͥ褷-g=yes ޤ -g Ǥ̤᡼
        Ф-g=no Ǥ̤᡼ϽФʤ

    --digest[=<yes|no>]
    -g[=<yes|no>]
        Ͽ줿ޤȤɤ߲Ȥ뤫ɤ롣
        -d=yes ޤ -d ǤޤȤɤ߲Ȥʤ롣-d=no (뤤
        -d ץդʤ) ̾Ȥʤ롣

    --notifyadmin[=<yes|no>]
    -a[=<yes|no>]
        η̤鷺ĴԤΤ뤫ɤ롣
        ⤷Υɥ쥹ϿƤʤ顢Τʤۤ褤!
        -a=yes ޤ -a ǴԤΤ롣-a=no Τʤ
        -a ץ̵硢ꥹȤΥǥեȤѤ롣

    --file <ե̾ | ->
    -f <ե̾ | ->
        ΥץɬܡƱʿʸեꤹ롣
        ᡼륢ɥ쥹 1Ԥ 1ĤĤȤ롣ե̾ `-' 
        ˤɸϤȤ.

    --help
    -h
        Υåɽ롣

    ꥹ̾
        ɬܡƱꥹȤꡣ
ƥ२顼ƤƤޤ: %(content)s̤ο᡼ˤʸղäޤ֤ޤȤɤߡפźդʸ֤ޤȤɤߡפƬդʸ(ܼκǽʸ)᡼ƬˤʸղäޤꥹԤʸϡˤ
 ԰᡼ˤϲɲäޤդƤФ
<a href="?VARHELP/privacy/sender/member_moderation_action"
></a>˴ޤʸDMARC %(quarantine)sݥꥷĥɥᥤ󤫤ƤФ
<a href="?VARHELP/privacy/sender/member_moderation_action"
></a>˴ޤƥʸƤФƵΤ˴ޤʸΤˤϥꥹȴԤ
ɥ쥹 %%(listowner)s Ȥƴޤ뤳ȤǤǺ
ǥեȤΥ᡼ʸ֤ޤƥ %(sz)s"host_name" ϡΥۥȤŻҥ᡼ Mailman Υɥ쥹
 Ȥ̾ǡ̤ϤΥۥȤΥ᡼(MX) ɥ쥹Ǥ
 ʣΥɥ쥹ѤǤ硢
 Ѥ륢ɥ쥹򤳤ꤷޤʤ¸ <b>info</b> °ˤϡ桼򥯥ȥץȹ
餹褦ʵ路 HTMLɤޤޤƤޤΤᡢѹϵѲޤ⤷ɤƤѹɬפǤС
Mailman Ф˥륢ʤФʤޤ
ѹˤ bin/withlist 뤤 bin/config_list Ȥä
mlist.info ꤷޤ
                        <em>ꥹȴ</em>ϡΥ᡼󥰥ꥹȤܤ򤹤٤
ǤޤԤϴWebڡ
٤ƤΥꥹѿѹǤޤ

<p><em>ꥹȻʲ</em>ϸ¤¤ƤΤǡ
ꥹȤưѹ뤳ȤϤǤޤ
ξǧѲ, α᡼νʤɤδȤǤޤ
<em>ꥹȴ</em>⿽뤳ȤǤޤ

<p>ꥹȽͭԤλŻԤȻʲԤʬˤϡ
ε̤λʲԥѥɤꤷޤ
ˡ<a href="%(adminurl)s/general">Ūץ</a>
ʲԤΥ᡼륢ɥ쥹Ƥ<a href="http://www.faqs.org/rfcs/rfc2369.html">RFC 2369</a>ˤ
<tt>List-Post:</tt> إåդ뤳Ȥ侩Ƥޤ
Ȥ<em>ʥ</em>Υ᡼󥰥ꥹȤʤɤǤϡ
βƤǤ̤βƤǤޤ
Τ褦ʥꥹȤǤϡ<tt>List-Post:</tt>إåϸθˤʤޤ顢
<em></em>ǡΥإåĤʤ褦ˤޤ
(¾ <tt>List-*:</tt>إå˱ƶޤ)Mailman ưƥ%(year)iǯ%(month)s%(day)i()ν`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>Ȥ̾Υ᡼αƤޤ
ꥹȻʲԤ˾ǧޤϵݤᡢ
ä֤˹ʤäǽޤαƤ᡼ϡǤ˥ꥹȴԤޤȡ󤬰פޤIPɥ쥹ѤäƤޤ?˥塼ФưƤޥΥۥ̾ꥹȥɥ쥹 (: mailman@example.com) Τ褦˴ʥ᡼륢ɥ쥹
ǽ񤤤Ƥ˽񤤤ꥹȤڡǡΥꥹȤ
ɥ쥹ߤ˽񤤤ƤϤޤ󡣤⤷ξΥꥹȤä
ˤϥ᡼뤬ʤʤޤ
ޤȴԤɥᥤޤǤλꥹȻػߤƤ
⤷ʤȤˤդƤꥹȥɥ쥹 (: mailman@example.com) Τ褦˴ʥ᡼륢ɥ쥹
ǽ񤤤Ƥ
ޤȴԤɥᥤޤǤλꥹȻػߤƤ
⤷ʤȤˤդƤꥹȴԤΥ᡼륢ɥ쥹ʣδԤ
 ̡ιԤˤʤ٤Ƥ褤Ԥ֤ޤȤɤߡפؤѹػߤƤΤǡ
  ץѹǤޤǤ
  ¾ΥץѹޤԤפؤѹػߤƤΤǡ
  ץѹǤޤǤ
  ¾ΥץѹλޤꥹȴԤ¾ΥꥹȤˤĤƤ
ѥѹϤǤޤꥹȴԤϡβ¾ΥꥹȤˤ륪ץѹ뤳Ȥ
Ǥޤ󡣤ΥꥹȤǤΥץѹޤꥹȴԤ¾ΥꥹȤˤĤƤβѥѹϤǤޤ
Υ᡼󥰥ꥹȤΥѥɤѹޤꥹȴԤϡβ¾ΥꥹȤˤ̾᡼륢ɥ쥹
ѹ뤳ȤϤǤޤ󡣤, ΥꥹȤˤĤƤѹޤꥹȴԤϤβˤĤ¾򸫤뤳Ȥ
ǤޤꥹȻʲԤΥ᡼륢ɥ쥹ʣλʲԤ
 ̡ιԤˤʤ٤Ƥ褤ꥹȤΥѥɤˤ뤳ȤϤǤޤꥹȤΥѥɤˤ뤳ȤϤǤޤϤ˴ޤꥹȡΥץ̵ˤϡƤΥ᡼
ꥹȤ XML Ϥޤ-l ե饰ʣդ뤳ȤǤޤ᡼󥰥ꥹ `%(listname)s' Web 󥿥եȤä
ޤΥ᡼󥰥ꥹȤκλˤϡ
/etc/aliases (ޤƱ)򹹿ɬפޤޤ`newaliases'
ץμ¹ԤɬפǤ礦

ʲ, /etc/aliases ٤ܤǤ:
Web 󥿥եǥ᡼󥰥ꥹ `%(listname)s' 
ޤǽŪ˺뤿ˡ
/etc/aliases (ޤƱΥե)򹹿ɬפޤ
ޤ, `newaliases'ץμ¹ԤɬפǤ礦

ʲ, /etc/aliases ԤǤ:
ޥ qrunner ΥåǤޤ
̤Υޥ qrunner äƤ褦Ǥ
ޥ qrunner åǤޤǤ¿ʬ¾ΥۥȤ
ץäƤΤǤϤʤȻפޤۥȤζۤ
åȤƤʤɤĴ٤뤳ȤϤǤޤΤǡư
åƤ뤤ϡʤåե뤬ŤʤäƤ
ȤΤäƤʤ顢-s ե饰դ mailmanctl ƵưƤ

åե: %(LOCKFILE)s
åۥ:   %(status)s

λޤޥ qrunner åǤޤ
ȤƤʤåե뤬ĤäƤΤ⤷ޤ
-sե饰Ĥ mailmanctl ⤦ٵưƤ
ߤΥ顼ưǤ⤫ޤޤ᡼󥰥ꥹ %(list_name)s  Υɥ쥹 %(change_from)s 
%(change_to)s ؤѹޤ
ػߤƤեǤĤƤʤեǤػߤƤեĥҤǤĤƤʤեĥҤǤ˥塼롼פ¥ݥꥷԤ Usenet Υ˥塼롼̾ɥ쥹ϴѤߤǤ: %(newaddr)sɥ쥹Ȥƻꤵ줿 %(newaddr)s ϡ %(listname)s 
ϿƤޤѹפꤵƤ뤿ᡢ
ǧξ塢%(safeuser)s ¾Τ٤ƤΥꥹȤϿƤ륢ɥ쥹
ѹޤΤޤȤɤߤ %(volume)s ,  %(number)s Ǥδ顼̵С顼˴ޤ
ͤǤ<em></em>ηٹ᡼ֳ֤ޤ?
 ͤǤʤ¸ڡˤϡ桼򥯥ȥץȹ
餹褦ʵ路 HTMLɤޤޤƤޤΤᡢѹϵѲޤ⤷ɤƤѹɬפǤС
Mailman Ф˥륢ʤФʤޤ
             ľTo:뤤Cc:˸ƤΥɥ쥹˥ꥹȰ
               ᡼ΥԡΤ򤱤ǡĹåɤ Cc: 
               ĹӤΤ򤱤뤿 Cc: 饢ɥ쥹
               ȤޤΤȤˤä DKIM̾줿ꡢ
               򾷤ꤹ뤳Ȥ뤿ᡢ˾ޤȤǤ
               ʤ⤷ޤ Cc: إå˼äΤ򤱤ˤ
               ֤פ˥åȤޤɽ뤳ΥꥹȤ̾ (ʸؤѹǽ)᡼륳ޥɤη̤ϰʲΤȤǤ
ޤ줿ޥɥ᡼źդޤ
᡼륳ޥɤη%(hostname)s ΥȴԤʤΥ᡼󥰥ꥹ %(listname)s
δѥɤѹޤߤϰʲΤ褦ˤʤäƤޤ

    %(notifypassword)s

ʸΥꥹȴˤϤΥѥɤѤƤ
̤ΥѥɤѹȻפϡ
ʲδڡѹƤ

    %(adminurl)s
̾ʸϲԤ &lt;br&gt; ѹ뤳<em>ʳ</em>
 HTMLȤư뤿ᡢ󥯤ѤߥƥȤʤȤȤޤ
 ʬʳϲԤʤǤ
 ޤ, ѹʬ褯åƤ - 
 HTML˴ְ㤤(ĤƤʤʤ)Υڡ
 ɽʤȤ⤢ޤե륿ϡʲ
<a href="https://docs.python.org/2/library/re.html">ɽ
ե륿</a> Ƥ줿᡼ʬषޤ(<a href="https://docs.python.org/ja/2.7/library/re.html">ܸʸؤΥ</a>)
᡼ <code>Subject:</code>  <code>Keywords:</code> إå
ե륿Ŭ礷᡼ϡꤴȤ˺줿<em>Хå</em>
ޤ줾βϡʬꤿХåȤǡ
ΥХåȤΥ᡼뤳ȤǤޤ
ɤΥХåȤˤʤä᡼ޤ
<p>
ϡǤȤޤ󡣤ޤȤɤߤǤϻȤޤΤդƤ
<p>
᡼ʸʬ<code>Subject:</code>  <code>Keyword:</code>
ꤹ뤳ȤǤޤξ硢
<a href="?VARHELP=topics/topics_bodylines_limit">topics_bodylines_limit</a>
ѿǡԿǤޤΥǤϡιԿʸ椫Υɤ
õޤʸΥϤιԿ뤤ϡإåǤʤʹԤ
ФƤ饹ȥåפޤͤ򥼥ˤƤȡʸΥ
ʤޤ(Ĥޤ <code>Keywords:</code>  <code>Subject:</code>
إå򸫤ޤ) ͤˤƤȡإåǤʤʹԤ
ФƤޤʸ򥹥󤷤ޤѥ `%(safepattern)s' ɽǤϤޤ
λ˴ޤѿ `m'  %(listname)s  MailList 󥹥󥹤ǤαοϤޤ᡼󥰥ꥹȤδ(ͭ)ˤ2Ĥ䤬ޤ
<em>ꥹȴ</em>ϤΥ᡼󥰥ꥹȤΤ٤ƤΥѥ᡼
ĤƵˤԤʤޤWebڡ̤ѹǤ
٤Ƥѿѹ뤳ȤǤޤ

<p><em>ꥹȻʲ</em> λŻϡꤵƤޤ
ꥹȤѿѹ뤳ȤϤǤޤ󤬡αδ
뤳ȤǤޤĤޤꡢαǧݤ뤳ȡ
αƥ᡼뤳ȤʤɤǤ<em>ꥹȴ</em>
⡢򤹤뤳ȤǤޤ

<p>ꥹȽͭԤλŻԤȻʲԤʬˤϡ
<a href="passwords">̤λʲԥѥɤ</a>
Ƥޤ<a href="?VARHELP=general/moderator">ʲԤ
᡼륢ɥ쥹</a>Ƥǡѹ褦ȤƤΤ
ꥹȴԤˤĤƤǤ᡼󥰥ꥹȤδ(ͭ)ˤ2Ĥ䤬ޤ
<em>ꥹȴ</em>ϤΥ᡼󥰥ꥹȤΤ٤ƤΥѥ᡼
ĤƵˤԤʤޤWebڡ̤ѹǤ
٤Ƥѿѹ뤳ȤǤޤ

<p><em>ꥹȻʲ</em> λŻϡꤵƤޤ
ꥹȤѿѹ뤳ȤϤǤޤ󤬡αδ
뤳ȤǤޤĤޤꡢαǧݤ뤳ȡ
αƥ᡼뤳ȤʤɤǤ<em>ꥹȴ</em>
⡢򤹤뤳ȤǤޤ

<p>ꥹȽͭԤλŻԤȻʲԤʬˤϡ
<a href="passwords">
̤λʲԥѥɤ</a>ƤޤΥˤϻʲԤ
᡼륢ɥ쥹Ƥǡѹ褦ȤƤΤ
ꥹȻʲԤˤĤƤǤȯ٤ޤȤɤߤޤեϤ˱ȡ󤬤ʤ뤤ϲƤޤ<b>%(listname)s ᡼󥰥ꥹȤݤ꤬ȯޤ
%(sitelist)s ΥȴԤϢƤʲϡΥ᡼󥰥ꥹȤǻѤǤΰǤ
<a href="?VARHELP=language/preferred_language">ǥեȤθ</a>
Ͼ򤵤ޤMailmanμư顼᡼뼫ưƥ椹ˤꤷޤ
γפϰʲ̤Ǥ

 <p>Mailmanϡä顼Τ2ξ褦
 ޤ: ĤޤꡢΥ᡼륢ɥ쥹ȡ顼򵯤
 ο٤Ǥ٤<em></em>ޤ<em></em>ǡ
 줾̿Ū顼ޤϰŪ顼бޤȽǤ񤷤
 ϡ٤Ȥޤ

 <p>顼᡼뤫ɥ쥹ФʤС
 顼᡼̵뤵ޤɥ쥹Фϡβ
 <em>顼</em>Ϳ졢顼ΤȤûޤ
 顼 1夤顼 0.5ûޤ
 顼11ûޤäơ鶯
 顼110󤢤äƤ⡢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> 2ĤѿǤޤ

<p>ˤ⤦Ľפܤޤ: ٤δ֤᤮顢
 -- δ֤ˤβΥ顼᡼뤬ʤä -- 顼ϡ
<a href="?VARHELP=bounce/bounce_info_stale_after">Ťʤä</a>
ΤȤ˴ޤä, ͤȥ顼Ĵ뤳
ǡ顼򵯤ؤߤޤǤδ֤Ǥޤ
ͤϡꥹȤήƤ٤ˤĴƤ3ϡ᡼󥰥ꥹȰǤإåʬ˻Ȥޤ
ǤʷˡƥꥹȤŪӤ狼䤹
򵭽ҤƤΥեǤJavaScriptͭˤɬפޤΥ᡼󥰥ꥹȤ %(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' ꥹ
  ޤξ祽եȥѹ revision control system
  (浡) ƤޤѹˤĤƤε
  ̤γȯԥ᡼󥰥ꥹȤǹԤޤ
  ΥפΥ᡼󥰥ꥹȤ򥵥ݡȤ뤿ˤϡ<tt>reply_goes_to_list</tt>ˤ
  <tt>̤Υɥ쥹</tt>塢 <tt>Reply-To:</tt> ɥ쥹ꤷƤ

<p>ʤƥ᡼<tt>Reply-To:</tt>إåդƤȡѹޤϡΥ᡼󥰥ꥹȤΥǥեͤȤꤵƤǤ
<a href="?VARHELP=language/available_languages">¾θ</a>
ꤹȡƥ˻ѤǤ줬
٤褦ˤʤޤ
¾Τ٤ƤϥǥեȤθǹԤޤ
Webȥ᡼ΥåŬѤޤ
Ƥ᡼ˤŬѤޤΥꥹΥꥹȤǤϡ֤ޤȤɤߡפϤǤޤΥꥹȤˤϲޤΥ᡼󥰥ꥹȤƤ¤Ƥޤ
Ƥ줿᡼ǧޤǤޤȤɤѥꥹȤǤޤȤɤѤΥ᡼󥰥ꥹȤǤ!Υ᡼󥰥ꥹȤۿ᡼
<tt>Reply-To:</tt> إåФޤ
<em>Ƽ</em>֤ȡ<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' ꥹ
ޤΥꥹȤϡեȥѹӥƥ
(RCS) ƤޤѹˤĤƤε
̤γȯԥ᡼󥰥ꥹȤǹԤޤ
Τ褦ʥ᡼󥰥ꥹȤαѤˤϡ<tt>̤Υɥ쥹</tt>
ӡ <tt>Reply-To:</tt> ɥ쥹¹ԥꥹȤƥɥ쥹
ꤷƤΥڡ, ꥹȴԤˤ᡼󥰥ꥹȺΥڡǤ
<strong>νϸ᤹ȤǤޤ</strong>
ǤΤǡΥ᡼󥰥ꥹȤӤ򤷡ޤΥꥹȤ⤦פǤ
ˤ狼äƤʤ¤ϼ¹Ԥ٤ǤϤޤ
<p>ޤεǽ¹ԤƤ⡢ʤٹꥹȲˤޤ
Ĥޤꡢ塢᡼󥰥ꥹȰΥ᡼䡢
ꥹȤδο᡼ʤɤϤ٤ƥ顼ˤʤޤ
<p>᡼󥰥ꥹȤ¸ˤƱ˺륪ץ󤬤ޤ
᡼󥰥ꥹȤεϿ¸Ƥˡ¸ˤ<strong>ʤ</strong>
Ȥ򤪴ᤷޤ
<p>ʤΤˤ⤦٤ǥꥹȴѥɤϤƤޤΥǤȲθ˴ؤݥꥷǤޤ
ޤꥹȤ뤫ɤǤޤ
¸ˤΥץ饤ХˤĤƤ <a href="%(admin)s/archive">
¸˥ץ</a> ꤷƤ)ΥǤϡۿǥ᡼򸺤餹
Ƽǥ᡼ե륿ꤷޤΥǤϥ᡼ΰˤƼΥե륿
ꤷޤǤϡ˥塼롼פ(ǥ졼)ݥꥷ
᡼󥰥ꥹȤ¥ݥꥷȤκѤˤĤꤷޤ
ϡ˥塼롼<em></em>žƤϤޤޤΤǡ
˥塼롼פžžΥ˥塼롼
ǥ졼ƥå(դ)ǤʤС
ץ<em>̵</em>ꤷƤ

<p>˥塼롼פǥ졼ƥåɤʤ, Υ᡼󥰥ꥹȥɥ쥹
˥塼롼פλʲԥɥ쥹ꤷƤ⤫ޤޤ
<em>դ</em>֤ȡƤϻʲԤˤ뾵ǧԤˤʤޤ
᡼󥰥ꥹȤƤ줿᡼ϡ
˥塼롼פžĤޤ᡼󥰥ꥹȤ
ˡǧʤФʤޤ

<p><em><tt>Approved</tt>إåȴԤΥѥɤդ줿᡼
ǧ³̤ޤ󡣤ĤޤꡢƤθ¤ĿͤľܥꥹȤ
˥塼ƤǤ뤳Ȥˤʤޤ</em>

<p>Ǹˡ˥塼롼פǥ졼ƥåɤꤵƤƤ⡢
ͳƤǤ褦ꤷС
<em>ꥹȤϸ롼פդ</em>Ǥ
֤ȡ̾MailmanλʲλȤߤǥ᡼뤬ۿ졢˥塼
ž뵭ˤϤ٤<tt>Approved</tt>إåդޤꤷ̾Ƭդޤ
᡼륽եȤΰ̤ǡꥹȤΥ᡼뤬̤䤹ʤޤ
ꤹϴʷˤƤ
ꥹ̾ĹȤϡ狼٤ûȤǤ礦
ˡ
%%d ؼҤֹ̤뤳ȤǤޤ
: [listname %%d] -> [listname 123], (listname %%05d) -> (listname 00123)˥塼Ф̾ꤷޤ name:port ηǥݡֹ
ꤹ뤳ȤǤޤ

˥塼Ф Mailman ȤĵǽǤϤޤ
ʤϴ NNTP Ф˥ʤФʤ餺
 NNTPФϥ᡼󥰥ꥹȤưƤޥ
֥˥塼ɤ߽񤭤ǤۥȡפǧʤФʤޤʸϤ񤷤ؤδʸ
 Ϥ˽񤭤ޤޤʸλĤʬˤ
 ꥹȤǽפʥ᡼륢ɥ쥹 URL ˤĤƤ
 餫ƤޤǤ餽ä
 ΤɬפϤޤ󡣤ˤϥꥹȤŪ
 åȤΥݥꥷȤäͭ
 Ĥƽ񤤤Ƥ<p> ʸϤϰʲε§˽äƹޤ֤ʤޤ:
<ul><li>1Ԥ70ʸˤʤ褦˹Եͤ᤬ʤޤ
    <li>ʸǻϤޤԤϹԵͤᤵޤ
    <li>Ԥζڤˤʤޤ
</ul>CAPTHAޤǤΥɥ쥹ѹˤϡߤΥɥ쥹ȿɥ쥹
ʲ˵ƤѹΤ򿷤ɥ쥹Ťɥ쥹
뤤ξˤϤ줾бåܥå˥åޤ᡼󥰥ꥹȤκλˤ, /etc/aliases (ޤƱ
ե) ˡʲιԤɲäƤ
ޤ`newaliases' ޥɤμ¹ԤɬפǤ礦
%(realname)s 񡢥ѥ˺Τꡢ
ץѹˤϡϿ᡼륢ɥ쥹%(either)s:
<p><center> ɽƤʤꥹȤδڡϡΥڡ URL 
'/' ȥꥹȤ̾ %(extra)s դ URL ˥Ƥ
θ¤С<a href="%(creatorurl)s">᡼
ꥹȤ</a>ȤǤޤ

<p>ꥹȤ (%(msgcount)d ):
¿ޤ %(i)dե륿ξܺ᡼˥ޥåꥭɡ1ԤˤĤ1̾:ꤹˤϡ̾ȥѥλ꤬ɬפǤ
Դ̵뤵ޤȥ륳⤷ԤưϿƤΤȤ
Τ餻ʤä OFF ˤƤ¾Υ᡼󥰥ꥹ
ȴץफ Mailman ˰ܹԤʤɤͭǤ礦1ѥɤ˺Τ硢ON ˤޤ
ϳƼѥ˺Τߤ뤳ȤǤޤ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_subscriptions.db ǡ١򹹿ͥåȥ˥塼οɼ򹹿¸ [%(archive)s] κե򹹿Ƥޤ%(listname)s ᡼󥰥ꥹȤ򹹿αΥǡ١򹹿%(hexlversion)s  %(hextversion)s إåץ졼ˡ:ΥץȤȻꤵ줿إåƤ
Ƥػߤ뤳ȤǤޤ
 оݤˤʤΤϤΥإåФɽǤ
 ޥå󥰤ʸʸ̤˹Ԥ졢
 '#' ǻϤޤԤϥȤȤߤʤޤ
 <p>㡧<pre>to: .*@public.com </pre>
  <em>to</em>() Υ᡼إåΥɥ쥹
  '@public.com' ɤäƤȤ̣Ǥ
 <p>Ԥƶ򤬤ˤϡɽϤޤ
 ȤХפ֥饱åȤѤơ¿
 ˡDzǤޤΥץǻꤹ륿פźեեޤ
ƹԤˤ MIME <tt>type/subtype</tt> (: <tt>image/gif</tt>)
ҤȤĤĽ񤭤ޤsubtype άȤ type Ĥ٤Ƥ
եޤ(: <tt>image</tt>)

<p>Ԥ̵뤵ޤ

<p>Ĥե륿פ
<a href="?VARHELP=contentfilter/pass_mime_types">pass_mime_types</a>
򻲾ȤƤΥץǤϡꤵ줿ե륿װʳźեեޤ
ɬפʾȷ
<a href="?VARHELP=contentfilter/filter_mime_types">filter_mime_types</a>
ƱǤ

<p><b>:</b>ΥꥹȤ˹ܤɲäȤϡ
ɬ<tt>multipart</tt>ꤷƤ
multipartʤźեեΤ᡼Ϥ٤Ƶݤޤ`%(addr)s' 񤵤ޤ: %(listname)sɥ쥹/̾ưãααƳǧƲѤΥץڡ Mailman С:٥ȥʥꥹαԽɽ̾Υڡ̾򸫤ꥹȴڡعԤꥹȤΰڡعԤٹ: αID˽ʣꡣ̵뤷ޤ: %(id)s.ٹ: ꥹȤΥåǤޤ: %(listname)sǥ쥯ȥ꤬ޤ: %(d)sٹ!  .pck ե: %(pckfile)sٹ! ǥ쥯ȥǤϤޤ: %(dirpath)sٹ! ѡߥå꤬Ф뤫⤷ޤٹ: ٹ: ¸˥ǥ쥯ȥ꤬ other-executable (o+x) 
      ʤäƤޤʤΥƥΥ桼¸
      ɤळȤǤޤ󥹥ȡޥ˥奢ˤϡ
      ɤ齤Ǥ뤫񤤤ƤޤΤǡͤˤƤٹ: %(src)s Ǥޤ -- %(rest)sǰǤʤϤΥ᡼󥰥ꥹȤ񤷤Ƥޤ
񤹤ˤϡ<a href="%(listinfourl)s">ꥹڡ</a>
ؤɤ轵ޥ᡼Υƥȥե"%(realname)s" ᡼󥰥ꥹ %(digmode)s ؤ褦褦!ˤϤɤΤ褦ʼ礬ɬפǤ?<br>"umbrella_list" ꤹȡΥ᡼󥰥ꥹȤ
¾Υ᡼󥰥ꥹ(ҥꥹ)ȤƥꥹȤˤʤޤ
ξ硢ǧѥ˺ΤʤɤδΤϡ
ꥹȤΥɥ쥹ˤ餺ˡΥꥹȤδԤ
ʤФʤޤ󡣲Υɥ쥹ˤꤹ
եåդäޤ̾Υեå
ˤ "-owner" Ȥޤ "umbrella_list" 
֤פ硢ϻȤޤ<a href="?VARHELP=nondigest/personalize">Ŀ</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>åȤƤƤϡ
ʲԤǧޤαޤ
ԤϡǥեȤDzƤ¤뤫ɤǤޤ

<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>Υƥȥܥåǡ1Ԥ1ĤΥ᡼륢ɥ쥹ϿǤޤ;
Ԥκǽ ^ 򵭽Ҥ
<a href="https://docs.python.org/2/library/re.html">Python
ɽ</a>ˤʤޤ(<a href="https://docs.python.org/ja/2.7/library/re.html">ܸʸؤΥ</a>)
ХååϡPython  raw stringˡΤ꤫
ϤƤ(Ĥޤꡢñ1ĥХååǤ)

<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ޤϥ᡼ǹԤʤޤ
ŪˤϡñǤ褦ͳˤޤ
(Ǥʤȡʤ꺤ޤ)

<p>ꥹȤˤäƤϻʲԤǧʤǤʤ褦
ꤹ뤳Ȥ⤢ޤȤвҤΥ᡼󥰥ꥹȤǡɬҰ
ϿƤʤФʤʤʤɤǤޤȤɤߤȤɤηǥեͤˤޤ?ꤹȡ̾αϲԤΥѥɤɬפˤʤޤ˾ǧɬפǤäƤ⡢Υɥ쥹
             Ԥξǧʤ˵Ĥޤ1ԤˤĤ1IJɥ쥹
             ޤɽȤȤϡԤκǽ ^ ǻϤ
             (ʸʸζ̤Ϥޤ)ΥץͭˤȡꥹȤؤƤ򤹤٤ƶ۵ޤ¤
ǧΤαޤȤХꥹȤǤε𤷤Ƽ꤬Ĥ
ʤʤäˡѴ֤ߤ褦ʤȤ˻ȤޤѹǤ ...źեեݴɤȡ֥֥饦ǥǤ¸ˤ
¸졢᡼ʸˤϥ󥯤ޤźեե
˾õƤޤˤϡźեեפΥץ
ȤäƤååפ(ɤդ)ȤȤϡοƤä
 ž򳫻ϤȤȤǤΥ˥塼롼פ
 ̵뤵ޤϡʤȤ˥塼ɤǤơ
 ߤ ִɡפˤΤƱȤǤ
 ååפȥ᡼󥰥ꥹȤβϰε
 뤳ȤϤޤƤ줿ֿǤ
ۤȤɤΥ᡼󥰥ꥹȤǤ <tt>Ƽ</tt>
֤Ȥ <em></em> 侩ޤɤ⡼ɤ򿷵Υǥեͤˤޤ?Mailman 顼ХƥˤäꤷƤޤ
顼򤹤٤ƲϤ뤳ȤԲǽǤ
2Ĥͳǡѿ<em>Ϥ</em>ꤷƤ٤Ǥ
1) ˤβΥ顼ʤΤǤСư
򤹤ɬפ뤫顣 2) MailmanȯԤ˥顼᡼ꡢ
бƤ餦ȤǤ뤫顣
<p>顼᡼Ѥ蘆줿ʤСѿ<em></em>
ˤȡФǤʤä顼Τ˴ʸν
ʤ褦ˤǤޤ
<p><b>:</b> , ΥꥹȤ -adminɥ쥹᡼
٤Ƥ˱ƶޤΥɥ쥹ϸ߻ѤƤ餺
ѤƤϤޤ󤬡ϻȤƤޤ⤷ï
ɥ쥹˥᡼Ф硢<em></em>
ꤵƤȡΥ᡼˴Ƥޤޤ
<a href="?VARHELP=autoreply/autoresponse_admin_text">ư
</a>Ȥä -owner  -admin ƤΥ᡼бۤ褤
⤷ޤ̾Ǥͤ?᡼źǯϤϤ˴Ϥžʤˤǧ᡼պѤߤγǧԤ֤ǤˤΥ᡼󥰥ꥹȤβˤʤäƤޤ!ѤߤǤ!˲ˤʤäƤޤˤΥ᡼륢ɥ쥹񤷤Ƥޤ줿᡼륢ɥ쥹Ǥ϶ػߤƤޤ
¤ϿˤΤȻפ
Υꥹȴ԰ˤϢ: %(owneraddr)s줿᡼륢ɥ쥹Ǥ϶ػߤƤޤ
¤ϿˤΤȻפ
Υꥹȴ԰ˤϢ: %(owneraddr)sʤϤΥꥹȤؤƤػߤƤޤʤ%(listname)s ᡼󥰥ꥹȤβǤϤޤFrom: إåΥ᡼륢ɥ쥹Υɥᥤ󼨤Ƥ DMARC /Υ
ݥꥷˤꡢΥ᡼󥰥ꥹȤؤƤϵޤ
ƤϼưŪ˵ݤޤݤθΤȻפ
᡼󥰥ꥹȴ %(listowner)s ˤϢ᡼󥰥ꥹȲ̾αĤޤ᡼󥰥ꥹȤ븢¤ޤΥ᡼󥰥ꥹȤ븢¤ϤޤʤϲǤϤޤ
񤷤᡼륢ɥ쥹ѹޤǤ?ʲURLǤʤθĿͥץڡ˥Ǥޤ:ʲΥեɬפʾƿ᡼󥰥ꥹȤ
뤳ȤǤޤ᡼󥰥ꥹȤ̾ϡ
ꥹȤƤݤδܥɥ쥹ˤʤޤΤǡ
ʸΥե٥åȤϤƤϥꥹ̾ѹ
뤳ȤϤǤޤ
<p>ޤǽΥꥹȴԤΥ᡼륢ɥ쥹ɬפǤ
ꥹȺ˥ꥹȤνѥɤ԰ޤ
ꥹȴԤϡѥɤѹꥹȴԤɲäǤޤ</p>
<p>MailmanưŪ˽ѥɤС
μưǡ֤Ϥפӡѥ϶Τޤޤ
ƤƤ</p>
<p>᡼󥰥ꥹȤˤϡꥹȺ¤ɬפǤ
Ȥˤ<em>ꥹȺ</em>ΥѥɤֲϤƤ
ȴԤΥѥɤȤޤ¾<tt>Reply-To:</tt>ꤹȤˤϡΥɥ쥹άǤޤ
ͤꥻåȤޤ<a href="?VARHELP=gateway/nntp_host">˥塼</a>
<a href="?VARHELP=gateway/linked_newsgroup">˥塼롼</a>
ꤷʤȥ˥塼ȥͭˤʤޤѥɤְäƤᡢѥɤѹޤǤ
դ password ޥɤ¹ԤߤΥѥɤ
󤻤Ƥ顢⤦ٻƤѥɤޤꥹ̾ϤƤꥹȴԤꤷƤѥɤ㤤ޤ%(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>
Ǥơ᡼륢ɥ쥹
<ul><li><b>᡼륢ɥ쥹:</b> %(newaddr)s
 %(globallys)s ѹ褦˿ޤ
<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>ܥ򲡤ƥ᡼󥰥ꥹȤΥ᡼
ƳƤ
Dz褵 <em>ä</em>ܥ򲡤ƤƤ줿᡼ԿʥإåޤʤΥ᡼ϵݤޤ餯ʤϥ᡼󥰥ꥹȤ
ǤϤʤꥹȤΥݥꥷDzʳƤػߤƤޤ
ݤθΤȻפϥ᡼󥰥ꥹȴ
%(listowner)s ˤϢ%(listname)s Ƥ줿᡼ϡʲԤξǧԤǤʤƥ᡼, ŬڤȻפޤʤΥ᡼ϵݤޤ᡼뤬Ĺޤ; %(kb)d KB ʲûƤ%(listname)s οꥹȥѥ᡼󥰥ꥹ: %(listname)sʤΥѥɤ: %(password)sѥɤפޤ̾:ϡǧ뤿˥ꥹȻʲԤžޤ줿᡼륢ɥ쥹ϥƥ꤬뤿ᡢ
ϼդޤǤϤ줿᡼륢ɥ쥹ˤϥƥ꤬뤿ᡢ
ϼդޤǤ.Ƥå뤿ˡꥹȴԤ
%(listowner)s žޤդޤ˽ޤ
᡼󥰥ꥹȤ꤬ɤʤäƤ뤫ˤޤ
ƳǧΥ᡼ꤹ뤫뤤ϥꥹȻʲԤǧޤ
ǧɬפʤȤϡˡ񤤤ǧ᡼ꤷޤ%(x)s ͳǤƤޤ
ꥹȻʲԤžޤΤǡʲԤ᡼ä塢
˴ؤ᡼ΤޤǧΤꥹȴԤžޤꡢꥹȻʲԤžޤ
˴ؤθ塢̤᡼Τޤ%(realname)s ᡼󥰥ꥹȤƤ줿۵ޥ᡼ϡ
ǧڤ˼ԤޤźդΥ᡼, MailmanäΥ᡼Ǥ
[----- %(typename)s ե뽪λ -----][----- %(typename)s ե볫 -----][źեեˤ᡼뤬˴ޤ][ܤ顼Ϥޤ][ͳϼƤޤ][ͳϼƤޤ][Ūݤ̤. åϤޤ][̵]1̤α᡼롣ack (ǧ) ץԤˤԤˤꥹȰ٤Ƥα᡼롣%(esender)s Τ٤Ƥα᡼ޤ%(path)s: Υǡ١ե %(octperms)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; Ȥߤޤ᡼ޤdelivery () offdelivery () onޤȤɤޤȤɤߥեåޤȤɤߥإådigest (ޤȤɤ)ץ%(d)s: ǥ쥯ȥϺ 02775 ǤʤФޤ%(path)s: ǥ쥯ȥΥѡߥå %(octperms)s ǤʤФޤߤ줿ɥ쥹dmarc_moderation_action ͤϥǥեͤȤꤷͰʾ
                           ǤʤФʤޤλ顼᡼ˤ顼᡼ˤduplicates (ʣ)ץ᡼륢ɥ쥹᡼Ǥγǧˤ¸˺
%(path)s եΥѡߥåϺ 660 ǤʤȤޤŤ HTML ¸ˤ b6 ư褦˥ѡߥåѹ
¸ˤ礭ȡ 1,2 ʬޤ...餫ͳˤʲΥꥹȤǸĤޤ:%(start)s  %(end)s ޤgenaliases μ¹Ԥ mm_cfg.MTA = %(mta)s פǤ᡼󥰥ꥹȰڡŤեα᡼եhide ()ץͭͤ:ꥹȺꥹȤΰˤ᡼󥰥ꥹȤΰꥹ̾ɬפǤŬ礹᡼󥰥ꥹȤޤ:mbox եϺ 0660 ǤʤФޤɥ쥹<br>̾Υڡ᡼ϤǤޤ: %(filebase)smyposts (ʬ)ץ̵̵ꥹȤޤ == ¹Ԥ˽λޤ̵̵֥<br>[ͳ]̵̵̵offonץmsgid  msgstr  .po ե뤫Ϥѥʿʸ¸᡼󥰥ꥹȤν¹:¸reCAPTCHA ˤ븡ưԤޤǤ: %(e_reason)sreCAPTCHA ˤ븡ڤ˼Ԥޤ: %(e_codes)sreminder (˺)ץ%(src)s ޤ%(src)s ǥ쥯ȥʲޤ%(categoryname)s ץΥڡ롣 ܤΥե뤫ʸ򥹥󤹤ʸ򥹥󤹤po ե򥹥󤷤 msgid  msgstr //ʤ%(path)s: եΥѡߥå %(octperms)s ǤʤФޤŤåեstop  end ޥɤƱ̣Ǥ
̾%(name)s ؤˤϴԤξǧɬפǤ%(realname)s ؤˤϻʲԤξǧɬפǤꥹȴڡꥹȴ᡼󥰥ꥹȰڡå롼ײʤ/ˤϻʲԤξǧɬפǤŤ qfile 򹹿Ԥξǧˤ᡼ǤγǧˤץΥڡWebǤγǧˤ%(esender)s Τ٤ƤΥ᡼򸫤WebǤγǧˤ
Back to Directory File Manager