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
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
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
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
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
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
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
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
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
>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
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
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:
- 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
13 matches
Mail list logo
