I have just tested a post to a new list created with the 2.1.2 mailman. Pretty much the same behavior, the .pck and .db files are created in qfiles/out. They look normal when I peek in with dumpdb. But nothing leaves the machine. No apparent errors anywhere.
Can I run the "qrunner --runner=OutgoingRunner:0:1 -s" manually and add some kind of degugging flag? On Wed, Aug 27, 2003 at 07:56:38AM -0400, Charles Gagnon wrote: > I've just upgraded my Mailman installation from a 2.0.x to a 2.1.2 > on a Solaris 8 server using Python 2.2.2. And I think I have a > problem with the OutgoingRunner but I can't put my finger on it. > Here a the symtoms: > > 1. After I start mailman, the mailmanctl never exits. I can still > see it in the process table. > 2. The "mailmanctl stop" command stops everything but NOT the > OutgoingRunner. I have to kill that one manually. > 3. If I send subscription requests (email or web), I see them pending in > logs/subscribe. I see a new file get created in qfiles/out. But > nothing gets out. I never get the confirmation message. > 4. I see no errors in logs/smtp-failure or any other files that > would help me put my finger on the problem. -- Charles Gagnon | My views are my views and they http://unixrealm.com | do not represent those of anybody charlesg at unixrealm.com | but me. I went to a bookstore and asked the saleswoman where the Self Help section was, she said if she told me it would defeat the purpose. -- Dennis Miller ------------------------------------------------------ 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/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
