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