On my debian 0.7.10-1 installation of roundup it seems
like that in notification mails, messages are encoded
with iso8859-1 instead of UTF-8. 

The mail header contains the line
Content-type: text/plain; charset=utf-8

With Thunderbird an, for example, "ö" character from
roundup displays as "?". If I change thunderbird to
intepret characters as iso-8859-1 it shows up correctly
as "ö". (The difference in coding for an "ö" character
is that it is "F6" hex in iso 8859-1 and "00F6" hex in
UTF-8. )

Messages seems to be encoded ok in html on the web.


Another problem, maybee related to the above is that
when I try to force EMAIL_CHARSET = 'iso-8859-1'  in
config.py, roundup complains with the error message in
the web page:

Edit Error: 'utf8' codec can't decode bytes in position
52-54: invalid data

(positions varies with the position of the "åäö"
letters in the message). No notification mail is sent.
If the message contains no "åäö" it works fine, mail is
sent with 

Content-type: text/plain; charset=iso-8859-1
in its header.

Logged In: YES 
user_id=6405

I just need to make sure I understand how you're making this happen. 
 
I can't reproduce it with 0.7.12 (currently in CVS, but no changes have 
been made in the email components for some time now) by: 
 
1. creating a new demo tracker, 
2. copying "templates/classic/detectors/nosyreaction.py" into 
    "demo/detectors" 
3. configuring the demo to send email, and 
4. entering a change note with the chars åäö in it. 
 
The email makes it to me fine, UTF-8 with the chars encoded correctly. 
 

Logged In: YES 
user_id=1211191

Doesn't work for me...

The second part of the bug report should maybee be an own 
bug report. Have you tested that? I would settle for using
iso-8859-1 if it worked.

Logged In: YES 
user_id=6405

Just to confirm; following the steps I indicate, using the latest Roundup 
0.7 version available (0.7.11), the email does not come through as UTF-8?

I've not looked into the second part of the report yet (apologies - I 
marked the report "Works For Me" prematurely). A cursory glance at the 
code does seem to indicate that the charset of UTF-8 is hard-coded in the 
headers regardless of the charset configured in the tracker.

Logged In: YES 
user_id=1211191

Have done this using the Debian package, following their
instructions, using the cgi method (not standalone server).
Didn't understand about step 2. since the "nosyreaction.py"
was already installed in the "demo/detectors" directory
(differing from the one in the "templates" directory only by
an added SHA checksum).

Still no UTF-8 chars in the mail.

Here is the package information. None of the suggested
packages are installed:

# dpkg -s roundup
Package: roundup
Status: install ok installed
Priority: optional
Section: web
Installed-Size: 2444
Maintainer: Bastian Kleineidam <calvin@XXX>
Architecture: all
Version: 0.7.11-1
Depends: python (>= 2.3), python (<< 2.4)
Suggests: python-gdbm, python-sqlite, python-psycopg,
libmetakit-python, python-mysqldb, python-bsddb3, runit
Conffiles:
 /etc/roundup/service/log/run 0b3f568608accf9bc9c37145dd65d1d0
 /etc/roundup/service/run 76e45a84fcec2001060848876c7dc594
 /etc/roundup/cgiconf.py e3a28bc30bf43bf033d95f82e7111903
 /etc/logrotate.d/roundup ab4afaa86ec66d5feab2611fb0a3ebe0
Description: issue-tracking system
 a simple-to-use and -install issue tracking system with
 command-line, web and e-mail interfaces. It is based on the
winning
 design from Ka-Ping Yee in the Software Carpentry "Track"
design
 competition.
 .
 If you install one or more of the suggested database
interface packages,
 you will be able to store tracker data in the corresponding
database.

Logged In: YES 
user_id=6405

Sorry for the long delay in resolution: is this still an issue?

Logged In: NO 

This is only a test, sorry.

Logged In: YES 
user_id=1211191

It's not an issue any more. It corrected itself somewhere
along the 8.3 installation. Thanks.