Hi Ross:

> BTW, google stuck the bounce message in my spam folder, as it did with many messages from
> your site. I was unable to decode from the headers what they thought the problem was.

I went a looked and have the same issue here. We have SPF defined, but no DKIM maybe that's 
the issue?

> The bounce message, from roundup-admin, said

Yeah, I did get your email on that.

> There was a problem with the message you sent:
>   'ascii' codec can't decode byte 0xe2 in position 28: ordinal not in range(128)
> I'm not exactly sure where to start count to get to 28 (headers? main body?), but the body
> begins (as rendered by google in the bounce mail)
>
>On Mon, May 18, 2026 at 8:45=E2=80=AFAM John Rouillard
>which certainly looks as if there are character coding issues.

The first = sign in the encoded line is at position 29, I don't remeber offhand if the
"position" is 0 or 1 based. I wonder what char is there in the original message. Maybe a
non-breaking space or something?

In any case the tracker is running roundup 1.6 ish under python 2. We are
a guest on the system and can't upgrade at the moment. There were a number of bugs
in encoding in 1.6 and python2.

> I fixed this in changeset:   8648:d2da5f9c2ea8.

There was a delay in pushing the changes upstream. Sourceforge was having issues.
So you might not have seen the changes for a bit.

> I wanted  to get the source repository and how to run roundup from there;
> I think it was the first spot I found that had the information, in particular the URL.

Got it. Well thanks for being an early beta tester for 2.6 8-).

-- rouilj