I tried sending e-mail to the new list I created this AM...
I emailed <listname>@domain.com...
I got the following error returned: sh: mailman not available for sendmail programs 554 "|/home/mailman/mail/mailman post listname"... Service unavailable
Also, I can't access the archives... I have 2 issues there.
I'm running on a virtual host and when I click on go to list archives, it goes to http://<masterhost>/pipermail/listname/ but then complains that the user has no permission (a cobalt error dialog box).
/pipermail exists in the conf files, and points to /home/mailman/archives/public listname exists in that folder and is a pointer to /home/mailman/archives/private/listname . and finally, listname exists in the /home/mailman/archives/private folder and has an index.html in it.
Why does it go back to the master domain name rather than the virtual host?
Will Nordmeyer wrote:
I tried sending e-mail to the new list I created this AM...
I emailed <listname>@domain.com...
I got the following error returned: sh: mailman not available for sendmail programs 554 "|/home/mailman/mail/mailman post listname"... Service unavailable
Also, I can't access the archives... I have 2 issues there.
I'm running on a virtual host and when I click on go to list archives, it goes to http://<masterhost>/pipermail/listname/ but then complains that the user has no permission (a cobalt error dialog box).
/pipermail exists in the conf files, and points to /home/mailman/archives/public listname exists in that folder and is a pointer to /home/mailman/archives/private/listname . and finally, listname exists in the /home/mailman/archives/private folder and has an index.html in it.
Why does it go back to the master domain name rather than the virtual host?
That's configured in /home/mailman/Mailman/Defaults.py. There are three variables to look for near the top: DEFAULT_EMAIL_HOST; DEFAULT_URL_HOST; and DEFAULT_URL_PATTERN.
Upon further review...
My apache server is complaining, when I go to www.sitename.com/pipermail/listname, with the following error:
Symbolic link not allowed: /home/mailman/archives/public/listname/
I tried replacing it with a hard link and the cobalt didn't really like it.
Is there a way to allow symbolic linking? I thought I'd had a symbolic link in other areas?
I'm still the same send issue too.
----- Original Message ----- From: "Will Nordmeyer" <will@willspc.net> To: <mailman-users@python.org> Sent: Wednesday, January 29, 2003 10:03 AM Subject: [Mailman-Users] mailman errors...
I tried sending e-mail to the new list I created this AM...
I emailed <listname>@domain.com...
I got the following error returned: sh: mailman not available for sendmail programs 554 "|/home/mailman/mail/mailman post listname"... Service unavailable
Also, I can't access the archives... I have 2 issues there.
I'm running on a virtual host and when I click on go to list archives, it goes to http://<masterhost>/pipermail/listname/ but then complains that the user has no permission (a cobalt error dialog box).
/pipermail exists in the conf files, and points to /home/mailman/archives/public listname exists in that folder and is a pointer to /home/mailman/archives/private/listname . and finally, listname exists in the /home/mailman/archives/private folder and has an index.html in it.
Why does it go back to the master domain name rather than the virtual host?
Will Nordmeyer wrote:
Upon further review...
My apache server is complaining, when I go to www.sitename.com/pipermail/listname, with the following error:
Symbolic link not allowed: /home/mailman/archives/public/listname/
Is www.sitename.com the server's hostname, or the ServerName of the VirtualHost mailman is served from? Make sure you have
<Directory /home/mailman/archives> Options +FollowSymlinks </Directory>
in your Apache config for the VirtualHost mailman is served from. I'm not sure what to do about inconsistent URLs as I am having the same problem myself. I don't know what to do about the error response when sending to a list either.
I tried replacing it with a hard link and the cobalt didn't really like it.
Is there a way to allow symbolic linking? I thought I'd had a symbolic link in other areas?
I'm still the same send issue too.
----- Original Message ----- From: "Will Nordmeyer" <will@willspc.net> To: <mailman-users@python.org> Sent: Wednesday, January 29, 2003 10:03 AM Subject: [Mailman-Users] mailman errors...
I tried sending e-mail to the new list I created this AM...
I emailed <listname>@domain.com...
I got the following error returned: sh: mailman not available for sendmail programs 554 "|/home/mailman/mail/mailman post listname"... Service unavailable
Also, I can't access the archives... I have 2 issues there.
I'm running on a virtual host and when I click on go to list archives, it goes to http://<masterhost>/pipermail/listname/ but then complains that the user has no permission (a cobalt error dialog box).
/pipermail exists in the conf files, and points to /home/mailman/archives/public listname exists in that folder and is a pointer to /home/mailman/archives/private/listname . and finally, listname exists in the /home/mailman/archives/private folder and has an index.html in it.
Why does it go back to the master domain name rather than the virtual host?
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/
This message was sent to: jgeorgeson@unboundtech.com Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/jgeorgeson%40unboundtec...
-- Justin Georgeson UnBound Technologies, Inc. http://www.unboundtech.com Main 713.329.9330 Fax 713.460.4051 Mobile 512.789.1962
5295 Hollister Road Houston, TX 77040 Real Applications using Real Wireless Intelligence(tm)
Tell apache to allow symlinks for that directory
Does your Sendmail use "smrsh" to protect it? If so you will need to follow the steps in FAQ 3.14 to setup smrsh to allow Mailman.
The sendmail problem could also be the GID of the Sendmail you are using verses the mail-GID that you configured Mailman to expect. This should also be covered in the FAQ.
Good Luck! - Jon Carnes
On Wed, 2003-01-29 at 14:43, Will Nordmeyer wrote:
Upon further review...
My apache server is complaining, when I go to www.sitename.com/pipermail/listname, with the following error:
Symbolic link not allowed: /home/mailman/archives/public/listname/
I tried replacing it with a hard link and the cobalt didn't really like it.
Is there a way to allow symbolic linking? I thought I'd had a symbolic link in other areas?
I'm still the same send issue too.
----- Original Message ----- From: "Will Nordmeyer" <will@willspc.net> To: <mailman-users@python.org> Sent: Wednesday, January 29, 2003 10:03 AM Subject: [Mailman-Users] mailman errors...
I tried sending e-mail to the new list I created this AM...
I emailed <listname>@domain.com...
I got the following error returned: sh: mailman not available for sendmail programs 554 "|/home/mailman/mail/mailman post listname"... Service unavailable
Also, I can't access the archives... I have 2 issues there.
I'm running on a virtual host and when I click on go to list archives, it goes to http://<masterhost>/pipermail/listname/ but then complains that the user has no permission (a cobalt error dialog box).
/pipermail exists in the conf files, and points to /home/mailman/archives/public listname exists in that folder and is a pointer to /home/mailman/archives/private/listname . and finally, listname exists in the /home/mailman/archives/private folder and has an index.html in it.
Why does it go back to the master domain name rather than the virtual host?
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/
This message was sent to: jonc@nc.rr.com Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/jonc%40nc.rr.com
participants (3)
-
Jon Carnes
-
Justin Georgeson
-
Will Nordmeyer