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

[jacob walcik]

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.

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