PageRenderTime 55ms CodeModel.GetById 15ms RepoModel.GetById 0ms app.codeStats 0ms

/branches/modernize_21_webui/mailman/Mailman/Defaults.py.in

#
Autoconf | 1350 lines | 390 code | 196 blank | 764 comment | 5 complexity | 9fcbe51809f62039b17c5f0cc3fb08a0 MD5 | raw file
Possible License(s): GPL-2.0

Large files files are truncated, but you can click here to view the full file

  1. # -*- python -*-
  2. # Copyright (C) 1998-2006 by the Free Software Foundation, Inc.
  3. #
  4. # This program is free software; you can redistribute it and/or
  5. # modify it under the terms of the GNU General Public License
  6. # as published by the Free Software Foundation; either version 2
  7. # of the License, or (at your option) any later version.
  8. #
  9. # This program is distributed in the hope that it will be useful,
  10. # but WITHOUT ANY WARRANTY; without even the implied warranty of
  11. # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
  12. # GNU General Public License for more details.
  13. #
  14. # You should have received a copy of the GNU General Public License
  15. # along with this program; if not, write to the Free Software
  16. # Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301,
  17. # USA.
  18. """Distributed default settings for significant Mailman config variables."""
  19. # NEVER make site configuration changes to this file. ALWAYS make them in
  20. # mm_cfg.py instead, in the designated area. See the comments in that file
  21. # for details.
  22. import os
  23. def seconds(s): return s
  24. def minutes(m): return m * 60
  25. def hours(h): return h * 60 * 60
  26. def days(d): return d * 60 * 60 * 24
  27. # Some convenient constants
  28. try:
  29. True, False
  30. except NameError:
  31. True = 1
  32. False = 0
  33. Yes = yes = On = on = True
  34. No = no = Off = off = False
  35. #####
  36. # General system-wide defaults
  37. #####
  38. # Should image logos be used? Set this to 0 to disable image logos from "our
  39. # sponsors" and just use textual links instead (this will also disable the
  40. # shortcut "favicon"). Otherwise, this should contain the URL base path to
  41. # the logo images (and must contain the trailing slash).. If you want to
  42. # disable Mailman's logo footer altogther, hack
  43. # Mailman/htmlformat.py:MailmanLogo(), which also contains the hardcoded links
  44. # and image names.
  45. IMAGE_LOGOS = '/icons/'
  46. # The name of the Mailman favicon
  47. SHORTCUT_ICON = 'mm-icon.png'
  48. # Don't change MAILMAN_URL, unless you want to point it at one of the mirrors.
  49. MAILMAN_URL = 'http://www.gnu.org/software/mailman/index.html'
  50. #MAILMAN_URL = 'http://www.list.org/'
  51. #MAILMAN_URL = 'http://mailman.sf.net/'
  52. # Mailman needs to know about (at least) two fully-qualified domain names
  53. # (fqdn); 1) the hostname used in your urls, and 2) the hostname used in email
  54. # addresses for your domain. For example, if people visit your Mailman system
  55. # with "http://www.dom.ain/mailman" then your url fqdn is "www.dom.ain", and
  56. # if people send mail to your system via "yourlist@dom.ain" then your email
  57. # fqdn is "dom.ain". DEFAULT_URL_HOST controls the former, and
  58. # DEFAULT_EMAIL_HOST controls the latter. Mailman also needs to know how to
  59. # map from one to the other (this is especially important if you're running
  60. # with virtual domains). You use "add_virtualhost(urlfqdn, emailfqdn)" to add
  61. # new mappings.
  62. #
  63. # If you don't need to change DEFAULT_EMAIL_HOST and DEFAULT_URL_HOST in your
  64. # mm_cfg.py, then you're done; the default mapping is added automatically. If
  65. # however you change either variable in your mm_cfg.py, then be sure to also
  66. # include the following:
  67. #
  68. # add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)
  69. #
  70. # because otherwise the default mappings won't be correct.
  71. DEFAULT_EMAIL_HOST = '@MAILHOST@'
  72. DEFAULT_URL_HOST = '@URLHOST@'
  73. DEFAULT_URL_PATTERN = 'http://%s/mailman/'
  74. # DEFAULT_HOST_NAME has been replaced with DEFAULT_EMAIL_HOST, however some
  75. # sites may have the former in their mm_cfg.py files. If so, we'll believe
  76. # that, otherwise we'll believe DEFAULT_EMAIL_HOST. Same for DEFAULT_URL.
  77. DEFAULT_HOST_NAME = None
  78. DEFAULT_URL = None
  79. HOME_PAGE = 'index.html'
  80. MAILMAN_SITE_LIST = 'mailman'
  81. # Normally when a site administrator authenticates to a web page with the site
  82. # password, they get a cookie which authorizes them as the list admin. It
  83. # makes me nervous to hand out site auth cookies because if this cookie is
  84. # cracked or intercepted, the intruder will have access to every list on the
  85. # site. OTOH, it's dang handy to not have to re-authenticate to every list on
  86. # the site. Set this value to Yes to allow site admin cookies.
  87. ALLOW_SITE_ADMIN_COOKIES = No
  88. # Command that is used to convert text/html parts into plain text. This
  89. # should output results to standard output. %(filename)s will contain the
  90. # name of the temporary file that the program should operate on.
  91. HTML_TO_PLAIN_TEXT_COMMAND = '/usr/bin/lynx -dump %(filename)s'
  92. #####
  93. # Virtual domains
  94. #####
  95. # Set up your virtual host mappings here. This is primarily used for the
  96. # thru-the-web list creation, so its effects are currently fairly limited.
  97. # Use add_virtualhost() call to add new mappings. The keys are strings as
  98. # determined by Utils.get_domain(), the values are as appropriate for
  99. # DEFAULT_HOST_NAME.
  100. VIRTUAL_HOSTS = {}
  101. # When set to Yes, the listinfo and admin overviews of lists on the machine
  102. # will be confined to only those lists whose web_page_url configuration option
  103. # host is included within the URL by which the page is visited - only those
  104. # "on the virtual host". When set to No, all advertised (i.e. public) lists
  105. # are included in the overview.
  106. VIRTUAL_HOST_OVERVIEW = On
  107. # Helper function; use this in your mm_cfg.py files. If optional emailhost is
  108. # omitted it defaults to urlhost with the first name stripped off, e.g.
  109. #
  110. # add_virtualhost('www.dom.ain')
  111. # VIRTUAL_HOST['www.dom.ain']
  112. # ==> 'dom.ain'
  113. #
  114. def add_virtualhost(urlhost, emailhost=None):
  115. DOT = '.'
  116. if emailhost is None:
  117. emailhost = DOT.join(urlhost.split(DOT)[1:])
  118. VIRTUAL_HOSTS[urlhost.lower()] = emailhost.lower()
  119. # And set the default
  120. add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)
  121. # Note that you will want to run bin/fix_url.py to change the domain of an
  122. # existing list. bin/fix_url.py must be run within the bin/withlist script,
  123. # like so: bin/withlist -l -r bin/fix_url.py <listname>
  124. #####
  125. # Spam avoidance defaults
  126. #####
  127. # This variable contains a list of 2-tuple of the format (header, regex) which
  128. # the Mailman/Handlers/SpamDetect.py module uses to match against the current
  129. # message. If the regex matches the given header in the current message, then
  130. # it is flagged as spam. header is case-insensitive and should not include
  131. # the trailing colon. regex is always matched with re.IGNORECASE.
  132. #
  133. # Note that the more searching done, the slower the whole process gets. Spam
  134. # detection is run against all messages coming to either the list, or the
  135. # -owners address, unless the message is explicitly approved.
  136. KNOWN_SPAMMERS = []
  137. #####
  138. # Web UI defaults
  139. #####
  140. # This is where the Cascading Style Sheet for the Mailman Web UI is located
  141. # All of the mailman specific classes begin with mm so that you can point
  142. # this variable to your site's own CSS. If you plan on doing this, you will
  143. # need to copy or create all the classes that are in the default mailman.css
  144. # into your sitewide css
  145. # The default uses an absolute path from the webroot of your server.
  146. # The default CSS is located in INSTALL directory $(PREFIX)/css
  147. # This file will need to be copied to $(WEBROOT)/css/mailman.css
  148. CSS_FILE = '/css/mailman.css'
  149. #####
  150. # Archive defaults
  151. #####
  152. # The url template for the public archives. This will be used in several
  153. # places, including the List-Archive: header, links to the archive on the
  154. # list's listinfo page, and on the list's admin page.
  155. #
  156. # This should be a string with "%(listname)s" somewhere in it. Mailman will
  157. # interpolate the name of the list into this. You can also include a
  158. # "%(hostname)s" in the string, into which Mailman will interpolate
  159. # the host name (usually DEFAULT_URL_HOST).
  160. PUBLIC_ARCHIVE_URL = 'http://%(hostname)s/pipermail/%(listname)s'
  161. # Are archives on or off by default?
  162. DEFAULT_ARCHIVE = On
  163. # Are archives public or private by default?
  164. # 0=public, 1=private
  165. DEFAULT_ARCHIVE_PRIVATE = 0
  166. # ARCHIVE_TO_MBOX
  167. #-1 - do not do any archiving
  168. # 0 - do not archive to mbox, use builtin mailman html archiving only
  169. # 1 - archive to mbox to use an external archiving mechanism only
  170. # 2 - archive to both mbox and builtin mailman html archiving -
  171. # use this to make both external archiving mechanism work and
  172. # mailman's builtin html archiving. the flat mail file can be
  173. # useful for searching, external archivers, etc.
  174. ARCHIVE_TO_MBOX = 2
  175. # 0 - yearly
  176. # 1 - monthly
  177. # 2 - quarterly
  178. # 3 - weekly
  179. # 4 - daily
  180. DEFAULT_ARCHIVE_VOLUME_FREQUENCY = 1
  181. DEFAULT_DIGEST_VOLUME_FREQUENCY = 1
  182. # These variables control the use of an external archiver. Normally if
  183. # archiving is turned on (see ARCHIVE_TO_MBOX above and the list's archive*
  184. # attributes) the internal Pipermail archiver is used. This is the default if
  185. # both of these variables are set to No. When either is set, the value should
  186. # be a shell command string which will get passed to os.popen(). This string
  187. # can contain the following substitution strings:
  188. #
  189. # %(listname)s -- gets the internal name of the list
  190. # %(hostname)s -- gets the email hostname for the list
  191. #
  192. # being archived will be substituted for this. Please note that os.popen() is
  193. # used.
  194. #
  195. # Note that if you set one of these variables, you should set both of them
  196. # (they can be the same string). This will mean your external archiver will
  197. # be used regardless of whether public or private archives are selected.
  198. PUBLIC_EXTERNAL_ARCHIVER = No
  199. PRIVATE_EXTERNAL_ARCHIVER = No
  200. # A filter module that converts from multipart messages to "flat" messages
  201. # (i.e. containing a single payload). This is required for Pipermail, and you
  202. # may want to set it to 0 for external archivers. You can also replace it
  203. # with your own module as long as it contains a process() function that takes
  204. # a MailList object and a Message object. It should raise
  205. # Errors.DiscardMessage if it wants to throw the message away. Otherwise it
  206. # should modify the Message object as necessary.
  207. ARCHIVE_SCRUBBER = 'Mailman.Handlers.Scrubber'
  208. # Control parameter whether Mailman.Handlers.Scrubber should use message
  209. # attachment's filename as is indicated by the filename parameter or use
  210. # 'attachement-xxx' instead. The default is set True because the applications
  211. # on PC and Mac begin to use longer non-ascii filenames. Historically, it
  212. # was set False in 2.1.6 for backward compatiblity but it was reset to True
  213. # for safer operation in mailman-2.1.7.
  214. SCRUBBER_DONT_USE_ATTACHMENT_FILENAME = True
  215. # Use of attachment filename extension per se is may be dangerous because
  216. # virus fakes it. You can set this True if you filter the attachment by
  217. # filename extension
  218. SCRUBBER_USE_ATTACHMENT_FILENAME_EXTENSION = False
  219. # This variable defines what happens to text/html subparts. They can be
  220. # stripped completely, escaped, or filtered through an external program. The
  221. # legal values are:
  222. # 0 - Strip out text/html parts completely, leaving a notice of the removal in
  223. # the message. If the outer part is text/html, the entire message is
  224. # discarded.
  225. # 1 - Remove any embedded text/html parts, leaving them as HTML-escaped
  226. # attachments which can be separately viewed. Outer text/html parts are
  227. # simply HTML-escaped.
  228. # 2 - Leave it inline, but HTML-escape it
  229. # 3 - Remove text/html as attachments but don't HTML-escape them. Note: this
  230. # is very dangerous because it essentially means anybody can send an HTML
  231. # email to your site containing evil JavaScript or web bugs, or other
  232. # nasty things, and folks viewing your archives will be susceptible. You
  233. # should only consider this option if you do heavy moderation of your list
  234. # postings.
  235. #
  236. # Note: given the current archiving code, it is not possible to leave
  237. # text/html parts inline and un-escaped. I wouldn't think it'd be a good idea
  238. # to do anyway.
  239. #
  240. # The value can also be a string, in which case it is the name of a command to
  241. # filter the HTML page through. The resulting output is left in an attachment
  242. # or as the entirety of the message when the outer part is text/html. The
  243. # format of the string must include a "%(filename)s" which will contain the
  244. # name of the temporary file that the program should operate on. It should
  245. # write the processed message to stdout. Set this to
  246. # HTML_TO_PLAIN_TEXT_COMMAND to specify an HTML to plain text conversion
  247. # program.
  248. ARCHIVE_HTML_SANITIZER = 1
  249. # Set this to Yes to enable gzipping of the downloadable archive .txt file.
  250. # Note that this is /extremely/ inefficient, so an alternative is to just
  251. # collect the messages in the associated .txt file and run a cron job every
  252. # night to generate the txt.gz file. See cron/nightly_gzip for details.
  253. GZIP_ARCHIVE_TXT_FILES = No
  254. # This sets the default `clobber date' policy for the archiver. When a
  255. # message is to be archived either by Pipermail or an external archiver,
  256. # Mailman can modify the Date: header to be the date the message was received
  257. # instead of the Date: in the original message. This is useful if you
  258. # typically receive messages with outrageous dates. Set this to 0 to retain
  259. # the date of the original message, or to 1 to always clobber the date. Set
  260. # it to 2 to perform `smart overrides' on the date; when the date is outside
  261. # ARCHIVER_ALLOWABLE_SANE_DATE_SKEW (either too early or too late), then the
  262. # received date is substituted instead.
  263. ARCHIVER_CLOBBER_DATE_POLICY = 2
  264. ARCHIVER_ALLOWABLE_SANE_DATE_SKEW = days(15)
  265. # Pipermail archives contain the raw email addresses of the posting authors.
  266. # Some view this as a goldmine for spam harvesters. Set this to Yes to
  267. # moderately obscure email addresses, but note that this breaks mailto: URLs
  268. # in the archives too.
  269. ARCHIVER_OBSCURES_EMAILADDRS = Yes
  270. # Pipermail assumes that message bodies contain US-ASCII text.
  271. # Change this option to define a different character set to be used as
  272. # the default character set for the archive. The term "character set"
  273. # is used in MIME to refer to a method of converting a sequence of
  274. # octets into a sequence of characters. If you change the default
  275. # charset, you might need to add it to VERBATIM_ENCODING below.
  276. DEFAULT_CHARSET = None
  277. # Most character set encodings require special HTML entity characters to be
  278. # quoted, otherwise they won't look right in the Pipermail archives. However
  279. # some character sets must not quote these characters so that they can be
  280. # rendered properly in the browsers. The primary issue is multi-byte
  281. # encodings where the octet 0x26 does not always represent the & character.
  282. # This variable contains a list of such characters sets which are not
  283. # HTML-quoted in the archives.
  284. VERBATIM_ENCODING = ['iso-2022-jp']
  285. # When the archive is public, should Mailman also make the raw Unix mbox file
  286. # publically available?
  287. PUBLIC_MBOX = No
  288. #####
  289. # Delivery defaults
  290. #####
  291. # Final delivery module for outgoing mail. This handler is used for message
  292. # delivery to the list via the smtpd, and to an individual user. This value
  293. # must be a string naming a module in the Mailman.Handlers package.
  294. #
  295. # WARNING: Sendmail has security holes and should be avoided. In fact, you
  296. # must read the Mailman/Handlers/Sendmail.py file before it will work for
  297. # you.
  298. #
  299. #DELIVERY_MODULE = 'Sendmail'
  300. DELIVERY_MODULE = 'SMTPDirect'
  301. # MTA should name a module in Mailman/MTA which provides the MTA specific
  302. # functionality for creating and removing lists. Some MTAs like Exim can be
  303. # configured to automatically recognize new lists, in which case the MTA
  304. # variable should be set to None. Use 'Manual' to print new aliases to
  305. # standard out (or send an email to the site list owner) for manual twiddling
  306. # of an /etc/aliases style file. Use 'Postfix' if you are using the Postfix
  307. # MTA -- but then also see POSTFIX_STYLE_VIRTUAL_DOMAINS.
  308. MTA = 'Manual'
  309. # If you set MTA='Postfix', then you also want to set the following variable,
  310. # depending on whether you're using virtual domains in Postfix, and which
  311. # style of virtual domain you're using. Set this to the empty list if you're
  312. # not using virtual domains in Postfix, or if you're using Sendmail-style
  313. # virtual domains (where all addresses are visible in all domains). If you're
  314. # using Postfix-style virtual domains, where aliases should only show up in
  315. # the virtual domain, set this variable to the list of host_name values to
  316. # write separate virtual entries for. I.e. if you run dom1.ain, dom2.ain, and
  317. # dom3.ain, but only dom2 and dom3 are virtual, set this variable to the list
  318. # ['dom2.ain', 'dom3.ain']. Matches are done against the host_name attribute
  319. # of the mailing lists. See the Postfix section of the installation manual
  320. # for details.
  321. POSTFIX_STYLE_VIRTUAL_DOMAINS = []
  322. # These variables describe the program to use for regenerating the aliases.db
  323. # and virtual-mailman.db files, respectively, from the associated plain text
  324. # files. The file being updated will be appended to this string (with a
  325. # separating space), so it must be appropriate for os.system().
  326. POSTFIX_ALIAS_CMD = '/usr/sbin/postalias'
  327. POSTFIX_MAP_CMD = '/usr/sbin/postmap'
  328. # Ceiling on the number of recipients that can be specified in a single SMTP
  329. # transaction. Set to 0 to submit the entire recipient list in one
  330. # transaction. Only used with the SMTPDirect DELIVERY_MODULE.
  331. SMTP_MAX_RCPTS = 500
  332. # Ceiling on the number of SMTP sessions to perform on a single socket
  333. # connection. Some MTAs have limits. Set this to 0 to do as many as we like
  334. # (i.e. your MTA has no limits). Set this to some number great than 0 and
  335. # Mailman will close the SMTP connection and re-open it after this number of
  336. # consecutive sessions.
  337. SMTP_MAX_SESSIONS_PER_CONNECTION = 0
  338. # Maximum number of simultaneous subthreads that will be used for SMTP
  339. # delivery. After the recipients list is chunked according to SMTP_MAX_RCPTS,
  340. # each chunk is handed off to the smptd by a separate such thread. If your
  341. # Python interpreter was not built for threads, this feature is disabled. You
  342. # can explicitly disable it in all cases by setting MAX_DELIVERY_THREADS to
  343. # 0. This feature is only supported with the SMTPDirect DELIVERY_MODULE.
  344. #
  345. # NOTE: This is an experimental feature and limited testing shows that it may
  346. # in fact degrade performance, possibly due to Python's global interpreter
  347. # lock. Use with caution.
  348. MAX_DELIVERY_THREADS = 0
  349. # SMTP host and port, when DELIVERY_MODULE is 'SMTPDirect'. Make sure the
  350. # host exists and is resolvable (i.e., if it's the default of "localhost" be
  351. # sure there's a localhost entry in your /etc/hosts file!)
  352. SMTPHOST = 'localhost'
  353. SMTPPORT = 0 # default from smtplib
  354. # Command for direct command pipe delivery to sendmail compatible program,
  355. # when DELIVERY_MODULE is 'Sendmail'.
  356. SENDMAIL_CMD = '/usr/lib/sendmail'
  357. # Set these variables if you need to authenticate to your NNTP server for
  358. # Usenet posting or reading. If no authentication is necessary, specify None
  359. # for both variables.
  360. NNTP_USERNAME = None
  361. NNTP_PASSWORD = None
  362. # Set this if you have an NNTP server you prefer gatewayed lists to use.
  363. DEFAULT_NNTP_HOST = ''
  364. # These variables controls how headers must be cleansed in order to be
  365. # accepted by your NNTP server. Some servers like INN reject messages
  366. # containing prohibited headers, or duplicate headers. The NNTP server may
  367. # reject the message for other reasons, but there's little that can be
  368. # programmatically done about that. See Mailman/Queue/NewsRunner.py
  369. #
  370. # First, these headers (case ignored) are removed from the original message.
  371. NNTP_REMOVE_HEADERS = ['nntp-posting-host', 'nntp-posting-date', 'x-trace',
  372. 'x-complaints-to', 'xref', 'date-received', 'posted',
  373. 'posting-version', 'relay-version', 'received']
  374. # Next, these headers are left alone, unless there are duplicates in the
  375. # original message. Any second and subsequent headers are rewritten to the
  376. # second named header (case preserved).
  377. NNTP_REWRITE_DUPLICATE_HEADERS = [
  378. ('to', 'X-Original-To'),
  379. ('cc', 'X-Original-Cc'),
  380. ('content-transfer-encoding', 'X-Original-Content-Transfer-Encoding'),
  381. ('mime-version', 'X-MIME-Version'),
  382. ]
  383. # All `normal' messages which are delivered to the entire list membership go
  384. # through this pipeline of handler modules. Lists themselves can override the
  385. # global pipeline by defining a `pipeline' attribute.
  386. GLOBAL_PIPELINE = [
  387. # These are the modules that do tasks common to all delivery paths.
  388. 'SpamDetect',
  389. 'Approve',
  390. 'Replybot',
  391. 'Moderate',
  392. 'Hold',
  393. 'MimeDel',
  394. 'Scrubber',
  395. 'Emergency',
  396. 'Tagger',
  397. 'CalcRecips',
  398. 'AvoidDuplicates',
  399. 'Cleanse',
  400. 'CleanseDKIM',
  401. 'CookHeaders',
  402. # And now we send the message to the digest mbox file, and to the arch and
  403. # news queues. Runners will provide further processing of the message,
  404. # specific to those delivery paths.
  405. 'ToDigest',
  406. 'ToArchive',
  407. 'ToUsenet',
  408. # Now we'll do a few extra things specific to the member delivery
  409. # (outgoing) path, finally leaving the message in the outgoing queue.
  410. 'AfterDelivery',
  411. 'Acknowledge',
  412. 'ToOutgoing',
  413. ]
  414. # This is the pipeline which messages sent to the -owner address go through
  415. OWNER_PIPELINE = [
  416. 'SpamDetect',
  417. 'Replybot',
  418. 'CleanseDKIM',
  419. 'OwnerRecips',
  420. 'ToOutgoing',
  421. ]
  422. # This defines syslog() format strings for the SMTPDirect delivery module (see
  423. # DELIVERY_MODULE above). Valid %()s string substitutions include:
  424. #
  425. # time -- the time in float seconds that it took to complete the smtp
  426. # hand-off of the message from Mailman to your smtpd.
  427. #
  428. # size -- the size of the entire message, in bytes
  429. #
  430. # #recips -- the number of actual recipients for this message.
  431. #
  432. # #refused -- the number of smtp refused recipients (use this only in
  433. # SMTP_LOG_REFUSED).
  434. #
  435. # listname -- the `internal' name of the mailing list for this posting
  436. #
  437. # msg_<header> -- the value of the delivered message's given header. If
  438. # the message had no such header, then "n/a" will be used. Note though
  439. # that if the message had multiple such headers, then it is undefined
  440. # which will be used.
  441. #
  442. # allmsg_<header> - Same as msg_<header> above, but if there are multiple
  443. # such headers in the message, they will all be printed, separated by
  444. # comma-space.
  445. #
  446. # sender -- the "sender" of the messages, which will be the From: or
  447. # envelope-sender as determeined by the USE_ENVELOPE_SENDER variable
  448. # below.
  449. #
  450. # The format of the entries is a 2-tuple with the first element naming the
  451. # file in logs/ to print the message to, and the second being a format string
  452. # appropriate for Python's %-style string interpolation. The file name is
  453. # arbitrary; qfiles/<name> will be created automatically if it does not
  454. # exist.
  455. # The format of the message printed for every delivered message, regardless of
  456. # whether the delivery was successful or not. Set to None to disable the
  457. # printing of this log message.
  458. SMTP_LOG_EVERY_MESSAGE = (
  459. 'smtp',
  460. '%(msg_message-id)s smtp to %(listname)s for %(#recips)d recips, completed in %(time).3f seconds')
  461. # This will only be printed if there were no immediate smtp failures.
  462. # Mutually exclusive with SMTP_LOG_REFUSED.
  463. SMTP_LOG_SUCCESS = (
  464. 'post',
  465. 'post to %(listname)s from %(sender)s, size=%(size)d, message-id=%(msg_message-id)s, success')
  466. # This will only be printed if there were any addresses which encountered an
  467. # immediate smtp failure. Mutually exclusive with SMTP_LOG_SUCCESS.
  468. SMTP_LOG_REFUSED = (
  469. 'post',
  470. 'post to %(listname)s from %(sender)s, size=%(size)d, message-id=%(msg_message-id)s, %(#refused)d failures')
  471. # This will be logged for each specific recipient failure. Additional %()s
  472. # keys are:
  473. #
  474. # recipient -- the failing recipient address
  475. # failcode -- the smtp failure code
  476. # failmsg -- the actual smtp message, if available
  477. SMTP_LOG_EACH_FAILURE = (
  478. 'smtp-failure',
  479. 'delivery to %(recipient)s failed with code %(failcode)d: %(failmsg)s')
  480. # These variables control the format and frequency of VERP-like delivery for
  481. # better bounce detection. VERP is Variable Envelope Return Path, defined
  482. # here:
  483. #
  484. # http://cr.yp.to/proto/verp.txt
  485. #
  486. # This involves encoding the address of the recipient as we (Mailman) know it
  487. # into the envelope sender address (i.e. the SMTP `MAIL FROM:' address).
  488. # Thus, no matter what kind of forwarding the recipient has in place, should
  489. # it eventually bounce, we will receive an unambiguous notice of the bouncing
  490. # address.
  491. #
  492. # However, we're technically only "VERP-like" because we're doing the envelope
  493. # sender encoding in Mailman, not in the MTA. We do require cooperation from
  494. # the MTA, so you must be sure your MTA can be configured for extended address
  495. # semantics.
  496. #
  497. # The first variable describes how to encode VERP envelopes. It must contain
  498. # these three string interpolations:
  499. #
  500. # %(bounces)s -- the list-bounces mailbox will be set here
  501. # %(mailbox)s -- the recipient's mailbox will be set here
  502. # %(host)s -- the recipient's host name will be set here
  503. #
  504. # This example uses the default below.
  505. #
  506. # FQDN list address is: mylist@dom.ain
  507. # Recipient is: aperson@a.nother.dom
  508. #
  509. # The envelope sender will be mylist-bounces+aperson=a.nother.dom@dom.ain
  510. #
  511. # Note that your MTA /must/ be configured to deliver such an addressed message
  512. # to mylist-bounces!
  513. VERP_FORMAT = '%(bounces)s+%(mailbox)s=%(host)s'
  514. # The second describes a regular expression to unambiguously decode such an
  515. # address, which will be placed in the To: header of the bounce message by the
  516. # bouncing MTA. Getting this right is critical -- and tricky. Learn your
  517. # Python regular expressions. It must define exactly three named groups,
  518. # bounces, mailbox and host, with the same definition as above. It will be
  519. # compiled case-insensitively.
  520. VERP_REGEXP = r'^(?P<bounces>[^+]+?)\+(?P<mailbox>[^=]+)=(?P<host>[^@]+)@.*$'
  521. # VERP format and regexp for probe messages
  522. VERP_PROBE_FORMAT = '%(bounces)s+%(token)s'
  523. VERP_PROBE_REGEXP = r'^(?P<bounces>[^+]+?)\+(?P<token>[^@]+)@.*$'
  524. # Set this Yes to activate VERP probe for disabling by bounce
  525. VERP_PROBES = No
  526. # A perfect opportunity for doing VERP is the password reminders, which are
  527. # already addressed individually to each recipient. Set this to Yes to enable
  528. # VERPs on all password reminders.
  529. VERP_PASSWORD_REMINDERS = No
  530. # Another good opportunity is when regular delivery is personalized. Here
  531. # again, we're already incurring the performance hit for addressing each
  532. # individual recipient. Set this to Yes to enable VERPs on all personalized
  533. # regular deliveries (personalized digests aren't supported yet).
  534. VERP_PERSONALIZED_DELIVERIES = No
  535. # And finally, we can VERP normal, non-personalized deliveries. However,
  536. # because it can be a significant performance hit, we allow you to decide how
  537. # often to VERP regular deliveries. This is the interval, in number of
  538. # messages, to do a VERP recipient address. The same variable controls both
  539. # regular and digest deliveries. Set to 0 to disable occasional VERPs, set to
  540. # 1 to VERP every delivery, or to some number > 1 for only occasional VERPs.
  541. VERP_DELIVERY_INTERVAL = 0
  542. # For nicer confirmation emails, use a VERP-like format which encodes the
  543. # confirmation cookie in the reply address. This lets us put a more user
  544. # friendly Subject: on the message, but requires cooperation from the MTA.
  545. # Format is like VERP_FORMAT above, but with the following substitutions:
  546. #
  547. # %(addr)s -- the list-confirm mailbox will be set here
  548. # %(cookie)s -- the confirmation cookie will be set here
  549. VERP_CONFIRM_FORMAT = '%(addr)s+%(cookie)s'
  550. # This is analogous to VERP_REGEXP, but for splitting apart the
  551. # VERP_CONFIRM_FORMAT. MUAs have been observed that mung
  552. # From: local_part@host
  553. # into
  554. # To: "local_part" <local_part@host>
  555. # when replying, so we skip everything up to '<' if any.
  556. VERP_CONFIRM_REGEXP = r'^(.*<)?(?P<addr>[^+]+?)\+(?P<cookie>[^@]+)@.*$'
  557. # Set this to Yes to enable VERP-like (more user friendly) confirmations
  558. VERP_CONFIRMATIONS = No
  559. # This is the maximum number of automatic responses sent to an address because
  560. # of -request messages or posting hold messages. This limit prevents response
  561. # loops between Mailman and misconfigured remote email robots. Mailman
  562. # already inhibits automatic replies to any message labeled with a header
  563. # "Precendence: bulk|list|junk". This is a fallback safety valve so it should
  564. # be set fairly high. Set to 0 for no limit (probably useful only for
  565. # debugging).
  566. MAX_AUTORESPONSES_PER_DAY = 10
  567. #####
  568. # Qrunner defaults
  569. #####
  570. # Which queues should the qrunner master watchdog spawn? This is a list of
  571. # 2-tuples containing the name of the qrunner class (which must live in a
  572. # module of the same name within the Mailman.Queue package), and the number of
  573. # parallel processes to fork for each qrunner. If more than one process is
  574. # used, each will take an equal subdivision of the hash space.
  575. # BAW: Eventually we may support weighted hash spaces.
  576. # BAW: Although not enforced, the # of slices must be a power of 2
  577. QRUNNERS = [
  578. ('ArchRunner', 1), # messages for the archiver
  579. ('BounceRunner', 1), # for processing the qfile/bounces directory
  580. ('CommandRunner', 1), # commands and bounces from the outside world
  581. ('IncomingRunner', 1), # posts from the outside world
  582. ('NewsRunner', 1), # outgoing messages to the nntpd
  583. ('OutgoingRunner', 1), # outgoing messages to the smtpd
  584. ('VirginRunner', 1), # internally crafted (virgin birth) messages
  585. ('RetryRunner', 1), # retry temporarily failed deliveries
  586. ]
  587. # Set this to Yes to use the `Maildir' delivery option. If you change this
  588. # you will need to re-run bin/genaliases for MTAs that don't use list
  589. # auto-detection.
  590. #
  591. # WARNING: If you want to use Maildir delivery, you /must/ start Mailman's
  592. # qrunner as root, or you will get permission problems.
  593. #
  594. # NOTE: Maildir delivery is experimental for Mailman 2.1.
  595. USE_MAILDIR = No
  596. # NOTE: If you set USE_MAILDIR = Yes, add the following line to your mm_cfg.py
  597. # file (uncommented of course!)
  598. # QRUNNERS.append(('MaildirRunner', 1))
  599. # After processing every file in the qrunner's slice, how long should the
  600. # runner sleep for before checking the queue directory again for new files?
  601. # This can be a fraction of a second, or zero to check immediately
  602. # (essentially busy-loop as fast as possible).
  603. QRUNNER_SLEEP_TIME = seconds(1)
  604. # When a message that is unparsable (by the email package) is received, what
  605. # should we do with it? The most common cause of unparsable messages is
  606. # broken MIME encapsulation, and the most common cause of that is viruses like
  607. # Nimda. Set this variable to No to discard such messages, or to Yes to store
  608. # them in qfiles/bad subdirectory.
  609. QRUNNER_SAVE_BAD_MESSAGES = Yes
  610. # This flag causes Mailman to fsync() its data files after writing and
  611. # flushing its contents. While this ensures the data is written to disk,
  612. # avoiding data loss, it may be a performance killer. Note that this flag
  613. # affects both message pickles and MailList config.pck files.
  614. SYNC_AFTER_WRITE = No
  615. #####
  616. # General defaults
  617. #####
  618. # The default language for this server. Whenever we can't figure out the list
  619. # context or user context, we'll fall back to using this language. See
  620. # LC_DESCRIPTIONS below for legal values.
  621. DEFAULT_SERVER_LANGUAGE = 'en'
  622. # When allowing only members to post to a mailing list, how is the sender of
  623. # the message determined? If this variable is set to Yes, then first the
  624. # message's envelope sender is used, with a fallback to the sender if there is
  625. # no envelope sender. Set this variable to No to always use the sender.
  626. #
  627. # The envelope sender is set by the SMTP delivery and is thus less easily
  628. # spoofed than the sender, which is typically just taken from the From: header
  629. # and thus easily spoofed by the end-user. However, sometimes the envelope
  630. # sender isn't set correctly and this will manifest itself by postings being
  631. # held for approval even if they appear to come from a list member. If you
  632. # are having this problem, set this variable to No, but understand that some
  633. # spoofed messages may get through.
  634. USE_ENVELOPE_SENDER = No
  635. # Membership tests for posting purposes are usually performed by looking at a
  636. # set of headers, passing the test if any of their values match a member of
  637. # the list. Headers are checked in the order given in this variable. The
  638. # value None means use the From_ (envelope sender) header. Field names are
  639. # case insensitive.
  640. SENDER_HEADERS = ('from', None, 'reply-to', 'sender')
  641. # How many members to display at a time on the admin cgi to unsubscribe them
  642. # or change their options?
  643. DEFAULT_ADMIN_MEMBER_CHUNKSIZE = 30
  644. # how many bytes of a held message post should be displayed in the admindb web
  645. # page? Use a negative number to indicate the entire message, regardless of
  646. # size (though this will slow down rendering those pages).
  647. ADMINDB_PAGE_TEXT_LIMIT = 4096
  648. # Set this variable to Yes to allow list owners to delete their own mailing
  649. # lists. You may not want to give them this power, in which case, setting
  650. # this variable to No instead requires list removal to be done by the site
  651. # administrator, via the command line script bin/rmlist.
  652. OWNERS_CAN_DELETE_THEIR_OWN_LISTS = No
  653. # Set this variable to Yes to allow list owners to set the "personalized"
  654. # flags on their mailing lists. Turning these on tells Mailman to send
  655. # separate email messages to each user instead of batching them together for
  656. # delivery to the MTA. This gives each member a more personalized message,
  657. # but can have a heavy impact on the performance of your system.
  658. OWNERS_CAN_ENABLE_PERSONALIZATION = No
  659. # Should held messages be saved on disk as Python pickles or as plain text?
  660. # The former is more efficient since we don't need to go through the
  661. # parse/generate roundtrip each time, but the latter might be preferred if you
  662. # want to edit the held message on disk.
  663. HOLD_MESSAGES_AS_PICKLES = Yes
  664. # This variable controls the order in which list-specific category options are
  665. # presented in the admin cgi page.
  666. ADMIN_CATEGORIES = [
  667. # First column
  668. 'general', 'passwords', 'language', 'members', 'nondigest', 'digest',
  669. # Second column
  670. 'privacy', 'bounce', 'archive', 'gateway', 'autoreply',
  671. 'contentfilter', 'topics',
  672. ]
  673. # See "Bitfield for user options" below; make this a sum of those options, to
  674. # make all new members of lists start with those options flagged. We assume
  675. # by default that people don't want to receive two copies of posts. Note
  676. # however that the member moderation flag's initial value is controlled by the
  677. # list's config variable default_member_moderation.
  678. DEFAULT_NEW_MEMBER_OPTIONS = 256
  679. # Specify the type of passwords to use, when Mailman generates the passwords
  680. # itself, as would be the case for membership requests where the user did not
  681. # fill in a password, or during list creation, when auto-generation of admin
  682. # passwords was selected.
  683. #
  684. # Set this value to Yes for classic Mailman user-friendly(er) passwords.
  685. # These generate semi-pronounceable passwords which are easier to remember.
  686. # Set this value to No to use more cryptographically secure, but harder to
  687. # remember, passwords -- if your operating system and Python version support
  688. # the necessary feature (specifically that /dev/urandom be available).
  689. USER_FRIENDLY_PASSWORDS = Yes
  690. # This value specifies the default lengths of member and list admin passwords
  691. MEMBER_PASSWORD_LENGTH = 8
  692. ADMIN_PASSWORD_LENGTH = 10
  693. #####
  694. # List defaults. NOTE: Changing these values does NOT change the
  695. # configuration of an existing list. It only defines the default for new
  696. # lists you subsequently create.
  697. #####
  698. # Should a list, by default be advertised? What is the default maximum number
  699. # of explicit recipients allowed? What is the default maximum message size
  700. # allowed?
  701. DEFAULT_LIST_ADVERTISED = Yes
  702. DEFAULT_MAX_NUM_RECIPIENTS = 10
  703. DEFAULT_MAX_MESSAGE_SIZE = 40 # KB
  704. # These format strings will be expanded w.r.t. the dictionary for the
  705. # mailing list instance.
  706. DEFAULT_SUBJECT_PREFIX = "[%(real_name)s] "
  707. # DEFAULT_SUBJECT_PREFIX = "[%(real_name)s %%d]" # for numbering
  708. DEFAULT_MSG_HEADER = ""
  709. DEFAULT_MSG_FOOTER = """_______________________________________________
  710. %(real_name)s mailing list
  711. %(real_name)s@%(host_name)s
  712. %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
  713. """
  714. # Where to put subject prefix for 'Re:' messages:
  715. #
  716. # old style: Re: [prefix] test
  717. # new style: [prefix 123] Re: test ... (number is optional)
  718. #
  719. # Old style is default for backward compatibility. New style is forced if a
  720. # list owner set %d (numbering) in prefix. If the site owner had applied new
  721. # style patch (from SF patch area) before, he/she may want to set this No in
  722. # mm_cfg.py.
  723. OLD_STYLE_PREFIXING = Yes
  724. # Scrub regular delivery
  725. DEFAULT_SCRUB_NONDIGEST = False
  726. # Mail command processor will ignore mail command lines after designated max.
  727. DEFAULT_MAIL_COMMANDS_MAX_LINES = 25
  728. # Is the list owner notified of admin requests immediately by mail, as well as
  729. # by daily pending-request reminder?
  730. DEFAULT_ADMIN_IMMED_NOTIFY = Yes
  731. # Is the list owner notified of subscribes/unsubscribes?
  732. DEFAULT_ADMIN_NOTIFY_MCHANGES = No
  733. # Discard held messages after this days
  734. DEFAULT_MAX_DAYS_TO_HOLD = 0
  735. # Should list members, by default, have their posts be moderated?
  736. DEFAULT_DEFAULT_MEMBER_MODERATION = No
  737. # Should non-member posts which are auto-discarded also be forwarded to the
  738. # moderators?
  739. DEFAULT_FORWARD_AUTO_DISCARDS = Yes
  740. # What shold happen to non-member posts which are do not match explicit
  741. # non-member actions?
  742. # 0 = Accept
  743. # 1 = Hold
  744. # 2 = Reject
  745. # 3 = Discard
  746. DEFAULT_GENERIC_NONMEMBER_ACTION = 1
  747. # Bounce if 'To:', 'Cc:', or 'Resent-To:' fields don't explicitly name list?
  748. # This is an anti-spam measure
  749. DEFAULT_REQUIRE_EXPLICIT_DESTINATION = Yes
  750. # Alternate names acceptable as explicit destinations for this list.
  751. DEFAULT_ACCEPTABLE_ALIASES ="""
  752. """
  753. # For mailing lists that have only other mailing lists for members:
  754. DEFAULT_UMBRELLA_LIST = No
  755. # For umbrella lists, the suffix for the account part of address for
  756. # administrative notices (subscription confirmations, password reminders):
  757. DEFAULT_UMBRELLA_MEMBER_ADMIN_SUFFIX = "-owner"
  758. # This variable controls whether monthly password reminders are sent.
  759. DEFAULT_SEND_REMINDERS = Yes
  760. # Send welcome messages to new users?
  761. DEFAULT_SEND_WELCOME_MSG = Yes
  762. # Send goodbye messages to unsubscribed members?
  763. DEFAULT_SEND_GOODBYE_MSG = Yes
  764. # Wipe sender information, and make it look like the list-admin
  765. # address sends all messages
  766. DEFAULT_ANONYMOUS_LIST = No
  767. # {header-name: regexp} spam filtering - we include some for example sake.
  768. DEFAULT_BOUNCE_MATCHING_HEADERS = """
  769. # Lines that *start* with a '#' are comments.
  770. to: friend@public.com
  771. message-id: relay.comanche.denmark.eu
  772. from: list@listme.com
  773. from: .*@uplinkpro.com
  774. """
  775. # Mailman can be configured to "munge" Reply-To: headers for any passing
  776. # messages. One the one hand, there are a lot of good reasons not to munge
  777. # Reply-To: but on the other, people really seem to want this feature. See
  778. # the help for reply_goes_to_list in the web UI for links discussing the
  779. # issue.
  780. # 0 - Reply-To: not munged
  781. # 1 - Reply-To: set back to the list
  782. # 2 - Reply-To: set to an explicit value (reply_to_address)
  783. DEFAULT_REPLY_GOES_TO_LIST = 0
  784. # Mailman can be configured to strip any existing Reply-To: header, or simply
  785. # extend any existing Reply-To: with one based on the above setting.
  786. DEFAULT_FIRST_STRIP_REPLY_TO = No
  787. # SUBSCRIBE POLICY
  788. # 0 - open list (only when ALLOW_OPEN_SUBSCRIBE is set to 1) **
  789. # 1 - confirmation required for subscribes
  790. # 2 - admin approval required for subscribes
  791. # 3 - both confirmation and admin approval required
  792. #
  793. # ** please do not choose option 0 if you are not allowing open
  794. # subscribes (next variable)
  795. DEFAULT_SUBSCRIBE_POLICY = 1
  796. # Does this site allow completely unchecked subscriptions?
  797. ALLOW_OPEN_SUBSCRIBE = No
  798. # The default policy for unsubscriptions. 0 (unmoderated unsubscribes) is
  799. # highly recommended!
  800. # 0 - unmoderated unsubscribes
  801. # 1 - unsubscribes require approval
  802. DEFAULT_UNSUBSCRIBE_POLICY = 0
  803. # Private_roster == 0: anyone can see, 1: members only, 2: admin only.
  804. DEFAULT_PRIVATE_ROSTER = 1
  805. # When exposing members, make them unrecognizable as email addrs, so
  806. # web-spiders can't pick up addrs for spam purposes.
  807. DEFAULT_OBSCURE_ADDRESSES = Yes
  808. # RFC 2369 defines List-* headers which are added to every message sent
  809. # through to the mailing list membership. These are a very useful aid to end
  810. # users and should always be added. However, not all MUAs are compliant and
  811. # if a list's membership has many such users, they may clamor for these
  812. # headers to be suppressed. By setting this variable to Yes, list owners will
  813. # be given the option to suppress these headers. By setting it to No, list
  814. # owners will not be given the option to suppress these headers (although some
  815. # header suppression may still take place, i.e. for announce-only lists, or
  816. # lists with no archives).
  817. ALLOW_RFC2369_OVERRIDES = Yes
  818. # Defaults for content filtering on mailing lists. DEFAULT_FILTER_CONTENT is
  819. # a flag which if set to true, turns on content filtering.
  820. DEFAULT_FILTER_CONTENT = No
  821. # DEFAULT_FILTER_MIME_TYPES is a list of MIME types to be removed. This is a
  822. # list of strings of the format "maintype/subtype" or simply "maintype".
  823. # E.g. "text/html" strips all html attachments while "image" strips all image
  824. # types regardless of subtype (jpeg, gif, etc.).
  825. DEFAULT_FILTER_MIME_TYPES = []
  826. # DEFAULT_PASS_MIME_TYPES is a list of MIME types to be passed through.
  827. # Format is the same as DEFAULT_FILTER_MIME_TYPES
  828. DEFAULT_PASS_MIME_TYPES = ['multipart/mixed',
  829. 'multipart/alternative',
  830. 'text/plain']
  831. # DEFAULT_FILTER_FILENAME_EXTENSIONS is a list of filename extensions to be
  832. # removed. It is useful because many viruses fake their content-type as
  833. # harmless ones while keep their extension as executable and expect to be
  834. # executed when victims 'open' them.
  835. DEFAULT_FILTER_FILENAME_EXTENSIONS = [
  836. 'exe', 'bat', 'cmd', 'com', 'pif', 'scr', 'vbs', 'cpl'
  837. ]
  838. # DEFAULT_PASS_FILENAME_EXTENSIONS is a list of filename extensions to be
  839. # passed through. Format is the same as DEFAULT_FILTER_FILENAME_EXTENSIONS.
  840. DEFAULT_PASS_FILENAME_EXTENSIONS = []
  841. # Replace multipart/alternative with its first alternative.
  842. DEFAULT_COLLAPSE_ALTERNATIVES = Yes
  843. # Whether text/html should be converted to text/plain after content filtering
  844. # is performed. Conversion is done according to HTML_TO_PLAIN_TEXT_COMMAND
  845. DEFAULT_CONVERT_HTML_TO_PLAINTEXT = Yes
  846. # Default action to take on filtered messages.
  847. # 0 = Discard, 1 = Reject, 2 = Forward, 3 = Preserve
  848. DEFAULT_FILTER_ACTION = 0
  849. # Whether to allow list owners to preserve content filtered messages to a
  850. # special queue on the disk.
  851. OWNERS_CAN_PRESERVE_FILTERED_MESSAGES = Yes
  852. # Check for administrivia in messages sent to the main list?
  853. DEFAULT_ADMINISTRIVIA = Yes
  854. #####
  855. # Digestification defaults. Same caveat applies here as with list defaults.
  856. #####
  857. # Will list be available in non-digested form?
  858. DEFAULT_NONDIGESTABLE = Yes
  859. # Will list be available in digested form?
  860. DEFAULT_DIGESTABLE = Yes
  861. DEFAULT_DIGEST_HEADER = ""
  862. DEFAULT_DIGEST_FOOTER = DEFAULT_MSG_FOOTER
  863. DEFAULT_DIGEST_IS_DEFAULT = No
  864. DEFAULT_MIME_IS_DEFAULT_DIGEST = No
  865. DEFAULT_DIGEST_SIZE_THRESHHOLD = 30 # KB
  866. DEFAULT_DIGEST_SEND_PERIODIC = Yes
  867. # Headers which should be kept in both RFC 1153 (plain) and MIME digests. RFC
  868. # 1153 also specifies these headers in this exact order, so order matters.
  869. MIME_DIGEST_KEEP_HEADERS = [
  870. 'Date', 'From', 'To', 'Cc', 'Subject', 'Message-ID', 'Keywords',
  871. # I believe we should also keep these headers though.
  872. 'In-Reply-To', 'References', 'Content-Type', 'MIME-Version',
  873. 'Content-Transfer-Encoding', 'Precedence', 'Reply-To',
  874. # Mailman 2.0 adds these headers
  875. 'Message',
  876. ]
  877. PLAIN_DIGEST_KEEP_HEADERS = [
  878. 'Message', 'Date', 'From',
  879. 'Subject', 'To', 'Cc',
  880. 'Message-ID', 'Keywords',
  881. 'Content-Type',
  882. ]
  883. #####
  884. # Bounce processing defaults. Same caveat applies here as with list defaults.
  885. #####
  886. # Should we do any bounced mail response at all?
  887. DEFAULT_BOUNCE_PROCESSING = Yes
  888. # How often should the bounce qrunner process queued detected bounces?
  889. REGISTER_BOUNCES_EVERY = minutes(15)
  890. # Bounce processing works like this: when a bounce from a member is received,
  891. # we look up the `bounce info' for this member. If there is no bounce info,
  892. # this is the first bounce we've received from this member. In that case, we
  893. # record today's date, and initialize the bounce score (see below for initial
  894. # value).
  895. #
  896. # If there is existing bounce info for this member, we look at the last bounce
  897. # receive date. If this date is farther away from today than the `bounce
  898. # expiration interval', we throw away all the old data and initialize the
  899. # bounce score as if this were the first bounce from the member.
  900. #
  901. # Otherwise, we increment the bounce score. If we can determine whether the
  902. # bounce was soft or hard (i.e. transient or fatal), then we use a score value
  903. # of 0.5 for soft bounces and 1.0 for hard bounces. Note that we only score
  904. # one bounce per day. If the bounce score is then greater than the `bounce
  905. # threshold' we disable the member's address.
  906. #
  907. # After disabling the address, we can send warning messages to the member,
  908. # providing a confirmation cookie/url for them to use to re-enable their
  909. # delivery. After a configurable period of time, we'll delete the address.
  910. # When we delete the address due to bouncing, we'll send one last message to
  911. # the member.
  912. # Bounce scores greater than this value get disabled.
  913. DEFAULT_BOUNCE_SCORE_THRESHOLD = 5.0
  914. # Bounce information older than this interval is considered stale, and is
  915. # discarded.
  916. DEFAULT_BOUNCE_INFO_STALE_AFTER = days(7)
  917. # The number of notifications to send to the disabled/removed member before we
  918. # remove them from the list. A value of 0 means we remove the address
  919. # immediately (with one last notification). Note that the first one is sent
  920. # upon change of status to disabled.
  921. DEFAULT_BOUNCE_YOU_ARE_DISABLED_WARNINGS = 3
  922. # The interval of time between disabled warnings.
  923. DEFAULT_BOUNCE_YOU_ARE_DISABLED_WARNINGS_INTERVAL = days(7)
  924. # Does the list owner get messages to the -bounces (and -admin) address that
  925. # failed to match by the bounce detector?
  926. DEFAULT_BOUNCE_UNRECOGNIZED_GOES_TO_LIST_OWNER = Yes
  927. # Notifications on bounce actions. The first specifies whether the list owner
  928. # should get a notification when a member is disabled due to bouncing, while
  929. # the second specifies whether the owner should get one when the member is
  930. # removed due to bouncing.
  931. DEFAULT_BOUNCE_NOTIFY_OWNER_ON_DISABLE = Yes
  932. DEFAULT_BOUNCE_NOTIFY_OWNER_ON_REMOVAL = Yes
  933. #####
  934. # General time limits
  935. #####
  936. # Default length of time a pending request is live before it is evicted from
  937. # the pending database.
  938. PENDING_REQUEST_LIFE = days(3)
  939. # How long should messages which have delivery failures continue to be
  940. # retried? After this period of time, a message that has failed recipients
  941. # will be dequeued and those recipients will never receive the message.
  942. DELIVERY_RETRY_PERIOD = days(5)
  943. # How long should we wait before we retry a temporary delivery failure?
  944. DELIVERY_RETRY_WAIT = hours(1)
  945. #####
  946. # Lock management defaults
  947. #####
  948. # These variables control certain aspects of lock acquisition and retention.
  949. # They should be tuned as appropriate for your environment. All variables are
  950. # specified in units of floating point seconds. YOU MAY NEED TO TUNE THESE
  951. # VARIABLES DEPENDING ON THE SIZE OF YOUR LISTS, THE PERFORMANCE OF YOUR
  952. # HARDWARE, NETWORK AND GENERAL MAIL HANDLING CAPABILITIES, ETC.
  953. # Set this to On to turn on MailList object lock debugging messages, which
  954. # will be written to logs/locks. If you think you're having lock problems, or
  955. # just want to tune the locks for your system, turn on lock debugging.
  956. LIST_LOCK_DEBUGGING = Off
  957. # This variable specifies how long the lock will be retained for a specific
  958. # operation on a mailing list. Watch your logs/lock file and if you see a lot
  959. # of lock breakages, you might need to bump this up. However if you set this
  960. # too high, a faulty script (or incorrect use of bin/withlist) can prevent the
  961. # list from being used until the lifetime expires. This is probably one of
  962. # the most crucial tuning variables in the system.
  963. LIST_LOCK_LIFETIME = hours(5)
  964. # This variable specifies how long an attempt will be made to acquire a list
  965. # lock by the incoming qrunner process. If the lock acquisition times out,
  966. # the message will be re-queued for later delivery.
  967. LIST_LOCK_TIMEOUT = seconds(10)
  968. # Set this to On to turn on lock debugging messages for the pending requests
  969. # database, which will be written to logs/locks. If you think you're having
  970. # lock problems, or just want to tune the locks for your system, turn on lock
  971. # debugging.
  972. PENDINGDB_LOCK_DEBUGGING = Off
  973. #####
  974. # Nothing below here is user configurable. Most of these values are in this
  975. # file for internal system convenience. Don't change any of them or override
  976. # any of them in your mm_cfg.py file!
  977. #####
  978. # These directories are used to find various important files in the Mailman
  979. # installation. PREFIX and EXEC_PREFIX are set by configure and should point
  980. # to the installation directory of the Mailman package.
  981. PYTHON = '@PYTHON@'
  982. PREFIX = '@prefix@'
  983. EXEC_PREFIX = '@exec_prefix@'
  984. VAR_PREFIX = '@VAR_PREFIX@'
  985. # Work around a bogus autoconf 2.12 bug
  986. if EXEC_PREFIX == '${prefix}':
  987. EXEC_PREFIX = PREFIX
  988. # CGI extension, change using configure script
  989. CGIEXT = '@CGIEXT@'
  990. # Group id that group-owns the Mailman installation
  991. MAILMAN_USER = '@MAILMAN_USER@'
  992. MAILMAN_GROUP = '@MAILMAN_GROUP@'
  993. # Enumeration for Mailman cgi widget types
  994. Toggle = 1
  995. Radio = 2
  996. String = 3
  997. Text = 4
  998. Email = 5
  999. EmailList = 6
  1000. Host = 7
  1001. Number = 8
  1002. F

Large files files are truncated, but you can click here to view the full file