[Mailman-Users] Mail not going out

Richard Barrett r.barrett at openinfo.co.uk
Sun Jun 22 13:12:40 CEST 2003


At 04:05 22/06/2003, SysAdmin wrote:

>   Version of mailman: 2.1.2
>   How it was installed: source
>   Version of OS your server is running: Linux 2.2.16C32_III+VPN
>   The MTA: Postfix

With MM 2.1.x the processing of message queues is done by qrunner daemons 
which are normally started by $prefix/bin/mailmanctl script. Again, it is 
normal for mailmanctl to be run from a startup script.

The previous version, MM 2.0.x, used a qrunner cron job which ran every 
minute to do the same thing. The FAQ entry you have looked at may well be 
referring to MM 2.0.x rather than the 2.1.x you are running.

If you look in the INSTALL document in the MM build directory under the 
heading "4. Final system set-up" you will see it tells you to run 
mailmanctl to get things going, after some necessary precursor steps such 
as creating the 'mailman' site list. It also explains how to run mailmanctl 
via a startup script.


>I looked at the FAQ at http://www.python.org/cgi-bin/faqw-mm.py and found
>the entry about the cron (3.1.4(5)).
>
>These are my results:
>
>[mailman bin]# /usr/bin/python -S /home/mailman/cron/qrunner
>/usr/bin/python: can't open file '/home/mailman/cron/qrunner'
>
>[mailman bin]# cd ../cron
>
>[mailman cron]# ls
>bumpdigests  crontab.in  gate_news    nightly_gzip  paths.pyc
>checkdbs     disabled    mailpasswds  paths.py      senddigests
>
>[mailman cron]# ls -al
>total 52
>drwxrwsr-x   2 root     mailman      1024 Jun  3 08:50 .
>drwxrwsr-x  22 mailman  mailman      1024 May 29 17:44 ..
>-rwxr-xr-x   1 root     mailman      2374 May 29 17:19 bumpdigests
>-rwxr-xr-x   1 root     mailman      5716 May 29 17:19 checkdbs
>-rw-r--r--   1 root     mailman      1231 May 29 17:19 crontab.in
>-rwxr-xr-x   1 root     mailman      7643 May 29 17:19 disabled
>-rwxr-xr-x   1 root     mailman      9986 May 29 17:19 gate_news
>-rwxr-xr-x   1 root     mailman      8319 May 29 17:19 mailpasswds
>-rwxr-xr-x   1 root     mailman      4376 May 29 17:19 nightly_gzip
>-rw-r--r--   1 root     mailman      2425 May 29 17:19 paths.py
>-rw-r--r--   1 mailman  mailman       678 Jun  3 08:50 paths.pyc
>-rwxr-xr-x   1 root     mailman      2363 May 29 17:19 senddigests
>
>So, it appears that there is no /home/mailman/cron/qrunner file.
>How do I create one? Why was it not created at installation?
>
>Here's cron for mailman:
>
># DO NOT EDIT THIS FILE - edit the master and reinstall.
># (crontab.in installed on Tue Jun  3 08:46:25 2003)
># (Cron version -- $Id: crontab.c,v 2.13 1994/01/17 03:20:37 vixie Exp $)
># At 8AM every day, mail reminders to admins as to pending requests.
># They are less likely to ignore these reminders if they're mailed
># early in the morning, but of course, this is local time... ;)
>0 8 * * * /usr/bin/python -S /home/mailman/cron/checkdbs
>#
># At 9AM, send notifications to disabled members that are due to be
># reminded to re-enable their accounts.
>0 9 * * * /usr/bin/python -S /home/mailman/cron/disabled
>#
># Noon, mail digests for lists that do periodic as well as threshhold 
>delivery.
>0 12 * * * /usr/bin/python -S /home/mailman/cron/senddigests
>#
># 5 AM on the first of each month, mail out password reminders.
>0 5 1 * * /usr/bin/python -S /home/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/bin/python -S 
>/home/mailman/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/bin/python -S /home/mailman/cron/nightly_gzip
>
>So, there is no cron entry for qrunner being run every minute.
>
>What should the entry for this look like and why wasn't it created on
>installation?
>
>If anyone can help answer these questions without flaming me for being an
>idiot (I concede that already, so don't belabor it), I would appreciate
>the help. I'm obviously--and truly--a novice at Mailman, but want to
>become more knowledgeable.
>
>Thanks.
>Bill
>
>==============================================================================
>     Bill Casti, CQA                                 Email: help at quality.org
>      Text messaging: billcell at quality.org             Fax: 1 270 738 2842
>       Cell: +1 571 283 1802                 Tollfree Cell: 1 888 388-1640
>       Cell: +1 703 244 0497                 Tollfree Cell: 1 877 289 2645
>------------------------------------------------------------------------------
>                 There's no limit to what can be accomplished
>                  if it doesn't matter who gets the credit.
>==============================================================================
>
>
>
>------------------------------------------------------
>Mailman-Users mailing list
>Mailman-Users at python.org
>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: r.barrett at openinfo.co.uk
>Unsubscribe or change your options at
>http://mail.python.org/mailman/options/mailman-users/r.barrett%40openinfo.co.uk

------------------------------------------------------------------------------
Richard Barrett                                      http://www.openinfo.co.uk





More information about the Mailman-Users mailing list