summaryrefslogtreecommitdiff
path: root/mailman/debian.py
blob: 1f745fc9e11555884fc76df3d3c82b19019d98d5 (plain)
  1. # -*- python -*-
  2. # -*- coding: us-ascii -*-
  3. ## "debian" mailing list configuration settings
  4. ## captured on Tue Mar 20 08:52:14 2007
  5. ## General options
  6. #
  7. # Fundamental list characteristics, including descriptive info and basic
  8. # behaviors.
  9. # The capitalization of this name can be changed to make it presentable
  10. # in polite company as a proper noun, or to make an acronym part all
  11. # upper case, etc. However, the name will be advertised as the email
  12. # address (e.g., in subscribe confirmation notices), so it should not be
  13. # otherwise altered. (Email addresses are not case sensitive, but they
  14. # are sensitive to almost everything else :-)
  15. real_name = 'Debian'
  16. # There are two ownership roles associated with each mailing list. The
  17. # list administrators are the people who have ultimate control over all
  18. # parameters of this mailing list. They are able to change any list
  19. # configuration variable available through these administration web
  20. # pages.
  21. #
  22. # The list moderators have more limited permissions; they are not able
  23. # to change any list configuration variable, but they are allowed to
  24. # tend to pending administration requests, including approving or
  25. # rejecting held subscription requests, and disposing of held postings.
  26. # Of course, the list administrators can also tend to pending requests.
  27. #
  28. # In order to split the list ownership duties into administrators and
  29. # moderators, you must set a separate moderator password, and also
  30. # provide the email addresses of the list moderators. Note that the
  31. # field you are changing here specifies the list administrators.
  32. owner = ['dr@jones.dk']
  33. # There are two ownership roles associated with each mailing list. The
  34. # list administrators are the people who have ultimate control over all
  35. # parameters of this mailing list. They are able to change any list
  36. # configuration variable available through these administration web
  37. # pages.
  38. #
  39. # The list moderators have more limited permissions; they are not able
  40. # to change any list configuration variable, but they are allowed to
  41. # tend to pending administration requests, including approving or
  42. # rejecting held subscription requests, and disposing of held postings.
  43. # Of course, the list administrators can also tend to pending requests.
  44. #
  45. # In order to split the list ownership duties into administrators and
  46. # moderators, you must set a separate moderator password, and also
  47. # provide the email addresses of the list moderators in this section.
  48. # Note that the field you are changing here specifies the list
  49. # moderators.
  50. moderator = []
  51. # This description is used when the mailing list is listed with other
  52. # mailing lists, or in headers, and so forth. It should be as succinct
  53. # as you can get it, while still identifying what the list is.
  54. description = 'Discussions regarding unofficial Debian packages at debian.jones.dk'
  55. # The text will be treated as html except that newlines will be
  56. # translated to <br> - so you can use links, preformatted text, etc, but
  57. # don't put in carriage returns except where you mean to separate
  58. # paragraphs. And review your changes - bad html (like some
  59. # unterminated HTML constructs) can prevent display of the entire
  60. # listinfo page.
  61. info = ''
  62. # This text will be prepended to subject lines of messages posted to the
  63. # list, to distinguish mailing list messages in mailbox summaries.
  64. # Brevity is premium here, it's ok to shorten long mailing list names to
  65. # something more concise, as long as it still identifies the mailing
  66. # list. You can also add a sequential number by %d substitution
  67. # directive. eg.; [listname %d] -> [listname 123] (listname %05d) ->
  68. # (listname 00123)
  69. #
  70. subject_prefix = '[Debian] '
  71. # Hide the sender of a message, replacing it with the list address
  72. # (Removes From, Sender and Reply-To fields)
  73. #
  74. # legal values are:
  75. # 0 = "No"
  76. # 1 = "Yes"
  77. anonymous_list = 0
  78. # Should any existing Reply-To: header found in the original message be
  79. # stripped? If so, this will be done regardless of whether an explict
  80. # Reply-To: header is added by Mailman or not.
  81. #
  82. # legal values are:
  83. # 0 = "No"
  84. # 1 = "Yes"
  85. first_strip_reply_to = 0
  86. # This option controls what Mailman does to the Reply-To: header in
  87. # messages flowing through this mailing list. When set to Poster, no
  88. # Reply-To: header is added by Mailman, although if one is present in
  89. # the original message, it is not stripped. Setting this value to
  90. # either This list or Explicit address causes Mailman to insert a
  91. # specific Reply-To: header in all messages, overriding the header in
  92. # the original message if necessary (Explicit address inserts the value
  93. # of <a href="?VARHELP=general/reply_to_address">reply_to_address).
  94. #
  95. # There are many reasons not to introduce or override the Reply-To:
  96. # header. One is that some posters depend on their own Reply-To:
  97. # settings to convey their valid return address. Another is that
  98. # modifying Reply-To: makes it much more difficult to send private
  99. # replies. See <a
  100. # href="http://www.unicom.com/pw/reply-to-harmful.html">`Reply-To'
  101. # Munging Considered Harmful for a general discussion of this issue.
  102. # See <a
  103. # href="http://www.metasystema.net/essays/reply-to.mhtml">Reply-To
  104. # Munging Considered Useful for a dissenting opinion.
  105. #
  106. # Some mailing lists have restricted posting privileges, with a parallel
  107. # list devoted to discussions. Examples are `patches' or `checkin'
  108. # lists, where software changes are posted by a revision control system,
  109. # but discussion about the changes occurs on a developers mailing list.
  110. # To support these types of mailing lists, select Explicit address and
  111. # set the Reply-To: address below to point to the parallel list.
  112. #
  113. # legal values are:
  114. # 0 = "Poster"
  115. # 1 = "This list"
  116. # 2 = "Explicit address"
  117. reply_goes_to_list = 1
  118. # This is the address set in the Reply-To: header when the <a
  119. # href="?VARHELP=general/reply_goes_to_list">reply_goes_to_list option
  120. # is set to Explicit address.
  121. #
  122. # There are many reasons not to introduce or override the Reply-To:
  123. # header. One is that some posters depend on their own Reply-To:
  124. # settings to convey their valid return address. Another is that
  125. # modifying Reply-To: makes it much more difficult to send private
  126. # replies. See <a
  127. # href="http://www.unicom.com/pw/reply-to-harmful.html">`Reply-To'
  128. # Munging Considered Harmful for a general discussion of this issue.
  129. # See <a
  130. # href="http://www.metasystema.net/essays/reply-to.mhtml">Reply-To
  131. # Munging Considered Useful for a dissenting opinion.
  132. #
  133. # Some mailing lists have restricted posting privileges, with a parallel
  134. # list devoted to discussions. Examples are `patches' or `checkin'
  135. # lists, where software changes are posted by a revision control system,
  136. # but discussion about the changes occurs on a developers mailing list.
  137. # To support these types of mailing lists, specify the explicit
  138. # Reply-To: address here. You must also specify Explicit address in the
  139. # reply_goes_to_list variable.
  140. #
  141. # Note that if the original message contains a Reply-To: header, it will
  142. # not be changed.
  143. reply_to_address = ''
  144. # Set this to yes when this list is intended to cascade only to other
  145. # mailing lists. When set, meta notices like confirmations and password
  146. # reminders will be directed to an address derived from the member's
  147. # address - it will have the value of "umbrella_member_suffix" appended
  148. # to the member's account name.
  149. #
  150. # legal values are:
  151. # 0 = "No"
  152. # 1 = "Yes"
  153. umbrella_list = 0
  154. # When "umbrella_list" is set to indicate that this list has other
  155. # mailing lists as members, then administrative notices like
  156. # confirmations and password reminders need to not be sent to the member
  157. # list addresses, but rather to the owner of those member lists. In
  158. # that case, the value of this setting is appended to the member's
  159. # account name for such notices. `-owner' is the typical choice. This
  160. # setting has no effect when "umbrella_list" is "No".
  161. umbrella_member_suffix = '-owner'
  162. # Turn this on if you want password reminders to be sent once per month
  163. # to your members. Note that members may disable their own individual
  164. # password reminders.
  165. #
  166. # legal values are:
  167. # 0 = "No"
  168. # 1 = "Yes"
  169. send_reminders = 0
  170. # This value, if any, will be added to the front of the new-subscriber
  171. # welcome message. The rest of the welcome message already describes
  172. # the important addresses and URLs for the mailing list, so you don't
  173. # need to include any of that kind of stuff here. This should just
  174. # contain mission-specific kinds of things, like etiquette policies or
  175. # team orientation, or that kind of thing.
  176. #
  177. # Note that this text will be wrapped, according to the following rules:
  178. # Each paragraph is filled so that no line is longer than 70 characters.
  179. # Any line that begins with whitespace is not filled. A blank line
  180. # separates paragraphs.
  181. #
  182. welcome_msg = ''
  183. # Turn this off only if you plan on subscribing people manually and
  184. # don't want them to know that you did so. This option is most useful
  185. # for transparently migrating lists from some other mailing list manager
  186. # to Mailman.
  187. #
  188. # legal values are:
  189. # 0 = "No"
  190. # 1 = "Yes"
  191. send_welcome_msg = 1
  192. # Text sent to people leaving the list. If empty, no special text will
  193. # be added to the unsubscribe message.
  194. goodbye_msg = ''
  195. # Send goodbye message to members when they are unsubscribed?
  196. #
  197. # legal values are:
  198. # 0 = "No"
  199. # 1 = "Yes"
  200. send_goodbye_msg = 1
  201. # List moderators (and list administrators) are sent daily reminders of
  202. # requests pending approval, like subscriptions to a moderated list, or
  203. # postings that are being held for one reason or another. Setting this
  204. # option causes notices to be sent immediately on the arrival of new
  205. # requests as well.
  206. #
  207. # legal values are:
  208. # 0 = "No"
  209. # 1 = "Yes"
  210. admin_immed_notify = 1
  211. # Should administrator get notices of subscribes and unsubscribes?
  212. #
  213. # legal values are:
  214. # 0 = "No"
  215. # 1 = "Yes"
  216. admin_notify_mchanges = 1
  217. # Send mail to poster when their posting is held for approval?
  218. #
  219. # legal values are:
  220. # 0 = "No"
  221. # 1 = "Yes"
  222. respond_to_post_requests = 1
  223. # When this option is enabled, all list traffic is emergency moderated,
  224. # i.e. held for moderation. Turn this option on when your list is
  225. # experiencing a flamewar and you want a cooling off period.
  226. #
  227. # legal values are:
  228. # 0 = "No"
  229. # 1 = "Yes"
  230. emergency = 0
  231. # When a new member is subscribed to this list, their initial set of
  232. # options is taken from the this variable's setting.
  233. new_member_options = 256
  234. # Administrivia tests will check postings to see whether it's really
  235. # meant as an administrative request (like subscribe, unsubscribe, etc),
  236. # and will add it to the the administrative requests queue, notifying
  237. # the administrator of the new request, in the process.
  238. #
  239. # legal values are:
  240. # 0 = "No"
  241. # 1 = "Yes"
  242. administrivia = 1
  243. # Maximum length in kilobytes (KB) of a message body. Use 0 for no
  244. # limit.
  245. max_message_size = 40
  246. # The "host_name" is the preferred name for email to mailman-related
  247. # addresses on this host, and generally should be the mail host's
  248. # exchanger address, if any. This setting can be useful for selecting
  249. # among alternative names of a host that has multiple addresses.
  250. host_name = 'jones.dk'
  251. # RFC 2369 defines a set of List-* headers that are normally added to
  252. # every message sent to the list membership. These greatly aid end-users
  253. # who are using standards compliant mail readers. They should normally
  254. # always be enabled.
  255. #
  256. # However, not all mail readers are standards compliant yet, and if you
  257. # have a large number of members who are using non-compliant mail
  258. # readers, they may be annoyed at these headers. You should first try
  259. # to educate your members as to why these headers exist, and how to hide
  260. # them in their mail clients. As a last resort you can disable these
  261. # headers, but this is not recommended (and in fact, your ability to
  262. # disable these headers may eventually go away).
  263. #
  264. # legal values are:
  265. # 0 = "No"
  266. # 1 = "Yes"
  267. include_rfc2369_headers = 1
  268. # The List-Post: header is one of the headers recommended by RFC 2369.
  269. # However for some announce-only mailing lists, only a very select group
  270. # of people are allowed to post to the list; the general membership is
  271. # usually not allowed to post. For lists of this nature, the List-Post:
  272. # header is misleading. Select No to disable the inclusion of this
  273. # header. (This does not affect the inclusion of the other List-*:
  274. # headers.)
  275. #
  276. # legal values are:
  277. # 0 = "No"
  278. # 1 = "Yes"
  279. include_list_post_header = 1
  280. # Discard held messages older than this number of days. Use 0 for no
  281. # automatic discarding.
  282. max_days_to_hold = 0
  283. ## Language options
  284. #
  285. # Natural language (internationalization) options.
  286. # This is the default natural language for this mailing list. If more
  287. # than one language is supported then users will be able to select their
  288. # own preferences for when they interact with the list. All other
  289. # interactions will be conducted in the default language. This applies
  290. # to both web-based and email-based messages, but not to email posted by
  291. # list members.
  292. preferred_language = 'en'
  293. # These are all the natural languages supported by this list. Note that
  294. # the default language must be included.
  295. available_languages = ['da', 'de', 'en', 'no', 'sv']
  296. # If your mailing list's default language uses a non-ASCII character set
  297. # and the prefix contains non-ASCII characters, the prefix will always
  298. # be encoded according to the relevant standards. However, if your
  299. # prefix contains only ASCII characters, you may want to set this option
  300. # to Never to disable prefix encoding. This can make the subject
  301. # headers slightly more readable for users with mail readers that don't
  302. # properly handle non-ASCII encodings.
  303. #
  304. # Note however, that if your mailing list receives both encoded and
  305. # unencoded subject headers, you might want to choose As needed. Using
  306. # this setting, Mailman will not encode ASCII prefixes when the rest of
  307. # the header contains only ASCII characters, but if the original header
  308. # contains non-ASCII characters, it will encode the prefix. This avoids
  309. # an ambiguity in the standards which could cause some mail readers to
  310. # display extra, or missing spaces between the prefix and the original
  311. # header.
  312. #
  313. # legal values are:
  314. # 0 = "Never"
  315. # 1 = "Always"
  316. # 2 = "As needed"
  317. encode_ascii_prefixes = 0
  318. ## Nondigest options
  319. #
  320. # Policies concerning immediately delivered list traffic.
  321. # Can subscribers choose to receive mail immediately, rather than in
  322. # batched digests?
  323. #
  324. # legal values are:
  325. # 0 = "No"
  326. # 1 = "Yes"
  327. nondigestable = 1
  328. # Text prepended to the top of every immediately-delivery message. This
  329. # text can include Python format strings which are resolved against list
  330. # attributes. The list of substitutions allowed are:
  331. #
  332. #
  333. # real_name - The "pretty" name of the list; usually the list name with
  334. # capitalization.
  335. #
  336. # list_name - The name by which the list is identified in URLs, where
  337. # case is significant.
  338. #
  339. # host_name - The fully qualified domain name that the list server runs
  340. # on.
  341. #
  342. # web_page_url - The base URL for Mailman. This can be appended with,
  343. # e.g. listinfo/%(list_name)s to yield the listinfo page for the mailing
  344. # list.
  345. #
  346. # description - The brief description of the mailing list.
  347. #
  348. # info - The full description of the mailing list.
  349. #
  350. # cgiext - The extension added to CGI scripts.
  351. #
  352. #
  353. msg_header = ''
  354. # Text appended to the bottom of every immediately-delivery message.
  355. # This text can include Python format strings which are resolved against
  356. # list attributes. The list of substitutions allowed are:
  357. #
  358. #
  359. # real_name - The "pretty" name of the list; usually the list name with
  360. # capitalization.
  361. #
  362. # list_name - The name by which the list is identified in URLs, where
  363. # case is significant.
  364. #
  365. # host_name - The fully qualified domain name that the list server runs
  366. # on.
  367. #
  368. # web_page_url - The base URL for Mailman. This can be appended with,
  369. # e.g. listinfo/%(list_name)s to yield the listinfo page for the mailing
  370. # list.
  371. #
  372. # description - The brief description of the mailing list.
  373. #
  374. # info - The full description of the mailing list.
  375. #
  376. # cgiext - The extension added to CGI scripts.
  377. #
  378. #
  379. msg_footer = """_______________________________________________
  380. %(real_name)s mailing list
  381. %(real_name)s@%(host_name)s
  382. %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s"""
  383. # When you scrub attachments, they are stored in archive area and links
  384. # are made in the message so that the member can access via web browser.
  385. # If you want the attachments totally disappear, you can use content
  386. # filter options.
  387. #
  388. # legal values are:
  389. # 0 = "No"
  390. # 1 = "Yes"
  391. scrub_nondigest = False
  392. ## Digest options
  393. #
  394. # Batched-delivery digest characteristics.
  395. # Can list members choose to receive list traffic bunched in digests?
  396. #
  397. # legal values are:
  398. # 0 = "No"
  399. # 1 = "Yes"
  400. digestable = 1
  401. # Which delivery mode is the default for new users?
  402. #
  403. # legal values are:
  404. # 0 = "Regular"
  405. # 1 = "Digest"
  406. digest_is_default = 0
  407. # When receiving digests, which format is default?
  408. #
  409. # legal values are:
  410. # 0 = "Plain"
  411. # 1 = "MIME"
  412. mime_is_default_digest = 0
  413. # How big in Kb should a digest be before it gets sent out?
  414. digest_size_threshhold = 30
  415. # Should a digest be dispatched daily when the size threshold isn't
  416. # reached?
  417. #
  418. # legal values are:
  419. # 0 = "No"
  420. # 1 = "Yes"
  421. digest_send_periodic = 1
  422. # Text attached (as an initial message, before the table of contents) to
  423. # the top of digests. This text can include Python format strings which
  424. # are resolved against list attributes. The list of substitutions
  425. # allowed are:
  426. #
  427. #
  428. # real_name - The "pretty" name of the list; usually the list name with
  429. # capitalization.
  430. #
  431. # list_name - The name by which the list is identified in URLs, where
  432. # case is significant.
  433. #
  434. # host_name - The fully qualified domain name that the list server runs
  435. # on.
  436. #
  437. # web_page_url - The base URL for Mailman. This can be appended with,
  438. # e.g. listinfo/%(list_name)s to yield the listinfo page for the mailing
  439. # list.
  440. #
  441. # description - The brief description of the mailing list.
  442. #
  443. # info - The full description of the mailing list.
  444. #
  445. # cgiext - The extension added to CGI scripts.
  446. #
  447. #
  448. digest_header = ''
  449. # Text attached (as a final message) to the bottom of digests. This text
  450. # can include Python format strings which are resolved against list
  451. # attributes. The list of substitutions allowed are:
  452. #
  453. #
  454. # real_name - The "pretty" name of the list; usually the list name with
  455. # capitalization.
  456. #
  457. # list_name - The name by which the list is identified in URLs, where
  458. # case is significant.
  459. #
  460. # host_name - The fully qualified domain name that the list server runs
  461. # on.
  462. #
  463. # web_page_url - The base URL for Mailman. This can be appended with,
  464. # e.g. listinfo/%(list_name)s to yield the listinfo page for the mailing
  465. # list.
  466. #
  467. # description - The brief description of the mailing list.
  468. #
  469. # info - The full description of the mailing list.
  470. #
  471. # cgiext - The extension added to CGI scripts.
  472. #
  473. #
  474. digest_footer = """_______________________________________________
  475. %(real_name)s mailing list
  476. %(real_name)s@%(host_name)s
  477. %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s"""
  478. # When a new digest volume is started, the volume number is incremented
  479. # and the issue number is reset to 1.
  480. #
  481. # legal values are:
  482. # 0 = "Yearly"
  483. # 1 = "Monthly"
  484. # 2 = "Quarterly"
  485. # 3 = "Weekly"
  486. # 4 = "Daily"
  487. digest_volume_frequency = 1
  488. ## Privacy options
  489. #
  490. # This section allows you to configure subscription and membership
  491. # exposure policy. You can also control whether this list is public or
  492. # not. See also the <a
  493. # href="http://mail.jones.dk/cgi-bin/mailman/admin/debian/archive">Archival
  494. # Options</a> section for separate archive-related privacy settings.
  495. # Advertise this list when people ask what lists are on this machine?
  496. #
  497. # legal values are:
  498. # 0 = "No"
  499. # 1 = "Yes"
  500. advertised = 1
  501. # Confirm (*) - email confirmation required Require approval - require
  502. # list administrator approval for subscriptions Confirm and approve -
  503. # both confirm and approve
  504. #
  505. # (*) when someone requests a subscription, Mailman sends them a notice
  506. # with a unique subscription request number that they must reply to in
  507. # order to subscribe. This prevents mischievous (or malicious) people
  508. # from creating subscriptions for others without their consent.
  509. #
  510. # legal values are:
  511. # 1 = "Confirm"
  512. # 2 = "Require approval"
  513. # 3 = "Confirm and approve"
  514. subscribe_policy = 1
  515. # When members want to leave a list, they will make an unsubscription
  516. # request, either via the web or via email. Normally it is best for you
  517. # to allow open unsubscriptions so that users can easily remove
  518. # themselves from mailing lists (they get really upset if they can't get
  519. # off lists!).
  520. #
  521. # For some lists though, you may want to impose moderator approval
  522. # before an unsubscription request is processed. Examples of such lists
  523. # include a corporate mailing list that all employees are required to be
  524. # members of.
  525. #
  526. # legal values are:
  527. # 0 = "No"
  528. # 1 = "Yes"
  529. unsubscribe_policy = 0
  530. # Addresses in this list are banned outright from subscribing to this
  531. # mailing list, with no further moderation required. Add addresses one
  532. # per line; start the line with a ^ character to designate a regular
  533. # expression match.
  534. ban_list = []
  535. # When set, the list of subscribers is protected by member or admin
  536. # password authentication.
  537. #
  538. # legal values are:
  539. # 0 = "Anyone"
  540. # 1 = "List members"
  541. # 2 = "List admin only"
  542. private_roster = 0
  543. # Setting this option causes member email addresses to be transformed
  544. # when they are presented on list web pages (both in text and as links),
  545. # so they're not trivially recognizable as email addresses. The
  546. # intention is to prevent the addresses from being snarfed up by
  547. # automated web scanners for use by spammers.
  548. #
  549. # legal values are:
  550. # 0 = "No"
  551. # 1 = "Yes"
  552. obscure_addresses = 1
  553. ## Privacy options
  554. #
  555. # When a message is posted to the list, a series of moderation steps are
  556. # take to decide whether the a moderator must first approve the message
  557. # or not. This section contains the controls for moderation of both
  558. # member and non-member postings.
  559. #
  560. # <p>Member postings are held for moderation if their <b>moderation
  561. # flag</b> is turned on. You can control whether member postings are
  562. # moderated by default or not.
  563. #
  564. # <p>Non-member postings can be automatically <a
  565. # href="?VARHELP=privacy/sender/accept_these_nonmembers" >accepted</a>,
  566. # <a href="?VARHELP=privacy/sender/hold_these_nonmembers">held for
  567. # moderation</a>, <a
  568. # href="?VARHELP=privacy/sender/reject_these_nonmembers" >rejected</a>
  569. # (bounced), or <a
  570. # href="?VARHELP=privacy/sender/discard_these_nonmembers"
  571. # >discarded</a>, either individually or as a group. Any posting from a
  572. # non-member who is not explicitly accepted, rejected, or discarded,
  573. # will have their posting filtered by the <a
  574. # href="?VARHELP=privacy/sender/generic_nonmember_action">general
  575. # non-member rules</a>.
  576. #
  577. # <p>In the text boxes below, add one address per line; start the line
  578. # with a ^ character to designate a <a href=
  579. # "http://www.python.org/doc/current/lib/module-re.html" >Python regular
  580. # expression</a>. When entering backslashes, do so as if you were using
  581. # Python raw strings (i.e. you generally just use a single backslash).
  582. #
  583. # <p>Note that non-regexp matches are always done first.
  584. # Each list member has a moderation flag which says whether messages
  585. # from the list member can be posted directly to the list, or must first
  586. # be approved by the list moderator. When the moderation flag is turned
  587. # on, list member postings must be approved first. You, the list
  588. # administrator can decide whether a specific individual's postings will
  589. # be moderated or not.
  590. #
  591. # When a new member is subscribed, their initial moderation flag takes
  592. # its value from this option. Turn this option off to accept member
  593. # postings by default. Turn this option on to, by default, moderate
  594. # member postings first. You can always manually set an individual
  595. # member's moderation bit by using the membership management screens.
  596. #
  597. # legal values are:
  598. # 0 = "No"
  599. # 1 = "Yes"
  600. default_member_moderation = 0
  601. # Hold -- this holds the message for approval by the list moderators.
  602. #
  603. # Reject -- this automatically rejects the message by sending a bounce
  604. # notice to the post's author. The text of the bounce notice can be <a
  605. # href="?VARHELP=privacy/sender/member_moderation_notice" >configured by
  606. # you.
  607. #
  608. # Discard -- this simply discards the message, with no notice sent to
  609. # the post's author.
  610. #
  611. #
  612. # legal values are:
  613. # 0 = "Hold"
  614. # 1 = "Reject"
  615. # 2 = "Discard"
  616. member_moderation_action = 0
  617. # Text to include in any <a
  618. # href="?VARHELP/privacy/sender/member_moderation_action" >rejection
  619. # notice to be sent to moderated members who post to this list.
  620. member_moderation_notice = ''
  621. # Postings from any of these non-members will be automatically accepted
  622. # with no further moderation applied. Add member addresses one per
  623. # line; start the line with a ^ character to designate a regular
  624. # expression match.
  625. accept_these_nonmembers = []
  626. # Postings from any of these non-members will be immediately and
  627. # automatically held for moderation by the list moderators. The sender
  628. # will receive a notification message which will allow them to cancel
  629. # their held message. Add member addresses one per line; start the line
  630. # with a ^ character to designate a regular expression match.
  631. hold_these_nonmembers = []
  632. # Postings from any of these non-members will be automatically rejected.
  633. # In other words, their messages will be bounced back to the sender with
  634. # a notification of automatic rejection. This option is not appropriate
  635. # for known spam senders; their messages should be <a
  636. # href="?VARHELP=privacy/sender/discard_these_nonmembers" >automatically
  637. # discarded.
  638. #
  639. # Add member addresses one per line; start the line with a ^ character
  640. # to designate a regular expression match.
  641. reject_these_nonmembers = []
  642. # Postings from any of these non-members will be automatically
  643. # discarded. That is, the message will be thrown away with no further
  644. # processing or notification. The sender will not receive a
  645. # notification or a bounce, however the list moderators can optionally
  646. # <a href="?VARHELP=privacy/sender/forward_auto_discards" >receive
  647. # copies of auto-discarded messages..
  648. #
  649. # Add member addresses one per line; start the line with a ^ character
  650. # to designate a regular expression match.
  651. discard_these_nonmembers = []
  652. # When a post from a non-member is received, the message's sender is
  653. # matched against the list of explicitly <a
  654. # href="?VARHELP=privacy/sender/accept_these_nonmembers" >accepted,
  655. # held, <a href="?VARHELP=privacy/sender/reject_these_nonmembers"
  656. # >rejected (bounced), and <a
  657. # href="?VARHELP=privacy/sender/discard_these_nonmembers" >discarded
  658. # addresses. If no match is found, then this action is taken.
  659. #
  660. # legal values are:
  661. # 0 = "Accept"
  662. # 1 = "Hold"
  663. # 2 = "Reject"
  664. # 3 = "Discard"
  665. generic_nonmember_action = 1
  666. # Should messages from non-members, which are automatically discarded,
  667. # be forwarded to the list moderator?
  668. #
  669. # legal values are:
  670. # 0 = "No"
  671. # 1 = "Yes"
  672. forward_auto_discards = 1
  673. # Text to include in any rejection notice to be sent to non-members who
  674. # post to this list. This notice can include the list's owner address by
  675. # %(listowner)s and replaces the internally crafted default message.
  676. nonmember_rejection_notice = ''
  677. ## Privacy options
  678. #
  679. # This section allows you to configure various filters based on the
  680. # recipient of the message.
  681. # Many (in fact, most) spams do not explicitly name their myriad
  682. # destinations in the explicit destination addresses - in fact often the
  683. # To: field has a totally bogus address for obfuscation. The constraint
  684. # applies only to the stuff in the address before the '@' sign, but
  685. # still catches all such spams.
  686. #
  687. # The cost is that the list will not accept unhindered any postings
  688. # relayed from other addresses, unless
  689. #
  690. #
  691. # The relaying address has the same name, or
  692. #
  693. # The relaying address name is included on the options that specifies
  694. # acceptable aliases for the list.
  695. #
  696. #
  697. #
  698. # legal values are:
  699. # 0 = "No"
  700. # 1 = "Yes"
  701. require_explicit_destination = 1
  702. # Alternate addresses that are acceptable when
  703. # `require_explicit_destination' is enabled. This option takes a list
  704. # of regular expressions, one per line, which is matched against every
  705. # recipient address in the message. The matching is performed with
  706. # Python's re.match() function, meaning they are anchored to the start
  707. # of the string.
  708. #
  709. # For backwards compatibility with Mailman 1.1, if the regexp does not
  710. # contain an `@', then the pattern is matched against just the local
  711. # part of the recipient address. If that match fails, or if the pattern
  712. # does contain an `@', then the pattern is matched against the entire
  713. # recipient address.
  714. #
  715. # Matching against the local part is deprecated; in a future release,
  716. # the pattern will always be matched against the entire recipient
  717. # address.
  718. acceptable_aliases = ''
  719. # If a posting has this number, or more, of recipients, it is held for
  720. # admin approval. Use 0 for no ceiling.
  721. max_num_recipients = 10
  722. ## Privacy options
  723. #
  724. # This section allows you to configure various anti-spam filters posting
  725. # filters, which can help reduce the amount of spam your list members
  726. # end up receiving.
  727. #
  728. # Each header filter rule has two parts, a list of regular expressions,
  729. # one per line, and an action to take. Mailman matches the message's
  730. # headers against every regular expression in the rule and if any match,
  731. # the message is rejected, held, or discarded based on the action you
  732. # specify. Use Defer to temporarily disable a rule.
  733. #
  734. # You can have more than one filter rule for your list. In that case,
  735. # each rule is matched in turn, with processing stopped after the first
  736. # match.
  737. #
  738. # Note that headers are collected from all the attachments (except for
  739. # the mailman administrivia message) and matched against the regular
  740. # expressions. With this feature, you can effectively sort out messages
  741. # with dangerous file types or file name extensions.
  742. header_filter_rules = []
  743. # Use this option to prohibit posts according to specific header values.
  744. # The target value is a regular-expression for matching against the
  745. # specified header. The match is done disregarding letter case. Lines
  746. # beginning with '#' are ignored as comments.
  747. #
  748. # For example:to: .*@public.com says to hold all postings with a To:
  749. # mail header containing '@public.com' anywhere among the addresses.
  750. #
  751. # Note that leading whitespace is trimmed from the regexp. This can be
  752. # circumvented in a number of ways, e.g. by escaping or bracketing it.
  753. bounce_matching_headers = """
  754. # Lines that *start* with a '#' are comments.
  755. to: friend@public.com
  756. message-id: relay.comanche.denmark.eu
  757. from: list@listme.com
  758. from: .*@uplinkpro.com"""
  759. ## Bounce options
  760. #
  761. # These policies control the automatic bounce processing system in
  762. # Mailman. Here's an overview of how it works.
  763. #
  764. # <p>When a bounce is received, Mailman tries to extract two pieces of
  765. # information from the message: the address of the member the message
  766. # was intended for, and the severity of the problem causing the bounce.
  767. # The severity can be either <em>hard</em> or <em>soft</em> meaning
  768. # either a fatal error occurred, or a transient error occurred. When in
  769. # doubt, a hard severity is used.
  770. #
  771. # <p>If no member address can be extracted from the bounce, then the
  772. # bounce is usually discarded. Otherwise, each member is assigned a
  773. # <em>bounce score</em> and every time we encounter a bounce from this
  774. # member we increment the score. Hard bounces increment by 1 while soft
  775. # bounces increment by 0.5. We only increment the bounce score once per
  776. # day, so even if we receive ten hard bounces from a member per day,
  777. # their score will increase by only 1 for that day.
  778. #
  779. # <p>When a member's bounce score is greater than the <a
  780. # href="?VARHELP=bounce/bounce_score_threshold">bounce score
  781. # threshold</a>, the subscription is disabled. Once disabled, the
  782. # member will not receive any postings from the list until their
  783. # membership is explicitly re-enabled (either by the list administrator
  784. # or the user). However, they will receive occasional reminders that
  785. # their membership has been disabled, and these reminders will include
  786. # information about how to re-enable their membership.
  787. #
  788. # <p>You can control both the <a
  789. # href="?VARHELP=bounce/bounce_you_are_disabled_warnings">number of
  790. # reminders</a> the member will receive and the <a
  791. # href="?VARHELP=bounce/bounce_you_are_disabled_warnings_interval"
  792. # >frequency</a> with which these reminders are sent.
  793. #
  794. # <p>There is one other important configuration variable; after a
  795. # certain period of time -- during which no bounces from the member are
  796. # received -- the bounce information is <a
  797. # href="?VARHELP=bounce/bounce_info_stale_after">considered stale</a>
  798. # and discarded. Thus by adjusting this value, and the score threshold,
  799. # you can control how quickly bouncing members are disabled. You should
  800. # tune both of these to the frequency and traffic volume of your list.
  801. # By setting this value to No, you disable all automatic bounce
  802. # processing for this list, however bounce messages will still be
  803. # discarded so that the list administrator isn't inundated with them.
  804. #
  805. # legal values are:
  806. # 0 = "No"
  807. # 1 = "Yes"
  808. bounce_processing = 1
  809. # Each subscriber is assigned a bounce score, as a floating point
  810. # number. Whenever Mailman receives a bounce from a list member, that
  811. # member's score is incremented. Hard bounces (fatal errors) increase
  812. # the score by 1, while soft bounces (temporary errors) increase the
  813. # score by 0.5. Only one bounce per day counts against a member's
  814. # score, so even if 10 bounces are received for a member on the same
  815. # day, their score will increase by just 1.
  816. #
  817. # This variable describes the upper limit for a member's bounce score,
  818. # above which they are automatically disabled, but not removed from the
  819. # mailing list.
  820. bounce_score_threshold = 5.0
  821. # The number of days after which a member's bounce information is
  822. # discarded, if no new bounces have been received in the interim. This
  823. # value must be an integer.
  824. bounce_info_stale_after = 7
  825. # How many Your Membership Is Disabled warnings a disabled member should
  826. # get before their address is removed from the mailing list. Set to 0
  827. # to immediately remove an address from the list once their bounce score
  828. # exceeds the threshold. This value must be an integer.
  829. bounce_you_are_disabled_warnings = 3
  830. # The number of days between sending the Your Membership Is Disabled
  831. # warnings. This value must be an integer.
  832. bounce_you_are_disabled_warnings_interval = 7
  833. # While Mailman's bounce detector is fairly robust, it's impossible to
  834. # detect every bounce format in the world. You should keep this
  835. # variable set to Yes for two reasons: 1) If this really is a permanent
  836. # bounce from one of your members, you should probably manually remove
  837. # them from your list, and 2) you might want to send the message on to
  838. # the Mailman developers so that this new format can be added to its
  839. # known set.
  840. #
  841. # If you really can't be bothered, then set this variable to No and all
  842. # non-detected bounces will be discarded without further processing.
  843. #
  844. # Note: This setting will also affect all messages sent to your list's
  845. # -admin address. This address is deprecated and should never be used,
  846. # but some people may still send mail to this address. If this happens,
  847. # and this variable is set to No those messages too will get discarded.
  848. # You may want to set up an autoresponse message for email to the -owner
  849. # and -admin address.
  850. #
  851. # legal values are:
  852. # 0 = "No"
  853. # 1 = "Yes"
  854. bounce_unrecognized_goes_to_list_owner = 1
  855. # By setting this value to No, you turn off notification messages that
  856. # are normally sent to the list owners when a member's delivery is
  857. # disabled due to excessive bounces. An attempt to notify the member
  858. # will always be made.
  859. #
  860. # legal values are:
  861. # 0 = "No"
  862. # 1 = "Yes"
  863. bounce_notify_owner_on_disable = 1
  864. # By setting this value to No, you turn off notification messages that
  865. # are normally sent to the list owners when a member is unsubscribed due
  866. # to excessive bounces. An attempt to notify the member will always be
  867. # made.
  868. #
  869. # legal values are:
  870. # 0 = "No"
  871. # 1 = "Yes"
  872. bounce_notify_owner_on_removal = 1
  873. ## Archive options
  874. #
  875. # List traffic archival policies.
  876. # Archive messages?
  877. #
  878. # legal values are:
  879. # 0 = "No"
  880. # 1 = "Yes"
  881. archive = 1
  882. # Is archive file source for public or private archival?
  883. #
  884. # legal values are:
  885. # 0 = "public"
  886. # 1 = "private"
  887. archive_private = 0
  888. # How often should a new archive volume be started?
  889. #
  890. # legal values are:
  891. # 0 = "Yearly"
  892. # 1 = "Monthly"
  893. # 2 = "Quarterly"
  894. # 3 = "Weekly"
  895. # 4 = "Daily"
  896. archive_volume_frequency = 2
  897. ## Gateway options
  898. #
  899. # Mail-to-News and News-to-Mail gateway services.
  900. # This value may be either the name of your news server, or optionally
  901. # of the format name:port, where port is a port number.
  902. #
  903. # The news server is not part of Mailman proper. You have to already
  904. # have access to an NNTP server, and that NNTP server must recognize the
  905. # machine this mailing list runs on as a machine capable of reading and
  906. # posting news.
  907. nntp_host = ''
  908. # The name of the Usenet group to gateway to and/or from.
  909. linked_newsgroup = ''
  910. # Should new posts to the mailing list be sent to the newsgroup?
  911. #
  912. # legal values are:
  913. # 0 = "No"
  914. # 1 = "Yes"
  915. gateway_to_news = 0
  916. # Should new posts to the newsgroup be sent to the mailing list?
  917. #
  918. # legal values are:
  919. # 0 = "No"
  920. # 1 = "Yes"
  921. gateway_to_mail = 0
  922. # This setting determines the moderation policy of the newsgroup and its
  923. # interaction with the moderation policy of the mailing list. This only
  924. # applies to the newsgroup that you are gatewaying to, so if you are
  925. # only gatewaying from Usenet, or the newsgroup you are gatewaying to is
  926. # not moderated, set this option to None.
  927. #
  928. # If the newsgroup is moderated, you can set this mailing list up to be
  929. # the moderation address for the newsgroup. By selecting Moderated, an
  930. # additional posting hold will be placed in the approval process. All
  931. # messages posted to the mailing list will have to be approved before
  932. # being sent on to the newsgroup, or to the mailing list membership.
  933. #
  934. # Note that if the message has an Approved header with the list's
  935. # administrative password in it, this hold test will be bypassed,
  936. # allowing privileged posters to send messages directly to the list and
  937. # the newsgroup.
  938. #
  939. # Finally, if the newsgroup is moderated, but you want to have an open
  940. # posting policy anyway, you should select Open list, moderated group.
  941. # The effect of this is to use the normal Mailman moderation facilities,
  942. # but to add an Approved header to all messages that are gatewayed to
  943. # Usenet.
  944. #
  945. # legal values are:
  946. # 0 = "None"
  947. # 1 = "Open list, moderated group"
  948. # 2 = "Moderated"
  949. news_moderation = 0
  950. # Mailman prefixes Subject: headers with text you can customize and
  951. # normally, this prefix shows up in messages gatewayed to Usenet. You
  952. # can set this option to No to disable the prefix on gated messages. Of
  953. # course, if you turn off normal Subject: prefixes, they won't be
  954. # prefixed for gated messages either.
  955. #
  956. # legal values are:
  957. # 0 = "No"
  958. # 1 = "Yes"
  959. news_prefix_subject_too = 1
  960. ## Autoreply options
  961. #
  962. # Auto-responder characteristics.<p>
  963. #
  964. # In the text fields below, string interpolation is performed with the
  965. # following key/value substitutions: <p><ul> <li><b>listname</b> -
  966. # <em>gets the name of the mailing list</em> <li><b>listurl</b> -
  967. # <em>gets the list's listinfo URL</em> <li><b>requestemail</b> -
  968. # <em>gets the list's -request address</em> <li><b>owneremail</b> -
  969. # <em>gets the list's -owner address</em> </ul>
  970. #
  971. # <p>For each text field, you can either enter the text directly into
  972. # the text box, or you can specify a file on your local system to upload
  973. # as the text.
  974. # Should Mailman send an auto-response to mailing list posters?
  975. #
  976. # legal values are:
  977. # 0 = "No"
  978. # 1 = "Yes"
  979. autorespond_postings = 0
  980. # Auto-response text to send to mailing list posters.
  981. autoresponse_postings_text = ''
  982. # Should Mailman send an auto-response to emails sent to the -owner
  983. # address?
  984. #
  985. # legal values are:
  986. # 0 = "No"
  987. # 1 = "Yes"
  988. autorespond_admin = 0
  989. # Auto-response text to send to -owner emails.
  990. autoresponse_admin_text = ''
  991. # Should Mailman send an auto-response to emails sent to the -request
  992. # address? If you choose yes, decide whether you want Mailman to
  993. # discard the original email, or forward it on to the system as a normal
  994. # mail command.
  995. #
  996. # legal values are:
  997. # 0 = "No"
  998. # 1 = "Yes, w/discard"
  999. # 2 = "Yes, w/forward"
  1000. autorespond_requests = 0
  1001. # Auto-response text to send to -request emails.
  1002. autoresponse_request_text = ''
  1003. # Number of days between auto-responses to either the mailing list or
  1004. # -request/-owner address from the same poster. Set to zero (or
  1005. # negative) for no grace period (i.e. auto-respond to every message).
  1006. autoresponse_graceperiod = 90
  1007. ## Contentfilter options
  1008. #
  1009. # Policies concerning the content of list traffic.
  1010. #
  1011. # <p>Content filtering works like this: when a message is received by
  1012. # the list and you have enabled content filtering, the individual
  1013. # attachments are first compared to the <a
  1014. # href="?VARHELP=contentfilter/filter_mime_types">filter types</a>. If
  1015. # the attachment type matches an entry in the filter types, it is
  1016. # discarded.
  1017. #
  1018. # <p>Then, if there are <a
  1019. # href="?VARHELP=contentfilter/pass_mime_types">pass types</a> defined,
  1020. # any attachment type that does <em>not</em> match a pass type is also
  1021. # discarded. If there are no pass types defined, this check is skipped.
  1022. #
  1023. # <p>After this initial filtering, any <tt>multipart</tt> attachments
  1024. # that are empty are removed. If the outer message is left empty after
  1025. # this filtering, then the whole message is discarded.
  1026. #
  1027. # <p> Then, each <tt>multipart/alternative</tt> section will be replaced
  1028. # by just the first alternative that is non-empty after filtering if <a
  1029. # href="?VARHELP=contentfilter/collapse_alternatives"
  1030. # >collapse_alternatives</a> is enabled.
  1031. #
  1032. # <p>Finally, any <tt>text/html</tt> parts that are left in the message
  1033. # may be converted to <tt>text/plain</tt> if <a
  1034. # href="?VARHELP=contentfilter/convert_html_to_plaintext"
  1035. # >convert_html_to_plaintext</a> is enabled and the site is configured
  1036. # to allow these conversions.
  1037. # Should Mailman filter the content of list traffic according to the
  1038. # settings below?
  1039. #
  1040. # legal values are:
  1041. # 0 = "No"
  1042. # 1 = "Yes"
  1043. filter_content = 0
  1044. # Use this option to remove each message attachment that matches one of
  1045. # these content types. Each line should contain a string naming a MIME
  1046. # type/subtype, e.g. image/gif. Leave off the subtype to remove all
  1047. # parts with a matching major content type, e.g. image.
  1048. #
  1049. # Blank lines are ignored.
  1050. #
  1051. # See also <a href="?VARHELP=contentfilter/pass_mime_types"
  1052. # >pass_mime_types for a content type whitelist.
  1053. filter_mime_types = ''
  1054. # Use this option to remove each message attachment that does not have a
  1055. # matching content type. Requirements and formats are exactly like <a
  1056. # href="?VARHELP=contentfilter/filter_mime_types" >filter_mime_types.
  1057. #
  1058. # Note: if you add entries to this list but don't add multipart to this
  1059. # list, any messages with attachments will be rejected by the pass
  1060. # filter.
  1061. pass_mime_types = """multipart/mixed
  1062. multipart/alternative
  1063. text/plain"""
  1064. # Remove message attachments that have a matching filename extension.
  1065. filter_filename_extensions = """exe
  1066. bat
  1067. cmd
  1068. com
  1069. pif
  1070. scr
  1071. vbs
  1072. cpl"""
  1073. # Remove message attachments that don't have a matching filename
  1074. # extension. Leave this field blank to skip this filter test.
  1075. pass_filename_extensions = ''
  1076. # Should Mailman collapse multipart/alternative to its first part
  1077. # content?
  1078. #
  1079. # legal values are:
  1080. # 0 = "No"
  1081. # 1 = "Yes"
  1082. collapse_alternatives = True
  1083. # Should Mailman convert text/html parts to plain text? This conversion
  1084. # happens after MIME attachments have been stripped.
  1085. #
  1086. # legal values are:
  1087. # 0 = "No"
  1088. # 1 = "Yes"
  1089. convert_html_to_plaintext = 1
  1090. # One of these actions is taken when the message matches one of the
  1091. # content filtering rules, meaning, the top-level content type matches
  1092. # one of the <a href="?VARHELP=contentfilter/filter_mime_types"
  1093. # >filter_mime_types, or the top-level content type does not match one
  1094. # of the <a href="?VARHELP=contentfilter/pass_mime_types"
  1095. # >pass_mime_types, or if after filtering the subparts of the message,
  1096. # the message ends up empty.
  1097. #
  1098. # Note this action is not taken if after filtering the message still
  1099. # contains content. In that case the message is always forwarded on to
  1100. # the list membership.
  1101. #
  1102. # When messages are discarded, a log entry is written containing the
  1103. # Message-ID of the discarded message. When messages are rejected or
  1104. # forwarded to the list owner, a reason for the rejection is included in
  1105. # the bounce message to the original author. When messages are
  1106. # preserved, they are saved in a special queue directory on disk for the
  1107. # site administrator to view (and possibly rescue) but otherwise
  1108. # discarded. This last option is only available if enabled by the site
  1109. # administrator.
  1110. #
  1111. # legal values are:
  1112. # 0 = "Discard"
  1113. # 1 = "Reject"
  1114. # 2 = "Forward to List Owner"
  1115. # 3 = "Preserve"
  1116. filter_action = 0
  1117. ## Topics options
  1118. #
  1119. # List topic keywords
  1120. # The topic filter categorizes each incoming email message according to
  1121. # <a href="http://www.python.org/doc/current/lib/module-re.html">regular
  1122. # expression filters you specify below. If the message's Subject: or
  1123. # Keywords: header contains a match against a topic filter, the message
  1124. # is logically placed into a topic bucket. Each user can then choose to
  1125. # only receive messages from the mailing list for a particular topic
  1126. # bucket (or buckets). Any message not categorized in a topic bucket
  1127. # registered with the user is not delivered to the list.
  1128. #
  1129. # Note that this feature only works with regular delivery, not digest
  1130. # delivery.
  1131. #
  1132. # The body of the message can also be optionally scanned for Subject:
  1133. # and Keywords: headers, as specified by the <a
  1134. # href="?VARHELP=topics/topics_bodylines_limit">topics_bodylines_limit
  1135. # configuration variable.
  1136. #
  1137. # legal values are:
  1138. # 0 = "Disabled"
  1139. # 1 = "Enabled"
  1140. topics_enabled = 0
  1141. # The topic matcher will scan this many lines of the message body
  1142. # looking for topic keyword matches. Body scanning stops when either
  1143. # this many lines have been looked at, or a non-header-like body line is
  1144. # encountered. By setting this value to zero, no body lines will be
  1145. # scanned (i.e. only the Keywords: and Subject: headers will be
  1146. # scanned). By setting this value to a negative number, then all body
  1147. # lines will be scanned until a non-header-like line is encountered.
  1148. #
  1149. topics_bodylines_limit = 5
  1150. # Each topic keyword is actually a regular expression, which is matched
  1151. # against certain parts of a mail message, specifically the Keywords:
  1152. # and Subject: message headers. Note that the first few lines of the
  1153. # body of the message can also contain a Keywords: and Subject: "header"
  1154. # on which matching is also performed.
  1155. topics = []