Re: [Mailman-Users] shunting after "decoding Unicode is notsupported"

On 5/17/09 5:49 PM, Mark Sapiro wrote: > David Newman wrote: > >> On 5/13/09 10:06 PM, David Newman wrote: >>> Mailman 2.1.12 >>> >>> Had a server crash. Built a new server, compiled MM 2.1.12 from source >>> and restored the lists, data, and archives from a backup. >>> >>> Messages are going to t

Re: [Mailman-Users] shunting after "decoding Unicode is notsupported"

David Newman wrote: >On 5/13/09 10:06 PM, David Newman wrote: >> Mailman 2.1.12 >> >> Had a server crash. Built a new server, compiled MM 2.1.12 from source >> and restored the lists, data, and archives from a backup. >> >> Messages are going to the list but most aren't getting archived, with >>

Re: [Mailman-Users] shunting after "decoding Unicode is not supported"

On 5/13/09 10:06 PM, David Newman wrote: > Mailman 2.1.12 > > Had a server crash. Built a new server, compiled MM 2.1.12 from source > and restored the lists, data, and archives from a backup. > > Messages are going to the list but most aren't getting archived, with > errors like the one pasted b

[Mailman-Users] shunting after "decoding Unicode is not supported"

Mailman 2.1.12 Had a server crash. Built a new server, compiled MM 2.1.12 from source and restored the lists, data, and archives from a backup. Messages are going to the list but most aren't getting archived, with errors like the one pasted below. This has come up before: http://mail.python.org

Re: [Mailman-Users] Shunting problem and suggestions

Steve Campbell wrote: >I've got a single user out of approximately 250 that seems to always get >shunted. It's a problem with extended character set characters being >sent. She uses Outlook for an MUA. > >Can a user be whitelisted in any way to prevent the shunt tests from >being done? Where mi

[Mailman-Users] Shunting problem and suggestions

I've got a single user out of approximately 250 that seems to always get shunted. It's a problem with extended character set characters being sent. She uses Outlook for an MUA. Can a user be whitelisted in any way to prevent the shunt tests from being done? Where might I look on her machine to

Re: [Mailman-Users] Shunting & unknown encoding question

Mark Sapiro wrote: > >Look at the message (bin/show_qfiles >qfiles/shunt/1197373305.4631159+54681260563e1d1577b352329843c2fa738ba81.pck). > >I think you will see an RFC 2047 encoded Subject: header. I.e. >something like > > Subject: =?iso-8859-1?q?this=20is=20some=20text?= > >except the characterse

Re: [Mailman-Users] Shunting & unknown encoding question

Paul Key wrote: > >I have had an email shunted and am not sure why - any ideas why the encoding >is unknown? > >Dec 11 11:43:42 2007 (24788) Uncaught runner exception: unknown encoding: >unknown >Dec 11 11:43:42 2007 (24788) Traceback (most recent call last): > File "/usr/local/mailman/Mailman/Q

[Mailman-Users] Shunting & unknown encoding question

MM 2.1.3 Solaris 9 I have had an email shunted and am not sure why - any ideas why the encoding is unknown? Dec 11 11:43:42 2007 (24788) Uncaught runner exception: unknown encoding: unknown Dec 11 11:43:42 2007 (24788) Traceback (most recent call last): File "/usr/local/mailman/Mailman/Queue/

Re: [Mailman-Users] shunting - archive problem?

Sruli Shaffren wrote: > >I am looking for help on a problem with one of my lists. Currently >everything is shunting. This is using version 2.1.6 of Mailman: >Feb 28 08:04:24 2007 (16894) Uncaught runner exception: >[EMAIL PROTECTED] >Feb 28 08:04:24 2007 (16894) Traceback (most recent call last):

[Mailman-Users] shunting - archive problem?

Hi, I am looking for help on a problem with one of my lists. Currently everything is shunting. This is using version 2.1.6 of Mailman: Feb 28 08:04:24 2007 (16894) Uncaught runner exception: [EMAIL PROTECTED] Feb 28 08:04:24 2007 (16894) Traceback (most recent call last): File "/usr/share/mail

Re: [Mailman-Users] Shunting problem

Mark Sapiro wrote: >NFN Smith wrote: > >>2) What do I need to do to clear the problem that is causing shunting? > > >See 1). Note: if you meant what do you need to do to prevent this from happening again, upgrade to Mailman 2.1.7 or later. -- Mark Sapiro <[EMAIL PROTECTED]> The highway i

Re: [Mailman-Users] Shunting problem

NFN Smith wrote: >I'm running Mailman 2.1.5 on a Debian 3.1 box. In the last few days, >I'm getting an increasing number of messages shunted, with error logs >that look like: > >> Jan 30 23:10:53 2007 (3315) Uncaught runner exception: decoding >Unicode is not supported >> Jan 30 23:10:53 2007 (33

[Mailman-Users] Shunting problem

I'm running Mailman 2.1.5 on a Debian 3.1 box. In the last few days, I'm getting an increasing number of messages shunted, with error logs that look like: > Jan 30 23:10:53 2007 (3315) Uncaught runner exception: decoding Unicode is not supported > Jan 30 23:10:53 2007 (3315) Traceback (most recen

Re: [Mailman-Users] Shunting Problem

Stephan Jennewein wrote: > >Today I got the following problem with one of my maillinglists. >Unshunt didn't help because the mails are allways ending up in >qfiles/shunt. Is there a solution to this problem ? > >Greets >Stephan > >Nov 24 00:16:05 2006 (10169) Uncaught runner exception: us-ascii >No

[Mailman-Users] Shunting Problem

Hi, Today I got the following problem with one of my maillinglists. Unshunt didn't help because the mails are allways ending up in qfiles/shunt. Is there a solution to this problem ? Greets Stephan Nov 24 00:16:05 2006 (10169) Uncaught runner exception: us-ascii Nov 24 00:16:05 2006 (10169) Trac

Re: [Mailman-Users] shunting messages

Mark Sapiro wrote: > Noah wrote: > > >> Take a look at this. I ran bin/unshunt >> >> now i have a ton of 'SHUNT' errors in the /usr/local/mailman/logs/error >> >> >> so it looks like there are some python errors here. please look below. >> I am not sure where to go from here. >> >> # pkg_inf

Re: [Mailman-Users] shunting messages

Noah wrote: >Take a look at this. I ran bin/unshunt > >now i have a ton of 'SHUNT' errors in the /usr/local/mailman/logs/error > > >so it looks like there are some python errors here. please look below. >I am not sure where to go from here. > ># pkg_info | grep python >python-2.3.5_1 An i

[Mailman-Users] shunting messages

Take a look at this. I ran bin/unshunt now i have a ton of 'SHUNT' errors in the /usr/local/mailman/logs/error so it looks like there are some python errors here. please look below. I am not sure where to go from here. # pkg_info | grep python python-2.3.5_1 An interpreted object-orien

Re: [Mailman-Users] shunting

Mark Sapiro wrote: > >If Scrubber (which is invoked to flatten the message for the plain >digest) throws an exception in this process, pre Mailman 2.1.7 this >caused the message to be shunted and the list would effectively stop >as this all occurs before archiving and regular delivery, and the >who

Re: [Mailman-Users] shunting

Imre Gergely wrote: > >after solving this, i figured, on my lists nobody ever uses digest mode, so i >just disabled it on all lists, then deleted digest.mbox. i guess with this >setup, if a list gets a broken message which mailman can't handle, it will be >shunted and that's it, the rest of the lis

Re: [Mailman-Users] shunting

Mark Sapiro wrote: > Mark Sapiro wrote: >> There is a malformed message - something wrong with an attachment >> filename - in lists//digest.mbox for the offending list. >> >> See >> >> where the actual message problem is differe

Re: [Mailman-Users] shunting

Mark Sapiro wrote: > >There is a malformed message - something wrong with an attachment >filename - in lists//digest.mbox for the offending list. > >See > >where the actual message problem is different, but the solution is the >sa

Re: [Mailman-Users] shunting

Imre Gergely wrote: > >mailman just started to behave strangely. i have a couple (20-30) lists, and >one or two started to 'now work' all of a sudden. mail sent to that list >disappears. >i looked in /var/log/mailman/error, and there i found these errors: > >May 27 12:02:42 2006 (10050) Uncaught ru

[Mailman-Users] shunting

hi mailman just started to behave strangely. i have a couple (20-30) lists, and one or two started to 'now work' all of a sudden. mail sent to that list disappears. i looked in /var/log/mailman/error, and there i found these errors: May 27 12:02:42 2006 (10050) Uncaught runner exception: unpack

Re: [Mailman-Users] shunting problem (unpack list of wrong size)

Mike wrote: >It may also be difficult to properly recover the digest. > > > Hi Mike - problem solved and it had nothing to do with python, Mailman or any of the mail clients. When I went to edit the digest.mbox file I noticed it was 1.4 gigabytes in size (!). And this from a list that was jus

Re: [Mailman-Users] shunting problem (unpack list of wrong size)

Jim Savoy wrote: > >here is the dumbdb (the names were changed to protect the >innocent). I don't >see anything unusual, and I should point out that this list has been up >and running for >years without incident, and all of its users (only a dozen or so) have >sent to it >successfully until a co

Re: [Mailman-Users] shunting problem (unpack list of wrong size)

>Also, can you do either bin/dumpdb or bin/show_qfiles on the shunt >queue entry and perhaps see what the problem with the message is? > > > OK Mike - here is the dumbdb (the names were changed to protect the innocent). I don't see anything unusual, and I should point out that this list has bee

Re: [Mailman-Users] shunting problem (unpack list of wrong size)

Jim Savoy wrote: > > The error message we get is: > >== > > Mar 23 12:37:33 2006 (19290) Uncaught runner exception: unpack list of >wrong size > . > . > . > File "/mail/mail

[Mailman-Users] shunting problem (unpack list of wrong size)

Hello all, Of our 770+ lists, a couple have some shunting problems (the unshunt command fails to release queued up messages in the shunt directory). We are still running v2.1.5 with plans to upgrade in May, but I was hoping to get a fix for this before then. The error message we get is:

Re: [Mailman-Users] Shunting msgs.

Hi I think i found a solution to my problem at least. On further inspection the function that produced the error was the one appending the standard footer. When i remove the footer text in mailman, the msgs. are deliverd normally /thomas On Jan 2, 2006, at 12:48, Stephen J. Turnbull wrot

Re: [Mailman-Users] Shunting msgs.

> "Thomas" == Thomas von Hassel <[EMAIL PROTECTED]> writes: Thomas> Hi i have a mailman 2.1.6 installation on freebsd 4.9 Thomas> Many of the msgs. to my lists are beging shunted with this Thomas> error: Thomas> Uncaught runner exception: 'ascii' codec can't decode byte T

Re: [Mailman-Users] Shunting msgs.

Hi, Thomas von Hassel wrote: > Hi > > i have a mailman 2.1.6 installation on freebsd 4.9 > > Many of the msgs. to my lists are beging shunted with this error: > > Uncaught runner exception: 'ascii' codec can't decode byte 0xe6 in > position 18: ordinal not in range(128) > > Most of these msg

Re: [Mailman-Users] Shunting msgs.

On Jan 1, 2006, at 22:43, Thomas von Hassel wrote: > Hi > > i have a mailman 2.1.6 installation on freebsd 4.9 > > Many of the msgs. to my lists are beging shunted with this error: > > Uncaught runner exception: 'ascii' codec can't decode byte 0xe6 in > position 18: ordinal not in range(128) > >

[Mailman-Users] Shunting msgs.

Hi i have a mailman 2.1.6 installation on freebsd 4.9 Many of the msgs. to my lists are beging shunted with this error: Uncaught runner exception: 'ascii' codec can't decode byte 0xe6 in position 18: ordinal not in range(128) Most of these msgs. are normal, plaintext msgs. Is there a way to

[Mailman-Users] Shunting - Where Did they Go?

I am re-asking this as it seems I am not the only one with this problem and none of use received an answer. I had a problem and my MTA restart itself automatically. Mailman threw the following error:(SMTP log) Aug 27 04:38:41 2004 (26555) All recipients refused: please run connect() first Au

[Mailman-Users] Shunting - Where Did they Go?

I had a problem and my MTA restart itself automatically. Mailman threw the following error:(SMTP log) Aug 27 04:38:41 2004 (26555) All recipients refused: please run connect() first Aug 27 04:38:41 2004 (26555) All recipients refused: please run connect() first Aug 27 04:38:41 2004 (26555) All

[Mailman-Users] Shunting due to unknown encoding?

The following is an error log entry that *seems* to be associated with Mailman holding up delivery of messages. If I do a bin/unshunt, that seems to end the constipation for a while, although the same entries get into the error log anew. Any idea what can be done about this? It appears to me that

[Mailman-Users] shunting is expensive

The essential question is: Does anyone know how to either parallelize the shunting, so mailman process multiple messages and doesn't just stall at the shunting or make shunting at least a degree of magnitude faster. The full story: So, the ValueError: Empty module name is still a pretty big

[Mailman-Users] Shunting problem

- I create a new list - Subscribe my self to the list - Send a test message - Mass subscribe 50 email addresses to the new list - Send a message It never arrives and it shunted. I checked the error log and I get this. This is a little frustrating as new lists work but fail the moment I add new use