Richard Healy wrote:
> Mark Sapiro wrote:
>
>> To elaborate on the "installation is wrong" theory, if the mail wrapper
>> is built pointing to a scripts/ directory with a paths.py with a
>> 'prefix' different from the 'prefix' in the bin/ d
Mark Sapiro wrote:
> To elaborate on the "installation is wrong" theory, if the mail wrapper
> is built pointing to a scripts/ directory with a paths.py with a
> 'prefix' different from the 'prefix' in the bin/ directory, this could
> mess things up.
>
> I gather Mailman was working and stopped w
Mark Sapiro wrote:
>
>
> Is your 'in' queue sliced? I.e., do you have anything involving
> QRUNNERS in mm_cfg.py? Or from the other view, in the 'ps' output
> does the command for IncomingRunner contain the option
> '--runner=IncomingRunner:0:1'? If it says 0:1, it's not sliced, but if
> for exa
Brad Knowles wrote:
> At 12:17 PM -0400 4/19/07, Richard Healy wrote:
>
>> Mail is being received and passed to mailman and
>> placed in
>> the mailman queue - where it sits.
>
> If the mail is getting into the Mailman queue and not being proces
I'm running mailman 2.1.5 on RH FC3.
Okay, I've searched the list and have read through many posts. I've read the
FAQ about what to check
(http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq03.014.htp).
Checked
everyone and made sure all was working: crons, mailmanctl, etc. Qrunner is
