Roundup Tracker - Issues


Author rouilj
Recipients ber, marcus.priesch, rouilj, schlatterbeck
Date 2022-06-07.20:24:30
Message-id <>
This is an interesting issue. Bern, Ralf this ticket has a message that when process by 
the mail gateway resulted in a UunicodeDecodeError with python 2.7 and roundup 1.6.1
(run as

I think this bug is fixed in the current development release as I don't get an error 
message when I run a current dev tracker under python 2 or 3.

Does this look like a reasonable way to test. I generated the test message using:

  (echo From; curl https://issues.roundup- ) | sed -e 's/\[issue[0-9]*]/[issue1]/' -e 
's/' > unencode.msg

where is the address for my admin user.

This creates an mbox style mail spool file that I used as:

  python3 roundup/scripts/ trackers/issue.tracker mailbox unencode.msg

I did the same with python2 and a python2 tracker homedir.

I verified that the characters that should cause the error were stored in db/msg/msgXX
by running 'od -c' on the file and verifying the 3 digit non-ascii character codes
on the line before the answer: header.

It might be worth looking at

for background and

for other still open encoding issues that sadly do not have reproduction steps.

Do you think I should try to set up a 1.6.1 install to test with to verify that
my test method can cause the issue?

If you guys think this is a valid test, I'll close this ticket out as not-reproducable.
Date User Action Args
2022-06-07 20:24:30rouiljsetmessageid: <>
2022-06-07 20:24:30rouiljsetrecipients: + rouilj, schlatterbeck, ber, marcus.priesch
2022-06-07 20:24:30rouiljlinkissue2551209 messages
2022-06-07 20:24:30rouiljcreate