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