Mercurial > p > roundup > code
view doc/roundup-demo.1 @ 3945:1dd64778bc45
Mail improvements:
- Implement new config option in mail-section "ignore_alternatives" to
ignore alternatives in a multipart/alternative mail. The *last*
text/plain part of the *first* multipart/alternative is used as the
message, if ignore_alternatives is set all other alternative parts of
the first multipart/alternative that contained a text/plain part are
ignored. Other multipart/alternative or other multipart are attached
as before. This fixes [SF#959811] "Multipart/alternative handling
considered bad". Note that this also changes which text/plain part is
attached as the message if there are several text/plain parts in a
multipart: Previously the *first* text/plain would be attached. Now we
attach the *last* one, this is more in line with rfc 2046, sec. 5.1.4.
according to Philipp Gortan.
- Fix bug in attachment of text parts: If there are multiple text/plain
parts in a nested multipart, the previous code would attach the
multipart serialisation instead of the text/plain serialisation as a
file to the issue in some cases.
- Add regression tests for the new config-option and bug-fixes above.
| author | Ralf Schlatterbeck <schlatterbeck@users.sourceforge.net> |
|---|---|
| date | Wed, 14 Nov 2007 14:57:47 +0000 |
| parents | 4992da7c96ae |
| children | 5cd913b94e25 |
line wrap: on
line source
.TH ROUNDUP-SERVER 1 "27 July 2004" .SH NAME roundup-demo \- create a roundup "demo" tracker and launch its web interface .SH SYNOPSIS \fBroundup-demo\fP [\fIbackend\fP [\fBnuke\fP]] .SH OPTIONS .TP \fBnuke\fP Create a fresh demo tracker (deleting the existing one if any). If the additional \fIbackend\fP argument is specified, the new demo tracker will use the backend named (one of "anydbm", "sqlite", "metakit", "mysql" or "postgresql"; subject to availability on your system). .TH DESCRIPTION This command creates a fresh demo tracker for you to experiment with. The email features of Roundup will be turned off (so the nosy feature won't send email). It does this by removing the \fInosyreaction.py\fP module from the demo tracker's \fIdetectors\fP directory. If you wish, you may modify the demo tracker by editing its configuration files and HTML templates. See the \fIcustomisation\fP manual for information about how to do that. Once you've fiddled with the demo tracker, you may use it as a template for creating your real, live tracker. Simply run the \fIroundup-admin\fP command to install the tracker from inside the demo tracker home directory, and it will be listed as an available template for installation. No data will be copied over. .SH AUTHOR This manpage was written by Richard Jones <richard@users.sourceforge.net>.