Re: [Mailman-Users] Messages got stuck in "in" queue due to one"bad"message

Quoting Mark Sapiro <[EMAIL PROTECTED]>: > Xueshan Feng wrote: > > >Quoting Mark Sapiro <[EMAIL PROTECTED]>: > > > >>> All four of them? > > > >Only 3: > > > >mailman:/var/lib/mailman/qfiles# ps -ef | grep Inco > >list 21394 21383 0 18:45 ?00:00:17 /usr/bin/python > >/var/lib/mailman

Re: [Mailman-Users] Messages got stuck in "in" queue due to one"bad"message

Xueshan Feng wrote: >Quoting Mark Sapiro <[EMAIL PROTECTED]>: > >>> All four of them? > >Only 3: > >mailman:/var/lib/mailman/qfiles# ps -ef | grep Inco >list 21394 21383 0 18:45 ?00:00:17 /usr/bin/python >/var/lib/mailman/bin/qrunner --runner=IncomingRunner:0:4 -s >list 21395 2138

Re: [Mailman-Users] Messages got stuck in "in" queue due to one"bad"message

Quoting Mark Sapiro <[EMAIL PROTECTED]>: > Xueshan Feng wrote: > > >On Tue, 2007-02-20 at 15:37 -0800, Mark Sapiro wrote: > >> Xueshan Feng wrote: > >> > >> Actually, If I understand the situation correctly, IncomingRunner will > >> not be running. It will die and be restarted, but after the 10t

Re: [Mailman-Users] Messages got stuck in "in" queue due to one"bad"message

Xueshan Feng wrote: >On Tue, 2007-02-20 at 15:37 -0800, Mark Sapiro wrote: >> Xueshan Feng wrote: >> >> Actually, If I understand the situation correctly, IncomingRunner will >> not be running. It will die and be restarted, but after the 10th >> restart/die, it won't restart again (but this seems

Re: [Mailman-Users] Messages got stuck in "in" queue due to one"bad"message

Stephen J. Turnbull wrote: > >At least in earlier implementations of the email lib and Mailman, the >original parse of the message was not enclosed in the shunt mechanism, >so the exception got caught by the catchall handler, not the shunt >handler. You're right Stephen. I overlooked that. The deq

Re: [Mailman-Users] Messages got stuck in "in" queue due to one "bad"message

On Tue, 2007-02-20 at 15:37 -0800, Mark Sapiro wrote: > Xueshan Feng wrote: > > > >We are running mailman 2.1.9. Recently we had a problem that mailman's > >Incoming qrunner died hard, which caused messages accumulated under > >qfiles/in directory. Restarting mailman didn't help. We finally > >ide

Re: [Mailman-Users] Messages got stuck in "in" queue due to one "bad"message

Mark Sapiro writes: > >2. Why this message didn't get moved to shunt directory? > > I don't know why it didn't shunt. At least in earlier implementations of the email lib and Mailman, the original parse of the message was not enclosed in the shunt mechanism, so the exception got caught by the

Re: [Mailman-Users] Mailbox Not Found

Greg Sims wrote: > >For <[EMAIL PROTECTED]>, Site (dom.ain/xx.xx.xx.xx) said: 550 sorry, >no mailbox here by that name. (#5.7.17) You need aliases or whatever in your MTA to deliver such mail to Mailman. What you need depends on your MTA which is ? Searching the FAQ

Re: [Mailman-Users] Messages got stuck in "in" queue due to one "bad"message

Xueshan Feng wrote: > >We are running mailman 2.1.9. Recently we had a problem that mailman's >Incoming qrunner died hard, which caused messages accumulated under >qfiles/in directory. Restarting mailman didn't help. We finally >identified a message on top of the queue, moved it aside, restarted >

[Mailman-Users] Messages got stuck in "in" queue due to one "bad" message

Hello, We are running mailman 2.1.9. Recently we had a problem that mailman's Incoming qrunner died hard, which caused messages accumulated under qfiles/in directory. Restarting mailman didn't help. We finally identified a message on top of the queue, moved it aside, restarted mailman again, then

[Mailman-Users] Mailbox Not Found

Hi There, I have mailman installed, created a list, configured the list, loaded some email addresses and installed custom .html and .txt files. I tested the system by subscribing to the list using the custom subscribe.html file we've used in the past. I received a confirmation email requestin

Re: [Mailman-Users] importing held messages from dr system

That did it. Thank you very much for the help. On 2/20/07, Mark Sapiro <[EMAIL PROTECTED]> wrote: > > Lawren Quigley-Jones wrote: > > >Is there a way to import held messages from one mail system to > another? I > >have multiple mailman servers but only manage them from one web > interface. > >Wh

Re: [Mailman-Users] importing held messages from dr system

Lawren Quigley-Jones wrote: >Is there a way to import held messages from one mail system to another? I >have multiple mailman servers but only manage them from one web interface. >When a message gets held on one of the mail servers that is not primary it >is not accessible via the web interface.

Re: [Mailman-Users] Adding Mhonarc to existing Mailman installation

[EMAIL PROTECTED] wrote: > >What happens if I move a config.pck running on stock 2.1.9 (version >96) to this new tree? Is there something in Mailman that figures out >how to remunge the config.pck file? Yes! This is the key to migrating a list to a new version in any context. See the definitio

[Mailman-Users] Adding Mhonarc to existing Mailman installation

I am building a new Mailman 2.1.9 installation tree, and want to configure it with Mhonarc and Mnogosearch. I notice that the Mhonarc patches change the config.pck version number from 96 to 96.2 because there seem to be some changes to the file definition. I have signed up on the mmi mailman-mno

[Mailman-Users] importing held messages from dr system

Is there a way to import held messages from one mail system to another? I have multiple mailman servers but only manage them from one web interface. When a message gets held on one of the mail servers that is not primary it is not accessible via the web interface. I've tried simply copying the pc

Re: [Mailman-Users] Excluding one list from nightly htdig

Jason Ogresovich wrote: >All, > >We have several lists that are indexed with the nightly htdig script. >There is one list I would like to exclude from htdig (it's too big, not >very important, and brings the server to a crawl when htdig runs on this >list). I examined the list configuration options

[Mailman-Users] Excluding one list from nightly htdig

All, We have several lists that are indexed with the nightly htdig script. There is one list I would like to exclude from htdig (it's too big, not very important, and brings the server to a crawl when htdig runs on this list). I examined the list configuration options using the config_list scr