summaryrefslogtreecommitdiff
path: root/mailman/customers.py
blob: d983288d08226ee47e06f45af6c60091c775c4c8 (plain)
  1. ## "customers" mailing list configuration settings -*- python -*-
  2. ## captured on Thu Jun 5 08:58:36 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 = 'Customers'
  14. # There are two ownership roles associated with each mailing list. The
  15. # list administrators are the people who have ultimate control over all
  16. # parameters of this mailing list. They are able to change any list
  17. # configuration variable available through these administration web
  18. # pages.
  19. #
  20. # The list moderators have more limited permissions; they are not able
  21. # to change any list configuration variable, but they are allowed to
  22. # tend to pending administration requests, including approving or
  23. # rejecting held subscription requests, and disposing of held postings.
  24. # Of course, the list administrators can also tend to pending requests.
  25. #
  26. # In order to split the list ownership duties into administrators and
  27. # moderators, you must set a separate moderator password, and also
  28. # provide the email addresses of the list moderators. Note that the
  29. # field you are changing here specifies the list administrators.
  30. owner = ['jonas@bitbase.dk']
  31. # There are two ownership roles associated with each mailing list. The
  32. # list administrators are the people who have ultimate control over all
  33. # parameters of this mailing list. They are able to change any list
  34. # configuration variable available through these administration web
  35. # pages.
  36. #
  37. # The list moderators have more limited permissions; they are not able
  38. # to change any list configuration variable, but they are allowed to
  39. # tend to pending administration requests, including approving or
  40. # rejecting held subscription requests, and disposing of held postings.
  41. # Of course, the list administrators can also tend to pending requests.
  42. #
  43. # In order to split the list ownership duties into administrators and
  44. # moderators, you must set a separate moderator password, and also
  45. # provide the email addresses of the list moderators in this section.
  46. # Note that the field you are changing here specifies the list
  47. # moderators.
  48. moderator = []
  49. # This description is used when the mailing list is listed with other
  50. # mailing lists, or in headers, and so forth. It should be as succinct
  51. # as you can get it, while still identifying what the list is.
  52. description = 'Customers at Bitbase (for announcements)'
  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 = """Customers at Bitbase (for announcements)
  60. This list is for announcements to (english speaking) customers at Bitbase e.g. about changes to services or malfunctions.
  61. The list is closed for subscribption, and only Bitbase staff can send to it.
  62. The archive is public."""
  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 = '[Bitbase] '
  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 = 1
  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 = 2
  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 = 'teknik@bitbase.dk'
  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 = ''
  181. # Turn this off only if you plan on subscribing people manually and
  182. # don't want them to know that you did so. This option is most useful
  183. # for transparently migrating lists from some other mailing list manager
  184. # to Mailman.
  185. #
  186. # legal values are:
  187. # 0 = "No"
  188. # 1 = "Yes"
  189. send_welcome_msg = 1
  190. # Text sent to people leaving the list. If empty, no special text will
  191. # be added to the unsubscribe message.
  192. goodbye_msg = ''
  193. # Send goodbye message to members when they are unsubscribed?
  194. #
  195. # legal values are:
  196. # 0 = "No"
  197. # 1 = "Yes"
  198. send_goodbye_msg = 1
  199. # List moderators (and list administrators) are sent daily reminders of
  200. # requests pending approval, like subscriptions to a moderated list, or
  201. # postings that are being held for one reason or another. Setting this
  202. # option causes notices to be sent immediately on the arrival of new
  203. # requests as well.
  204. #
  205. # legal values are:
  206. # 0 = "No"
  207. # 1 = "Yes"
  208. admin_immed_notify = 1
  209. # Should administrator get notices of subscribes and unsubscribes?
  210. #
  211. # legal values are:
  212. # 0 = "No"
  213. # 1 = "Yes"
  214. admin_notify_mchanges = 1
  215. # Approval notices are sent when mail triggers certain of the limits
  216. # except routine list moderation and spam filters, for which notices are
  217. # not sent. This option overrides ever sending the notice.
  218. #
  219. # legal values are:
  220. # 0 = "No"
  221. # 1 = "Yes"
  222. respond_to_post_requests = 1
  223. # When this option is enabled, all list traffic is emergency moderated,
  224. # i.e. held for moderation. Turn this option on when your list is
  225. # experiencing a flamewar and you want a cooling off period.
  226. #
  227. # legal values are:
  228. # 0 = "No"
  229. # 1 = "Yes"
  230. emergency = 0
  231. # When a new member is subscribed to this list, their initial set of
  232. # options is taken from the this variable's setting.
  233. new_member_options = 256
  234. # Administrivia tests will check postings to see whether it's really
  235. # meant as an administrative request (like subscribe, unsubscribe, etc),
  236. # and will add it to the the administrative requests queue, notifying
  237. # the administrator of the new request, in the process.
  238. #
  239. # legal values are:
  240. # 0 = "No"
  241. # 1 = "Yes"
  242. administrivia = 1
  243. # Maximum length in kilobytes (KB) of a message body. Use 0 for no
  244. # limit.
  245. max_message_size = 40
  246. # The "host_name" is the preferred name for email to mailman-related
  247. # addresses on this host, and generally should be the mail host's
  248. # exchanger address, if any. This setting can be useful for selecting
  249. # among alternative names of a host that has multiple addresses.
  250. host_name = 'bitbase.dk'
  251. # RFC 2369 defines a set of List-* headers that are normally added to
  252. # every message sent to the list membership. These greatly aid end-users
  253. # who are using standards compliant mail readers. They should normally
  254. # always be enabled.
  255. #
  256. # However, not all mail readers are standards compliant yet, and if you
  257. # have a large number of members who are using non-compliant mail
  258. # readers, they may be annoyed at these headers. You should first try
  259. # to educate your members as to why these headers exist, and how to hide
  260. # them in their mail clients. As a last resort you can disable these
  261. # headers, but this is not recommended (and in fact, your ability to
  262. # disable these headers may eventually go away).
  263. #
  264. # legal values are:
  265. # 0 = "No"
  266. # 1 = "Yes"
  267. include_rfc2369_headers = 1
  268. # The List-Post: header is one of the headers recommended by RFC 2369.
  269. # However for some announce-only mailing lists, only a very select group
  270. # of people are allowed to post to the list; the general membership is
  271. # usually not allowed to post. For lists of this nature, the List-Post:
  272. # header is misleading. Select No to disable the inclusion of this
  273. # header. (This does not affect the inclusion of the other List-*:
  274. # headers.)
  275. #
  276. # legal values are:
  277. # 0 = "No"
  278. # 1 = "Yes"
  279. include_list_post_header = 1
  280. ## Language options
  281. #
  282. # Natural language (internationalization) options.
  283. # This is the default natural language for this mailing list. If more
  284. # than one language is supported then users will be able to select their
  285. # own preferences for when they interact with the list. All other
  286. # interactions will be conducted in the default language. This applies
  287. # to both web-based and email-based messages, but not to email posted by
  288. # list members.
  289. preferred_language = 'en'
  290. # These are all the natural languages supported by this list. Note that
  291. # the default language must be included.
  292. available_languages = ['en']
  293. # If your mailing list's default language uses a non-ASCII character set
  294. # and the prefix contains non-ASCII characters, the prefix will always
  295. # be encoded according to the relevant standards. However, if your
  296. # prefix contains only ASCII characters, you may want to set this option
  297. # to Never to disable prefix encoding. This can make the subject
  298. # headers slightly more readable for users with mail readers that don't
  299. # properly handle non-ASCII encodings.
  300. #
  301. # Note however, that if your mailing list receives both encoded and
  302. # unencoded subject headers, you might want to choose As needed. Using
  303. # this setting, Mailman will not encode ASCII prefixes when the rest of
  304. # the header contains only ASCII characters, but if the original header
  305. # contains non-ASCII characters, it will encode the prefix. This avoids
  306. # an ambiguity in the standards which could cause some mail readers to
  307. # display extra, or missing spaces between the prefix and the original
  308. # header.
  309. #
  310. # legal values are:
  311. # 0 = "Never"
  312. # 1 = "Always"
  313. # 2 = "As needed"
  314. encode_ascii_prefixes = 0
  315. ## Nondigest options
  316. #
  317. # Policies concerning immediately delivered list traffic.
  318. # Can subscribers choose to receive mail immediately, rather than in
  319. # batched digests?
  320. #
  321. # legal values are:
  322. # 0 = "No"
  323. # 1 = "Yes"
  324. nondigestable = 1
  325. # Text prepended to the top of every immediately-delivery message. This
  326. # text can include Python format strings which are resolved against list
  327. # attributes. The list of substitutions allowed are:
  328. #
  329. #
  330. # real_name - The `pretty' name of the list; usually the list name with
  331. # capitalization.
  332. #
  333. # list_name - The name by which the list is identified in URLs, where
  334. # case is significant. (For backwards compability, _internal_name is
  335. # equivalent.)
  336. #
  337. # host_name - The fully qualified domain name that the list server runs
  338. # on.
  339. #
  340. # web_page_url - The base URL for Mailman. This can be appended with,
  341. # e.g. listinfo/%(internal_name)s to yield the listinfo page for the
  342. # mailing list.
  343. #
  344. # description - The brief description of the mailing list.
  345. #
  346. # info - The full description of the mailing list.
  347. #
  348. # cgiext - The extension added to CGI scripts.
  349. #
  350. #
  351. msg_header = ''
  352. # Text appended to the bottom of every immediately-delivery message.
  353. # This text can include Python format strings which are resolved against
  354. # list attributes. The list of substitutions allowed are:
  355. #
  356. #
  357. # real_name - The `pretty' name of the list; usually the list name with
  358. # capitalization.
  359. #
  360. # list_name - The name by which the list is identified in URLs, where
  361. # case is significant. (For backwards compability, _internal_name is
  362. # equivalent.)
  363. #
  364. # host_name - The fully qualified domain name that the list server runs
  365. # on.
  366. #
  367. # web_page_url - The base URL for Mailman. This can be appended with,
  368. # e.g. listinfo/%(internal_name)s to yield the listinfo page for the
  369. # mailing list.
  370. #
  371. # description - The brief description of the mailing list.
  372. #
  373. # info - The full description of the mailing list.
  374. #
  375. # cgiext - The extension added to CGI scripts.
  376. #
  377. #
  378. msg_footer = """_______________________________________________
  379. %(real_name)s mailing list
  380. %(real_name)s@%(host_name)s
  381. %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s"""
  382. ## Digest options
  383. #
  384. # Batched-delivery digest characteristics.
  385. # Can list members choose to receive list traffic bunched in digests?
  386. #
  387. # legal values are:
  388. # 0 = "No"
  389. # 1 = "Yes"
  390. digestable = 0
  391. # Which delivery mode is the default for new users?
  392. #
  393. # legal values are:
  394. # 0 = "Regular"
  395. # 1 = "Digest"
  396. digest_is_default = 0
  397. # When receiving digests, which format is default?
  398. #
  399. # legal values are:
  400. # 0 = "Plain"
  401. # 1 = "MIME"
  402. mime_is_default_digest = 0
  403. # How big in Kb should a digest be before it gets sent out?
  404. digest_size_threshhold = 30
  405. # Should a digest be dispatched daily when the size threshold isn't
  406. # reached?
  407. #
  408. # legal values are:
  409. # 0 = "No"
  410. # 1 = "Yes"
  411. digest_send_periodic = 1
  412. # Text attached (as an initial message, before the table of contents) to
  413. # the top of digests. This text can include Python format strings which
  414. # are resolved against list attributes. The list of substitutions
  415. # allowed are:
  416. #
  417. #
  418. # real_name - The `pretty' name of the list; usually the list name with
  419. # capitalization.
  420. #
  421. # list_name - The name by which the list is identified in URLs, where
  422. # case is significant. (For backwards compability, _internal_name is
  423. # equivalent.)
  424. #
  425. # host_name - The fully qualified domain name that the list server runs
  426. # on.
  427. #
  428. # web_page_url - The base URL for Mailman. This can be appended with,
  429. # e.g. listinfo/%(internal_name)s to yield the listinfo page for the
  430. # mailing list.
  431. #
  432. # description - The brief description of the mailing list.
  433. #
  434. # info - The full description of the mailing list.
  435. #
  436. # cgiext - The extension added to CGI scripts.
  437. #
  438. #
  439. digest_header = ''
  440. # Text attached (as a final message) to the bottom of digests. This text
  441. # can include Python format strings which are resolved against list
  442. # attributes. The list of substitutions allowed are:
  443. #
  444. #
  445. # real_name - The `pretty' name of the list; usually the list name with
  446. # capitalization.
  447. #
  448. # list_name - The name by which the list is identified in URLs, where
  449. # case is significant. (For backwards compability, _internal_name is
  450. # equivalent.)
  451. #
  452. # host_name - The fully qualified domain name that the list server runs
  453. # on.
  454. #
  455. # web_page_url - The base URL for Mailman. This can be appended with,
  456. # e.g. listinfo/%(internal_name)s to yield the listinfo page for the
  457. # mailing list.
  458. #
  459. # description - The brief description of the mailing list.
  460. #
  461. # info - The full description of the mailing list.
  462. #
  463. # cgiext - The extension added to CGI scripts.
  464. #
  465. #
  466. digest_footer = """_______________________________________________
  467. %(real_name)s mailing list
  468. %(real_name)s@%(host_name)s
  469. %(web_page_url)slistinfo%(cgiext)s/%(_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.bitbase.dk/mailman/admin/customers/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 = 1
  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@bitbase.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 = 1
  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. # Use this option to prohibit posts according to specific header values.
  717. # The target value is a regular-expression for matching against the
  718. # specified header. The match is done disregarding letter case. Lines
  719. # beginning with '#' are ignored as comments.
  720. #
  721. # For example:to: .*@public.com says to hold all postings with a To:
  722. # mail header containing '@public.com' anywhere among the addresses.
  723. #
  724. # Note that leading whitespace is trimmed from the regexp. This can be
  725. # circumvented in a number of ways, e.g. by escaping or bracketing it.
  726. bounce_matching_headers = """# Lines that *start* with a '#' are comments.
  727. to: friend@public.com
  728. message-id: relay.comanche.denmark.eu
  729. from: list@listme.com
  730. from: .*@uplinkpro.com"""
  731. ## Bounce options
  732. #
  733. # These policies control the automatic bounce processing system in
  734. # Mailman. Here's an overview of how it works.
  735. #
  736. # <p>When a bounce is received, Mailman tries to extract two pieces of
  737. # information from the message: the address of the member the message
  738. # was intended for, and the severity of the problem causing the bounce.
  739. # The severity can be either <em>hard</em> or <em>soft</em> meaning
  740. # either a fatal error occurred, or a transient error occurred. When in
  741. # doubt, a hard severity is used.
  742. #
  743. # <p>If no member address can be extracted from the bounce, then the
  744. # bounce is usually discarded. Otherwise, each member is assigned a
  745. # <em>bounce score</em> and every time we encounter a bounce from this
  746. # member we increment the score. Hard bounces increment by 1 while soft
  747. # bounces increment by 0.5. We only increment the bounce score once per
  748. # day, so even if we receive ten hard bounces from a member per day,
  749. # their score will increase by only 1 for that day.
  750. #
  751. # <p>When a member's bounce score is greater than the <a
  752. # href="?VARHELP=bounce/bounce_score_threshold">bounce score
  753. # threshold</a>, the subscription is disabled. Once disabled, the
  754. # member will not receive any postings from the list until their
  755. # membership is explicitly re-enabled (either by the list administrator
  756. # or the user). However, they will receive occasional reminders that
  757. # their membership has been disabled, and these reminders will include
  758. # information about how to re-enable their membership.
  759. #
  760. # <p>You can control both the <a
  761. # href="?VARHELP=bounce/bounce_you_are_disabled_warnings">number of
  762. # reminders</a> the member will receive and the <a
  763. # href="?VARHELP=bounce/bounce_you_are_disabled_warnings_interval"
  764. # >frequency</a> with which these reminders are sent.
  765. #
  766. # <p>There is one other important configuration variable; after a
  767. # certain period of time -- during which no bounces from the member are
  768. # received -- the bounce information is <a
  769. # href="?VARHELP=bounce/bounce_info_stale_after">considered stale</a>
  770. # and discarded. Thus by adjusting this value, and the score threshold,
  771. # you can control how quickly bouncing members are disabled. You should
  772. # tune both of these to the frequency and traffic volume of your list.
  773. # By setting this value to No, you disable all automatic bounce
  774. # processing for this list, however bounce messages will still be
  775. # discarded so that the list administrator isn't inundated with them.
  776. #
  777. # legal values are:
  778. # 0 = "No"
  779. # 1 = "Yes"
  780. bounce_processing = 1
  781. # The maximum member bounce score before the member's subscription is
  782. # disabled. This value can be a floating point number.
  783. bounce_score_threshold = 5.0
  784. # The number of days after which a member's bounce information is
  785. # discarded, if no new bounces have been received in the interim. This
  786. # value must be an integer.
  787. bounce_info_stale_after = 7
  788. # How many Your Membership Is Disabled warnings a disabled member should
  789. # get before their address is removed from the mailing list. Set to 0
  790. # to immediately remove an address from the list once their bounce score
  791. # exceeds the threshold. This value must be an integer.
  792. bounce_you_are_disabled_warnings = 3
  793. # The number of days between sending the Your Membership Is Disabled
  794. # warnings. This value must be an integer.
  795. bounce_you_are_disabled_warnings_interval = 7
  796. # While Mailman's bounce detector is fairly robust, it's impossible to
  797. # detect every bounce format in the world. You should keep this
  798. # variable set to Yes for two reasons: 1) If this really is a permanent
  799. # bounce from one of your members, you should probably manually remove
  800. # them from your list, and 2) you might want to send the message on to
  801. # the Mailman developers so that this new format can be added to its
  802. # known set.
  803. #
  804. # If you really can't be bothered, then set this variable to No and all
  805. # non-detected bounces will be discarded without further processing.
  806. #
  807. # Note: This setting will also affect all messages sent to your list's
  808. # -admin address. This address is deprecated and should never be used,
  809. # but some people may still send mail to this address. If this happens,
  810. # and this variable is set to No those messages too will get discarded.
  811. # You may want to set up an autoresponse message for email to the -owner
  812. # and -admin address.
  813. #
  814. # legal values are:
  815. # 0 = "No"
  816. # 1 = "Yes"
  817. bounce_unrecognized_goes_to_list_owner = 1
  818. # By setting this value to No, you turn off notification messages that
  819. # are normally sent to the list owners when a member's delivery is
  820. # disabled due to excessive bounces. An attempt to notify the member
  821. # will always be made.
  822. #
  823. # legal values are:
  824. # 0 = "No"
  825. # 1 = "Yes"
  826. bounce_notify_owner_on_disable = 1
  827. # By setting this value to No, you turn off notification messages that
  828. # are normally sent to the list owners when a member is unsubscribed due
  829. # to excessive bounces. An attempt to notify the member will always be
  830. # made.
  831. #
  832. # legal values are:
  833. # 0 = "No"
  834. # 1 = "Yes"
  835. bounce_notify_owner_on_removal = 1
  836. ## Archive options
  837. #
  838. # List traffic archival policies.
  839. # Archive messages?
  840. #
  841. # legal values are:
  842. # 0 = "No"
  843. # 1 = "Yes"
  844. archive = 1
  845. # Is archive file source for public or private archival?
  846. #
  847. # legal values are:
  848. # 0 = "public"
  849. # 1 = "private"
  850. archive_private = 0
  851. # How often should a new archive volume be started?
  852. #
  853. # legal values are:
  854. # 0 = "Yearly"
  855. # 1 = "Monthly"
  856. # 2 = "Quarterly"
  857. # 3 = "Weekly"
  858. # 4 = "Daily"
  859. archive_volume_frequency = 2
  860. ## Gateway options
  861. #
  862. # Mail-to-News and News-to-Mail gateway services.
  863. # The News server is not part of Mailman proper. You have to already
  864. # have access to a NNTP server, and that NNTP server has to recognize
  865. # the machine this mailing list runs on as a machine capable of reading
  866. # and posting news.
  867. nntp_host = ''
  868. # The name of the Usenet group to gateway to and/or from.
  869. linked_newsgroup = ''
  870. # Should new posts to the mailing list be sent to the newsgroup?
  871. #
  872. # legal values are:
  873. # 0 = "No"
  874. # 1 = "Yes"
  875. gateway_to_news = 0
  876. # Should new posts to the newsgroup be sent to the mailing list?
  877. #
  878. # legal values are:
  879. # 0 = "No"
  880. # 1 = "Yes"
  881. gateway_to_mail = 0
  882. # This setting determines the moderation policy of the newsgroup and its
  883. # interaction with the moderation policy of the mailing list. This only
  884. # applies to the newsgroup that you are gatewaying to, so if you are
  885. # only gatewaying from Usenet, or the newsgroup you are gatewaying to is
  886. # not moderated, set this option to None.
  887. #
  888. # If the newsgroup is moderated, you can set this mailing list up to be
  889. # the moderation address for the newsgroup. By selecting Moderated, an
  890. # additional posting hold will be placed in the approval process. All
  891. # messages posted to the mailing list will have to be approved before
  892. # being sent on to the newsgroup, or to the mailing list membership.
  893. #
  894. # Note that if the message has an Approved header with the list's
  895. # administrative password in it, this hold test will be bypassed,
  896. # allowing privileged posters to send messages directly to the list and
  897. # the newsgroup.
  898. #
  899. # Finally, if the newsgroup is moderated, but you want to have an open
  900. # posting policy anyway, you should select Open list, moderated group.
  901. # The effect of this is to use the normal Mailman moderation facilities,
  902. # but to add an Approved header to all messages that are gatewayed to
  903. # Usenet.
  904. #
  905. # legal values are:
  906. # 0 = "None"
  907. # 1 = "Open list, moderated group"
  908. # 2 = "Moderated"
  909. news_moderation = 0
  910. # Mailman prefixes Subject: headers with text you can customize and
  911. # normally, this prefix shows up in messages gatewayed to Usenet. You
  912. # can set this option to No to disable the prefix on gated messages. Of
  913. # course, if you turn off normal Subject: prefixes, they won't be
  914. # prefixed for gated messages either.
  915. #
  916. # legal values are:
  917. # 0 = "No"
  918. # 1 = "Yes"
  919. news_prefix_subject_too = 1
  920. ## Autoreply options
  921. #
  922. # Auto-responder characteristics.<p>
  923. #
  924. # In the text fields below, string interpolation is performed with the
  925. # following key/value substitutions: <p><ul> <li><b>listname</b> -
  926. # <em>gets the name of the mailing list</em> <li><b>listurl</b> -
  927. # <em>gets the list's listinfo URL</em> <li><b>requestemail</b> -
  928. # <em>gets the list's -request address</em> <li><b>owneremail</b> -
  929. # <em>gets the list's -owner address</em> </ul>
  930. #
  931. # <p>For each text field, you can either enter the text directly into
  932. # the text box, or you can specify a file on your local system to upload
  933. # as the text.
  934. # Should Mailman send an auto-response to mailing list posters?
  935. #
  936. # legal values are:
  937. # 0 = "No"
  938. # 1 = "Yes"
  939. autorespond_postings = 0
  940. # Auto-response text to send to mailing list posters.
  941. autoresponse_postings_text = ''
  942. # Should Mailman send an auto-response to emails sent to the -owner
  943. # address?
  944. #
  945. # legal values are:
  946. # 0 = "No"
  947. # 1 = "Yes"
  948. autorespond_admin = 0
  949. # Auto-response text to send to -owner emails.
  950. autoresponse_admin_text = ''
  951. # Should Mailman send an auto-response to emails sent to the -request
  952. # address? If you choose yes, decide whether you want Mailman to
  953. # discard the original email, or forward it on to the system as a normal
  954. # mail command.
  955. #
  956. # legal values are:
  957. # 0 = "No"
  958. # 1 = "Yes, w/discard"
  959. # 2 = "Yes, w/forward"
  960. autorespond_requests = 0
  961. # Auto-response text to send to -request emails.
  962. autoresponse_request_text = ''
  963. # Number of days between auto-responses to either the mailing list or
  964. # -request/-owner address from the same poster. Set to zero (or
  965. # negative) for no grace period (i.e. auto-respond to every message).
  966. autoresponse_graceperiod = 90
  967. ## Contentfilter options
  968. #
  969. # Policies concerning the content of list traffic.
  970. #
  971. # <p>Content filtering works like this: when a message is received by
  972. # the list and you have enabled content filtering, the individual
  973. # attachments are first compared to the <a
  974. # href="?VARHELP=contentfilter/filter_mime_types">filter types</a>. If
  975. # the attachment type matches an entry in the filter types, it is
  976. # discarded.
  977. #
  978. # <p>Then, if there are <a
  979. # href="?VARHELP=contentfilter/pass_mime_types">pass types</a> defined,
  980. # any attachment type that does <em>not</em> match a pass type is also
  981. # discarded. If there are no pass types defined, this check is skipped.
  982. #
  983. # <p>After this initial filtering, any <tt>multipart</tt> attachments
  984. # that are empty are removed. If the outer message is left empty after
  985. # this filtering, then the whole message is discarded. Then, each
  986. # <tt>multipart/alternative</tt> section will be replaced by just the
  987. # first alternative that is non-empty after filtering.
  988. #
  989. # <p>Finally, any <tt>text/html</tt> parts that are left in the message
  990. # may be converted to <tt>text/plain</tt> if <a
  991. # href="?VARHELP=contentfilter/convert_html_to_plaintext"
  992. # >convert_html_to_plaintext</a> is enabled and the site is configured
  993. # to allow these conversions.
  994. # Should Mailman filter the content of list traffic according to the
  995. # settings below?
  996. #
  997. # legal values are:
  998. # 0 = "No"
  999. # 1 = "Yes"
  1000. filter_content = 0
  1001. # Use this option to remove each message attachment that matches one of
  1002. # these content types. Each line should contain a string naming a MIME
  1003. # type/subtype, e.g. image/gif. Leave off the subtype to remove all
  1004. # parts with a matching major content type, e.g. image.
  1005. #
  1006. # Blank lines are ignored.
  1007. #
  1008. # See also <a href="?VARHELP=contentfilter/pass_mime_types"
  1009. # >pass_mime_types for a content type whitelist.
  1010. filter_mime_types = ''
  1011. # Use this option to remove each message attachment that does not have a
  1012. # matching content type. Requirements and formats are exactly like <a
  1013. # href="?VARHELP=contentfilter/filter_mime_types" >filter_mime_types.
  1014. #
  1015. # Note: if you add entries to this list but don't add multipart to this
  1016. # list, any messages with attachments will be rejected by the pass
  1017. # filter.
  1018. pass_mime_types = """multipart/mixed
  1019. multipart/alternative
  1020. text/plain"""
  1021. # Should Mailman convert text/html parts to plain text? This conversion
  1022. # happens after MIME attachments have been stripped.
  1023. #
  1024. # legal values are:
  1025. # 0 = "No"
  1026. # 1 = "Yes"
  1027. convert_html_to_plaintext = 1
  1028. # One of these actions is take when the message matches one of the
  1029. # content filtering rules, meaning, the top-level content type matches
  1030. # one of the <a href="?VARHELP=contentfilter/filter_mime_types"
  1031. # >filter_mime_types, or the top-level content type does not match one
  1032. # of the <a href="?VARHELP=contentfilter/pass_mime_types"
  1033. # >pass_mime_types, or if after filtering the subparts of the message,
  1034. # the message ends up empty.
  1035. #
  1036. # Note this action is not taken if after filtering the message still
  1037. # contains content. In that case the message is always forwarded on to
  1038. # the list membership.
  1039. #
  1040. # When messages are discarded, a log entry is written containing the
  1041. # Message-ID of the discarded message. When messages are rejected or
  1042. # forwarded to the list owner, a reason for the rejection is included in
  1043. # the bounce message to the original author. When messages are
  1044. # preserved, they are saved in a special queue directory on disk for the
  1045. # site administrator to view (and possibly rescue) but otherwise
  1046. # discarded. This last option is only available if enabled by the site
  1047. # administrator.
  1048. #
  1049. # legal values are:
  1050. # 0 = "Discard"
  1051. # 1 = "Reject"
  1052. # 2 = "Forward to List Owner"
  1053. # 3 = "Preserve"
  1054. filter_action = 0
  1055. ## Topics options
  1056. #
  1057. # List topic keywords
  1058. # The topic filter categorizes each incoming email message according to
  1059. # <a href="http://www.python.org/doc/current/lib/module-re.html">regular
  1060. # expression filters you specify below. If the message's Subject: or
  1061. # Keywords: header contains a match against a topic filter, the message
  1062. # is logically placed into a topic bucket. Each user can then choose to
  1063. # only receive messages from the mailing list for a particular topic
  1064. # bucket (or buckets). Any message not categorized in a topic bucket
  1065. # registered with the user is not delivered to the list.
  1066. #
  1067. # Note that this feature only works with regular delivery, not digest
  1068. # delivery.
  1069. #
  1070. # The body of the message can also be optionally scanned for Subject:
  1071. # and Keywords: headers, as specified by the <a
  1072. # href="?VARHELP=topics/topics_bodylines_limit">topics_bodylines_limit
  1073. # configuration variable.
  1074. #
  1075. # legal values are:
  1076. # 0 = "Disabled"
  1077. # 1 = "Enabled"
  1078. topics_enabled = 0
  1079. # The topic matcher will scan this many lines of the message body
  1080. # looking for topic keyword matches. Body scanning stops when either
  1081. # this many lines have been looked at, or a non-header-like body line is
  1082. # encountered. By setting this value to zero, no body lines will be
  1083. # scanned (i.e. only the Keywords: and Subject: headers will be
  1084. # scanned). By setting this value to a negative number, then all body
  1085. # lines will be scanned until a non-header-like line is encountered.
  1086. #
  1087. topics_bodylines_limit = 5
  1088. # Each topic keyword is actually a regular expression, which is matched
  1089. # against certain parts of a mail message, specifically the Keywords:
  1090. # and Subject: message headers. Note that the first few lines of the
  1091. # body of the message can also contain a Keywords: and Subject: "header"
  1092. # on which matching is also performed.
  1093. topics = []