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