I hope to fix it tomorrow, but I can't be sure. Maybe it will fix itself
and I'll just abandon the digest for today. Very few people use the
digest feature, normally it goes out at noonish eastern time.
All I've had time to do done is grab a stack trace, seems like there's
some characters in an email that mailman doesn't like. If anyone wants
to lend a hand, this is from a lightly modified senddigests from mailman
to get a stack trace:
Traceback (most recent call last):
File "/usr/lib/mailman/cron/sd", line 106, in <module>
main()
File "/usr/lib/mailman/cron/sd", line 89, in main
mlist.send_digest_now()
File "/var/lib/mailman/Mailman/Digester.py", line 60, in send_digest_now
ToDigest.send_digests(self, mboxfp)
File "/var/lib/mailman/Mailman/Handlers/ToDigest.py", line 147, in
send_digests
send_i18n_digests(mlist, mboxfp)
File "/var/lib/mailman/Mailman/Handlers/ToDigest.py", line 347, in
send_i18n_digests
payload = unicode(payload, mcset, 'replace'
File "/usr/lib/python2.7/encodings/base64_codec.py", line 41, in base64_decode
assert errors == 'strict'
AssertionError
--
Ian Kelling | Senior Systems Administrator, Free Software Foundation
GPG Key: B125 F60B 7B28 7FF6 A2B7 DF8F 170A F0E2 9542 95DF
https://fsf.org | https://gnu.org
