diff options
37 files changed, 0 insertions, 37 deletions
diff --git a/src/mailman/archiving/docs/common.txt b/src/mailman/archiving/docs/common.txt index 42cdaa12e..62b407486 100644 --- a/src/mailman/archiving/docs/common.txt +++ b/src/mailman/archiving/docs/common.txt @@ -5,7 +5,6 @@ Archivers Mailman supports pluggable archivers, and it comes with several default archivers. - >>> from mailman.app.lifecycle import create_list >>> mlist = create_list('test@example.com') >>> msg = message_from_string("""\ ... From: aperson@example.org diff --git a/src/mailman/docs/chains.txt b/src/mailman/docs/chains.txt index 4154d983a..f9ed156b1 100644 --- a/src/mailman/docs/chains.txt +++ b/src/mailman/docs/chains.txt @@ -25,7 +25,6 @@ The Discard chain simply throws the message away. >>> print chain.description Discard a message and stop processing. - >>> from mailman.app.lifecycle import create_list >>> mlist = create_list('_xtest@example.com') >>> msg = message_from_string("""\ ... From: aperson@example.com diff --git a/src/mailman/docs/mlist-addresses.txt b/src/mailman/docs/mlist-addresses.txt index 644a4a580..3f44008fb 100644 --- a/src/mailman/docs/mlist-addresses.txt +++ b/src/mailman/docs/mlist-addresses.txt @@ -5,7 +5,6 @@ Mailing list addresses Every mailing list has a number of addresses which are publicly available. These are defined in the IMailingListAddresses interface. - >>> from mailman.app.lifecycle import create_list >>> mlist = create_list('_xtest@example.com') The posting address is where people send messages to be posted to the mailing diff --git a/src/mailman/docs/pipelines.txt b/src/mailman/docs/pipelines.txt index 51dfd7a61..cf848f1d9 100644 --- a/src/mailman/docs/pipelines.txt +++ b/src/mailman/docs/pipelines.txt @@ -9,7 +9,6 @@ consist of a sequence of handlers, each of which is applied in turn. Unlike rules and chains, there is no way to stop a pipeline from processing the message once it's started. - >>> from mailman.app.lifecycle import create_list >>> mlist = create_list('xtest@example.com') >>> print mlist.pipeline built-in diff --git a/src/mailman/docs/users.txt b/src/mailman/docs/users.txt index a261812e2..73e4f3b77 100644 --- a/src/mailman/docs/users.txt +++ b/src/mailman/docs/users.txt @@ -165,7 +165,6 @@ membership role. >>> org = user_manager.get_address('zperson@example.org') >>> net = user_manager.get_address('zperson@example.net') - >>> from mailman.app.lifecycle import create_list >>> mlist_1 = create_list('xtest_1@example.com') >>> mlist_2 = create_list('xtest_2@example.com') >>> mlist_3 = create_list('xtest_3@example.com') diff --git a/src/mailman/pipeline/docs/ack-headers.txt b/src/mailman/pipeline/docs/ack-headers.txt index ddaa313dc..0f4d8ab9e 100644 --- a/src/mailman/pipeline/docs/ack-headers.txt +++ b/src/mailman/pipeline/docs/ack-headers.txt @@ -8,7 +8,6 @@ transformations. Some headers get added, others get changed. Some of these changes depend on mailing list settings and others depend on how the message is getting sent through the system. We'll take things one-by-one. - >>> from mailman.app.lifecycle import create_list >>> mlist = create_list('_xtest@example.com') >>> mlist.subject_prefix = '' diff --git a/src/mailman/pipeline/docs/acknowledge.txt b/src/mailman/pipeline/docs/acknowledge.txt index c304bd8bf..f8e9d9d87 100644 --- a/src/mailman/pipeline/docs/acknowledge.txt +++ b/src/mailman/pipeline/docs/acknowledge.txt @@ -6,7 +6,6 @@ When a user posts a message to a mailing list, and that user has chosen to receive acknowledgments of their postings, Mailman will sent them such an acknowledgment. - >>> from mailman.app.lifecycle import create_list >>> mlist = create_list('_xtest@example.com') >>> mlist.real_name = 'XTest' >>> mlist.preferred_language = 'en' diff --git a/src/mailman/pipeline/docs/after-delivery.txt b/src/mailman/pipeline/docs/after-delivery.txt index 19673d91c..eef153c7d 100644 --- a/src/mailman/pipeline/docs/after-delivery.txt +++ b/src/mailman/pipeline/docs/after-delivery.txt @@ -7,7 +7,6 @@ by the rest of the handlers in the incoming queue pipeline, a couple of bookkeeping pieces of information are updated. >>> import datetime - >>> from mailman.app.lifecycle import create_list >>> mlist = create_list('_xtest@example.com') >>> post_time = datetime.datetime.now() - datetime.timedelta(minutes=10) >>> mlist.last_post_time = post_time diff --git a/src/mailman/pipeline/docs/archives.txt b/src/mailman/pipeline/docs/archives.txt index c6351a659..51fd600bc 100644 --- a/src/mailman/pipeline/docs/archives.txt +++ b/src/mailman/pipeline/docs/archives.txt @@ -8,7 +8,6 @@ delivery processes while messages are archived. This also allows external archivers to work in a separate process from the main Mailman delivery processes. - >>> from mailman.app.lifecycle import create_list >>> handler = config.handlers['to-archive'] >>> mlist = create_list('_xtest@example.com') >>> switchboard = config.switchboards['archive'] diff --git a/src/mailman/pipeline/docs/avoid-duplicates.txt b/src/mailman/pipeline/docs/avoid-duplicates.txt index 1493c4d04..22fc85207 100644 --- a/src/mailman/pipeline/docs/avoid-duplicates.txt +++ b/src/mailman/pipeline/docs/avoid-duplicates.txt @@ -7,7 +7,6 @@ reduce the reception of duplicate messages. It does this by removing certain recipients from the list of recipients that earlier handler modules (e.g. CalcRecips) calculates. - >>> from mailman.app.lifecycle import create_list >>> mlist = create_list('_xtest@example.com') Create some members we're going to use. diff --git a/src/mailman/pipeline/docs/calc-recips.txt b/src/mailman/pipeline/docs/calc-recips.txt index dbab492cb..1b1903bf8 100644 --- a/src/mailman/pipeline/docs/calc-recips.txt +++ b/src/mailman/pipeline/docs/calc-recips.txt @@ -6,7 +6,6 @@ Every message that makes it through to the list membership gets sent to a set of recipient addresses. These addresses are calculated by one of the handler modules and depends on a host of factors. - >>> from mailman.app.lifecycle import create_list >>> mlist = create_list('_xtest@example.com') Recipients are calculate from the list members, so add a bunch of members to diff --git a/src/mailman/pipeline/docs/cleanse.txt b/src/mailman/pipeline/docs/cleanse.txt index a1838d36e..155de0673 100644 --- a/src/mailman/pipeline/docs/cleanse.txt +++ b/src/mailman/pipeline/docs/cleanse.txt @@ -6,7 +6,6 @@ All messages posted to a list get their headers cleansed. Some headers are related to additional permissions that can be granted to the message and other headers can be used to fish for membership. - >>> from mailman.app.lifecycle import create_list >>> mlist = create_list('_xtest@example.com') Headers such as Approved, Approve, and Urgent are used to grant special diff --git a/src/mailman/pipeline/docs/decorate.txt b/src/mailman/pipeline/docs/decorate.txt index 246e67096..e5b3db8d8 100644 --- a/src/mailman/pipeline/docs/decorate.txt +++ b/src/mailman/pipeline/docs/decorate.txt @@ -6,7 +6,6 @@ Message decoration is the process of adding headers and footers to the original message. A handler module takes care of this based on the settings of the mailing list and the type of message being processed. - >>> from mailman.app.lifecycle import create_list >>> mlist = create_list('_xtest@example.com') >>> msg_text = """\ ... From: aperson@example.org diff --git a/src/mailman/pipeline/docs/file-recips.txt b/src/mailman/pipeline/docs/file-recips.txt index b84b2181d..3180df1fb 100644 --- a/src/mailman/pipeline/docs/file-recips.txt +++ b/src/mailman/pipeline/docs/file-recips.txt @@ -6,7 +6,6 @@ Mailman can calculate the recipients for a message from a Sendmail-style include file. This file must be called members.txt and it must live in the list's data directory. - >>> from mailman.app.lifecycle import create_list >>> mlist = create_list('_xtest@example.com') diff --git a/src/mailman/pipeline/docs/nntp.txt b/src/mailman/pipeline/docs/nntp.txt index 7b013aabf..5c859c0ae 100644 --- a/src/mailman/pipeline/docs/nntp.txt +++ b/src/mailman/pipeline/docs/nntp.txt @@ -6,7 +6,6 @@ Mailman has an NNTP gateway, whereby messages posted to the mailing list can be forwarded onto an NNTP newsgroup. Typically this means Usenet, but since NNTP is to Usenet as IP is to the web, it's more general than that. - >>> from mailman.app.lifecycle import create_list >>> mlist = create_list('_xtest@example.com') Gatewaying from the mailing list to the newsgroup happens through a separate diff --git a/src/mailman/pipeline/docs/reply-to.txt b/src/mailman/pipeline/docs/reply-to.txt index 18b821d7f..841320f7f 100644 --- a/src/mailman/pipeline/docs/reply-to.txt +++ b/src/mailman/pipeline/docs/reply-to.txt @@ -8,7 +8,6 @@ transformations. Some headers get added, others get changed. Some of these changes depend on mailing list settings and others depend on how the message is getting sent through the system. We'll take things one-by-one. - >>> from mailman.app.lifecycle import create_list >>> mlist = create_list('_xtest@example.com') Reply-to munging refers to the behavior where a mailing list can be configured diff --git a/src/mailman/pipeline/docs/scrubber.txt b/src/mailman/pipeline/docs/scrubber.txt index 446843f51..9c019d6e4 100644 --- a/src/mailman/pipeline/docs/scrubber.txt +++ b/src/mailman/pipeline/docs/scrubber.txt @@ -7,7 +7,6 @@ messages and in components such as the archiver. Its primary purpose is to scrub attachments from messages so that binary goop doesn't end up in an archive message. - >>> from mailman.app.lifecycle import create_list >>> mlist = create_list('_xtest@example.com') >>> mlist.preferred_language = 'en' diff --git a/src/mailman/pipeline/docs/subject-munging.txt b/src/mailman/pipeline/docs/subject-munging.txt index e7f55add6..20f3b04ed 100644 --- a/src/mailman/pipeline/docs/subject-munging.txt +++ b/src/mailman/pipeline/docs/subject-munging.txt @@ -8,7 +8,6 @@ transformations. Some headers get added, others get changed. Some of these changes depend on mailing list settings and others depend on how the message is getting sent through the system. We'll take things one-by-one. - >>> from mailman.app.lifecycle import create_list >>> mlist = create_list('_xtest@example.com') diff --git a/src/mailman/pipeline/docs/tagger.txt b/src/mailman/pipeline/docs/tagger.txt index 46cdedcb7..ea3355f1a 100644 --- a/src/mailman/pipeline/docs/tagger.txt +++ b/src/mailman/pipeline/docs/tagger.txt @@ -9,7 +9,6 @@ double duty as the 'topic tag'. Each message that flows the mailing list has its Subject: and Keywords: headers compared against these regular expressions. The message then gets tagged with the topic names of each hit. - >>> from mailman.app.lifecycle import create_list >>> mlist = create_list('_xtest@example.com') Topics must be enabled for Mailman to do any topic matching, even if topics diff --git a/src/mailman/pipeline/docs/to-outgoing.txt b/src/mailman/pipeline/docs/to-outgoing.txt index a8e67ec9f..e04620f8b 100644 --- a/src/mailman/pipeline/docs/to-outgoing.txt +++ b/src/mailman/pipeline/docs/to-outgoing.txt @@ -10,7 +10,6 @@ term somewhat incorrectly, but within the spirit of the standard, which basically describes how to encode the recipient's address in the originator headers for unambigous bounce processing. - >>> from mailman.app.lifecycle import create_list >>> mlist = create_list('_xtest@example.com') >>> switchboard = config.switchboards['out'] diff --git a/src/mailman/queue/docs/archiver.txt b/src/mailman/queue/docs/archiver.txt index e79eb6839..11fd1d98e 100644 --- a/src/mailman/queue/docs/archiver.txt +++ b/src/mailman/queue/docs/archiver.txt @@ -5,7 +5,6 @@ Archiving Mailman can archive to any number of archivers that adhere to the IArchiver interface. By default, there's a Pipermail archiver. - >>> from mailman.app.lifecycle import create_list >>> mlist = create_list('test@example.com') >>> transaction.commit() diff --git a/src/mailman/queue/docs/lmtp.txt b/src/mailman/queue/docs/lmtp.txt index d4509aee7..5961bea50 100644 --- a/src/mailman/queue/docs/lmtp.txt +++ b/src/mailman/queue/docs/lmtp.txt @@ -45,7 +45,6 @@ will get a 550 error. Once the mailing list is created, the posting address is valid. - >>> from mailman.app.lifecycle import create_list >>> create_list('mylist@example.com') <mailing list "mylist@example.com" at ...> diff --git a/src/mailman/queue/docs/news.txt b/src/mailman/queue/docs/news.txt index a0535babc..01b554097 100644 --- a/src/mailman/queue/docs/news.txt +++ b/src/mailman/queue/docs/news.txt @@ -7,7 +7,6 @@ NNTP newsgroup. One of the most important things this runner does is prepare the message for Usenet (yes, I know that NNTP is not Usenet, but this runner was originally written to gate to Usenet, which has its own rules). - >>> from mailman.app.lifecycle import create_list >>> mlist = create_list('_xtest@example.com') >>> mlist.linked_newsgroup = 'comp.lang.python' diff --git a/src/mailman/queue/docs/runner.txt b/src/mailman/queue/docs/runner.txt index 2c07f30ca..8438f2576 100644 --- a/src/mailman/queue/docs/runner.txt +++ b/src/mailman/queue/docs/runner.txt @@ -15,7 +15,6 @@ The basic architecture of qrunner is implemented in the base class that all runners inherit from. This base class implements a .run() method that runs continuously in a loop until the .stop() method is called. - >>> from mailman.app.lifecycle import create_list >>> mlist = create_list('_xtest@example.com') Here is a very simple derived qrunner class. Queue runners use a diff --git a/src/mailman/rest/docs/lists.txt b/src/mailman/rest/docs/lists.txt index f4e2ed9ce..460ca3585 100644 --- a/src/mailman/rest/docs/lists.txt +++ b/src/mailman/rest/docs/lists.txt @@ -13,7 +13,6 @@ yet though. Create a mailing list in a domain and it's accessible via the API. - >>> from mailman.app.lifecycle import create_list >>> create_list('test-one@example.com') <mailing list "test-one@example.com" at ...> >>> transaction.commit() diff --git a/src/mailman/rules/docs/administrivia.txt b/src/mailman/rules/docs/administrivia.txt index 4da0a81b1..082409622 100644 --- a/src/mailman/rules/docs/administrivia.txt +++ b/src/mailman/rules/docs/administrivia.txt @@ -7,7 +7,6 @@ commands in the Subject header or first few lines of the payload. This is used to catch messages posted to the list which should have been sent to the -request robot address. - >>> from mailman.app.lifecycle import create_list >>> mlist = create_list('_xtest@example.com') >>> mlist.administrivia = True >>> rule = config.rules['administrivia'] diff --git a/src/mailman/rules/docs/approve.txt b/src/mailman/rules/docs/approve.txt index 868827cf0..b92df3bdc 100644 --- a/src/mailman/rules/docs/approve.txt +++ b/src/mailman/rules/docs/approve.txt @@ -14,7 +14,6 @@ approval queue. This has several use cases: In order to support this, a mailing list can be given a 'moderator password' which is shared among all the administrators. - >>> from mailman.app.lifecycle import create_list >>> mlist = create_list('_xtest@example.com') >>> mlist.moderator_password = 'abcxyz' diff --git a/src/mailman/rules/docs/emergency.txt b/src/mailman/rules/docs/emergency.txt index 4ee3e8e74..70f455dca 100644 --- a/src/mailman/rules/docs/emergency.txt +++ b/src/mailman/rules/docs/emergency.txt @@ -5,7 +5,6 @@ Emergency When the mailing list has its emergency flag set, all messages posted to the list are held for moderator approval. - >>> from mailman.app.lifecycle import create_list >>> mlist = create_list('_xtest@example.com') >>> msg = message_from_string("""\ ... From: aperson@example.com diff --git a/src/mailman/rules/docs/header-matching.txt b/src/mailman/rules/docs/header-matching.txt index 9956832ea..217625fb0 100644 --- a/src/mailman/rules/docs/header-matching.txt +++ b/src/mailman/rules/docs/header-matching.txt @@ -6,7 +6,6 @@ Mailman can do pattern based header matching during its normal rule processing. There is a set of site-wide default header matches specified in the configuration file under the [spam.headers] section. - >>> from mailman.app.lifecycle import create_list >>> mlist = create_list('_xtest@example.com') Because the default [spam.headers] section is empty, we'll just extend the diff --git a/src/mailman/rules/docs/loop.txt b/src/mailman/rules/docs/loop.txt index 927df0e9b..bb6da364b 100644 --- a/src/mailman/rules/docs/loop.txt +++ b/src/mailman/rules/docs/loop.txt @@ -5,7 +5,6 @@ Posting loops To avoid a posting loop, Mailman has a rule to check for the existence of an X-BeenThere header with the value of the list's posting address. - >>> from mailman.app.lifecycle import create_list >>> mlist = create_list('_xtest@example.com') >>> rule = config.rules['loop'] >>> print rule.name diff --git a/src/mailman/rules/docs/max-size.txt b/src/mailman/rules/docs/max-size.txt index 264281b65..e3cc0ccf9 100644 --- a/src/mailman/rules/docs/max-size.txt +++ b/src/mailman/rules/docs/max-size.txt @@ -7,7 +7,6 @@ specified maximum. Generally this is used to prevent huge attachments from getting posted to the list. This value is calculated in terms of KB (1024 bytes). - >>> from mailman.app.lifecycle import create_list >>> mlist = create_list('_xtest@example.com') >>> rule = config.rules['max-size'] >>> print rule.name diff --git a/src/mailman/rules/docs/moderation.txt b/src/mailman/rules/docs/moderation.txt index 335dd4f5b..b268e9d4a 100644 --- a/src/mailman/rules/docs/moderation.txt +++ b/src/mailman/rules/docs/moderation.txt @@ -7,7 +7,6 @@ postings, then only members with a cleared moderation flag will be able to email the list without having those messages be held for approval. The 'moderation' rule determines whether the message should be moderated or not. - >>> from mailman.app.lifecycle import create_list >>> mlist = create_list('_xtest@example.com') >>> rule = config.rules['moderation'] >>> print rule.name diff --git a/src/mailman/rules/docs/news-moderation.txt b/src/mailman/rules/docs/news-moderation.txt index 269079505..79ebde772 100644 --- a/src/mailman/rules/docs/news-moderation.txt +++ b/src/mailman/rules/docs/news-moderation.txt @@ -9,7 +9,6 @@ posted to the newsgroup, and from there, gated to the mailing list. It's a circuitous route, but it works nonetheless by holding all messages posted directly to the mailing list. - >>> from mailman.app.lifecycle import create_list >>> mlist = create_list('_xtest@example.com') >>> rule = config.rules['news-moderation'] >>> print rule.name diff --git a/src/mailman/rules/docs/no-subject.txt b/src/mailman/rules/docs/no-subject.txt index fa26006ef..733de00e4 100644 --- a/src/mailman/rules/docs/no-subject.txt +++ b/src/mailman/rules/docs/no-subject.txt @@ -5,7 +5,6 @@ No Subject header This rule matches if the message has no Subject header, or if the header is the empty string when stripped. - >>> from mailman.app.lifecycle import create_list >>> mlist = create_list('_xtest@example.com') >>> rule = config.rules['no-subject'] >>> print rule.name diff --git a/src/mailman/rules/docs/recipients.txt b/src/mailman/rules/docs/recipients.txt index 724faa8ad..344a5f95f 100644 --- a/src/mailman/rules/docs/recipients.txt +++ b/src/mailman/rules/docs/recipients.txt @@ -5,7 +5,6 @@ Maximum number of recipients The 'max-recipients' rule matches when there are more than the maximum allowed number of explicit recipients addressed by the message. - >>> from mailman.app.lifecycle import create_list >>> mlist = create_list('_xtest@example.com') >>> rule = config.rules['max-recipients'] >>> print rule.name diff --git a/src/mailman/rules/docs/rules.txt b/src/mailman/rules/docs/rules.txt index a21816944..e61ea547e 100644 --- a/src/mailman/rules/docs/rules.txt +++ b/src/mailman/rules/docs/rules.txt @@ -47,7 +47,6 @@ Individual rules can be checked to see if they match, by running the rule's `check()` method. This returns a boolean indicating whether the rule was matched or not. - >>> from mailman.app.lifecycle import create_list >>> mlist = create_list('_xtest@example.com') >>> msg = message_from_string("""\ ... From: aperson@example.com diff --git a/src/mailman/rules/docs/suspicious.txt b/src/mailman/rules/docs/suspicious.txt index 59b4493c4..e99fb49c4 100644 --- a/src/mailman/rules/docs/suspicious.txt +++ b/src/mailman/rules/docs/suspicious.txt @@ -6,7 +6,6 @@ Suspicious headers are a way for Mailman to hold messages that match a particular regular expression. This mostly historical feature is fairly confusing to users, and the list attribute that controls this is misnamed. - >>> from mailman.app.lifecycle import create_list >>> mlist = create_list('_xtest@example.com') >>> rule = config.rules['suspicious-header'] >>> print rule.name |