It wasn't immediately obvious to me that the crontab in question needed to be installed under the "mailman" ID.
On FreeBSD, they have individual crontab entries, but also /etc/crontab -- where most of my stuff goes.
I've put this into mailman's crontab, and manually ran the qrunner, and the messages got delivered and the archive was visible. That seems to fix it major issue in question.
Note that confirmations of posts were not sent out -- and I've subsequently tried this since then, and the post gets processed, and I did configure it to send a confirmation back to the poster.
Yeah, the crontab was a flagrant oversight -- but maybe the docs could emphasize this a bit, for those that might run into this.
Thanks for everyone's help.
At 10:16 PM 7/3/2001 -0400, Forrest Aldrich wrote:
Here is my crontab, per your request:
# At 5PM every day, mail reminders to admins as to pending requests
0 17 * * * /usr/local/bin/python -S /local5/mailman/cron/checkdbs
#
# Noon, mail digests for lists that do periodic as well as threshhold delivery.
0 12 * * * /usr/local/bin/python -S /local5/mailman/cron/senddigests
#
# 5 AM on the first of each month, mail out password reminders.
0 5 1 * * /usr/local/bin/python -S /local5/mailman/cron/mailpasswds
#
# Every 5 mins, try to gate news to mail. You can comment this one out
# if you don't want to allow gating, or don't have any going on right now,
# or want to exclusively use a callback strategy instead of polling.
# 0,5,10,15,20,25,30,35,40,45,50,55 * * * * /usr/local/bin/python -S /local5/mail
man/cron/gate_news
#
# At 3:27am every night, regenerate the gzip'd archive file. Only
# turn this on if the internal archiver is used and
# GZIP_ARCHIVE_TXT_FILES is false in mm_cfg.py
27 3 * * * /usr/local/bin/python -S /local5/mailman/cron/nightly_gzip
#
# Retry failed deliveries once per minute.
* * * * * /usr/local/bin/python -S /local5/mailman/cron/qrunner
