# Bulgarian translation for GNU MailMan 2.1.15 # Copyright (C) 2004, 2005, 2006, 2007, 2009, 2013 Free Software Foundation, Inc. # Alexander Shopov , 2004, 2005, 2006, 2007, 2009, 2013. # Ognyan Rangelov , 2013. # msgid "" msgstr "" "Project-Id-Version: GNU MailMan 2.1.15\n" "POT-Creation-Date: Sun Mar 25 16:40:47 2012\n" "PO-Revision-Date: 2013-06-12 16:00+0300\n" "Last-Translator: Alexander Shopov \n" "Language-Team: Bulgarian \n" "Language: bg\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/Cgi/create.py:305 msgid "" "You can create a new mailing list by entering the\n" " relevant information into the form below. The name of the mailing list\n" " will be used as the primary address for posting messages to the list, " "so\n" " it should be lowercased. You will not be able to change this once the\n" " list is created.\n" "\n" "

You also need to enter the email address of the initial list owner.\n" " Once the list is created, the list owner will be given notification, " "along\n" " with the initial list password. The list owner will then be able to\n" " modify the password and add or remove additional list owners.\n" "\n" "

If you want Mailman to automatically generate the initial list admin\n" " password, click on `Yes' in the autogenerate field below, and leave the\n" " initial list password fields empty.\n" "\n" "

You must have the proper authorization to create new mailing lists.\n" " Each site should have a list creator's password, which you can\n" " enter in the field at the bottom. Note that the site administrator's\n" " password can also be used for authentication.\n" " " msgstr "" "Можете да създадете нов пощенски списък като въведете съответната\n" "информация във формуляра отдолу. Името на пощенския списък ще се\n" "използва като основния адрес за е-поща за изпращане на писма до\n" "списъка. Затова името трябва да се състои от малки букви. Няма да\n" "имате повече възможност да променяте името след създаването на спиъка.\n" "\n" "

Трябва да въведете и адреса на е-поща на първоначалния ръководител.\n" "След като списъкът бъде създаден, ръководителят ще получи уведомление,\n" "в което ще бъде посочена първоначалната парола за списъка.\n" "Ръководителят на списъка ще може да променя паролата и да добавя други\n" "ръководители на списъка.\n" "\n" "

Трябва да имате необходимите права, за да създавате нови пощенски\n" "списъци. Всеки сайт има парола за съдателя на списъци,\n" "която можете да въведете в полето отдолу. Забележете, че паролата на\n" "администратора на сайта също може да бъде използвана за идентификация." #: Mailman/Commands/cmd_set.py:37 msgid "" "\n" " set help\n" " Show this detailed help.\n" "\n" " set show [address=

]\n" " View your current option settings. If you're posting from an " "address\n" " other than your membership address, specify your membership address\n" " with `address=
' (no brackets around the email address, and " "no\n" " quotes!).\n" "\n" " set authenticate [address=
]\n" " To set any of your options, you must include this command first, " "along\n" " with your membership password. If you're posting from an address\n" " other than your membership address, specify your membership address\n" " with `address=
' (no brackets around the email address, and " "no\n" " quotes!).\n" "\n" " set ack on\n" " set ack off\n" " When the `ack' option is turned on, you will receive an\n" " acknowledgement message whenever you post a message to the list.\n" "\n" " set digest plain\n" " set digest mime\n" " set digest off\n" " When the `digest' option is turned off, you will receive postings\n" " immediately when they are posted. Use `set digest plain' if " "instead\n" " you want to receive postings bundled into a plain text digest\n" " (i.e. RFC 1153 digest). Use `set digest mime' if instead you want " "to\n" " receive postings bundled together into a MIME digest.\n" "\n" " set delivery on\n" " set delivery off\n" " Turn delivery on or off. This does not unsubscribe you, but " "instead\n" " tells Mailman not to deliver messages to you for now. This is " "useful\n" " if you're going on vacation. Be sure to use `set delivery on' when\n" " you return from vacation!\n" "\n" " set myposts on\n" " set myposts off\n" " Use `set myposts off' to not receive copies of messages you post to\n" " the list. This has no effect if you're receiving digests.\n" "\n" " set hide on\n" " set hide off\n" " Use `set hide on' to conceal your email address when people request\n" " the membership list.\n" "\n" " set duplicates on\n" " set duplicates off\n" " Use `set duplicates off' if you want Mailman to not send you " "messages\n" " if your address is explicitly mentioned in the To: or Cc: fields of\n" " the message. This can reduce the number of duplicate postings you\n" " will receive.\n" "\n" " set reminders on\n" " set reminders off\n" " Use `set reminders off' if you want to disable the monthly password\n" " reminder for this mailing list.\n" msgstr "" "\n" " set help\n" " Показване на подробната помощ.\n" "\n" " set show [address=<АДРЕС>] Показване на текущите настройки. Ако\n" " изпращате това писмо от адрес различен от този, с който сте се\n" " абонирали, трябва да укажете втория чрез опцията\n" " „address=<АДРЕС>“ (без счупени скоби около адреса и без\n" " кавичките!).\n" "\n" " set authenticate <ПАРОЛА> [address=<АДРЕС>]\n" " За да зададете някаква настройка, трябва първо да включите\n" " тази команда заедно с паролата на абонамента ви. Ако\n" " изпращате това писмо от адрес различен от този, с който сте се\n" " абонирали, трябва да укажете втория чрез опцията\n" " „address=<АДРЕС>“ (без счупени скоби около адреса и без\n" " кавичките!).\n" "\n" " set ack on\n" " set ack off\n" " Когато настройката „ack“ е включена, ще получавате\n" " потвърждаващо съобщение всеки пък, когато изпратите писмо до\n" " пощенския списък.\n" "\n" " set digest plain\n" " set digest mime\n" " set digest off\n" " Когато настройката „digest“ (за резюмета) е изключена, ще\n" " получавате писмата веднага след получаването им от пощенския\n" " списък. Използвайте командата „set digest plain“, за да\n" " получавате писмата в сбор от резюмета в текстов формат (по RFC\n" " 1153). Използвайте командата „set digest mime“, ако\n" " предпочитате да получавате резюмето във формат MIME.\n" "\n" " set delivery on\n" " set delivery off\n" " Включване и изключване на доставянето на съобщения. Тази\n" " настройка не прекратява абонамента ви, вместо това Mailman\n" " престава да ви доставя писмата от списъка. Тази възможност е\n" " удобна, когато излизате в отпуск. Не забравяйте след това\n" " отново да включите доставянето с командата „set delivery on“!\n" "\n" " set myposts on\n" " set myposts off\n" " Използвайте командата „set myposts off“, за да не получавате\n" " копия на писмата, които пращате до списъка. Тази настройка\n" " ням значение, ако използвате режим на резюмета.\n" "\n" " set hide on\n" " set hide off\n" " Използвайте командата „set hide on“, когато искате адресът ви\n" " на е-поща да е скрит, когато хората изискват списъка на\n" " абонатите на списъка.\n" "\n" " set duplicates on\n" " set duplicates off\n" " Използвайте командата „set duplicates off“, ако искате Mailman\n" " де не ви праща писмата, ако адресът ви е изрично упоменат в\n" " полетата „To:“ и „Cc:“ на писмото. Това може да намали броя\n" " на повтарящите се писма, които получавате.\n" "\n" " set reminders on\n" " set reminders off\n" " Използвайте командата „set reminders off“, за да изключите\n" " ежемесечните напомнящи писма на паролата ви да този пощенски\n" " списък.\n" #: Mailman/Gui/Bounce.py:32 msgid "" "These policies control the automatic bounce processing system\n" " in Mailman. Here's an overview of how it works.\n" "\n" "

When a bounce is received, Mailman tries to extract two " "pieces\n" " of information from the message: the address of the member the\n" " message was intended for, and the severity of the problem " "causing\n" " the bounce. The severity can be either hard or\n" " soft meaning either a fatal error occurred, or a\n" " transient error occurred. When in doubt, a hard severity is " "used.\n" "\n" "

If no member address can be extracted from the bounce, then " "the\n" " bounce is usually discarded. Otherwise, each member is assigned " "a\n" " bounce score and every time we encounter a bounce from\n" " this member we increment the score. Hard bounces increment by " "1\n" " while soft bounces increment by 0.5. We only increment the " "bounce\n" " score once per day, so even if we receive ten hard bounces from " "a\n" " member per day, their score will increase by only 1 for that " "day.\n" "\n" "

When a member's bounce score is greater than the\n" " bounce score\n" " threshold, the subscription is disabled. Once disabled, " "the\n" " member will not receive any postings from the list until their\n" " membership is explicitly re-enabled (either by the list\n" " administrator or the user). However, they will receive " "occasional\n" " reminders that their membership has been disabled, and these\n" " reminders will include information about how to re-enable their\n" " membership.\n" "\n" "

You can control both the\n" " number\n" " of reminders the member will receive and the\n" " frequency with which these reminders are sent.\n" "\n" "

There is one other important configuration variable; after a\n" " certain period of time -- during which no bounces from the " "member\n" " are received -- the bounce information is\n" " considered\n" " stale and discarded. Thus by adjusting this value, and the\n" " score threshold, you can control how quickly bouncing members " "are\n" " disabled. You should tune both of these to the frequency and\n" " traffic volume of your list." msgstr "" "Тези политики управляват системата за автоматично управление на " "неполучените\n" " писма в Mailman. Тя работи по следния начин.\n" "\n" "

При получаването на известие за неполучаване, Mailman\n" " се опитва да извлече следните две данни от писмото:\n" " адресът на абоната, за който е било предназначено\n" " съобщението и сериозността на причината за неполучаване.\n" " Тя може да е или тежка или лека в\n" " зависимост от това дали грешката е фатална или временна.\n" " Когато това не е сигурно се приема, че причината е тежка.\n" "\n" "

Известия, от които не може да се извлече адрес на\n" " абонат, обикновено се пренебрегват. В противен случай, се\n" " въвеждат точки за неполучаване. Всеки път при\n" " получаване на известие за неполучаване от определен член,\n" " неговите точки се увеличават. Неполучаванията поради\n" " тежка причина увеличават точките с една, а тези поради\n" " лека — с 0,5. Точките се увеличават само ежедневно, но\n" " само веднъж. Дори и да са пристигнали 10 известия за\n" " неполучаване поради тежко причина, точките за деня ще се\n" " увеличат само с 1.\n" "\n" "

Когато точките за неполучаване на абонат надминат прага за\n" " неполучаване, се прекратява пращането на писма от\n" " списъка до абоната, докато не бъде позволено наново (или\n" " от ръководителя на списъка, или от самия абонат).\n" " Периодично до абоната ще бъдат пращани напомняния, че\n" " пращането на писма е било прекратено, в които е включена\n" " информация за начина на повторно позволяване на\n" " изпращането на писма.\n" "\n" "

Можете да зададете както броя\n" " на напомнянията, които абонатът ще получи, така и честотата, с която те биват изпращани.\n" "\n" "

Има още една важна променлива за настройване — след\n" " определен период от време, в течение на който не е\n" " получено нито едно известие, че абонатът не е получил\n" " писмо, информацията за неполучаване се счита\n" " за остаряла и бива изтрита. Чрез тази променлива и\n" " прага за неполучаване можете да управлявате скоростта на\n" " прекратяване на пращането на писма до неполучаващите\n" " абонати. Трябва да ги настроите в зависимост от честотата\n" " и обема на трафика на вашия списък." #: Mailman/Gui/Bounce.py:124 msgid "" "While Mailman's bounce detector is fairly robust, it's\n" " impossible to detect every bounce format in the world. You\n" " should keep this variable set to Yes for two reasons: " "1)\n" " If this really is a permanent bounce from one of your members,\n" " you should probably manually remove them from your list, and " "2)\n" " you might want to send the message on to the Mailman " "developers\n" " so that this new format can be added to its known set.\n" "\n" "

If you really can't be bothered, then set this variable to\n" " No and all non-detected bounces will be discarded\n" " without further processing.\n" "\n" "

Note: This setting will also affect all messages " "sent\n" " to your list's -admin address. This address is deprecated and\n" " should never be used, but some people may still send mail to " "this\n" " address. If this happens, and this variable is set to\n" " No those messages too will get discarded. You may " "want\n" " to set up an\n" " autoresponse\n" " message for email to the -owner and -admin address." msgstr "" #: Mailman/Gui/ContentFilter.py:42 msgid "" "Policies concerning the content of list traffic.\n" "\n" "

Content filtering works like this: when a message is\n" " received by the list and you have enabled content filtering, " "the\n" " individual attachments are first compared to the\n" " filter\n" " types. If the attachment type matches an entry in the " "filter\n" " types, it is discarded.\n" "\n" "

Then, if there are pass types\n" " defined, any attachment type that does not match a\n" " pass type is also discarded. If there are no pass types " "defined,\n" " this check is skipped.\n" "\n" "

After this initial filtering, any multipart\n" " attachments that are empty are removed. If the outer message " "is\n" " left empty after this filtering, then the whole message is\n" " discarded.\n" "\n" "

Then, each multipart/alternative section will\n" " be replaced by just the first alternative that is non-empty " "after\n" " filtering if\n" " collapse_alternatives is enabled.\n" "\n" "

Finally, any text/html parts that are left in the\n" " message may be converted to text/plain if\n" " convert_html_to_plaintext is enabled and the site is\n" " configured to allow these conversions." msgstr "" #: Mailman/Gui/ContentFilter.py:130 msgid "" "One of these actions is taken when the message matches one of\n" " the content filtering rules, meaning, the top-level\n" " content type matches one of the filter_mime_types, or the top-level content type does\n" " not match one of the\n" " pass_mime_types, or if after filtering the subparts of " "the\n" " message, the message ends up empty.\n" "\n" "

Note this action is not taken if after filtering the " "message\n" " still contains content. In that case the message is always\n" " forwarded on to the list membership.\n" "\n" "

When messages are discarded, a log entry is written\n" " containing the Message-ID of the discarded message. When\n" " messages are rejected or forwarded to the list owner, a reason\n" " for the rejection is included in the bounce message to the\n" " original author. When messages are preserved, they are saved " "in\n" " a special queue directory on disk for the site administrator " "to\n" " view (and possibly rescue) but otherwise discarded. This last\n" " option is only available if enabled by the site\n" " administrator." msgstr "" #: Mailman/Gui/General.py:81 msgid "" "There are two ownership roles associated with each mailing\n" " list. The list administrators are the people who " "have\n" " ultimate control over all parameters of this mailing list. " "They\n" " are able to change any list configuration variable available\n" " through these administration web pages.\n" "\n" "

The list moderators have more limited permissions;\n" " they are not able to change any list configuration variable, " "but\n" " they are allowed to tend to pending administration requests,\n" " including approving or rejecting held subscription requests, " "and\n" " disposing of held postings. Of course, the list\n" " administrators can also tend to pending requests.\n" "\n" "

In order to split the list ownership duties into\n" " administrators and moderators, you must\n" " set a separate moderator password,\n" " and also provide the email\n" " addresses of the list moderators. Note that the field you\n" " are changing here specifies the list administrators." msgstr "" #: Mailman/Gui/General.py:105 msgid "" "There are two ownership roles associated with each mailing\n" " list. The list administrators are the people who " "have\n" " ultimate control over all parameters of this mailing list. " "They\n" " are able to change any list configuration variable available\n" " through these administration web pages.\n" "\n" "

The list moderators have more limited permissions;\n" " they are not able to change any list configuration variable, " "but\n" " they are allowed to tend to pending administration requests,\n" " including approving or rejecting held subscription requests, " "and\n" " disposing of held postings. Of course, the list\n" " administrators can also tend to pending requests.\n" "\n" "

In order to split the list ownership duties into\n" " administrators and moderators, you must\n" " set a separate moderator password,\n" " and also provide the email addresses of the list moderators in\n" " this section. Note that the field you are changing here\n" " specifies the list moderators." msgstr "" #: Mailman/Gui/General.py:176 msgid "" "This option controls what Mailman does to the\n" " Reply-To: header in messages flowing through this\n" " mailing list. When set to Poster, no Reply-To:\n" " header is added by Mailman, although if one is present in the\n" " original message, it is not stripped. Setting this value to\n" " either This list or Explicit address causes\n" " Mailman to insert a specific Reply-To: header in all\n" " messages, overriding the header in the original message if\n" " necessary (Explicit address inserts the value of reply_to_address).\n" "\n" "

There are many reasons not to introduce or override the\n" " Reply-To: header. One is that some posters depend on\n" " their own Reply-To: settings to convey their valid\n" " return address. Another is that modifying Reply-To:\n" " makes it much more difficult to send private replies. See `Reply-" "To'\n" " Munging Considered Harmful for a general discussion of " "this\n" " issue. See Reply-" "To\n" " Munging Considered Useful for a dissenting opinion.\n" "\n" "

Some mailing lists have restricted posting privileges, with " "a\n" " parallel list devoted to discussions. Examples are `patches' " "or\n" " `checkin' lists, where software changes are posted by a " "revision\n" " control system, but discussion about the changes occurs on a\n" " developers mailing list. To support these types of mailing\n" " lists, select Explicit address and set the\n" " Reply-To: address below to point to the parallel\n" " list." msgstr "" #: Mailman/Gui/General.py:210 msgid "" "This is the address set in the Reply-To: header\n" " when the reply_goes_to_list\n" " option is set to Explicit address.\n" "\n" "

There are many reasons not to introduce or override the\n" " Reply-To: header. One is that some posters depend on\n" " their own Reply-To: settings to convey their valid\n" " return address. Another is that modifying Reply-To:\n" " makes it much more difficult to send private replies. See `Reply-" "To'\n" " Munging Considered Harmful for a general discussion of " "this\n" " issue. See Reply-" "To\n" " Munging Considered Useful for a dissenting opinion.\n" "\n" "

Some mailing lists have restricted posting privileges, with " "a\n" " parallel list devoted to discussions. Examples are `patches' " "or\n" " `checkin' lists, where software changes are posted by a " "revision\n" " control system, but discussion about the changes occurs on a\n" " developers mailing list. To support these types of mailing\n" " lists, specify the explicit Reply-To: address here. " "You\n" " must also specify Explicit address in the\n" " reply_goes_to_list\n" " variable.\n" "\n" "

Note that if the original message contains a\n" " Reply-To: header, it will not be changed." msgstr "" #: Mailman/Gui/Language.py:95 msgid "" "If your mailing list's default language uses a non-ASCII\n" " character set and the prefix contains non-ASCII characters, " "the\n" " prefix will always be encoded according to the relevant\n" " standards. However, if your prefix contains only ASCII\n" " characters, you may want to set this option to Never " "to\n" " disable prefix encoding. This can make the subject headers\n" " slightly more readable for users with mail readers that don't\n" " properly handle non-ASCII encodings.\n" "\n" "

Note however, that if your mailing list receives both " "encoded\n" " and unencoded subject headers, you might want to choose As\n" " needed. Using this setting, Mailman will not encode " "ASCII\n" " prefixes when the rest of the header contains only ASCII\n" " characters, but if the original header contains non-ASCII\n" " characters, it will encode the prefix. This avoids an " "ambiguity\n" " in the standards which could cause some mail readers to " "display\n" " extra, or missing spaces between the prefix and the original\n" " header." msgstr "" #: Mailman/Gui/NonDigest.py:61 msgid "" "Normally, Mailman sends the regular delivery messages to\n" " the mail server in batches. This is much more efficent\n" " because it reduces the amount of traffic between Mailman " "and\n" " the mail server.\n" "\n" "

However, some lists can benefit from a more " "personalized\n" " approach. In this case, Mailman crafts a new message for\n" " each member on the regular delivery list. Turning this\n" " feature on may degrade the performance of your site, so " "you\n" " need to carefully consider whether the trade-off is worth " "it,\n" " or whether there are other ways to accomplish what you " "want.\n" " You should also carefully monitor your system load to make\n" " sure it is acceptable.\n" "\n" "

Select No to disable personalization and send\n" " messages to the members in batches. Select Yes " "to\n" " personalize deliveries and allow additional substitution\n" " variables in message headers and footers (see below). In\n" " addition, by selecting Full Personalization, the\n" " To header of posted messages will be modified " "to\n" " include the member's address instead of the list's posting\n" " address.\n" "\n" "

When personalization is enabled, a few more expansion\n" " variables can be included in the message header " "and\n" " message footer.\n" "\n" "

These additional substitution variables will be " "available\n" " for your headers and footers, when this feature is " "enabled:\n" "\n" "

\n" " " msgstr "" #: Mailman/Gui/Privacy.py:162 msgid "" "When a message is posted to the list, a series of\n" " moderation steps are taken to decide whether a moderator must\n" " first approve the message or not. This section contains the\n" " controls for moderation of both member and non-member postings.\n" "\n" "

Member postings are held for moderation if their\n" " moderation flag is turned on. You can control whether\n" " member postings are moderated by default or not.\n" "\n" "

Non-member postings can be automatically\n" " accepted,\n" " held " "for\n" " moderation,\n" " rejected (bounced), or\n" " discarded,\n" " either individually or as a group. Any\n" " posting from a non-member who is not explicitly accepted,\n" " rejected, or discarded, will have their posting filtered by the\n" " general\n" " non-member rules.\n" "\n" "

In the text boxes below, add one address per line; start the\n" " line with a ^ character to designate a Python regular expression. When entering backslashes, do " "so\n" " as if you were using Python raw strings (i.e. you generally " "just\n" " use a single backslash).\n" "\n" "

Note that non-regexp matches are always done first." msgstr "" #: Mailman/Gui/Topics.py:49 msgid "" "The topic filter categorizes each incoming email message\n" " according to regular\n" " expression filters you specify below. If the message's\n" " Subject: or Keywords: header contains " "a\n" " match against a topic filter, the message is logically placed\n" " into a topic bucket. Each user can then choose to " "only\n" " receive messages from the mailing list for a particular topic\n" " bucket (or buckets). Any message not categorized in a topic\n" " bucket registered with the user is not delivered to the list.\n" "\n" "

Note that this feature only works with regular delivery, " "not\n" " digest delivery.\n" "\n" "

The body of the message can also be optionally scanned for\n" " Subject: and Keywords: headers, as\n" " specified by the topics_bodylines_limit\n" " configuration variable." msgstr "" #: Mailman/Gui/Usenet.py:68 msgid "" "This setting determines the moderation policy of the\n" " newsgroup and its interaction with the moderation policy of " "the\n" " mailing list. This only applies to the newsgroup that you are\n" " gatewaying to, so if you are only gatewaying from\n" " Usenet, or the newsgroup you are gatewaying to is not " "moderated,\n" " set this option to None.\n" "\n" "

If the newsgroup is moderated, you can set this mailing " "list\n" " up to be the moderation address for the newsgroup. By " "selecting\n" " Moderated, an additional posting hold will be placed " "in\n" " the approval process. All messages posted to the mailing list\n" " will have to be approved before being sent on to the " "newsgroup,\n" " or to the mailing list membership.\n" "\n" "

Note that if the message has an Approved " "header\n" " with the list's administrative password in it, this hold test\n" " will be bypassed, allowing privileged posters to send messages\n" " directly to the list and the newsgroup.\n" "\n" "

Finally, if the newsgroup is moderated, but you want to " "have\n" " an open posting policy anyway, you should select Open " "list,\n" " moderated group. The effect of this is to use the normal\n" " Mailman moderation facilities, but to add an Approved\n" " header to all messages that are gatewayed to Usenet." msgstr "" #: bin/add_members:26 msgid "" "Add members to a list from the command line.\n" "\n" "Usage:\n" " add_members [options] listname\n" "\n" "Options:\n" "\n" " --regular-members-file=file\n" " -r file\n" " A file containing addresses of the members to be added, one\n" " address per line. This list of people become non-digest\n" " members. If file is `-', read addresses from stdin. Note that\n" " -n/--non-digest-members-file are deprecated synonyms for this " "option.\n" "\n" " --digest-members-file=file\n" " -d file\n" " Similar to above, but these people become digest members.\n" "\n" " --welcome-msg=\n" " -w \n" " Set whether or not to send the list members a welcome message,\n" " overriding whatever the list's `send_welcome_msg' setting is.\n" "\n" " --admin-notify=\n" " -a \n" " Set whether or not to send the list administrators a notification " "on\n" " the success/failure of these subscriptions, overriding whatever the\n" " list's `admin_notify_mchanges' setting is.\n" "\n" " --help\n" " -h\n" " Print this help message and exit.\n" "\n" " listname\n" " The name of the Mailman list you are adding members to. It must\n" " already exist.\n" "\n" "You must supply at least one of -r and -d options. At most one of the\n" "files can be `-'.\n" msgstr "" #: bin/arch:19 msgid "" "Rebuild a list's archive.\n" "\n" "Use this command to rebuild the archives for a mailing list. You may want " "to\n" "do this if you edit some messages in an archive, or remove some messages " "from\n" "an archive.\n" "\n" "Usage: %(PROGRAM)s [options] []\n" "\n" "Where options are:\n" " -h / --help\n" " Print this help message and exit.\n" "\n" " -q / --quiet\n" " Make the archiver output less verbose.\n" "\n" " --wipe\n" " First wipe out the original archive before regenerating. You " "usually\n" " want to specify this argument unless you're generating the archive " "in\n" " chunks.\n" "\n" " -s N\n" " --start=N\n" " Start indexing at article N, where article 0 is the first in the " "mbox.\n" " Defaults to 0.\n" "\n" " -e M\n" " --end=M\n" " End indexing at article M. This script is not very efficient with\n" " respect to memory management, and for large archives, it may not be\n" " possible to index the mbox entirely. For that reason, you can " "specify\n" " the start and end article numbers.\n" "\n" "Where is the path to a list's complete mbox archive. Usually this " "will\n" "be some path in the archives/private directory. For example:\n" "\n" "%% bin/arch mylist archives/private/mylist.mbox/mylist.mbox\n" "\n" " is optional. If it is missing, it is calculated.\n" msgstr "" #: bin/change_pw:20 msgid "" "Change a list's password.\n" "\n" "Prior to Mailman 2.1, list passwords were kept in crypt'd format -- " "usually.\n" "Some Python installations didn't have the crypt module available, so they'd\n" "fall back to md5. Then suddenly the Python installation might grow a crypt\n" "module and all list passwords would be broken.\n" "\n" "In Mailman 2.1, all list and site passwords are stored in SHA1 hexdigest\n" "form. This breaks list passwords for all existing pre-Mailman 2.1 lists, " "and\n" "since those passwords aren't stored anywhere in plain text, they cannot be\n" "retrieved and updated.\n" "\n" "Thus, this script generates new passwords for a list, and optionally sends " "it\n" "to all the owners of the list.\n" "\n" "Usage: change_pw [options]\n" "\n" "Options:\n" "\n" " --all / -a\n" " Change the password for all lists.\n" "\n" " --domain=domain\n" " -d domain\n" " Change the password for all lists in the virtual domain `domain'. " "It\n" " is okay to give multiple -d options.\n" "\n" " --listname=listname\n" " -l listname\n" " Change the password only for the named list. It is okay to give\n" " multiple -l options.\n" "\n" " --password=newpassword\n" " -p newpassword\n" " Use the supplied plain text password `newpassword' as the new " "password\n" " for any lists that are being changed (as specified by the -a, -d, " "and\n" " -l options). If not given, lists will be assigned a randomly\n" " generated new password.\n" "\n" " --quiet / -q\n" " Don't notify list owners of the new password. You'll have to have\n" " some other way of letting the list owners know the new password\n" " (presumably out-of-band).\n" "\n" " --help / -h\n" " Print this help message and exit.\n" msgstr "" #: bin/cleanarch:20 msgid "" "Clean up an .mbox archive file.\n" "\n" "The archiver looks for Unix-From lines separating messages in an mbox " "archive\n" "file. For compatibility, it specifically looks for lines that start with\n" "\"From \" -- i.e. the letters capital-F, lowercase-r, o, m, space, ignoring\n" "everything else on the line.\n" "\n" "Normally, any lines that start \"From \" in the body of a message should be\n" "escaped such that a > character is actually the first on a line. It is\n" "possible though that body lines are not actually escaped. This script\n" "attempts to fix these by doing a stricter test of the Unix-From lines. Any\n" "lines that start \"From \" but do not pass this stricter test are escaped " "with a\n" "> character.\n" "\n" "Usage: cleanarch [options] < inputfile > outputfile\n" "Options:\n" " -s n\n" " --status=n\n" " Print a # character every n lines processed\n" "\n" " -q / --quiet\n" " Don't print changed line information to standard error.\n" "\n" " -n / --dry-run\n" " Don't actually output anything.\n" "\n" " -h / --help\n" " Print this message and exit\n" msgstr "" #: bin/clone_member:19 msgid "" "Clone a member address.\n" "\n" "Cloning a member address means that a new member will be added who has all " "the\n" "same options and passwords as the original member address. Note that this\n" "operation is fairly trusting of the user who runs it -- it does no\n" "verification to the new address, it does not send out a welcome message, " "etc.\n" "\n" "The existing member's subscription is usually not modified in any way. If " "you\n" "want to remove the old address, use the -r flag. If you also want to " "change\n" "any list admin addresses, use the -a flag.\n" "\n" "Usage:\n" " clone_member [options] fromoldaddr tonewaddr\n" "\n" "Where:\n" "\n" " --listname=listname\n" " -l listname\n" " Check and modify only the named mailing lists. If -l is not given,\n" " then all mailing lists are scanned from the address. Multiple -l\n" " options can be supplied.\n" "\n" " --remove\n" " -r\n" " Remove the old address from the mailing list after it's been " "cloned.\n" "\n" " --admin\n" " -a\n" " Scan the list admin addresses for the old address, and clone or " "change\n" " them too.\n" "\n" " --quiet\n" " -q\n" " Do the modifications quietly.\n" "\n" " --nomodify\n" " -n\n" " Print what would be done, but don't actually do it. Inhibits the\n" " --quiet flag.\n" "\n" " --help\n" " -h\n" " Print this help message and exit.\n" "\n" " fromoldaddr (`from old address') is the old address of the user. " "tonewaddr\n" " (`to new address') is the new address of the user.\n" "\n" msgstr "" #: bin/config_list:20 msgid "" "Configure a list from a text file description.\n" "\n" "Usage: config_list [options] listname\n" "\n" "Options:\n" " --inputfile filename\n" " -i filename\n" " Configure the list by assigning each module-global variable in the\n" " file to an attribute on the list object, then saving the list. The\n" " named file is loaded with execfile() and must be legal Python code.\n" " Any variable that isn't already an attribute of the list object is\n" " ignored (a warning message is printed). See also the -c option.\n" "\n" " A special variable named `mlist' is put into the globals during the\n" " execfile, which is bound to the actual MailList object. This lets " "you\n" " do all manner of bizarre thing to the list object, but BEWARE! " "Using\n" " this can severely (and possibly irreparably) damage your mailing " "list!\n" "\n" " --outputfile filename\n" " -o filename\n" " Instead of configuring the list, print out a list's configuration\n" " variables in a format suitable for input using this script. In " "this\n" " way, you can easily capture the configuration settings for a\n" " particular list and imprint those settings on another list. " "filename\n" " is the file to output the settings to. If filename is `-', " "standard\n" " out is used.\n" "\n" " --checkonly\n" " -c\n" " With this option, the modified list is not actually changed. Only\n" " useful with -i.\n" "\n" " --verbose\n" " -v\n" " Print the name of each attribute as it is being changed. Only " "useful\n" " with -i.\n" "\n" " --help\n" " -h\n" " Print this help message and exit.\n" "\n" "The options -o and -i are mutually exclusive.\n" "\n" msgstr "" #: bin/dumpdb:19 msgid "" "Dump the contents of any Mailman `database' file.\n" "\n" "Usage: %(PROGRAM)s [options] filename\n" "\n" "Options:\n" "\n" " --marshal/-m\n" " Assume the file contains a Python marshal, overridding any " "automatic\n" " guessing.\n" "\n" " --pickle/-p\n" " Assume the file contains a Python pickle, overridding any automatic\n" " guessing.\n" "\n" " --noprint/-n\n" " Don't attempt to pretty print the object. This is useful if " "there's\n" " some problem with the object and you just want to get an unpickled\n" " representation. Useful with `python -i bin/dumpdb '. In " "that\n" " case, the root of the tree will be left in a global called \"msg\".\n" "\n" " --help/-h\n" " Print this help message and exit\n" "\n" "If the filename ends with `.db', then it is assumed that the file contains " "a\n" "Python marshal. If the file ends with `.pck' then it is assumed to contain " "a\n" "Python pickle. In either case, if you want to override the default " "assumption\n" "-- or if the file ends in neither suffix -- use the -p or -m flags.\n" msgstr "" "Извеждане на съдържанието на файл с база от данни на mailman.\n" "\n" "Употреба: %(PROGRAM)s [options] име_на_файл\n" "\n" "Опции:\n" "\n" " --marshal/-m\n" " Приемане, че файлът съдържа marshal на Python - да не се ползва\n" " автоматично разпознаване.\n" "\n" " --pickle/-p\n" " Приемане, че файлът съдържа pickle на Python - да не се ползва\n" " автоматично разпознаване.\n" "\n" " --noprint/-n\n" " Да не се предприема опит за отпечатване на обекта. Това е много\n" " полезно, ако има проблем с обекта и ви прябва несериализирано\n" " представяне. Полезно е с „python -i bin/dumpdb <файл>“. В този\n" " случай коренът на дървото ще бъде поставен в глобален обект на\n" " име „msg“.\n" "\n" " --help/-h\n" " Отпечатване на това съобщение и изход.\n" "\n" "Ако името на файла завършва с „.db“, приема се, че съдържа marshall на " "Python.\n" "Ако името на файла завършва с „.pck“, приема се, че съдържа pickle на " "Python.\n" "И в двата случая, ако искате да предотвратите автоматичното разпознаване на " "вида\n" "на файла, или ако разширението на файла е различно от горните - използвайте " "един\n" "от флаговете -p или -m.\n" #: bin/list_members:19 msgid "" "List all the members of a mailing list.\n" "\n" "Usage: %(PROGRAM)s [options] listname\n" "\n" "Where:\n" "\n" " --output file\n" " -o file\n" " Write output to specified file instead of standard out.\n" "\n" " --regular / -r\n" " Print just the regular (non-digest) members.\n" "\n" " --digest[=kind] / -d [kind]\n" " Print just the digest members. Optional argument can be \"mime\" " "or\n" " \"plain\" which prints just the digest members receiving that kind " "of\n" " digest.\n" "\n" " --nomail[=why] / -n [why]\n" " Print the members that have delivery disabled. Optional argument " "can\n" " be \"byadmin\", \"byuser\", \"bybounce\", or \"unknown\" which " "prints just the\n" " users who have delivery disabled for that reason. It can also be\n" " \"enabled\" which prints just those member for whom delivery is\n" " enabled.\n" "\n" " --fullnames / -f\n" " Include the full names in the output.\n" "\n" " --preserve / -p\n" " Output member addresses case preserved the way they were added to " "the\n" " list. Otherwise, addresses are printed in all lowercase.\n" "\n" " --invalid / -i\n" " Print only the addresses in the membership list that are invalid.\n" " Ignores -r, -d, -n.\n" "\n" " --unicode / -u\n" " Print addresses which are stored as Unicode objects instead of " "normal\n" " string objects. Ignores -r, -d, -n.\n" "\n" " --help\n" " -h\n" " Print this help message and exit.\n" "\n" " listname is the name of the mailing list to use.\n" "\n" "Note that if neither -r or -d is supplied, both regular members are printed\n" "first, followed by digest members, but no indication is given as to address\n" "status.\n" msgstr "" #: bin/mailmanctl:20 msgid "" "Primary start-up and shutdown script for Mailman's qrunner daemon.\n" "\n" "This script starts, stops, and restarts the main Mailman queue runners, " "making\n" "sure that the various long-running qrunners are still alive and kicking. " "It\n" "does this by forking and exec'ing the qrunners and waiting on their pids.\n" "When it detects a subprocess has exited, it may restart it.\n" "\n" "The qrunners respond to SIGINT, SIGTERM, and SIGHUP. SIGINT and SIGTERM " "both\n" "cause the qrunners to exit cleanly, but the master will only restart " "qrunners\n" "that have exited due to a SIGINT. SIGHUP causes the master and the " "qrunners\n" "to close their log files, and reopen then upon the next printed message.\n" "\n" "The master also responds to SIGINT, SIGTERM, and SIGHUP, which it simply\n" "passes on to the qrunners (note that the master will close and reopen its " "own\n" "log files on receipt of a SIGHUP). The master also leaves its own process " "id\n" "in the file data/master-qrunner.pid but you normally don't need to use this\n" "pid directly. The `start', `stop', `restart', and `reopen' commands handle\n" "everything for you.\n" "\n" "Usage: %(PROGRAM)s [options] [ start | stop | restart | reopen ]\n" "\n" "Options:\n" "\n" " -n/--no-restart\n" " Don't restart the qrunners when they exit because of an error or a\n" " SIGINT. They are never restarted if they exit in response to a\n" " SIGTERM. Use this only for debugging. Only useful if the `start'\n" " command is given.\n" "\n" " -u/--run-as-user\n" " Normally, this script will refuse to run if the user id and group " "id\n" " are not set to the `mailman' user and group (as defined when you\n" " configured Mailman). If run as root, this script will change to " "this\n" " user and group before the check is made.\n" "\n" " This can be inconvenient for testing and debugging purposes, so the -" "u\n" " flag means that the step that sets and checks the uid/gid is " "skipped,\n" " and the program is run as the current user and group. This flag is\n" " not recommended for normal production environments.\n" "\n" " Note though, that if you run with -u and are not in the mailman " "group,\n" " you may have permission problems, such as begin unable to delete a\n" " list's archives through the web. Tough luck!\n" "\n" " -s/--stale-lock-cleanup\n" " If mailmanctl finds an existing master lock, it will normally exit\n" " with an error message. With this option, mailmanctl will perform " "an\n" " extra level of checking. If a process matching the host/pid " "described\n" " in the lock file is running, mailmanctl will still exit, but if no\n" " matching process is found, mailmanctl will remove the apparently " "stale\n" " lock and make another attempt to claim the master lock.\n" "\n" " -q/--quiet\n" " Don't print status messages. Error messages are still printed to\n" " standard error.\n" "\n" " -h/--help\n" " Print this message and exit.\n" "\n" "Commands:\n" "\n" " start - Start the master daemon and all qrunners. Prints a message " "and\n" " exits if the master daemon is already running.\n" "\n" " stop - Stops the master daemon and all qrunners. After stopping, no\n" " more messages will be processed.\n" "\n" " restart - Restarts the qrunners, but not the master process. Use this\n" " whenever you upgrade or update Mailman so that the qrunners " "will\n" " use the newly installed code.\n" "\n" " reopen - This will close all log files, causing them to be re-opened " "the\n" " next time a message is written to them\n" msgstr "" #: bin/newlist:20 msgid "" "Create a new, unpopulated mailing list.\n" "\n" "Usage: %(PROGRAM)s [options] [listname [listadmin-addr [admin-password]]]\n" "\n" "Options:\n" "\n" " -l language\n" " --language=language\n" " Make the list's preferred language `language', which must be a two\n" " letter language code.\n" "\n" " -u urlhost\n" " --urlhost=urlhost\n" " Gives the list's web interface host name.\n" "\n" " -e emailhost\n" " --emailhost=emailhost\n" " Gives the list's email domain name.\n" "\n" " -q/--quiet\n" " Normally the administrator is notified by email (after a prompt) " "that\n" " their list has been created. This option suppresses the prompt and\n" " notification.\n" "\n" " -h/--help\n" " Print this help text and exit.\n" "\n" "You can specify as many of the arguments as you want on the command line:\n" "you will be prompted for the missing ones.\n" "\n" "Every Mailman list has two parameters which define the default host name " "for\n" "outgoing email, and the default URL for all web interfaces. When you\n" "configured Mailman, certain defaults were calculated, but if you are " "running\n" "multiple virtual Mailman sites, then the defaults may not be appropriate " "for\n" "the list you are creating.\n" "\n" "You also specify the domain to create your new list in by typing the " "command\n" "like so:\n" "\n" " newlist --urlhost=www.mydom.ain mylist\n" "\n" "where `www.mydom.ain' should be the base hostname for the URL to this " "virtual\n" "hosts's lists. E.g. with this setting people will view the general list\n" "overviews at http://www.mydom.ain/mailman/listinfo. Also, www.mydom.ain\n" "should be a key in the VIRTUAL_HOSTS mapping in mm_cfg.py/Defaults.py if\n" "the email hostname to be automatically determined.\n" "\n" "If you want the email hostname to be different from the one looked up by " "the\n" "VIRTUAL_HOSTS or if urlhost is not registered in VIRTUAL_HOSTS, you can " "specify\n" "`emailhost' like so:\n" "\n" " newlist --urlhost=www.mydom.ain --emailhost=mydom.ain mylist\n" "\n" "where `mydom.ain' is the mail domain name. If you don't specify emailhost " "but\n" "urlhost is not in the virtual host list, then mm_cfg.DEFAULT_EMAIL_HOST " "will\n" "be used for the email interface.\n" "\n" "For backward compatibility, you can also specify the domain to create your\n" "new list in by spelling the listname like so:\n" "\n" " mylist@www.mydom.ain\n" "\n" "where www.mydom.ain is used for `urlhost' but it will also be used for\n" "`emailhost' if it is not found in the virtual host table. Note that\n" "'--urlhost' and '--emailhost' have precedence to this notation.\n" "\n" "If you spell the list name as just `mylist', then the email hostname will " "be\n" "taken from DEFAULT_EMAIL_HOST and the url will be taken from DEFAULT_URL " "(as\n" "defined in your Defaults.py file or overridden by settings in mm_cfg.py).\n" "\n" "Note that listnames are forced to lowercase.\n" msgstr "" #: bin/qrunner:20 msgid "" "Run one or more qrunners, once or repeatedly.\n" "\n" "Each named runner class is run in round-robin fashion. In other words, the\n" "first named runner is run to consume all the files currently in its\n" "directory. When that qrunner is done, the next one is run to consume all " "the\n" "files in /its/ directory, and so on. The number of total iterations can be\n" "given on the command line.\n" "\n" "Usage: %(PROGRAM)s [options]\n" "\n" "Options:\n" "\n" " -r runner[:slice:range]\n" " --runner=runner[:slice:range]\n" " Run the named qrunner, which must be one of the strings returned by\n" " the -l option. Optional slice:range if given, is used to assign\n" " multiple qrunner processes to a queue. range is the total number " "of\n" " qrunners for this queue while slice is the number of this qrunner " "from\n" " [0..range).\n" "\n" " If using the slice:range form, you better make sure that each " "qrunner\n" " for the queue is given the same range value. If slice:runner is " "not\n" " given, then 1:1 is used.\n" "\n" " Multiple -r options may be given, in which case each qrunner will " "run\n" " once in round-robin fashion. The special runner `All' is shorthand\n" " for a qrunner for each listed by the -l option.\n" "\n" " --once\n" " -o\n" " Run each named qrunner exactly once through its main loop. " "Otherwise,\n" " each qrunner runs indefinitely, until the process receives a " "SIGTERM\n" " or SIGINT.\n" "\n" " -l/--list\n" " Shows the available qrunner names and exit.\n" "\n" " -v/--verbose\n" " Spit out more debugging information to the logs/qrunner log file.\n" "\n" " -s/--subproc\n" " This should only be used when running qrunner as a subprocess of " "the\n" " mailmanctl startup script. It changes some of the exit-on-error\n" " behavior to work better with that framework.\n" "\n" " -h/--help\n" " Print this message and exit.\n" "\n" "runner is required unless -l or -h is given, and it must be one of the " "names\n" "displayed by the -l switch.\n" "\n" "Note also that this script should be started up from mailmanctl as a normal\n" "operation. It is only useful for debugging if it is run separately.\n" msgstr "" #: bin/remove_members:20 msgid "" "Remove members from a list.\n" "\n" "Usage:\n" " remove_members [options] [listname] [addr1 ...]\n" "\n" "Options:\n" "\n" " --file=file\n" " -f file\n" " Remove member addresses found in the given file. If file is\n" " `-', read stdin.\n" "\n" " --all\n" " -a\n" " Remove all members of the mailing list.\n" " (mutually exclusive with --fromall)\n" "\n" " --fromall\n" " Removes the given addresses from all the lists on this system\n" " regardless of virtual domains if you have any. This option cannot " "be\n" " used -a/--all. Also, you should not specify a listname when using\n" " this option.\n" "\n" " --nouserack\n" " -n\n" " Don't send the user acknowledgements. If not specified, the list\n" " default value is used.\n" "\n" " --noadminack\n" " -N\n" " Don't send the admin acknowledgements. If not specified, the list\n" " default value is used.\n" "\n" " --help\n" " -h\n" " Print this help message and exit.\n" "\n" " listname is the name of the mailing list to use.\n" "\n" " addr1 ... are additional addresses to remove.\n" msgstr "" #: bin/sync_members:19 msgid "" "Synchronize a mailing list's membership with a flat file.\n" "\n" "This script is useful if you have a Mailman mailing list and a sendmail\n" ":include: style list of addresses (also as is used in Majordomo). For " "every\n" "address in the file that does not appear in the mailing list, the address " "is\n" "added. For every address in the mailing list that does not appear in the\n" "file, the address is removed. Other options control what happens when an\n" "address is added or removed.\n" "\n" "Usage: %(PROGRAM)s [options] -f file listname\n" "\n" "Where `options' are:\n" "\n" " --no-change\n" " -n\n" " Don't actually make the changes. Instead, print out what would be\n" " done to the list.\n" "\n" " --welcome-msg[=]\n" " -w[=]\n" " Sets whether or not to send the newly added members a welcome\n" " message, overriding whatever the list's `send_welcome_msg' setting\n" " is. With -w=yes or -w, the welcome message is sent. With -w=no, " "no\n" " message is sent.\n" "\n" " --goodbye-msg[=]\n" " -g[=]\n" " Sets whether or not to send the goodbye message to removed members,\n" " overriding whatever the list's `send_goodbye_msg' setting is. With\n" " -g=yes or -g, the goodbye message is sent. With -g=no, no message " "is\n" " sent.\n" "\n" " --digest[=]\n" " -d[=]\n" " Selects whether to make newly added members receive messages in\n" " digests. With -d=yes or -d, they become digest members. With -" "d=no\n" " (or if no -d option given) they are added as regular members.\n" "\n" " --notifyadmin[=]\n" " -a[=]\n" " Specifies whether the admin should be notified for each " "subscription\n" " or unsubscription. If you're adding a lot of addresses, you\n" " definitely want to turn this off! With -a=yes or -a, the admin is\n" " notified. With -a=no, the admin is not notified. With no -a " "option,\n" " the default for the list is used.\n" "\n" " --file \n" " -f \n" " This option is required. It specifies the flat file to synchronize\n" " against. Email addresses must appear one per line. If filename is\n" " `-' then stdin is used.\n" "\n" " --help\n" " -h\n" " Print this message.\n" "\n" " listname\n" " Required. This specifies the list to synchronize.\n" msgstr "" #: bin/withlist:20 msgid "" "General framework for interacting with a mailing list object.\n" "\n" "There are two ways to use this script: interactively or programmatically.\n" "Using it interactively allows you to play with, examine and modify a " "MailList\n" "object from Python's interactive interpreter. When running interactively, " "a\n" "MailList object called `m' will be available in the global namespace. It " "also\n" "loads the class MailList into the global namespace.\n" "\n" "Programmatically, you can write a function to operate on a MailList object,\n" "and this script will take care of the housekeeping (see below for " "examples).\n" "In that case, the general usage syntax is:\n" "\n" "%% bin/withlist [options] listname [args ...]\n" "\n" "Options:\n" "\n" " -l / --lock\n" " Lock the list when opening. Normally the list is opened unlocked\n" " (e.g. for read-only operations). You can always lock the file " "after\n" " the fact by typing `m.Lock()'\n" "\n" " Note that if you use this option, you should explicitly call m.Save" "()\n" " before exiting, since the interpreter's clean up procedure will not\n" " automatically save changes to the MailList object (but it will " "unlock\n" " the list).\n" "\n" " -i / --interactive\n" " Leaves you at an interactive prompt after all other processing is\n" " complete. This is the default unless the -r option is given.\n" "\n" " --run [module.]callable\n" " -r [module.]callable\n" " This can be used to run a script with the opened MailList object.\n" " This works by attempting to import `module' (which must be in the\n" " directory containing withlist, or already be accessible on your\n" " sys.path), and then calling `callable' from the module. callable " "can\n" " be a class or function; it is called with the MailList object as " "the\n" " first argument. If additional args are given on the command line,\n" " they are passed as subsequent positional args to the callable.\n" "\n" " Note that `module.' is optional; if it is omitted then a module " "with\n" " the name `callable' will be imported.\n" "\n" " The global variable `r' will be set to the results of this call.\n" "\n" " --all / -a\n" " This option only works with the -r option. Use this if you want to\n" " execute the script on all mailing lists. When you use -a you " "should\n" " not include a listname argument on the command line. The variable " "`r'\n" " will be a list of all the results.\n" "\n" " --quiet / -q\n" " Suppress all status messages.\n" "\n" " --help / -h\n" " Print this message and exit\n" "\n" "\n" "Here's an example of how to use the -r option. Say you have a file in the\n" "Mailman installation directory called `listaddr.py', with the following\n" "two functions:\n" "\n" "def listaddr(mlist):\n" " print mlist.GetListEmail()\n" "\n" "def requestaddr(mlist):\n" " print mlist.GetRequestEmail()\n" "\n" "Now, from the command line you can print the list's posting address by " "running\n" "the following from the command line:\n" "\n" "%% bin/withlist -r listaddr mylist\n" "Loading list: mylist (unlocked)\n" "Importing listaddr ...\n" "Running listaddr.listaddr() ...\n" "mylist@myhost.com\n" "\n" "And you can print the list's request address by running:\n" "\n" "%% bin/withlist -r listaddr.requestaddr mylist\n" "Loading list: mylist (unlocked)\n" "Importing listaddr ...\n" "Running listaddr.requestaddr() ...\n" "mylist-request@myhost.com\n" "\n" "As another example, say you wanted to change the password for a particular\n" "user on a particular list. You could put the following function in a file\n" "called `changepw.py':\n" "\n" "from Mailman.Errors import NotAMemberError\n" "\n" "def changepw(mlist, addr, newpasswd):\n" " try:\n" " mlist.setMemberPassword(addr, newpasswd)\n" " mlist.Save()\n" " except NotAMemberError:\n" " print 'No address matched:', addr\n" "\n" "and run this from the command line:\n" " %% bin/withlist -l -r changepw mylist somebody@somewhere.org foobar\n" msgstr "" #: cron/disabled:20 msgid "" "Process disabled members, recommended once per day.\n" "\n" "This script cruises through every mailing list looking for members whose\n" "delivery is disabled. If they have been disabled due to bounces, they will\n" "receive another notification, or they may be removed if they've received " "the\n" "maximum number of notifications.\n" "\n" "Use the --byadmin, --byuser, and --unknown flags to also send notifications " "to\n" "members whose accounts have been disabled for those reasons. Use --all to\n" "send the notification to all disabled members.\n" "\n" "Usage: %(PROGRAM)s [options]\n" "\n" "Options:\n" " -h / --help\n" " Print this message and exit.\n" "\n" " -o / --byadmin\n" " Also send notifications to any member disabled by the list\n" " owner/administrator.\n" "\n" " -m / --byuser\n" " Also send notifications to any member disabled by themselves.\n" "\n" " -u / --unknown\n" " Also send notifications to any member disabled for unknown reasons\n" " (usually a legacy disabled address).\n" "\n" " -b / --notbybounce\n" " Don't send notifications to members disabled because of bounces " "(the\n" " default is to notify bounce disabled members).\n" "\n" " -a / --all\n" " Send notifications to all disabled members.\n" "\n" " -f / --force\n" " Send notifications to disabled members even if they're not due a " "new\n" " notification yet.\n" "\n" " -l listname\n" " --listname=listname\n" " Process only the given list, otherwise do all lists.\n" msgstr ""