[Mailman-Users] Messages have stopped getting delivered to mailinglists

[Williams, Theona]

Here is what I see in the vette log. 
Jun 05 14:51:22 2008 (29076) Mailman post from held, message-id=n/a:
Message has implicit destination

~

When I run /u001/mailman/mail/mailman post mailman </dev/null
I receive the following message 

Group mismatch error.  Mailman expected the mail

wrapper script to be executed as group "mail", but

the system's mail server executed the mail script as

group "mailman".  Try tweaking the mail server to run the

script as group "mail", or re-run configure,

providing the command line option `--with-mail-gid=mailman'.


I am a bit skeptical to act on this error since I am getting the exact
same error on my test mailman server which works fine. Also, running the
./configure will erase many of the changes that I have made manually in
several files. Any suggestions? 

Theona Williams

-----Original Message-----
From: Mark Sapiro [mailto:mark at msapiro.net] 
Sent: Thursday, June 05, 2008 2:44 PM
To: Williams, Theona; mailman-users at python.org
Subject: RE: [Mailman-Users] Messages have stopped getting delivered to
mailinglists

Williams, Theona wrote:

>Received the following errors in /var/log/mailman/error file when I
>tried
>python /u001/mailman/scripts/post mailman </dev/null
>
>Jun 05 14:51:25 2008 mailowner(32760): mailowner script, list not
found:
>mailman
>
>
>Jun 05 14:51:25 2008 bounces(32761): bounces script, list not found:
>mailman 


Neither of those relates to the command you gave. The first is from the
'owner' script and the second is from the 'bounces' script.

Was there anything in the vette log?

If the post script invoked by

  python /u001/mailman/scripts/post mailman </dev/null

had issued the 'list not found' error, it would have been issued to the
terminal, so that indicates it didn't encounter that error.

This in turn indicates the wrapper that invokes the post, etc. scripts
is not invoking those in /u001/mailman/scripts/. This could mean that
/u001/mailman/mail/mailman was compiled with a different path (strings
/u001/mailman/mail/mailman might reveal this), or it could mean you
are running sendmail with smrsh, and the 'mailman' link in the smrsh
file (/var/adm/sm.bin, or where ever it happens to reside on your
system - alternatives include /etc/smrsh, /var/smrsh and
/usr/local/smrsh.) points to a different wrapper entirely.

-- 
Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan