Update: I removed all the 120 or so files from the qfiles directory,
with the exception of the original newsletter posting to the list,
and the newsletter started going out almost immediately to the 1880
subscribers. So what was it about those files that caused Mailman to
choke? I've saved
I don't know if this is relevant to the problem, but I do have my MTA
(sendmail) configured to resolve domains. Could the large number of
undelivered messages in qfiles cause Mailman to choke on the timeouts
and resolve errors it's no doubt getting from sendmail?
.\\ichelle
--
> One thing I've had to do before is to ps jax |grep qrunner, kill any
>running qrunner processes, and then cd to the locks dir, and delete any
>remaing locks, so a clean instance of qrunner can start next time the cron
>is processed. Probably not the best thing to do, but I have had to do it
>b
hi,
i've just installed mailman 2.0.8 and have set up a mailinglist.
everything works fine and now I wanted to convert the old mbox archiv
file to mailman. so I did a "cat oldarchiv >> archiv.mbox" and then a
"bin/arch archiv". most of the mails get converted correctly but the
mails from december
>Is anything showing up in mailman's error log? $prefix/mailman/logs/error.
>There could be something there to shed some light on this. As far as,
>getting rid of the extra postings, if they're still floating around the
>qfiles dir, just delete the corrosponding .msg, and .db files for the extra
