Re: [Mailman-Users] UnicodeDecodeError with Mailman 2.1 and Python 2.6

Mark Sapiro writes: > I don't know what you are grepping, but if it's the mbox, you shouldn't > be looking for "\xea", you should be looking for "ê". At least on recent BSD-based systems "\xea" is a well-defined escape sequence, interpreted as the hexadecimal representation of a byte. Dunno

[Mailman-Users] cron log looks odd

I get Mailman job logs that look like this: Sep 1 08:00:01 {my_node} CROND[29280]: (mailman) CMD (/usr/bin/python -S /usr/local/mailman/cron/checkdbs^M) Sep 1 09:00:01 {my_node} CROND[30120]: (mailman) CMD (/usr/bin/python -S /usr/local/mailman/cron/disabled^M) Sep 1 12:00:01 {my_node} atronus

Re: [Mailman-Users] UnicodeDecodeError with Mailman 2.1 and Python 2.6

On Tue, September 1, 2015 13:53, Mark Sapiro wrote: > There shouldn't be any non-ascii in a mbox. Well, maybe in a > "Content-Transfer-Encoding: 8bit" (or binary?) body part, but certainly > not in any headers. > > I don't know what you are grepping, but if it's the mbox, you shouldn't > be

Re: [Mailman-Users] cron log looks odd

On 09/01/2015 10:00 AM, Steve Matzura wrote: > I get Mailman job logs that look like this: > > Sep 1 08:00:01 {my_node} CROND[29280]: (mailman) CMD (/usr/bin/python > -S /usr/local/mailman/cron/checkdbs^M) > Sep 1 09:00:01 {my_node} CROND[30120]: (mailman) CMD (/usr/bin/python > -S

Re: [Mailman-Users] UnicodeDecodeError with Mailman 2.1 and Python 2.6

On 09/01/2015 10:26 AM, David Magda wrote: > > Looking at the mbox, there was only one place where \xea was in the > header, in a Subject line, using `grep --color='auto' -P -n "\xea"`. I > manually edited the mbox (making a copy first) and remove the accented-e > character with an ASCII "e", and

Re: [Mailman-Users] UnicodeDecodeError with Mailman 2.1 and Python 2.6

On Tue, September 1, 2015 14:35, Stephen J. Turnbull wrote: > Mark Sapiro writes: > > > I don't know what you are grepping, but if it's the mbox, you shouldn't > > be looking for "\xea", you should be looking for "ê". > > At least on recent BSD-based systems "\xea" is a well-defined escape >

Re: [Mailman-Users] UnicodeDecodeError with Mailman 2.1 and Python 2.6

[Actually send the reply to the list as well.] On Tue, September 1, 2015 12:15, Stephen J. Turnbull wrote: > David Magda writes: > > > When I run 'bin/arch mylistname' I get the following: > > > > [...] > > figuring article archives > > 2005-October > >

Re: [Mailman-Users] Archive looping

I must correct myself. First-- The monthly archive is 9,000 messages (137,000 is the total in the entire archive going back for years). Second-- Not all messages are getting rewritten one newline at a time. Only those with "An HTML attachment was scrubbed..." get the rewrite. Still

Re: [Mailman-Users] Archive looping

On 09/01/2015 07:27 AM, Joseph Brennan wrote: > > Yesterday the archive got into a weird state that I could not break by a > shutdown and fresh start. For each incoming message, it rewrites all of > the old messages with one extra newline. This useless activity takes > quite a while and has

Re: [Mailman-Users] cron log looks odd

On Tue, 1 Sep 2015 10:24:24 -0700, you wrote: >On 09/01/2015 10:00 AM, Steve Matzura wrote: >> I get Mailman job logs that look like this: >> >> Sep 1 08:00:01 {my_node} CROND[29280]: (mailman) CMD (/usr/bin/python >> -S /usr/local/mailman/cron/checkdbs^M) >> Sep 1 09:00:01 {my_node}

Re: [Mailman-Users] UnicodeDecodeError with Mailman 2.1 and Python 2.6

> On Sep 1, 2015, at 21:02, Mark Sapiro wrote: > > In my testing with GNU grep on Ubuntu 15.04, 'grep "\xea"' interprets \x > as a literal x and therefore looks for the string "xea", not for the > character whose hex value is EA. For the record/archives: GNU grep also as the

Re: [Mailman-Users] UnicodeDecodeError with Mailman 2.1 and Python 2.6

> On Sep 1, 2015, at 21:14, Mark Sapiro wrote: > > On 09/01/2015 12:09 PM, David Magda wrote: >> >> Could the new version of Python been chocking on a binary file whose >> format has changed from the old version? Is it prudent to do an "arch >> --wipe" when changing versions

Re: [Mailman-Users] Pluggable authentication for Mailman web interface?

On 09/01/2015 06:33 AM, Waldbieser, Carl wrote: > > I know that currently, mailman roles are set up such that the roles > themselves have a shared password per role. This is true for MM 2.1. It is not true for MM 3. > I want to be able to move away from that model and have roles assigned to

Re: [Mailman-Users] UnicodeDecodeError with Mailman 2.1 and Python 2.6

On 09/01/2015 12:09 PM, David Magda wrote: > > Could the new version of Python been chocking on a binary file whose > format has changed from the old version? Is it prudent to do an "arch > --wipe" when changing versions of Python? The exception is thrown in Python's sort() method. There are no

Re: [Mailman-Users] UnicodeDecodeError with Mailman 2.1 and Python 2.6

On 09/01/2015 12:16 PM, David Magda wrote: > On Tue, September 1, 2015 14:35, Stephen J. Turnbull wrote: >> Mark Sapiro writes: >> >> > I don't know what you are grepping, but if it's the mbox, you shouldn't >> > be looking for "\xea", you should be looking for "ê". >> >> At least on recent

Re: [Mailman-Users] UnicodeDecodeError with Mailman 2.1 and Python 2.6

On 09/01/2015 06:55 PM, David Magda wrote: > > The message in question seems to be from October 2005, and it has the > "Subject: Você […]” header. Running under Debian 5 (Python 2.5), archive > processing wasn’t an issue: messages were coming into the mbox and the HTML > page was being

[Mailman-Users] Archive looping

We have a list with a very large archive, over 137,000 messages in a month. It catches system alerts. This might just be a bad idea. Maybe we should archive by day. But it's been all right for many months up to now. I'm looking for ideas on how to solve a problem with the archives.

Re: [Mailman-Users] (no subject)

Hi dear mailman user is there any step by step video in youtube maybe with the requirements and the installation process? On Mon, Aug 31, 2015 at 9:27 PM, Nestor Praslin wrote: > Hi dear, how are you doing, I have a question?can anybody help me install > mailman and

Re: [Mailman-Users] Pluggable authentication for Mailman web interface?

I know that currently, mailman roles are set up such that the roles themselves have a shared password per role. I want to be able to move away from that model and have roles assigned to individual user accounts that would allow access to the admin interfaces for individual lists. For

[Mailman-Users] UnicodeDecodeError with Mailman 2.1 and Python 2.6

[Not sure if my first attempt made it out.] Hello, We recently upgrade from Debian 5 to 6, and are now having issues with Mailman. Messages are still flowing properly, but the web archives are not being generated since the upgrade. When I run 'bin/arch mylistname' I get the following: [...]

[Mailman-Users] UnicodeDecodeError with Mailman 2.1 and Python 2.6

Hello, We recently upgrade from Debian 5 to 6, and are now having issues with Mailman. Messages are still flowing properly, but the web archives are not being generated since the upgrade. When I run 'bin/arch mylistname' I get the following: [...] figuring article archives 2005-October

Re: [Mailman-Users] (no subject)

In a message of Mon, 31 Aug 2015 21:35:33 -0500, Nestor Praslin writes: >Hi dear mailman user is there any step by step video in youtube maybe with >the requirements and the installation process? I went to youtube. I searched for "mailman tutorial". The first 3 hits seem to be what you are

[Mailman-Users] (no subject)

Hi dear, how are you doing, I have a question?can anybody help me install mailman and make it run? I like to get in touch with you if so so that maybe ca help me installl it in my server because I have installed via webmin once but didn`t get it to run. -- Nestor Praslin International sihay.com

[Mailman-Users] UnicodeDecodeError with Mailman 2.1 and Python 2.6

David Magda writes: > When I run 'bin/arch mylistname' I get the following: > > [...] > figuring article archives > 2005-October > /usr/local/mailman-2.1.20/Mailman/Archiver/HyperDatabase.py:176: > UnicodeWarning: Unicode equal comparison failed to convert both arguments > to Unicode -