[Bug 1778363] [NEW] exception (utf8 codec) in pipermail

Olivier GERARD 1778363 at bugs.launchpad.net
Sat Jun 23 17:46:25 EDT 2018

Public bug reported:

After upgrading Mailman from 2.1.23 to  2.1.26-1 on Debian, things went smoothly,
the list's mbox is updated but the archives are not updated. 
In the error log, one sees, for every message

Jun 23 19:59:03 2018 (20419) SHUNTING: 1529776742.660616+f4a3eea82ed27ce3f481064f194162863c62b280
Jun 23 21:35:24 2018 (20419) Uncaught runner exception: 'utf8' codec can't decode byte 0xaa in position 26: invalid start byte
Jun 23 21:35:24 2018 (20419) Traceback (most recent call last):
  File "/var/lib/mailman/Mailman/Queue/Runner.py", line 119, in _oneloop
    self._onefile(msg, msgdata)
  File "/var/lib/mailman/Mailman/Queue/Runner.py", line 190, in _onefile
    keepqueued = self._dispose(mlist, msg, msgdata)
  File "/var/lib/mailman/Mailman/Queue/ArchRunner.py", line 77, in _dispose
  File "/var/lib/mailman/Mailman/Archiver/Archiver.py", line 214, in ArchiveMail
  File "/var/lib/mailman/Mailman/Archiver/pipermail.py", line 596, in processUnixMailbox
  File "/var/lib/mailman/Mailman/Archiver/pipermail.py", line 640, in add_article
    author = fixAuthor(article.decoded['author'])
  File "/var/lib/mailman/Mailman/Archiver/pipermail.py", line 63, in fixAuthor
    while i>0 and (L[i-1][0] in lowercase or
UnicodeDecodeError: 'utf8' codec can't decode byte 0xaa in position 26: invalid start byte

This is always the same complaint. I have checked shunted messages and the mbox itself
and I have not found any 0xaa value in them.

** Affects: mailman
     Importance: Undecided
         Status: New

** Tags: pipermail unicode

You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.

  exception (utf8 codec) in pipermail

To manage notifications about this bug go to:

More information about the Mailman-coders mailing list