[Mailman-Users] messages aren't being delivered to users, but are in the archive

[Richard Barrett]

At 22:08 24/06/2003, jacob walcik wrote:
>yup, the mailman user's crontab was installed as part of the rpm
>installation, and i've also tried running qrunner manually w/ the
>command it's issuing, and i don't receive any errors.
>
>assuming mailman's home is /var/mailman, where would i look for the
>"qfiles" file.  a "find ./ -name "qfiles" -print" from /var/mailman
>doesn't return anything.

Given your install in /var/mailman and a normal MM 2.0.x install there 
should be a directory called /var/mailman/qfiles. The script in 
/var/mailman/scripts takes delivery of incoming messages from the MTA 
creates a .msg and a .db file in that directory. The qrunner subsequently 
takes those files and processes them, sending mail out etc.

The actual qfiles directory used for enqueueing incoming messages is 
defined by the config variable QUEUE_DIR in $prefx/Mailman/Defaults.py or 
possibly (and unusually) overridden $prefix/Mailman/mm_cfg.py. If that 
directory doesn't exist then something in your install may be screwed.

But looking again at your original post you say the message is getting into 
the archives. That says the message is passing through qfiles, being picked 
up by the qrunner and so you would expect there to be some trace of its 
progress in one of Mailman's log files.

But you say the directory says $prefix/logs doesn't exist. The log file 
directory is defined by the config variable LOG_DIR in 
$prefix/Mailman/Defaults.py or possibly (and unusually) overridden 
$prefix/Mailman/mm_cfg.py. If that directory doesn't exist then something 
in your install may be screwed.

What value does the config variable DELIVERY_MODULE in 
$prefix/Mailman/Defaults.py or possibly overridden 
$prefix/Mailman/mm_cfg.py have and also SMTPHOST.

Are there are no logs and no sign of what is happening exists in MM's 
error, post, smtp and smtp-failure logs.

>this is actually the version of mailman that shipped w/ redhat 7.3.
>i've got it running on a different machine that was installed via the
>same process.  i wouldn't necessarily have any issues w/ upgrading to
>the 2.1 branch (the automatic attachment and html email filtering would
>be nice), but i'd still like to know if there's any particular reason
>why this isn't working.
>
>On Tuesday, Jun 24, 2003, at 15:20 US/Central, Richard Barrett wrote:
>
>>At 20:59 24/06/2003, jacob walcik wrote:
>>>hello
>>>
>>>i just installed mailman 2.0.9 on redhat 7.3, and i've run into a
>>>snag.
>>>
>>>i created a new list called "test", added the aliases for it to
>>>/etc/procmail/aliases, ran "postalias /etc/procmail/aliases", and
>>>then sent a message to my newly created list.
>>>
>>>i can see the message in the archive, and i can see in my maillog
>>>where the message was piped out to the wrapper script, but i haven't
>>>received the message at either of the accounts that i subscribed to
>>>the list.
>>>
>>>i don't see any errors in /var/log/messages, the check_perms script
>>>comes back clean, and i don't have a "logs" directory in /var/mailman
>>>as the faq states i should.  does anyone have any suggestions? (if
>>>someone can tell me how to enable mailman's logging, i'd appreciate
>>>that as well)
>>>
>>>thanks!
>>
>>The message is probably lodged in $prefix/qfiles.
>>
>>Did you install the mailman user's crontab. Without the qrunner, which
>>is a cron job, no mail will pass through Mailman. Try installing the
>>crontab in $prefix/cron/crontab.in as the mailman uid's crontab
>>
>>Also you are way out of date with the MM version you are running. The
>>last version of was MM 2.0.x was 2.0.13 which was released nearly a
>>year ago and that has superceded this year by MM 2.1.x which is up to
>>2.1.2. You should certainly consider upgrading although this is
>>probably not the reason for your problem.
>>
>>>--
>>>jacob walcik
>>>jwalcik at mail.utexas.edu
>>
>>----------------------------------------------------------------------- 
>>-------
>>Richard Barrett
>>http://www.openinfo.co.uk
>>
>--
>jacob walcik
>jwalcik at mail.utexas.edu

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