[Mailman-Users] Logging Archive Creation in MM2.1.7
msapiro at value.net
Tue Jan 3 03:22:42 CET 2006
Bryan Carbonnell wrote:
>The error I get is:
>Pickling archive state into /var/mailman/archives/private/dba-vb/pipermail.pck
>Traceback (most recent call last):
> File "./bin/arch", line 200, in ?
> File "./bin/arch", line 188, in main
> archiver.processUnixMailbox(fp, start, end)
> File "/var/mailman/Mailman/Archiver/pipermail.py", line 585, in
> File "/var/mailman/Mailman/Archiver/pipermail.py", line 626, in add_article
> File "/var/mailman/Mailman/Archiver/HyperArch.py", line 1116, in write_article
> File "/var/mailman/Mailman/Archiver/HyperArch.py", line 579, in as_text
> '\g<1>' + _(' at ') + '\g<2>', body)
> File "/usr/local/lib/python2.3/sre.py", line 143, in sub
> return _compile(pattern, 0).sub(repl, string, count)
>UnicodeDecodeError: 'ascii' codec can't decode byte 0xa3 in position
>2025: ordinal not in range(128)
>I have looked through the mbox file and all the ascii characters
>greater than 128 are in the body of the e-mails. The 2 characters that
>i can find are the British Pound sign and what appears to be a MS
>"smart" single quote.
The problem occurs when the archiver tries to obscure email addresses
in the body of a post (read from the .mbox file with bin/arch or
presumably, a new post being archived too) before adding it to the
monthly .txt file, and the body of the post contains a non-ascii
character or characters.
for another report and a patch that can be applied to allow rebuilding
of the archive.
The patch in the above report will not actually fix the problem as the
rebuilt archive will not have email addresses obscured in the .txt
files in the bodies of those posts with non-ascii characters.
Also the problem doesn't occur if
ARCHIVER_OBSCURES_EMAILADDRS = No
Mark Sapiro <msapiro at value.net> The highway is for gamblers,
San Francisco Bay Area, California better use your sense - B. Dylan
More information about the Mailman-Users