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 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 couple of weeks ago, using the same mail clients
they've always
used. I even blew away and re-created the list from scratch last week,
and it was
working fine until yesterday. Now, no users can send to it (myself
included). Everything
is put right into the shunt dira dn it stays there and cannot be
unshunted. Thanks.
This user is sending with the squirrelmail web program, but the list
members use other
clients as well (most of the users on this particular list are Mac users).
==
[- start pickle file -]
- start object 1 -
From [EMAIL PROTECTED] Wed Mar 22 21:27:56 2006
Received: from venus.netsrv.uleth.ca ([142.66.6.26]:47530
helo=webmail.uleth.ca)
by juliet.netsrv.uleth.ca with esmtpa (Exim 4.52) id
1FMHQS-00055L-4S
for [EMAIL PROTECTED]; Wed, 22 Mar 2006 21:27:56 -0700
Received: from 142.66.34.6 (SquirrelMail authenticated user usera)
by webmail.uleth.ca with HTTP; Wed, 22 Mar 2006 21:27:56 -0700 (MST)
Message-ID: [EMAIL PROTECTED]
Date: Wed, 22 Mar 2006 21:27:56 -0700 (MST)
From: User A [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
User-Agent: SquirrelMail/1.4.5
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
Subject: [ccc-l] Update
X-BeenThere: [EMAIL PROTECTED]
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: CCC Staff Mailing List ccc-l.uleth.ca
List-Unsubscribe: http://listserv.uleth.ca/mailman/listinfo/ccc-l,
mailto:[EMAIL PROTECTED]
List-Post: mailto:[EMAIL PROTECTED]
List-Help: mailto:[EMAIL PROTECTED]
List-Subscribe: http://listserv.uleth.ca/mailman/listinfo/ccc-l,
mailto:[EMAIL PROTECTED]
Hello all. Here is an update:
- start object 2 -
{ '_parsemsg': False,
'lang': 'en',
'listname': 'ccc-l',
'original_sender': '[EMAIL PROTECTED]',
'origsubj': 'Update',
'pipeline': [ 'ToDigest',
'ToArchive',
'ToUsenet',
'AfterDelivery',
'Acknowledge',
'ToOutgoing'],
'received_time': 1143088076.3202429,
'recips': [ '[EMAIL PROTECTED]',
'[EMAIL PROTECTED]',
'[EMAIL PROTECTED]',
'[EMAIL PROTECTED]',
'[EMAIL PROTECTED]'],
'tolist': 1,
'version': 3,
'whichq': '/mail/mailman/qfiles/in'}
[- end pickle file -]
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Security Policy:
http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
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 just re-created a week ago and only had 5 messages sent to it. Turns out the list owner set it up so that there was no limit on the size of the files users were allowed to send and one of the users sent a 1.4 gig .sit (Stuffit) file to the list (probably inadvertantly). Our MTA (exim) wouldn't have delivered it anyway, but Mailman and python were going wild trying to accomodate this large attachment (memory exhausted, plus a huge swap file being created each time), I also run a cron job every hour to unshunt things and that certainly added to the chaos. This also explains why other lists were either failing to deliver, or getting their messages late. Mailman was busy doing other things. It was not apparent from the messages in the shunt dir that this was a large file. Only digest.mbox revealed that. I am going to go through all of our lists now, searching for large digest files. Thanks for all your help. - jim - -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[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: == Mar 23 12:37:33 2006 (19290) Uncaught runner exception: unpack list of wrong size . . . File /mail/mailman/pythonlib/email/Utils.py, line 337, in decode_params charset, language, value = decode_rfc2231(EMPTYSTRING.join(value)) File /mail/mailman/pythonlib/email/Utils.py, line 284, in decode_rfc2231 charset, language, s = parts ValueError: unpack list of wrong size In pouring over the archives, Mark Shapiro wrote (in response to someone with the same problem): Other lists aren't having a problem because it's probably caused by one particular list member with a pathological MUA. And that this is related to the scrubbing of attachments for the digest or archives. But no one on this list is using the digest feature and archiving is turned off. Plus the user in question (the one sending the message) is using a generic webmail client, the same one many of our users employ, with no special character set or language options (that I can see anyway). Any ideas? Would an upgrade to 2.1.7 resolve this problem (I only say that because I perused the Mailman mailing list in reverse order from present date, and this issue was never raised again by anyone after 2.1.6 came out). Thanks! - jim - -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] subscription via -request
Hi all, I was wondering if there is a way to silently subscribe people to a list via the -request command processor (ie sending email commands to listname-request)? If I send the command: subscribe password nodigest [EMAIL PROTECTED] it works fine, but [EMAIL PROTECTED] is then sent a message asking that she confirm the subscription by clicking a link. Our users are confused enough as it is, and we would like to avoid this step. I realize that the confirmation step was created to prevent any old yahoo from subscribing people to lists without their consent, but how would any old yahoo know what the list password is? Seems like an unnecessary extra layer of protection. We are running Mailman 2.1.5. Thanks! - jim - PS I realize that we can silently subscribe people via the GUI and the command line, but we wish to do it via email and -request processor only. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] command-line query
I showed an example of one way to do this from the command line a couple of months back: http://mail.python.org/pipermail/mailman-users/2004-June/037287.html (Although that particular message shows how to moderate from the command line, so you'll want to change the mm_cfg.Yes to mm_cfg.No to make an 'unmoderate' tool.) Thanks Jim. I'll try it. PS Yesterday I began reading the mailman-users mailing list backwards and got as far as June 11th before leaving work. Your message was dated June 9th, so I would have found it today anyway! -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
[Mailman-Users] command-line query
Hi all, I am running Mailman v2.1.2 on a Linux Enterprise box. The membership of a number of our lists is dynamic and needs to be changed daily. I run a cronjob each morning that unsubscribes everyone and then re-subscribes the new members. Works fine with one slight hassle: I can't figure out how to doctor the 'moderation' flag from the command-line. By default the list is moderated, but some of the subscribers added are not to be moderated. Naturally I don't want to have to go into the GUI interface each day and change those flags! How can I set that from command line? It doesn't seem to be in the FAQ. Thanks! -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
