Mercurial > p > roundup > code
comparison doc/customizing.txt @ 3417:07c696890f55
mailgw subject parsing has configurable levels of strictness
nosy messages may be sent individually to all recipients
| author | Richard Jones <richard@users.sourceforge.net> |
|---|---|
| date | Fri, 07 Oct 2005 04:42:13 +0000 |
| parents | 80dc8011228e |
| children | 963003d2ffdd |
comparison
equal
deleted
inserted
replaced
| 3415:4a228402b810 | 3417:07c696890f55 |
|---|---|
| 1 =================== | 1 =================== |
| 2 Customising Roundup | 2 Customising Roundup |
| 3 =================== | 3 =================== |
| 4 | 4 |
| 5 :Version: $Revision: 1.184 $ | 5 :Version: $Revision: 1.185 $ |
| 6 | 6 |
| 7 .. This document borrows from the ZopeBook section on ZPT. The original is at: | 7 .. This document borrows from the ZopeBook section on ZPT. The original is at: |
| 8 http://www.zope.org/Documentation/Books/ZopeBook/current/ZPT.stx | 8 http://www.zope.org/Documentation/Books/ZopeBook/current/ZPT.stx |
| 9 | 9 |
| 10 .. contents:: | 10 .. contents:: |
| 253 | 253 |
| 254 default_class -- ``issue`` | 254 default_class -- ``issue`` |
| 255 Default class to use in the mailgw if one isn't supplied in email subjects. | 255 Default class to use in the mailgw if one isn't supplied in email subjects. |
| 256 To disable, leave the value blank. | 256 To disable, leave the value blank. |
| 257 | 257 |
| 258 subject_prefix_parsing -- ``strict`` | |
| 259 Controls the parsing of the [prefix] on subject lines in incoming emails. | |
| 260 ``strict`` will return an error to the sender if the [prefix] is not | |
| 261 recognised. ``loose`` will attempt to parse the [prefix] but just | |
| 262 pass it through as part of the issue title if not recognised. ``none`` | |
| 263 will always pass any [prefix] through as part of the issue title. | |
| 264 | |
| 265 subject_suffix_parsing -- ``strict`` | |
| 266 Controls the parsing of the [suffix] on subject lines in incoming emails. | |
| 267 ``strict`` will return an error to the sender if the [suffix] is not | |
| 268 recognised. ``loose`` will attempt to parse the [suffix] but just | |
| 269 pass it through as part of the issue title if not recognised. ``none`` | |
| 270 will always pass any [suffix] through as part of the issue title. | |
| 271 | |
| 272 subject_suffix_delimiters -- ``[]`` | |
| 273 Defines the brackets used for delimiting the commands suffix in a subject | |
| 274 line. | |
| 275 | |
| 276 subject_content_match -- ``always`` | |
| 277 Controls matching of the incoming email subject line against issue titles | |
| 278 in the case where there is no designator [prefix]. ``never`` turns off | |
| 279 matching. ``creation + interval`` or ``activity + interval`` will match | |
| 280 an issue for the interval after the issue's creation or last activity. | |
| 281 The interval is a standard Roundup interval. | |
| 282 | |
| 258 Section **nosy** | 283 Section **nosy** |
| 259 Nosy messages sending | 284 Nosy messages sending |
| 260 | 285 |
| 261 messages_to_author -- ``no`` | 286 messages_to_author -- ``no`` |
| 262 Send nosy messages to the author of the message. | 287 Send nosy messages to the author of the message. |
| 277 Do the recipients (``To:``, ``Cc:``) of a message get placed on the nosy | 302 Do the recipients (``To:``, ``Cc:``) of a message get placed on the nosy |
| 278 list? If ``new`` is used, then the recipients will only be added when a | 303 list? If ``new`` is used, then the recipients will only be added when a |
| 279 message creates a new issue. If ``yes``, then the recipients will be added | 304 message creates a new issue. If ``yes``, then the recipients will be added |
| 280 on followups too. If ``no``, they're never added to the nosy. | 305 on followups too. If ``no``, they're never added to the nosy. |
| 281 Allowed values: ``yes``, ``no``, ``new`` | 306 Allowed values: ``yes``, ``no``, ``new`` |
| 307 | |
| 308 email_sending -- ``single`` | |
| 309 Controls the email sending from the nosy reactor. If ``multiple`` then | |
| 310 a separate email is sent to each recipient. If ``single`` then a single | |
| 311 email is sent with each recipient as a CC address. | |
| 282 | 312 |
| 283 You may generate a new default config file using the ``roundup-admin | 313 You may generate a new default config file using the ``roundup-admin |
| 284 genconfig`` command. | 314 genconfig`` command. |
| 285 | 315 |
| 286 Configuration variables may be referred to in lower or upper case. In code, | 316 Configuration variables may be referred to in lower or upper case. In code, |