Hi Mark,

We're getting closer.  I changed the symbolic link in /etc/smrsh to the
following:

[EMAIL PROTECTED] smrsh]# ls -l
total 0
lrwxrwxrwx  1 root root 31 May  6 13:18 mailman ->
/usr/local/mailman/mail/mailman

Now I am getting the following error:

----- Forwarded Message ----
From: Mail Delivery Subsystem <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Sent: Tuesday, May 6, 2008 1:11:04 PM
Subject: Returned mail: see transcript for details

The original message was received at Tue, 6 May 2008 13:11:04 -0400
from my-hostname.domain.com [111.111.111.111]

  ----- The following addresses had permanent fatal errors -----
"|/usr/local/mailman/mail/mailman join test"
    (reason: 2)
    (expanded from: <[EMAIL PROTECTED]>)

  ----- Transcript of session follows -----
Group mismatch error.  Mailman expected the mail
wrapper script to be executed as group "mailman", but
the system's mail server executed the mail script as
group "mail".  Try tweaking the mail server to run the
script as group "mailman", or re-run configure, 
providing the command line option `--with-mail-gid=mail'.
554 5.3.0 unknown mailer error 2
Reporting-MTA: dns; my.domain.com
Received-From-MTA: DNS; my-hostname.domain.com
Arrival-Date: Tue, 6 May 2008 13:11:04 -0400

Final-Recipient: RFC822; [EMAIL PROTECTED]
X-Actual-Recipient: X-Unix; |/usr/local/mailman/mail/mailman join test
Action: failed
Status: 5.0.0
Diagnostic-Code: X-Unix; 2
Last-Attempt-Date: Tue, 6 May 2008 13:11:04 -0400

I tried to change the ownership of the symbolic link to mailman, but
that didn't seem to take:

[EMAIL PROTECTED] smrsh]# chown :mailman mailman
[EMAIL PROTECTED] smrsh]# ls -l
total 0
lrwxrwxrwx  1 root root 31 May  6 13:18 mailman ->
/usr/local/mailman/mail/mailman
[EMAIL PROTECTED] smrsh]#  

Thanks,

Bill


-----Original Message-----
From: Mark Sapiro [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, May 06, 2008 11:26 AM
To: Bill Honneus (honneus); mailman-users@python.org
Subject: RE: [Mailman-Users] Join List Problem

Bill Honneus wrote:
>
>I renamed the old mailman folder and restarted both mailman and apache.
>I retried emailing the list using my test-join alias and now got the 
>following error:
>
>From: Mail Delivery Subsystem <[EMAIL PROTECTED]>
>To: [EMAIL PROTECTED]
>Sent: Tuesday, May 6, 2008 10:45:53 AM
>Subject: Returned mail: see transcript for details
>
>The original message was received at Tue, 6 May 2008 10:45:53 -0400 
>from my.hostname.domain.com [111.111.111.111]
>
>  ----- The following addresses had permanent fatal errors ----- 
>"|/usr/local/mailman/mail/mailman join test"
>    (reason: Service unavailable)
>    (expanded from: <[EMAIL PROTECTED]>)
>
>  ----- Transcript of session follows -----
>smrsh: "mailman" not available for sendmail programs (stat failed)
>554 5.0.0 Service unavailable
>Reporting-MTA: dns; my.domain.com
>Received-From-MTA: DNS; my.hostname.domain.com
>Arrival-Date: Tue, 6 May 2008 10:45:53 -0400


Now we're getting somewhere. You have smrsh enabled in sendmail and it
is not allowed to execute the /usr/local/mailman/mail/mailman wrapper.
It probably was allowed to execute the old one which is why you didn't
see this before. I.e. you probably have a symlink from mailman to
/var/lib/mailman/mail/mailman is the smrsh directory which needs to be
changed (or added if not there) to go to
/usr/local/mailman/mail/mailman.

See <http://www.list.org/mailman-install/node32.html> and/or sec 3 of
<http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq04.078.htp>.


-- 
Mark Sapiro <[EMAIL PROTECTED]>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan

------------------------------------------------------
Mailman-Users mailing list
Mailman-Users@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/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: 
http://www.python.org/cgi-bin/faqw-mm.py?req=show&amp;file=faq01.027.htp

Reply via email to