Fra: Mark Sapiro [mailto:mark@msapiro.net] Sendt: 2. oktober 2017 17:26 Emne: [MM3-users] Re: Uncaught runner exception: 'str' object has no attribute 'decode'
Is there some kind of workaround, I can give my users or something that the list admins can do as a workaround?
There is no user or list admin workaround, but the defense is a fairly simple patch. See the MR at <https://gitlab.com/mailman/mailman/merge_requests/322> and the commit at <https://gitlab.com/mailman/mailman/commit/37b3f62afdf225a8e29b66fcefcdb56b9ba0cb1f>. The commit changes 7 files, but only two are needed. The rests are tests or reverting <https://gitlab.com/mailman/mailman/issues/256> which isn't necessary.
The only changes you need are those to mailman/email/message.py and mailman/mta/connection.py.
I am using Docker-mailman (not yet very familiar Docker and version control). I would expect I have to wait for a Docker-mailman release including this change, right?
I have at least five+ lists which almost haven't been working since my switch from Mailman 2.1 to Mailman 3.1 (Docker-mailman 0.1.1), and I am desperate trying to figure out whether it is best to fall back to the Mailman 2 server, for the time being, where the lists came from, or it is better to wait for an update to the Docker-image.
Will https://github.com/maxking/docker-mailman/milestone/2 fix my problems regarding failed mail handling and will it become available soon (when?) (https://github.com/maxking/docker-mailman/issues/147)?
-- Henrik Rasmussen <her@adm.ku.dk> University of Copenhagen, Danmark