How to integrate Sympa (mail list mgr) with Apache on Ubuntu 12.04 or later?
Installed Sympa on my Ubuntu 12.10 system ('apt-get install -y sympa'), rev 6.1.11. Can't get past web-server integration: http://www.sympa.org/manual/web-interface#web_server_setup. Have tried sudo + Apache2 integration methods. http:///wws and http:///static-sympa still experiences permissions problems.
Seeking an Ubuntu-specific procedure tailored to the 'sympa' package. Have yet to find anything. Suspect I'm not executing procedure properly and/or missing some "small" setp.
Alternatively: seeking means to simply "sanity check" the installation by granting apache2 (www-data) process "all/unsecure" rights to access anything, simply to ensure I've got everything installed properly. Then I can dial back to proper/secure permissions.
Thoughts?
12.04 installation 12.10 mailing-list
add a comment |
Installed Sympa on my Ubuntu 12.10 system ('apt-get install -y sympa'), rev 6.1.11. Can't get past web-server integration: http://www.sympa.org/manual/web-interface#web_server_setup. Have tried sudo + Apache2 integration methods. http:///wws and http:///static-sympa still experiences permissions problems.
Seeking an Ubuntu-specific procedure tailored to the 'sympa' package. Have yet to find anything. Suspect I'm not executing procedure properly and/or missing some "small" setp.
Alternatively: seeking means to simply "sanity check" the installation by granting apache2 (www-data) process "all/unsecure" rights to access anything, simply to ensure I've got everything installed properly. Then I can dial back to proper/secure permissions.
Thoughts?
12.04 installation 12.10 mailing-list
add a comment |
Installed Sympa on my Ubuntu 12.10 system ('apt-get install -y sympa'), rev 6.1.11. Can't get past web-server integration: http://www.sympa.org/manual/web-interface#web_server_setup. Have tried sudo + Apache2 integration methods. http:///wws and http:///static-sympa still experiences permissions problems.
Seeking an Ubuntu-specific procedure tailored to the 'sympa' package. Have yet to find anything. Suspect I'm not executing procedure properly and/or missing some "small" setp.
Alternatively: seeking means to simply "sanity check" the installation by granting apache2 (www-data) process "all/unsecure" rights to access anything, simply to ensure I've got everything installed properly. Then I can dial back to proper/secure permissions.
Thoughts?
12.04 installation 12.10 mailing-list
Installed Sympa on my Ubuntu 12.10 system ('apt-get install -y sympa'), rev 6.1.11. Can't get past web-server integration: http://www.sympa.org/manual/web-interface#web_server_setup. Have tried sudo + Apache2 integration methods. http:///wws and http:///static-sympa still experiences permissions problems.
Seeking an Ubuntu-specific procedure tailored to the 'sympa' package. Have yet to find anything. Suspect I'm not executing procedure properly and/or missing some "small" setp.
Alternatively: seeking means to simply "sanity check" the installation by granting apache2 (www-data) process "all/unsecure" rights to access anything, simply to ensure I've got everything installed properly. Then I can dial back to proper/secure permissions.
Thoughts?
12.04 installation 12.10 mailing-list
12.04 installation 12.10 mailing-list
asked Nov 13 '12 at 3:13
Johnny UtahhJohnny Utahh
17318
17318
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Addendum: Further in my installation trials I realize that this answer has been incomplete, so I'll edit it. The solution below solves the permission problems with the files in /static-sympa
. But you'll probably run in further problems down the line, because the config snippet in /etc/apache2/conf.d/sympa
is really incomplete. You can replace the whole contents of this file by the version shown at Debian Wiki. There you also find instructions how to create the necessary wrapper at /var/www/sympa/wwsympa.fcgi
. With this, Sympa itself and the web interface WWSympa should be working.
I realize this question is a bit older, but I just run into a similar problem. Maybe the solution I found can help others.
The Sympa package in Ubuntu seems to be a bit bungled, to say the least. One of the problems is that it tells Apache where to find its stuff, but doesn't give it permission to go there ;)
/static-sympa
is an Alias that is defined in /etc/apache2/conf.d/sympa
, along with the ScriptAlias for /wws
. The actual location for the files that are aliase'd to static-sympa
is /var/lib/sympa/static_content
. That, of course, is miles away from any DocumentRoot Apache knows about. And Apache is wary about integrating stuff from "outside", unless you explicitely tell it it's ok. So the default is, "you no touching anything there", i. e. "403 - Forbidden".
To give Apache the needed permission, you can just extend the configuration snippet, /etc/apache2/conf.d/sympa
. Below the existing Alias and ScriptAlias definition, you can do something along the lines of
# For anything below the (URL) location /static-sympa
<Location /static-sympa>
Order allow,deny # order of permissions: First handle 'allows', then 'denys'
Allow from All # allow access to anybody
</Location>
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f216506%2fhow-to-integrate-sympa-mail-list-mgr-with-apache-on-ubuntu-12-04-or-later%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Addendum: Further in my installation trials I realize that this answer has been incomplete, so I'll edit it. The solution below solves the permission problems with the files in /static-sympa
. But you'll probably run in further problems down the line, because the config snippet in /etc/apache2/conf.d/sympa
is really incomplete. You can replace the whole contents of this file by the version shown at Debian Wiki. There you also find instructions how to create the necessary wrapper at /var/www/sympa/wwsympa.fcgi
. With this, Sympa itself and the web interface WWSympa should be working.
I realize this question is a bit older, but I just run into a similar problem. Maybe the solution I found can help others.
The Sympa package in Ubuntu seems to be a bit bungled, to say the least. One of the problems is that it tells Apache where to find its stuff, but doesn't give it permission to go there ;)
/static-sympa
is an Alias that is defined in /etc/apache2/conf.d/sympa
, along with the ScriptAlias for /wws
. The actual location for the files that are aliase'd to static-sympa
is /var/lib/sympa/static_content
. That, of course, is miles away from any DocumentRoot Apache knows about. And Apache is wary about integrating stuff from "outside", unless you explicitely tell it it's ok. So the default is, "you no touching anything there", i. e. "403 - Forbidden".
To give Apache the needed permission, you can just extend the configuration snippet, /etc/apache2/conf.d/sympa
. Below the existing Alias and ScriptAlias definition, you can do something along the lines of
# For anything below the (URL) location /static-sympa
<Location /static-sympa>
Order allow,deny # order of permissions: First handle 'allows', then 'denys'
Allow from All # allow access to anybody
</Location>
add a comment |
Addendum: Further in my installation trials I realize that this answer has been incomplete, so I'll edit it. The solution below solves the permission problems with the files in /static-sympa
. But you'll probably run in further problems down the line, because the config snippet in /etc/apache2/conf.d/sympa
is really incomplete. You can replace the whole contents of this file by the version shown at Debian Wiki. There you also find instructions how to create the necessary wrapper at /var/www/sympa/wwsympa.fcgi
. With this, Sympa itself and the web interface WWSympa should be working.
I realize this question is a bit older, but I just run into a similar problem. Maybe the solution I found can help others.
The Sympa package in Ubuntu seems to be a bit bungled, to say the least. One of the problems is that it tells Apache where to find its stuff, but doesn't give it permission to go there ;)
/static-sympa
is an Alias that is defined in /etc/apache2/conf.d/sympa
, along with the ScriptAlias for /wws
. The actual location for the files that are aliase'd to static-sympa
is /var/lib/sympa/static_content
. That, of course, is miles away from any DocumentRoot Apache knows about. And Apache is wary about integrating stuff from "outside", unless you explicitely tell it it's ok. So the default is, "you no touching anything there", i. e. "403 - Forbidden".
To give Apache the needed permission, you can just extend the configuration snippet, /etc/apache2/conf.d/sympa
. Below the existing Alias and ScriptAlias definition, you can do something along the lines of
# For anything below the (URL) location /static-sympa
<Location /static-sympa>
Order allow,deny # order of permissions: First handle 'allows', then 'denys'
Allow from All # allow access to anybody
</Location>
add a comment |
Addendum: Further in my installation trials I realize that this answer has been incomplete, so I'll edit it. The solution below solves the permission problems with the files in /static-sympa
. But you'll probably run in further problems down the line, because the config snippet in /etc/apache2/conf.d/sympa
is really incomplete. You can replace the whole contents of this file by the version shown at Debian Wiki. There you also find instructions how to create the necessary wrapper at /var/www/sympa/wwsympa.fcgi
. With this, Sympa itself and the web interface WWSympa should be working.
I realize this question is a bit older, but I just run into a similar problem. Maybe the solution I found can help others.
The Sympa package in Ubuntu seems to be a bit bungled, to say the least. One of the problems is that it tells Apache where to find its stuff, but doesn't give it permission to go there ;)
/static-sympa
is an Alias that is defined in /etc/apache2/conf.d/sympa
, along with the ScriptAlias for /wws
. The actual location for the files that are aliase'd to static-sympa
is /var/lib/sympa/static_content
. That, of course, is miles away from any DocumentRoot Apache knows about. And Apache is wary about integrating stuff from "outside", unless you explicitely tell it it's ok. So the default is, "you no touching anything there", i. e. "403 - Forbidden".
To give Apache the needed permission, you can just extend the configuration snippet, /etc/apache2/conf.d/sympa
. Below the existing Alias and ScriptAlias definition, you can do something along the lines of
# For anything below the (URL) location /static-sympa
<Location /static-sympa>
Order allow,deny # order of permissions: First handle 'allows', then 'denys'
Allow from All # allow access to anybody
</Location>
Addendum: Further in my installation trials I realize that this answer has been incomplete, so I'll edit it. The solution below solves the permission problems with the files in /static-sympa
. But you'll probably run in further problems down the line, because the config snippet in /etc/apache2/conf.d/sympa
is really incomplete. You can replace the whole contents of this file by the version shown at Debian Wiki. There you also find instructions how to create the necessary wrapper at /var/www/sympa/wwsympa.fcgi
. With this, Sympa itself and the web interface WWSympa should be working.
I realize this question is a bit older, but I just run into a similar problem. Maybe the solution I found can help others.
The Sympa package in Ubuntu seems to be a bit bungled, to say the least. One of the problems is that it tells Apache where to find its stuff, but doesn't give it permission to go there ;)
/static-sympa
is an Alias that is defined in /etc/apache2/conf.d/sympa
, along with the ScriptAlias for /wws
. The actual location for the files that are aliase'd to static-sympa
is /var/lib/sympa/static_content
. That, of course, is miles away from any DocumentRoot Apache knows about. And Apache is wary about integrating stuff from "outside", unless you explicitely tell it it's ok. So the default is, "you no touching anything there", i. e. "403 - Forbidden".
To give Apache the needed permission, you can just extend the configuration snippet, /etc/apache2/conf.d/sympa
. Below the existing Alias and ScriptAlias definition, you can do something along the lines of
# For anything below the (URL) location /static-sympa
<Location /static-sympa>
Order allow,deny # order of permissions: First handle 'allows', then 'denys'
Allow from All # allow access to anybody
</Location>
edited Mar 2 at 11:44
Community♦
1
1
answered Jul 19 '13 at 19:14
Henning KockerbeckHenning Kockerbeck
3,9051725
3,9051725
add a comment |
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f216506%2fhow-to-integrate-sympa-mail-list-mgr-with-apache-on-ubuntu-12-04-or-later%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown