On 31/03/2011 02:59, Mark Sapiro wrote:
[/snip]
The lists/LISTNAME/config.pck file for the affected list is corrupted
in some way. The stored list object in this file has no msg_footer
attribute. This is an "impossible" error unless you maybe deleted it
with bin/withlist.
Can you access the web
Mollatt Ntini wrote:
>
>I have been having a rather queer problem. I am running several lists
>on my list server but having a problem with only one list.
[...]
>and an extract from the error log:
>
>=
>Mar 30 16:56:41 2011 (31246) SHUNTING:
>1301496673.9261229+2fab5f43dddedddbe043032cebf1eb3
Dear List,
I have been having a rather queer problem. I am running several lists
on my list server but having a problem with only one list. I have gone
through my server and tried to compare configs and have done check_perms
but have found no clue as to why it is failing to deliver to list
m
Jannis Leidel wrote:
>
>I recently upgaded on a debian server to mailman 2.1.8 and came
>across some problems.
>Emails sent to any of the running lists are shunted and therefore not
>delivered..
>
>The log states:
>
>May 04 17:29:48 2006 (16886) Uncaught runner exception: 'ascii' codec
>can't d
Hi list,
I recently upgaded on a debian server to mailman 2.1.8 and came
across some problems.
Emails sent to any of the running lists are shunted and therefore not
delivered..
The log states:
May 04 17:29:48 2006 (16886) Uncaught runner exception: 'ascii' codec
can't decode byte 0xfc in p
On 4/17/06, Mark Sapiro <[EMAIL PROTECTED]> wrote:
> Probably, because the queue entries may be defective. I.e. it appears
> that the message object in the .pck file is an unparsed string but
> '_parsemsg' is False in the message metadata.
Indeed, your supposition seems to be correct:
<- star
Patrick Bogen wrote:
>Traceback is as follows:
>
>Apr 17 11:37:11 2006 (11200) SHUNTING:
>1143744566.924134+af04699cdb8ee11fa521f987815fb056a487203c
>Apr 17 11:37:11 2006 (11200) Uncaught runner exception: 'str' object
>has no attribute 'get_sender'
>Apr 17 11:37:11 2006 (11200) Traceback (most re
Traceback is as follows:
Apr 17 11:37:11 2006 (11200) SHUNTING:
1143744566.924134+af04699cdb8ee11fa521f987815fb056a487203c
Apr 17 11:37:11 2006 (11200) Uncaught runner exception: 'str' object
has no attribute 'get_sender'
Apr 17 11:37:11 2006 (11200) Traceback (most recent call last):
File "/usr
George Booth wrote:
>
>Hmm...when I recreated the list the last time, I actually did turn off
>digesting. It doesn't require digesting, so I figured I'd turn it off, but
>got distracted by several fires that needed attending to and forgot I'd done
>that. Strange that none of the other lists are
- Original Message -
From: "Mark Sapiro" <[EMAIL PROTECTED]>
To: "George Booth" <[EMAIL PROTECTED]>;
Sent: Monday, April 04, 2005 2:44 PM
Subject: Re: [Mailman-Users] Shunted messages idea?
Your error trace below shows a problem in scrubbing an attachmen
George Booth wrote:
>
>There weren't any errors at all when running the unshunt command; the
>messages simply would be shunted again. However, this is even stranger; I
>blew away and recreated the list several times last week, all to no avail;
>today, I tried that one more time, and it seems to
- Original Message -
From: "Mark Sapiro" <[EMAIL PROTECTED]>
To: "George Booth" <[EMAIL PROTECTED]>;
Sent: Monday, April 04, 2005 12:02 PM
Subject: Re: [Mailman-Users] Shunted messages idea?
George Booth wrote:
I've encountered a very strange er
George Booth wrote:
>I've encountered a very strange error. Out of 779 lists, we have 1 that
>keeps shunting messages. Currently, there are 34 shunted messages that will
>not unshunt. I've completely blown away the list and recreated it several
>times, all to no avail. Any suggestions would be
I've encountered a very strange error. Out of 779 lists, we have 1 that
keeps shunting messages. Currently, there are 34 shunted messages that will
not unshunt. I've completely blown away the list and recreated it several
times, all to no avail. Any suggestions would be appreciated.
Running Mai
Mailman-Users:
I had a RedHat Linux server running mailman 2.1.5. I am trying to
determine what causes a message to be shunted. I have mailman configured
for smtpdirect to my primary mailserver. When I use the unshunt command
the message is delivered but the .pck file remains in the qfiles/sunt
Hi
For some reason, I had mailman choking on some messages but not others,
and a reinstall of mailman didn't fix it.. neither did a reinstall of
python. There were over 5400 files in qfiles/shunt, which was fun. I've
transferred my lists to a new system, copied across those files, and run
"unshu
16 matches
Mail list logo
