OK, I found out where the second error comes from. When there is no
administrator available, the message is sent to the site_owner from the
configuration file, but this entry is not converted to unicode before being set
in the msgdata dict.
Thus, when it's added to the database, Storm refuses it. The following patch
fixes this bug:
=== modified file 'src/mailman/handlers/owner_recipients.py'
--- src/mailman/handlers/owner_recipients.py 2013-01-01 14:05:42 +0000
+++ src/mailman/handlers/owner_recipients.py 2013-04-12 16:47:29 +0000
@@ -55,7 +55,7 @@
# To prevent -owner messages from going into a black hole, if there
# are no administrators available, the message goes to the site owner.
if len(recipients) == 0:
- msgdata['recipients'] = set((config.mailman.site_owner,))
+ msgdata['recipients'] = set((unicode(config.mailman.site_owner),))
else:
msgdata['recipients'] = recipients
# Don't decorate these messages with the header/footers. Eventually
--
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/1130957
Title:
Unicode errors in mailman3
To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/1130957/+subscriptions
_______________________________________________
Mailman-coders mailing list
[email protected]
http://mail.python.org/mailman/listinfo/mailman-coders
