Re: [Mailman-Users] Uncaught runner exception

On 3/12/19 2:37 AM, Lothar Schilling wrote: > > An example of a complete error message: > > Mar 11 17:02:22 2019 (15400) SHUNTING: > 1552320069.504329+15fb4f71a5404fd1af3dafbe2780486d5b474cc7 > Mar 11 17:22:37 2019 (15400) Uncaught runner exception: 'ascii' codec > can't decode byte 0xb5 in posit

Re: [Mailman-Users] Uncaught runner exception

> On 3/8/19 8:17 AM, Mark Sapiro wrote: >> On 3/8/19 12:05 AM, Lothar Schilling wrote: >>> Am 07.03.2019 um 23:54 schrieb Mark Sapiro: I would still like to find the underlying issue. I have been unable to duplicate it locally. I would appreciate it if before you run bin/unshunt, yo

Re: [Mailman-Users] Uncaught runner exception

On 3/8/19 8:17 AM, Mark Sapiro wrote: > On 3/8/19 12:05 AM, Lothar Schilling wrote: >> Am 07.03.2019 um 23:54 schrieb Mark Sapiro: > >>> I would still like to find the underlying issue. I have been unable to >>> duplicate it locally. I would appreciate it if before you run >>> bin/unshunt, you cou

Re: [Mailman-Users] Uncaught runner exception

On 3/8/19 12:05 AM, Lothar Schilling wrote: > Am 07.03.2019 um 23:54 schrieb Mark Sapiro: >> >> You can now reprocess them and add them to the archive by running >> Mailman's 'bin/unshunt' command. > Oh, that's what I did, unshunting them. They were processed and > archived. But the messages - almo

Re: [Mailman-Users] Uncaught runner exception

Am 07.03.2019 um 23:54 schrieb Mark Sapiro: > On 3/6/19 2:03 AM, Lothar Schilling wrote: > >> Following your instruction errors get now logged like this (where x is >> lower case, X upper case alphabet). >> >> Mar 06 10:36:56 2019 (16870) Exception in fixAuthor: Kxx Wxxx >> Mar 06 10:36:56 2019 (16

Re: [Mailman-Users] Uncaught runner exception

On 3/6/19 2:03 AM, Lothar Schilling wrote: > Following your instruction errors get now logged like this (where x is > lower case, X upper case alphabet). > > Mar 06 10:36:56 2019 (16870) Exception in fixAuthor: Kxx Wxxx > Mar 06 10:36:56 2019 (16870) Exception in fixAuthor: NXX - Fx▒xxx XX >

Re: [Mailman-Users] Uncaught runner exception

Thank you and sorry for my belated answer. Was out of office for a few days, carneval season in Germany... Am 02.03.2019 um 23:20 schrieb Mark Sapiro: > On 3/1/19 9:00 PM, Mark Sapiro wrote: >> To try to diagnose this further, you could try: >> >> === modified file 'Mailman/Archiver/pipermail.py'

Re: [Mailman-Users] Uncaught runner exception

On 3/1/19 9:00 PM, Mark Sapiro wrote: > > To try to diagnose this further, you could try: > > === modified file 'Mailman/Archiver/pipermail.py' > --- Mailman/Archiver/pipermail.py 2018-05-03 21:23:47 + > +++ Mailman/Archiver/pipermail.py 2019-03-02 04:51:23 + > @@ -60,9 +60,12 @@

Re: [Mailman-Users] Uncaught runner exception

On 3/1/19 9:15 AM, Mark Sapiro wrote: > On 2/28/19 5:26 AM, Lothar Schilling wrote: >> Hi everybody, >> >> a few weeks ago I upgraded from 2.1.16 (as far as I can remember...) to >> 2.1.29. Everything seemed to work fine at first. But then I found out >> that a lot of posts - actually far more than

[Mailman-Users] Uncaught runner exception

On 2/28/19 5:26 AM, Lothar Schilling wrote: > Hi everybody, > > a few weeks ago I upgraded from 2.1.16 (as far as I can remember...) to > 2.1.29. Everything seemed to work fine at first. But then I found out > that a lot of posts - actually far more than half of them - aren't > archived any longer

[Mailman-Users] Uncaught runner exception

Hi everybody, a few weeks ago I upgraded from 2.1.16 (as far as I can remember...) to 2.1.29. Everything seemed to work fine at first. But then I found out that a lot of posts - actually far more than half of them - aren't archived any longer. What logging the errors tells me is this: Feb 28 12:2

Re: [Mailman-Users] "Uncaught runner exception, No such file or directory" for files in "bounces" directory

--On 25. Juni 2012 08:22:32 -0700 Mark Sapiro wrote: See the FAQ at . Oops ... sorry. There was in fact a very old BounceRunner that had somehow survived a restart of Mailman. Thanks, Sebastian -- .:.Sebastian Hagedorn - RZKR-R1 (Gebäude 52), Zimmer 18.:.

Re: [Mailman-Users] "Uncaught runner exception, No such file or directory" for files in "bounces" directory

Sebastian Hagedorn wrote: > >Every day, we get several of these entries in the error log: > >2.1.14: > >Jun 25 08:00:17 2012 (12651) Skipping and preserving unparseable message: >1340604017.5663309+f03cd934fd9f24fb5ee97e641a2bf0611a43df85 >Jun 25 08:00:17 2012 (12651) Uncaught runner exception: [Er

[Mailman-Users] "Uncaught runner exception, No such file or directory" for files in "bounces" directory

Hi, today we successfully upgraded our installation from 2.1.14 to 2.1.15. Thanks for that! I have to admit that Mailman generally works so flawlessly that I usually don't look at its logs. Because of the update, today I did. And I noticed a pattern that I don't understand. It's not new, but I

Re: [Mailman-Users] Uncaught runner exception: 'ascii' codec can'tencode character u'\u201c'

On Feb 5, 2012, at 2:37 PM, Mark Sapiro wrote: > Sahil Tandon wrote: > >> I am seeing this error with all mail sent to just one (of several) >> mailman mailing lists that are operating without problems. I found some >> related discussions in the archives, but nothing that (as far as I could >>

Re: [Mailman-Users] Uncaught runner exception: 'ascii' codec can'tencode character u'\u201c'

Sahil Tandon wrote: >I am seeing this error with all mail sent to just one (of several) >mailman mailing lists that are operating without problems. I found some >related discussions in the archives, but nothing that (as far as I could >tell) corresponds to what I am seeing. > >Sorry for my MUA's

[Mailman-Users] Uncaught runner exception: 'ascii' codec can't encode character u'\u201c'

I am seeing this error with all mail sent to just one (of several) mailman mailing lists that are operating without problems. I found some related discussions in the archives, but nothing that (as far as I could tell) corresponds to what I am seeing. Sorry for my MUA's line wrapping: --- Feb 04

Re: [Mailman-Users] Uncaught Runner Exception

On 18/04/10 01:43, Mark Sapiro wrote: Mark Sapiro wrote: It appears that you (or someone) has installed the Spamassassin.py/spamd.py custom handler from and included it in the GLOBAL_PIPELINE or a lists' pipeline. Actually, on closer inspectio

Re: [Mailman-Users] Uncaught Runner Exception

Mark Sapiro wrote: > It appears that you (or someone) has installed the > Spamassassin.py/spamd.py custom handler from > and included it in > the GLOBAL_PIPELINE or a lists' pipeline. Actually, on closer inspection, I think the most current Spamass

Re: [Mailman-Users] Uncaught Runner Exception

James Kemp wrote: > >Over the last couple of weeks I've noticed that a number of legitimate >e-mails have failed to be delivered. All of these have been shunted and >an error like the one repeated below is written to the error log. [...] >Apr 17 21:22:28 2010 (2558) Uncaught runner exception: [Er

[Mailman-Users] Uncaught Runner Exception

I'm running mailman 2.1.13 on Ubuntu 9.10 out of the Ubuntu repositories. Mail server is postfix and I also have Apache and spamassassin on the same box, again all from the ubuntu repositories. Over the last couple of weeks I've noticed that a number of legitimate e-mails have failed to be d

Re: [Mailman-Users] Uncaught runner exception: regular_exclude_lists

> It has been implemented on the 2.2 branch which is not yet released, so > yes, you need to apply the patch to 2.1.12 if you need the > functionality. > > Also, rather than incrementing Version.DATA_FILE_VERSION further and > setting yourself up for this kind of problem again, you could leave it

Re: [Mailman-Users] Uncaught runner exception: regular_exclude_lists

Adam Nielsen wrote: >> >> Did the old installation have patches that increased it's >> DATA_FILE_VERSION? > >Ah, of course, I completely forgot about that! Yes, I had applied this >patch as you recommended when I installed the old version back in 2007: > >http://sourceforge.net/tracker/index.php?

Re: [Mailman-Users] Uncaught runner exception: regular_exclude_lists

> It appears that the new server is running 2.1.10 or later with the > "sibling lists" feature, and the old server from which the lists were > moved did not have this feature, so the lists did not have the > corresponding regular_exclude_lists and regular_include_lists > attributes. > > However, t

Re: [Mailman-Users] Uncaught runner exception: regular_exclude_lists

Adam Nielsen wrote: > >I've followed the FAQ to move some lists across to a new server, but now >on the new machine any message posted to a list gets passed to Mailman >and then disappears. The Mailman error log says this: > >Sep 24 10:34:18 2009 (5311) Uncaught runner exception: regular_exclude_l

[Mailman-Users] Uncaught runner exception: regular_exclude_lists

Hi all, I've followed the FAQ to move some lists across to a new server, but now on the new machine any message posted to a list gets passed to Mailman and then disappears. The Mailman error log says this: Sep 24 10:34:18 2009 (5311) Uncaught runner exception: regular_exclude_lists Sep 24 10:34:

Re: [Mailman-Users] Uncaught runner exception: unknownencoding:us-ascii

rp...@kinfolk.org wrote: > >On 2 Mar 2009 at 10:24, Mark Sapiro wrote: > >> >> Are you also getting many errors like the following? >> >> >Mar 02 10:39:54 2009 (30278) Failed to unlink/preserve backup file: >> >/var/mailman/qfiles/in/1236014500.0552149+5aed32c1bfbe6e4ac85c02c3518 >> >5 46e179e37b

Re: [Mailman-Users] Uncaught runner exception: unknownencoding:us-ascii

On 2 Mar 2009 at 10:24, Mark Sapiro wrote: > rp...@kinfolk.org wrote: > > > > # python > >Python 2.6.1 (r261:67515, Feb 28 2009, 15:18:21) > >[GCC 4.2.4] on linux2 > >Type "help", "copyright", "credits" or "license" for more > >information. > > > > > >I re-ran the configure and install of mailm

Re: [Mailman-Users] Uncaught runner exception: unknownencoding:us-ascii

rp...@kinfolk.org wrote: > > # python >Python 2.6.1 (r261:67515, Feb 28 2009, 15:18:21) >[GCC 4.2.4] on linux2 >Type "help", "copyright", "credits" or "license" for more >information. > > >I re-ran the configure and install of mailman, ran unshunt and the >errors still show using python 2.5: Wh

Re: [Mailman-Users] Uncaught runner exception: unknown encoding:us-ascii

On 2 Mar 2009 at 9:10, Mark Sapiro wrote: > rp...@kinfolk.org wrote: > > >Please help! Since upgrading to Mailman 2.1.12 and Python 2.6.1, my > >error log is filling up with messages like this and virtually no > >messages are moving through my mailing lists. Based on a search of > >the archives

Re: [Mailman-Users] Uncaught runner exception: unknown encoding:us-ascii

rp...@kinfolk.org wrote: >Please help! Since upgrading to Mailman 2.1.12 and Python 2.6.1, my >error log is filling up with messages like this and virtually no >messages are moving through my mailing lists. Based on a search of >the archives, I removed ALL digest.mbox files and ran unshunt. No

[Mailman-Users] Uncaught runner exception: unknown encoding: us-ascii

Please help! Since upgrading to Mailman 2.1.12 and Python 2.6.1, my error log is filling up with messages like this and virtually no messages are moving through my mailing lists. Based on a search of the archives, I removed ALL digest.mbox files and ran unshunt. No messages moved and the errors

Re: [Mailman-Users] Uncaught runner exception: int argument required

On 10/15/2008 11:23 AM, Mark Sapiro wrote: >>def rejection_notice(self, mlist): >>kb = self.__limit >>return _('''Your message was too big; please trim it to less than >> %(limit)d KB in size.''') > I din't know why you changed the above line, but the problem is where > you

Re: [Mailman-Users] Uncaught runner exception: int argument required

On 10/14/2008, Charles Marcus ([EMAIL PROTECTED]) wrote: > I'm only on 2.5.2, but I think I did update fairly recently... Umm... sorry, I had started to reply to the message about an issue with python 2.6 because I thought it might be related (but then decided to start a new thread), and forgot to

Re: [Mailman-Users] Uncaught runner exception: int argument required

Charles Marcus wrote: > >And here's the customized block in Hold.py: > >(Hmmm... did something weird happen when I copy/pasted after the last >update? Are there supposed to be dbl underscores (__) there?) Yes, the __ are correct. >Beginning at line 93: >class MessageTooBig(Errors.HoldMessage):

[Mailman-Users] Uncaught runner exception: int argument required

Greetings, Ok, I just discovered that I'm not getting notifications when someone sends a message that is too big... usually I get a notification, and can click the link and 'Tend to pending moderator requests', and discard & forward a copy to the list owner. I don't get too many of these, so didn

Re: [Mailman-Users] Uncaught runner exception: unknown encoding: gb2312

Thanks, added the line to the path.py in running system. this seems to be the solution in my case. First test was successful. I'll patch sources asap. Kind Regards RPr [...] Try the following in interactive python: >>> x = unicode('abcde', 'gb2312') >>> y = x.encode('gb2312') If either of

Re: [Mailman-Users] Uncaught runner exception: unknown encoding: gb2312

] Uncaught runner exception: unknown encoding: gb2312 On 6/22/06, Reinhard Proessler <[EMAIL PROTECTED]> wrote: > I searched in the Internet and mailing-lists and found only a hint to > install Chinesecodecs. But after applying these ChineseCodecs-1.1.0p > to python site-packa

Re: [Mailman-Users] Uncaught runner exception: unknown encoding: gb2312

Reinhard Proessler wrote: > >Some users reports that emails from a Chinese customer >do not reach the recipients from a list. The mails reach >our system, where stored in the archive folder, but not >forwarded to the list member. > >I took a look to the mailman error log and found (only) this entr

Re: [Mailman-Users] Uncaught runner exception: unknown encoding: gb2312

On 6/22/06, Reinhard Proessler <[EMAIL PROTECTED]> wrote: > I searched in the Internet and mailing-lists and found only a hint to > install > Chinesecodecs. But after applying these ChineseCodecs-1.1.0p to > python site-packages with python installer the problem still exists. Did you restart mailm

[Mailman-Users] Uncaught runner exception: unknown encoding: gb2312

Hello Some users reports that emails from a Chinese customer do not reach the recipients from a list. The mails reach our system, where stored in the archive folder, but not forwarded to the list member. I took a look to the mailman error log and found (only) this entry: Jun 21 16

Re: [Mailman-Users] Uncaught runner exception: 'utf8' codeccan'tdecode bytes in position 1-4: invalid data

Mark, I found the problematic email, look at this: ...more mail data here --TB36FDmn/VVEgNH/ Content-Type: application/msword Content-Disposition: attachment; filename*=utf-8''C%F3mo%20montar%20un%20servidor%20Samba%20PDC%20en%20una%20red%20de%20m%E1quinas%20MS%20Windows%20XP% Content-Trans

Re: [Mailman-Users] Uncaught runner exception: 'utf8' codeccan'tdecode bytes in position 1-4: invalid data

Aliet Santiesteban Sifontes wrote: >Thank's Mark, how could I find the bad message, You have to look through the digest.mbox file and find Content-Disposition: headers. Typically, such a header might look like Content-Disposition: attachment; filename="Some_name.ext" In your case, the

Re: [Mailman-Users] Uncaught runner exception: 'utf8' codec can'tdecode bytes in position 1-4: invalid data

Thank's Mark, how could I find the bad message, I'm worried because If I can make the list work again, I have the risk this happens again, is there any patch for this??. I think that this can be a potencial dos attack to other lists on the net. Best regards --- Mark Sapiro <[EMAIL PROTECTED]> wrot

Re: [Mailman-Users] Uncaught runner exception: 'utf8' codec can'tdecode bytes in position 1-4: invalid data

Aliet Santiesteban Sifontes wrote: >Hi list, I'm running mailman for several lists on >debian sarge, mailman-2.1.5-8, suddenly one of of the >lists stops working, maybe by spam or dos attack using >a bug in mailman, here the error, any ideas on how ti >fix this??: >Sep 11 13:34:35 2005 (12535) Unc

[Mailman-Users] Uncaught runner exception: 'utf8' codec can't decode bytes in position 1-4: invalid data

Hi list, I'm running mailman for several lists on debian sarge, mailman-2.1.5-8, suddenly one of of the lists stops working, maybe by spam or dos attack using a bug in mailman, here the error, any ideas on how ti fix this??: Sep 11 13:34:35 2005 (12535) Uncaught runner exception: 'utf8' codec can't

Re: [Mailman-Users] Uncaught runner exception

Salada, Duncan S.wrote: > >I have a follow-up question. Is there a source for information about the >contents of the qfiles and logs directories? Part of my time in dealing with >this problem was spent trying to figure out how to follow the path of a >message through mailman's different logs a

Re: [Mailman-Users] Uncaught runner exception

-3222 x375 > -Original Message- > From: Mark Sapiro [mailto:[EMAIL PROTECTED] > Sent: Monday, June 06, 2005 4:21 PM > To: Salada, Duncan S.; mailman-users@python.org > Subject: Re: [Mailman-Users] Uncaught runner exception > > > Salada, Duncan S.wrote: > > >I have a pr

Re: [Mailman-Users] Uncaught runner exception

Salada, Duncan S.wrote: >I have a problem with one of my lists. I have 4 lists, and 3 seem to be >working fine. The fourth one worked fine for the first couple of weeks, but >then started having problems. No changes were made to the configuration >during that time. The problem is this: mail

[Mailman-Users] Uncaught runner exception

I have a problem with one of my lists. I have 4 lists, and 3 seem to be working fine. The fourth one worked fine for the first couple of weeks, but then started having problems. No changes were made to the configuration during that time. The problem is this: mail will not go out to any of th

[Mailman-Users] Uncaught runner exception: 'str' object has no attribute 'get_sender'

Through my own stupidity, my qrunner was not running for a while (I forgot about an apt-get upgrade in progress). The messages that got sent to my lists during this time seem to be sitting in /var/lib/mailman/qfiles/shunt/ I cd'ed to /var/lib/mailman/ and ran python /usr/lib/mailman/bin/unshunt

[Mailman-Users] Uncaught runner exception: unknown encoding

Greetings, Yesterday morning I learned that my mailing lists weren't processing messages. When I checked, I discovered that qrunner wasn't running. That was easily fixed with "mailmanctl restart". This morning I decided to investigate and looked at /var/log/mailman/errors where I found Sep 02

Re: [Mailman-Users] Uncaught runner exception

Hi, David Relson wrote: FYI: Jun 04 09:09:06 2004 (18876) SHUNTING: 1086170174.3516641+c52aafd5601316eadd825f0a9ec902c5ac8fbc7e Jun 04 09:09:06 2004 (18876) Uncaught runner exception: ISO-2022-JP encoding error: invalid character \x96 Well behaved japanese mailers do not produce such an error and t

[Mailman-Users] Uncaught runner exception

FYI: Jun 04 09:09:06 2004 (18876) SHUNTING: 1086170174.3516641+c52aafd5601316eadd825f0a9ec902c5ac8fbc7e Jun 04 09:09:06 2004 (18876) Uncaught runner exception: ISO-2022-JP encoding error: invalid character \x96 Jun 04 09:09:06 2004 (18876) Traceback (most recent call last): File "/usr/lib/mailma

Re: [Mailman-Users] Uncaught runner exception: ASCII encoding error: ordinal not in range

Hi Jon, I'm running mailman-2.1.4 and I just received one of these exceptions this morning while mailman was sending out a reminder mail. So I'm not sure this bug is necessarily fixed as you suggested in October. My (2.1.4) trace is at the end of the message. -derek On Thu Oct 9 09:00:41 EDT 2

Re: [Mailman-Users] Uncaught runner exception: ASCII encoding error: ordinal not in range

I'm fairly certain that there is a patch that handles this problem, but you might want to simply update to the latest version of Mailman. I believe that problem is caused by a character that is out of range for the expected values. The character is probably one used by a different language. Your

[Mailman-Users] Uncaught runner exception: ASCII encoding error: ordinal not in range

For the second time in a few weeks, one of my lists has stopped delivering mail. (Mailman 2.1.1 w/ sendmail) Can anyone possibly provide some ideas on what the error below might mean and how I might solve it? Last time I ended up deleting and recreating the list as the solution. Could this possi

Re: [Mailman-Users] Uncaught runner exception: iterable argumentrequired

This bug report and the patch attached my help. Always worth checking the bug tracker :) http://sourceforge.net/tracker/ ?group_id=103&atid=300103&func=detail&aid=747470 On Tuesday, August 12, 2003, at 10:40 pm, Brian Burdette wrote: This is mailman 2.1.2 on RedHat linux 8.0 I get the follo

[Mailman-Users] Uncaught runner exception: iterable argumentrequired

This is mailman 2.1.2 on RedHat linux 8.0 I get the following error entry when sending to certain lists. mail is shunted. Rebuilding those lists resolves the problem, temporarily. Anyone able to shed a bit of light on this, or should I move it to mailman developers? Is more data needed, is th

[Mailman-Users] Uncaught runner exception

Hi I'm running mailman for the mailing list of http://www.aarons-jokes.com/ I'm currently sending out over 150,000 mails (over 7 lists) a day using an "announce only" type setup. Problem is mailman has been causing the server to crash on a regular basis. I am get VERY large number (1000's) of t

Re: [Mailman-Users] Uncaught runner exception

Just as a guess, I would say that you need to monitor your servers memory allocation while sending out a message. Your list may have outgrown the current resources. If this happens, then corruption can creep into your database and you may need to rebuild it. Do a database check. Also dump out y

[Mailman-Users] Uncaught runner exception

Hi I'm running mailman for the mailing list of http://www.aarons-jokes.com/ I'm currently sending out over 150,000 mails (over 7 lists) a day using an "announce only" type setup. Problem is mailman has been causing the server to crash on a regular basis. I am get VERY large number (1000's) of t

Re: [Mailman-Users] Uncaught runner exception: 'generator' object has no attribute 'insert'

Well, one thing you are doing wrong is sending this to the users list. All comments and problems for the 2.1 alpha should be directed to the dev list. The code base for 2.1 changes often enough that only the developers and a few power users are up to date on it. Jon Carnes === On Sunday 25 No

[Mailman-Users] Uncaught runner exception: 'generator' object has no attribute 'insert'

Hello, I am new to mailman, so bear with me. I have downloaded mailman-2.0.7 which works fine, than I have tried mailman 2.1 (also from cvs), and getting error message below in error log whenever I try to send email to [EMAIL PROTECTED] with word help in Subject line (I have tried also word help