22Customising Roundup
33===================
44
5- :Version: $Revision: 1.155 $
5+ :Version: $Revision: 1.156 $
66
77.. This document borrows from the ZopeBook section on ZPT. The original is at:
88 http://www.zope.org/Documentation/Books/ZopeBook/current/ZPT.stx
@@ -76,7 +76,10 @@ section "ConfigParser -- Configuration file parser":
7676
7777__ http://docs.python.org/lib/module-ConfigParser.html
7878
79- The configuration variables available are:
79+ Configuration variables may be referred to in lower or upper case. In code,
80+ variables not in the "main" section are referred to using their section and
81+ name, so "domain" in the section "mail" becomes MAIL_DOMAIN. The
82+ configuration variables available are:
8083
8184Section **main**
8285 database -- ``db``
@@ -88,11 +91,15 @@ Section **main**
8891 or relative to the directory containig this config file.
8992
9093 admin_email -- ``roundup-admin``
91- Email address that roundup will complain to if it runs into trouble.
94+ Email address that roundup will complain to if it runs into trouble. If
95+ the email address doesn't contain an ``@`` part, the MAIL_DOMAIN defined
96+ below is used.
9297
9398 dispatcher_email -- ``roundup-admin``
9499 The 'dispatcher' is a role that can get notified of new items to the
95- database. It is used by the ERROR_MESSAGES_TO config setting.
100+ database. It is used by the ERROR_MESSAGES_TO config setting. If the
101+ email address doesn't contain an ``@`` part, the MAIL_DOMAIN defined
102+ below is used.
96103
97104 email_from_tag -- default *blank*
98105 Additional text to include in the "name" part of the From: address used
0 commit comments