source: non-gtk/mailman/bg/500-999.po@ 1831

# Bulgarian translation for GNU MailMan 2.1.12
# Copyright (C) 2004, 2005, 2006, 2007, 2009 Free Software Foundation, Inc.
# Alexander Shopov <ash@contact.bg>, 2004, 2005, 2006, 2007, 2009.
#
#
msgid ""
msgstr ""
"Project-Id-Version: GNU MailMan 2.1.12\n"
"POT-Creation-Date: Sun Jan 11 08:28:57 2009\n"
"PO-Revision-Date: 2009-07-14 08:34+0300\n"
"Last-Translator: Alexander Shopov <ash@contact.bg>\n"
"Language-Team: Bulgarian <dict@fsa-bg.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: pygettext.py 1.4\n"
"Plural-Forms: nplurals=2; plural=n != 1;\n"

#: Mailman/Commands/cmd_password.py:17
msgid ""
"\n"
"    password [<oldpassword> <newpassword>] [address=<address>]\n"
"        Retrieve or change your password.  With no arguments, this returns\n"
"        your current password.  With arguments <oldpassword> and "
"<newpassword>\n"
"        you can change your password.\n"
"\n"
"        If you're posting from an address other than your membership "
"address,\n"
"        specify your membership address with `address=<address>' (no "
"brackets\n"
"        around the email address, and no quotes!).  Note that in this case "
"the\n"
"        response is always sent to the subscribed address.\n"
msgstr ""

#: Mailman/Commands/cmd_who.py:35
msgid ""
"\n"
"    who password [address=<address>]\n"
"        See the non-hidden members of this mailing list.  The roster is\n"
"        limited to list members only, and you must supply your membership\n"
"        password to retrieve it.  If you're posting from an address other\n"
"        than your membership address, specify your membership address with\n"
"        `address=<address>' (no brackets around the email address, and no\n"
"        quotes!). If you provide the list's admin or moderator password,\n"
"        hidden members will be included.\n"
msgstr ""

#: Mailman/Gui/Autoresponse.py:39
msgid ""
"Auto-responder characteristics.<p>\n"
"\n"
"In the text fields below, string interpolation is performed with\n"
"the following key/value substitutions:\n"
"<p><ul>\n"
"    <li><b>listname</b> - <em>gets the name of the mailing list</em>\n"
"    <li><b>listurl</b> - <em>gets the list's listinfo URL</em>\n"
"    <li><b>requestemail</b> - <em>gets the list's -request address</em>\n"
"    <li><b>owneremail</b> - <em>gets the list's -owner address</em>\n"
"</ul>\n"
"\n"
"<p>For each text field, you can either enter the text directly into the "
"text\n"
"box, or you can specify a file on your local system to upload as the text."
msgstr ""

#: Mailman/Gui/Bounce.py:88
msgid ""
"Each subscriber is assigned a bounce score, as a floating\n"
"             point number.  Whenever Mailman receives a bounce from a list\n"
"             member, that member's score is incremented.  Hard bounces "
"(fatal\n"
"             errors) increase the score by 1, while soft bounces (temporary\n"
"             errors) increase the score by 0.5.  Only one bounce per day\n"
"             counts against a member's score, so even if 10 bounces are\n"
"             received for a member on the same day, their score will "
"increase\n"
"             by just 1.\n"
"\n"
"             This variable describes the upper limit for a member's bounce\n"
"             score, above which they are automatically disabled, but not\n"
"             removed from the mailing list."
msgstr ""

#: Mailman/Gui/ContentFilter.py:82
msgid ""
"Use this option to remove each message attachment that\n"
"             matches one of these content types.  Each line should contain "
"a\n"
"             string naming a MIME <tt>type/subtype</tt>,\n"
"             e.g. <tt>image/gif</tt>.  Leave off the subtype to remove all\n"
"             parts with a matching major content type, e.g. <tt>image</tt>.\n"
"\n"
"             <p>Blank lines are ignored.\n"
"\n"
"             <p>See also <a href=\"?VARHELP=contentfilter/pass_mime_types\"\n"
"             >pass_mime_types</a> for a content type whitelist."
msgstr ""

#: Mailman/Gui/General.py:146
msgid ""
"This text will be prepended to subject lines of messages\n"
"             posted to the list, to distinguish mailing list messages in\n"
"             mailbox summaries.  Brevity is premium here, it's ok to "
"shorten\n"
"             long mailing list names to something more concise, as long as "
"it\n"
"             still identifies the mailing list.\n"
"             You can also add a sequential number by %%d substitution\n"
"             directive. eg.; [listname %%d] -> [listname 123]\n"
"                            (listname %%05d) -> (listname 00123)\n"
"             "
msgstr ""

#: Mailman/Gui/General.py:256
msgid ""
"When \"umbrella_list\" is set to indicate that this list has\n"
"             other mailing lists as members, then administrative notices "
"like\n"
"             confirmations and password reminders need to not be sent to "
"the\n"
"             member list addresses, but rather to the owner of those member\n"
"             lists.  In that case, the value of this setting is appended to\n"
"             the member's account name for such notices.  `-owner' is the\n"
"             typical choice.  This setting has no effect when \"umbrella_list"
"\"\n"
"             is \"No\"."
msgstr ""

#: Mailman/Gui/General.py:278
msgid ""
"This value, if any, will be added to the front of the\n"
"             new-subscriber welcome message.  The rest of the welcome "
"message\n"
"             already describes the important addresses and URLs for the\n"
"             mailing list, so you don't need to include any of that kind of\n"
"             stuff here.  This should just contain mission-specific kinds "
"of\n"
"             things, like etiquette policies or team orientation, or that "
"kind\n"
"             of thing.\n"
"\n"
"             <p>Note that this text will be wrapped, according to the\n"
"             following rules:\n"
"             <ul><li>Each paragraph is filled so that no line is longer "
"than\n"
"                     70 characters.\n"
"                 <li>Any line that begins with whitespace is not filled.\n"
"                 <li>A blank line separates paragraphs.\n"
"             </ul>"
msgstr ""

#: Mailman/Gui/General.py:387
msgid ""
"RFC 2369 defines a set of List-* headers that are\n"
"                 normally added to every message sent to the list "
"membership.\n"
"                 These greatly aid end-users who are using standards "
"compliant\n"
"                 mail readers.  They should normally always be enabled.\n"
"\n"
"                 <p>However, not all mail readers are standards compliant "
"yet,\n"
"                 and if you have a large number of members who are using\n"
"                 non-compliant mail readers, they may be annoyed at these\n"
"                 headers.  You should first try to educate your members as "
"to\n"
"                 why these headers exist, and how to hide them in their "
"mail\n"
"                 clients.  As a last resort you can disable these headers, "
"but\n"
"                 this is not recommended (and in fact, your ability to "
"disable\n"
"                 these headers may eventually go away)."
msgstr ""

#: Mailman/Gui/General.py:406
msgid ""
"The <tt>List-Post:</tt> header is one of the headers\n"
"             recommended by\n"
"             <a href=\"http://www.faqs.org/rfcs/rfc2369.html\">RFC 2369</"
"a>.\n"
"             However for some <em>announce-only</em> mailing lists, only a\n"
"             very select group of people are allowed to post to the list; "
"the\n"
"             general membership is usually not allowed to post.  For lists "
"of\n"
"             this nature, the <tt>List-Post:</tt> header is misleading.\n"
"             Select <em>No</em> to disable the inclusion of this header. "
"(This\n"
"             does not affect the inclusion of the other <tt>List-*:</tt>\n"
"             headers.)"
msgstr ""

#: Mailman/Gui/NonDigest.py:110
msgid ""
"When <a href=\"?VARHELP=nondigest/personalize\">personalization</a> is "
"enabled\n"
"for this list, additional substitution variables are allowed in your "
"headers\n"
"and footers:\n"
"\n"
"<ul><li><b>user_address</b> - The address of the user,\n"
"        coerced to lower case.\n"
"    <li><b>user_delivered_to</b> - The case-preserved address\n"
"        that the user is subscribed with.\n"
"    <li><b>user_password</b> - The user's password.\n"
"    <li><b>user_name</b> - The user's full name.\n"
"    <li><b>user_optionsurl</b> - The url to the user's option\n"
"        page.\n"
"</ul>\n"
msgstr ""

#: Mailman/Gui/Privacy.py:64
msgid ""
"None - no verification steps (<em>Not\n"
"                           Recommended </em>)<br>\n"
"                           Confirm (*) - email confirmation step required "
"<br>\n"
"                           Require approval - require list administrator\n"
"                           Approval for subscriptions <br>\n"
"                           Confirm and approve - both confirm and approve\n"
"                           \n"
"                           <p>(*) when someone requests a subscription,\n"
"                           Mailman sends them a notice with a unique\n"
"                           subscription request number that they must reply "
"to\n"
"                           in order to subscribe.<br>\n"
"\n"
"                           This prevents mischievous (or malicious) people\n"
"                           from creating subscriptions for others without\n"
"                           their consent."
msgstr ""

#: Mailman/Gui/Privacy.py:87
msgid ""
"Confirm (*) - email confirmation required <br>\n"
"                           Require approval - require list administrator\n"
"                           approval for subscriptions <br>\n"
"                           Confirm and approve - both confirm and approve\n"
"                           \n"
"                           <p>(*) when someone requests a subscription,\n"
"                           Mailman sends them a notice with a unique\n"
"                           subscription request number that they must reply "
"to\n"
"                           in order to subscribe.<br> This prevents\n"
"                           mischievous (or malicious) people from creating\n"
"                           subscriptions for others without their consent."
msgstr ""

#: Mailman/Gui/Privacy.py:120
msgid ""
"When members want to leave a list, they will make an\n"
"             unsubscription request, either via the web or via email.\n"
"             Normally it is best for you to allow open unsubscriptions so "
"that\n"
"             users can easily remove themselves from mailing lists (they "
"get\n"
"             really upset if they can't get off lists!).\n"
"\n"
"             <p>For some lists though, you may want to impose moderator\n"
"             approval before an unsubscription request is processed.  "
"Examples\n"
"             of such lists include a corporate mailing list that all "
"employees\n"
"             are required to be members of."
msgstr ""

#: Mailman/Gui/Privacy.py:200
msgid ""
"Each list member has a <em>moderation flag</em> which says\n"
"             whether messages from the list member can be posted directly "
"to\n"
"             the list, or must first be approved by the list moderator.  "
"When\n"
"             the moderation flag is turned on, list member postings must be\n"
"             approved first.  You, the list administrator can decide whether "
"a\n"
"             specific individual's postings will be moderated or not.\n"
"\n"
"             <p>When a new member is subscribed, their initial moderation "
"flag\n"
"             takes its value from this option.  Turn this option off to "
"accept\n"
"             member postings by default.  Turn this option on to, by "
"default,\n"
"             moderate member postings first.  You can always manually set "
"an\n"
"             individual member's moderation bit by using the\n"
"             <a href=\"%(adminurl)s/members\">membership management\n"
"             screens</a>."
msgstr ""

#: Mailman/Gui/Privacy.py:219
msgid ""
"<ul><li><b>Hold</b> -- this holds the message for approval\n"
"             by the list moderators.\n"
"\n"
"             <p><li><b>Reject</b> -- this automatically rejects the message "
"by\n"
"             sending a bounce notice to the post's author.  The text of the\n"
"             bounce notice can be <a\n"
"             href=\"?VARHELP=privacy/sender/member_moderation_notice\"\n"
"             >configured by you</a>.\n"
"\n"
"             <p><li><b>Discard</b> -- this simply discards the message, "
"with\n"
"             no notice sent to the post's author.\n"
"             </ul>"
msgstr ""

#: Mailman/Gui/Privacy.py:271
msgid ""
"Postings from any of these non-members will be automatically\n"
"             rejected.  In other words, their messages will be bounced back "
"to\n"
"             the sender with a notification of automatic rejection.  This\n"
"             option is not appropriate for known spam senders; their "
"messages\n"
"             should be\n"
"             <a href=\"?VARHELP=privacy/sender/discard_these_nonmembers\"\n"
"             >automatically discarded</a>.\n"
"\n"
"             <p>Add member addresses one per line; start the line with a ^\n"
"             character to designate a regular expression match."
msgstr ""

#: Mailman/Gui/Privacy.py:286
msgid ""
"Postings from any of these non-members will be automatically\n"
"             discarded.  That is, the message will be thrown away with no\n"
"             further processing or notification.  The sender will not "
"receive\n"
"             a notification or a bounce, however the list moderators can\n"
"             optionally <a href=\"?VARHELP=privacy/sender/"
"forward_auto_discards\"\n"
"             >receive copies of auto-discarded messages.</a>.\n"
"\n"
"             <p>Add member addresses one per line; start the line with a ^\n"
"             character to designate a regular expression match."
msgstr ""

#: Mailman/Gui/Privacy.py:301
msgid ""
"When a post from a non-member is received, the message's\n"
"             sender is matched against the list of explicitly\n"
"             <a href=\"?VARHELP=privacy/sender/accept_these_nonmembers\"\n"
"             >accepted</a>,\n"
"             <a href=\"?VARHELP=privacy/sender/hold_these_nonmembers\">held</"
"a>,\n"
"             <a href=\"?VARHELP=privacy/sender/reject_these_nonmembers\"\n"
"             >rejected</a> (bounced), and\n"
"             <a href=\"?VARHELP=privacy/sender/discard_these_nonmembers\"\n"
"             >discarded</a> addresses.  If no match is found, then this "
"action\n"
"             is taken."
msgstr ""

#: Mailman/Gui/Privacy.py:335
msgid ""
"Many (in fact, most) spams do not explicitly name their\n"
"             myriad destinations in the explicit destination addresses - in\n"
"             fact often the To: field has a totally bogus address for\n"
"             obfuscation.  The constraint applies only to the stuff in the\n"
"             address before the '@' sign, but still catches all such spams.\n"
"\n"
"             <p>The cost is that the list will not accept unhindered any\n"
"             postings relayed from other addresses, unless\n"
"\n"
"             <ol>\n"
"                 <li>The relaying address has the same name, or\n"
"\n"
"                 <li>The relaying address name is included on the options "
"that\n"
"                 specifies acceptable aliases for the list.\n"
"\n"
"             </ol>"
msgstr ""

#: Mailman/Gui/Privacy.py:356
msgid ""
"Alternate addresses that are acceptable when\n"
"             `require_explicit_destination' is enabled.  This option takes "
"a\n"
"             list of regular expressions, one per line, which is matched\n"
"             against every recipient address in the message.  The matching "
"is\n"
"             performed with Python's re.match() function, meaning they are\n"
"             anchored to the start of the string.\n"
"             \n"
"             <p>For backwards compatibility with Mailman 1.1, if the regexp\n"
"             does not contain an `@', then the pattern is matched against "
"just\n"
"             the local part of the recipient address.  If that match fails, "
"or\n"
"             if the pattern does contain an `@', then the pattern is "
"matched\n"
"             against the entire recipient address.\n"
"             \n"
"             <p>Matching against the local part is deprecated; in a future\n"
"             release, the pattern will always be matched against the entire\n"
"             recipient address."
msgstr ""

#: Mailman/Gui/Privacy.py:391
msgid ""
"Each header filter rule has two parts, a list of regular\n"
"             expressions, one per line, and an action to take.  Mailman\n"
"             matches the message's headers against every regular expression "
"in\n"
"             the rule and if any match, the message is rejected, held, or\n"
"             discarded based on the action you specify.  Use <em>Defer</em> "
"to\n"
"             temporarily disable a rule.\n"
"\n"
"             You can have more than one filter rule for your list.  In that\n"
"             case, each rule is matched in turn, with processing stopped "
"after\n"
"             the first match.\n"
"\n"
"             Note that headers are collected from all the attachments \n"
"             (except for the mailman administrivia message) and\n"
"             matched against the regular expressions. With this feature,\n"
"             you can effectively sort out messages with dangerous file\n"
"             types or file name extensions."
msgstr ""

#: Mailman/Gui/Privacy.py:412
msgid ""
"Use this option to prohibit posts according to specific\n"
"             header values.  The target value is a regular-expression for\n"
"             matching against the specified header.  The match is done\n"
"             disregarding letter case.  Lines beginning with '#' are "
"ignored\n"
"             as comments.\n"
"\n"
"             <p>For example:<pre>to: .*@public.com </pre> says to hold all\n"
"             postings with a <em>To:</em> mail header containing '@public."
"com'\n"
"             anywhere among the addresses.\n"
"\n"
"             <p>Note that leading whitespace is trimmed from the regexp.  "
"This\n"
"             can be circumvented in a number of ways, e.g. by escaping or\n"
"             bracketing it."
msgstr ""

#: Mailman/Gui/Topics.py:72
msgid ""
"The topic matcher will scan this many lines of the message\n"
"             body looking for topic keyword matches.  Body scanning stops "
"when\n"
"             either this many lines have been looked at, or a non-header-"
"like\n"
"             body line is encountered.  By setting this value to zero, no "
"body\n"
"             lines will be scanned (i.e. only the <code>Keywords:</code> "
"and\n"
"             <code>Subject:</code> headers will be scanned).  By setting "
"this\n"
"             value to a negative number, then all body lines will be "
"scanned\n"
"             until a non-header-like line is encountered.\n"
"             "
msgstr ""

#: bin/check_db:19
msgid ""
"Check a list's config database file for integrity.\n"
"\n"
"All of the following files are checked:\n"
"\n"
"    config.pck\n"
"    config.pck.last\n"
"    config.db\n"
"    config.db.last\n"
"    config.safety\n"
"\n"
"It's okay if any of these are missing.  config.pck and config.pck.last are\n"
"pickled versions of the config database file for 2.1a3 and beyond.  config."
"db\n"
"and config.db.last are used in all earlier versions, and these are Python\n"
"marshals.  config.safety is a pickle written by 2.1a3 and beyond when the\n"
"primary config.pck file could not be read.\n"
"\n"
"Usage: %(PROGRAM)s [options] [listname [listname ...]]\n"
"\n"
"Options:\n"
"\n"
"    --all / -a\n"
"        Check the databases for all lists.  Otherwise only the lists named "
"on\n"
"        the command line are checked.\n"
"\n"
"    --verbose / -v\n"
"        Verbose output.  The state of every tested file is printed.\n"
"        Otherwise only corrupt files are displayed.\n"
"\n"
"    --help / -h\n"
"        Print this text and exit.\n"
msgstr ""

#: bin/find_member:19
msgid ""
"Find all lists that a member's address is on.\n"
"\n"
"Usage:\n"
"    find_member [options] regex [regex [...]]\n"
"\n"
"Where:\n"
"    --listname=listname\n"
"    -l listname\n"
"        Include only the named list in the search.\n"
"\n"
"    --exclude=listname\n"
"    -x listname\n"
"        Exclude the named list from the search.\n"
"\n"
"    --owners\n"
"    -w\n"
"        Search list owners as well as members.\n"
"\n"
"    --help\n"
"    -h\n"
"        Print this help message and exit.\n"
"\n"
"    regex\n"
"        A Python regular expression to match against.\n"
"\n"
"The interaction between -l and -x is as follows.  If any -l option is given\n"
"then only the named list will be included in the search.  If any -x option "
"is\n"
"given but no -l option is given, then all lists will be search except those\n"
"specifically excluded.\n"
"\n"
"Regular expression syntax is Perl5-like, using the Python re module.  "
"Complete\n"
"specifications are at:\n"
"\n"
"http://docs.python.org/library/re.html\n"
"\n"
"Address matches are case-insensitive, but case-preserved addresses are\n"
"displayed.\n"
"\n"
msgstr ""

#: bin/fix_url.py:19
msgid ""
"Reset a list's web_page_url attribute to the default setting.\n"
"\n"
"This script is intended to be run as a bin/withlist script, i.e.\n"
"\n"
"% bin/withlist -l -r fix_url listname [options]\n"
"\n"
"Options:\n"
"    -u urlhost\n"
"    --urlhost=urlhost\n"
"        Look up urlhost in the virtual host table and set the web_page_url "
"and\n"
"        host_name attributes of the list to the values found.  This\n"
"        essentially moves the list from one virtual domain to another.\n"
"\n"
"        Without this option, the default web_page_url and host_name values "
"are\n"
"        used.\n"
"\n"
"    -v / --verbose\n"
"        Print what the script is doing.\n"
"\n"
"If run standalone, it prints this help text and exits.\n"
msgstr ""

#: bin/inject:20
msgid ""
"Inject a message from a file into Mailman's incoming queue.\n"
"\n"
"Usage: inject [options] [filename]\n"
"\n"
"Options:\n"
"\n"
"    -h / --help\n"
"        Print this text and exit.\n"
"\n"
"    -l listname\n"
"    --listname=listname\n"
"        The name of the list to inject this message to.  Required.\n"
"\n"
"    -q queuename\n"
"    --queue=queuename\n"
"        The name of the queue to inject the message to.  The queuename must "
"be\n"
"        one of the directories inside the qfiles directory.  If omitted, "
"the\n"
"        incoming queue is used.\n"
"\n"
"filename is the name of the plaintext message file to inject.  If omitted,\n"
"standard input is used.\n"
msgstr ""

#: bin/list_owners:20
msgid ""
"List the owners of a mailing list, or all mailing lists.\n"
"\n"
"Usage: %(PROGRAM)s [options] [listname ...]\n"
"Options:\n"
"\n"
"    -w / --with-listnames\n"
"        Group the owners by list names and include the list names in the\n"
"        output.  Otherwise, the owners will be sorted and uniquified based "
"on\n"
"        the email address.\n"
"\n"
"    -m / --moderators\n"
"        Include the list moderators in the output.\n"
"\n"
"    -h / --help\n"
"        Print this help message and exit.\n"
"\n"
"    listname\n"
"        Print the owners of the specified lists.  More than one can appear\n"
"        after the options.  If there are no listnames provided, the owners "
"of\n"
"        all the lists will be displayed.\n"
msgstr ""

#: bin/mmsitepass:19
msgid ""
"Set the site password, prompting from the terminal.\n"
"\n"
"The site password can be used in most if not all places that the list\n"
"administrator's password can be used, which in turn can be used in most "
"places\n"
"that a list users password can be used.\n"
"\n"
"Usage: %(PROGRAM)s [options] [password]\n"
"\n"
"Options:\n"
"\n"
"    -c/--listcreator\n"
"        Set the list creator password instead of the site password.  The "
"list\n"
"        creator is authorized to create and remove lists, but does not have\n"
"        the total power of the site administrator.\n"
"\n"
"    -h/--help\n"
"        Print this help message and exit.\n"
"\n"
"If password is not given on the command line, it will be prompted for.\n"
msgstr ""

#: bin/msgfmt.py:5
msgid ""
"Generate binary message catalog from textual translation description.\n"
"\n"
"This program converts a textual Uniforum-style message catalog (.po file) "
"into\n"
"a binary GNU catalog (.mo file).  This is essentially the same function as "
"the\n"
"GNU msgfmt program, however, it is a simpler implementation.\n"
"\n"
"Usage: msgfmt.py [OPTIONS] filename.po\n"
"\n"
"Options:\n"
"    -o file\n"
"    --output-file=file\n"
"        Specify the output file to write to.  If omitted, output will go to "
"a\n"
"        file named filename.mo (based off the input file name).\n"
"\n"
"    -h\n"
"    --help\n"
"        Print this message and exit.\n"
"\n"
"    -V\n"
"    --version\n"
"        Display version information and exit.\n"
msgstr ""

#: bin/rb-archfix:21
msgid ""
"Reduce disk space usage for Pipermail archives.\n"
"\n"
"Usage: %(PROGRAM)s [options] file ...\n"
"\n"
"Where options are:\n"
"    -h / --help\n"
"        Print this help message and exit.\n"
"\n"
"Only use this to 'fix' archive -article database files that have been "
"written\n"
"with Mailman 2.1.3 or earlier and have html_body attributes in them.  These\n"
"attributes can cause huge amounts of memory bloat and impact performance "
"for\n"
"high activity lists, particularly those where large text postings are made "
"to\n"
"them.\n"
"\n"
"Example:\n"
"\n"
"%% ls -1 archives/private/*/database/*-article | xargs %(PROGRAM)s\n"
"\n"
"You should run `bin/check_perms -f' after running this script.\n"
"\n"
"You will probably want to delete the -article.bak files created by this "
"script\n"
"when you are satisfied with the results.\n"
"\n"
"This script is provided for convenience purposes only.  It isn't supported.\n"
msgstr ""

#: bin/update:733
msgid ""
"\n"
"\n"
"NOTE NOTE NOTE NOTE NOTE\n"
"\n"
"    You are upgrading an existing Mailman installation, but I can't tell "
"what\n"
"    version you were previously running.\n"
"\n"
"    If you are upgrading from Mailman 1.0b9 or earlier you will need to\n"
"    manually update your mailing lists.  For each mailing list you need to\n"
"    copy the file templates/options.html lists/<listname>/options.html.\n"
"\n"
"    However, if you have edited this file via the Web interface, you will "
"have\n"
"    to merge your changes into this file, otherwise you will lose your\n"
"    changes.\n"
"\n"
"NOTE NOTE NOTE NOTE NOTE\n"
"\n"
msgstr ""

#: cron/cull_bad_shunt:20
msgid ""
"Cull bad and shunt queues, recommended once per day.\n"
"\n"
"This script goes through the 'bad' and 'shunt' queue directories and,\n"
"if mm_cfg.BAD_SHUNT_STALE_AFTER is > 0, it removes all files more than\n"
"that many seconds old.\n"
"\n"
"If mm_cfg.BAD_SHUNT_ARCHIVE_DIRECTORY is a writable directory, the old\n"
"files are moved there. Otherwise they are deleted.\n"
"\n"
"Only regular files immediately subordinate to the 'bad' and 'shunt'\n"
"directories are processed. Anything else is skipped.\n"
"\n"
"Usage: %(PROGRAM)s [options]\n"
"\n"
"Options:\n"
"    -h / --help\n"
"        Print this message and exit.\n"
msgstr ""