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