I had all 8 qrunners running.
I decided to re-install the whole box.
This time it worked.
I used all the FreeBSD Ports installs.
But I had to go back to the
mailman install and reconfigure it
to take messages as "mailman"
it was expecting "nobody"
Once I did that it seems to be working.
Thanks for your help.
Rich Bates
On Nov 7, 2006, at 3:36 PM, Mark Sapiro wrote:
> Richard Bates wrote:
>>
>> I searched the faq:
>> and tried to do all the items in faq
>> 3.14. Troubleshooting: No mail going out to lists members
>
>
> Did you check that mailmanctl and all 8 qrunners are running. Your
> symptom is that at least one of IncomingRunner and OutgoingRunner is
> not running,
>
>
>> I did notice that the mailuser "nobody" is getting mail every
>> 5 min I don't know what this message means...
>> === startmessage
>> From [EMAIL PROTECTED] Tue Nov 7 12:55:00 2006
>> X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on
>> mail2.telehouse.com
>> X-Spam-Level:
>> X-Spam-Status: No, score=-0.0 required=3.5 tests=NO_RELAYS
>> autolearn=no
>> version=3.1.7
>> X-Original-To: operator
>> Delivered-To: [EMAIL PROTECTED]
>> From: [EMAIL PROTECTED] (Cron Daemon)
>> To: [EMAIL PROTECTED]
>> Subject: Cron <[EMAIL PROTECTED]> /usr/libexec/save-entropy
>> X-Cron-Env: <SHELL=/bin/sh>
>> X-Cron-Env: <PATH=/etc:/bin:/sbin:/usr/bin:/usr/sbin>
>> X-Cron-Env: <HOME=/>
>> X-Cron-Env: <LOGNAME=operator>
>> X-Cron-Env: <USER=operator>
>> Date: Tue, 7 Nov 2006 12:55:00 -0500 (EST)
>> X-Procmail-Status1: Global
>> X-Virus-Status: No
>> X-Virus-Checker-Version: clamassassin 1.2.3 with clamscan / ClamAV
>> 0.88.5/2035/Sun Oct 15 16:42:30 2006
>>
>> YES: not found
>> ===== end message
>
>
> If this is related to Mailman, it is because something is messed up in
> mailman's crontab. The crontab sgould be running several daily jobs at
> various times plus cron/gate_news every 5 minutes. Thes should run as
> the mailman user. It looks like crond is trying to run the command
> 'YES' as 'operator'.
>> Nov 7 12:40:20 mail2 postfix/local[70183]: 814EA9581F:
>> to=<[EMAIL PROTECTED]>, relay=local, delay=0.21,
>> delays=0.02/0.01/0/0.17, dsn=2.0.0, status=sent (delivered to
>> command: /usr/local/mailman/mail/mailman post mylist)
>
>
> So the mail is being delivered properly to the wrapper.
>
>
>> Here is the /usr/local/mailman/data/aliases file
>
>
> So the aliases are OK
>
>
>> here is teh /usr/local/mailman/Mailman/mm_cfg.py
>> ===== Start mm_cfg.py
>> # -*- python -*-
>>
>> # Copyright (C) 1998,1999,2000,2001,2002 by the Free Software
>> Foundation, Inc.
>> #
>> # This program is free software; you can redistribute it and/or
>>
>> ###############################################
>> # Here's where we get the distributed defaults.
>>
>> from Defaults import *
>>
>> ##################################################
>> # Put YOUR site-specific settings below this line.
>> IMAGE_Logos = '/images/'
>> MTA = 'Postfix'
>> DEFAULT_EMAIL_HOST = 'mail2.mysite.com'
>> DEFAULT_URL_HOST = 'mail2.mysite.com'
>> ===== End mm_cfg.py
>
>
> If the above settings for DEFAULT_EMAIL_HOST and DEFAULT_URL_HOST are
> different from what is in Defaults.py, you shold also have after the
> two settings
>
> VIRTUAL_HOSTS.clear()
> add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)
>
> although this is not your immediate problem.
>
>
> Are the messaages in one of Mailman's queues? Do
>
> ls -laR qfiles/
>
> Are there any files of form tttt.tttt+xxxxxx.pck in any of the
> subdirectories of qfiles/?. If so, in which subdirectory?
>
> --
> Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers,
> San Francisco Bay Area, California better use your sense - B. Dylan
>
------------------------------------------------------
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/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Security Policy:
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
