[Mailman-Users] Apache/mailman2 on RHEL8.2

Steven Jones writes: > Trying to do a setup, Did you get the issue with missing mailman-*.timer files sorted, or are you problem-solving in parallel? > I get the default page OK but when I follow the link, > > "List administrators, you can visit the list admin overview page to > find the m

[Mailman-Users] Apache/mailman2 on RHEL8.2

Trying to do a setup, I get the default page OK but when I follow the link, "List administrators, you can visit the list admin overview page to find the management interface for your list." I get, Not Found The requested URL /mailman/admin was not found on this server. regards Steven

Re: [Mailman-Users] Apache subscription Referer rules

Jim Popovitch via Mailman-Users writes: > Mod_Rewrite is "too heavy" for something this simple. It's only too heavy if it actually has an unacceptable impact on system load. That said, I like the SetEnvIf* approach better. > SetEnvIfNoCase Referer "https://.*/mailman/listinfo/"; ListInfoRefer

Re: [Mailman-Users] Apache subscription Referer rules

On Tue, 2020-01-14 at 00:19 -0500, Bill Cole wrote: > On 10 Jan 2020, at 10:52, Jim Popovitch via Mailman-Users wrote: > > > (I think I asked this a few months back, but I couldn't locate any > > emails on it) > > > > What is the Apache rule syntax for rejecting subscription linking that > > does

Re: [Mailman-Users] Apache subscription Referer rules

On 10 Jan 2020, at 10:52, Jim Popovitch via Mailman-Users wrote: (I think I asked this a few months back, but I couldn't locate any emails on it) What is the Apache rule syntax for rejecting subscription linking that doesn't come from the same domain/site? First step: Header always set Re

[Mailman-Users] Apache subscription Referer rules

Jim Popovitch via Mailman-Users writes: > (I think I asked this a few months back, but I couldn't locate any > emails on it) > > What is the Apache rule syntax for rejecting subscription linking that > doesn't come from the same domain/site? Don't know what you need exactly, but mod_rewrite

[Mailman-Users] Apache subscription Referer rules

(I think I asked this a few months back, but I couldn't locate any emails on it) What is the Apache rule syntax for rejecting subscription linking that doesn't come from the same domain/site? tia, -Jim P. -- Mailman-Users mailing list Mailman-

Re: [Mailman-Users] Apache ScriptAlias and POST

Mark, Thanks very much for your pointer, the addition of a DEFAULT_URL_PATTERN as per the article you linked to solved my problem immediately. Regards, Geoff On Mon, 9 Dec 2019 at 21:25, Geoff Campbell wrote: > > Mark, > > > It is due to redirection losing POST data, but the culprit is

Re: [Mailman-Users] Apache ScriptAlias and POST

Mark, > It is due to redirection losing POST data, but the culprit is not > ScriptAlias. It is whatever you have in your Apache config that > redirects http to https. Ah, interesting. > I don't know why you couldn't find the answer in the archives. Well, I think the answer there is that there a

Re: [Mailman-Users] Apache ScriptAlias and POST

On 12/9/19 3:42 AM, Geoff Campbell wrote: > > Reading through this list, I see that this is apparently due to the > ScriptAlias redirection just silently dumping the data content of HTTP > POST requests. Which seems a bit odd to me, but what do I know? It is due to redirection losing POST data,

[Mailman-Users] Apache ScriptAlias and POST

All, I'm trying to get mailman up and running, using Apache as the web server, and I appear to have run into a fundamental and insoluble problem. Now, please be gentle with me, it's a good 15 years since I last used Linux servers in anger, and I am very far from being an expert with Apache config

[Mailman-Users] Apache 2.4 and Mailman

Lindsay Haisley writes: > Recent Ubuntu server installs of Apache 2.4 need "Require all granted" > in place of, or in addition to "Allow from all" to grant access The old "allow from ..." syntax has been deprecated in favor of the "require ... granted" syntax for quite a while. Recent Apache h

Re: [Mailman-Users] Apache 2.4 and Mailman

On 12/05/2014 11:07 AM, Mark Sapiro wrote: > > I'll consider adding something more generic about allowing access. I have updated the pages at , and

Re: [Mailman-Users] Apache 2.4 and Mailman

On 12/04/2014 10:40 PM, Lindsay Haisley wrote: > This is a relatively minor thing, but perhaps it should be mentioned in > the Install docs on > http://www.gnu.org/software/mailman/mailman-install/node10.html > > Recent Ubuntu server installs of Apache 2.4 need "Require all granted" > in place of,

[Mailman-Users] Apache 2.4 and Mailman

This is a relatively minor thing, but perhaps it should be mentioned in the Install docs on http://www.gnu.org/software/mailman/mailman-install/node10.html Recent Ubuntu server installs of Apache 2.4 need "Require all granted" in place of, or in addition to "Allow from all" to grant access to a po

Re: [Mailman-Users] Apache/Browser/Cookie-Problem?

Tobias Koopmann wrote: > >Now my Problem is the following: >After a user subscribes to a mailinglist and opens the confirmation link and >clicks the confirmation button hes got redirected to an "Enter confirmation >cookie"-Page. But after entering the confirmation cookie nothing happens, >the same

[Mailman-Users] Apache/Browser/Cookie-Problem?

Hello there, i'm relativ new to Mailman. Now I've got following Software working Apache + Mailman 2.1.13 + Postfix on Ubuntu 10.04 LTS Apache-configuration: # Sample configuration for Debian mailman with Apache # We can find mailman here: #ScriptAlias /cgi-bin/mailman/ /usr/lib/cgi-bin/mailman/

Re: [Mailman-Users] Apache startup warning/error: mailman DocumentRoot?

Tanstaafl wrote: > >Now, the path is correct, but there is no mailman directory in the >htdocs folder, so the warning is correct - and, to make matters worse, I >*do* have this path explicitly set in the >/etc/apache2/vhosts.d/lists.example.com config file, although I'm not >sure why now. And thi

Re: [Mailman-Users] Apache startup warning/error: mailman DocumentRoot?

-Original Message- > Anyway, here's the warning/error: > Warning: DocumentRoot [/var/www/localhost/htdocs/mailman] does not exist ^ > apache2: Could not reliably determine the servers fully qualified domain > name, using ###.###.###.### for Serve

[Mailman-Users] Apache startup warning/error: mailman DocumentRoot?

Hello again, There's another annoying warning message I get that I'd like to resolve, but I only get it at startup, so I keep forgetting about it. I had to shutdown the server this morning to move it to a new UPS, and saw it again when I started the server up, so now I'm asking. I know there's som

Re: [Mailman-Users] Apache > Mailman VHost Config - WAS: Re: Changinghost names, revisited... POSTFIX_STYLE_VIRTUAL_DOMAINS?

On 2010-05-04 1:44 PM, Mark Sapiro wrote: > Isn't there something like > > ScriptAlias /mailman/ "/path/to/mailman/cgi-bin/" > > and > > Alias /pipermail/ "/path/to/mailman/archives/public/" > > in something like /etc/apache2/conf.d/50_mailman.conf? > > That should be all you need. Ah, right,

Re: [Mailman-Users] Apache > Mailman VHost Config - WAS: Re: Changinghost names, revisited... POSTFIX_STYLE_VIRTUAL_DOMAINS?

Tanstaafl wrote: > >On 2010-05-03 6:24 PM, Mark Sapiro wrote: >> On 5/3/2010 2:05 PM, Tanstaafl wrote: >>> >>> I looked at /etc/apache2/modules.d/50_mailman.conf, but it doesn't show >>> anything about my hostname, so, what controls the root directory? > >> There is a ScriptAlias for mailman. If i

[Mailman-Users] Apache > Mailman VHost Config - WAS: Re: Changing host names, revisited... POSTFIX_STYLE_VIRTUAL_DOMAINS?

Splitting this off since it's a separate issue... On 2010-05-03 6:24 PM, Mark Sapiro wrote: > On 5/3/2010 2:05 PM, Tanstaafl wrote: >> On 2010-05-03 12:32 PM, Mark Sapiro wrote: >>> What about web server changes for the lists.example.com vs. >>> myhost.example.com change (there may not be any), an

Re: [Mailman-Users] Apache Configuration for Mailman

Carlos Williams wrote: >I am trying to install / configure MailMan on my mail server which is >running Postfix 2.6 & Apache 2 on CentOS 5 x64. I am following the >guide on the MailMan page labeled "5 Set up your web server". I am >confused here because it advises me to do the following: > > Scri

Re: [Mailman-Users] Apache Configuration for Mailman

On Thu, Oct 08, 2009 at 08:57:17AM -0400, Carlos Williams wrote: > it advises me to do the following: > > ScriptAlias /mailman/ /usr/lib/mailman/cgi-bin/ > > When I add that line into my /etc/httpd/conf/httpd.conf file, I get > this error when I restart Apache: > > [r...@mail conf]# serv

[Mailman-Users] Apache Configuration for Mailman

I am trying to install / configure MailMan on my mail server which is running Postfix 2.6 & Apache 2 on CentOS 5 x64. I am following the guide on the MailMan page labeled "5 Set up your web server". I am confused here because it advises me to do the following: ScriptAlias /mailman/ /usr/li

[Mailman-Users] Apache Configuration for Mailman

I am trying to install / configure MailMan on my mail server which is running Postfix 2.6 & Apache 2 on CentOS 5 x64. I am following the guide on the MailMan page labeled "5 Set up your web server". I am confused here because it advises me to do the following: ScriptAlias /mailman/ /usr/l

Re: [Mailman-Users] Apache does not have permission to accesspipermail/listname

This is a Fedora RPM so I will try the Fedora forums. Thanks Mark. Lars Olson wrote: > >Looks like you nailed it with your comment about SELinux. I just ran >setenforce 0 and tried again and was able to view the archive. Now the >question is how do I fix the SELinux problem? Sorry, that's

Re: [Mailman-Users] Apache does not have permission to access pipermail/listname

Lars Olson wrote: > >Looks like you nailed it with your comment about SELinux. I just ran >setenforce 0 and tried again and was able to view the archive. Now the >question is how do I fix the SELinux problem? Sorry, that's a SELinux question, not a Mailman question. I know essentially zero abou

Re: [Mailman-Users] Apache does not have permission toaccesspipermail/listname

Sorry about the dup post - I never did receive the original post or replies so I assumed it was lost... My error_log below [Tue Apr 14 23:22:14 2009] [error] [client 66.249.73.209] (13)Permission denied: access to /pipermail/whpnews/2006-February/author.html denied Looks like you nailed it with

Re: [Mailman-Users] Apache does not have permission to accesspipermail/listname

Lars Olson wrote: >I am receiving an apache forbidden page when I try to access my archives >after moving my lists to a new server. My old server was 2.1.8 - new server >is running 2.1.9 and using the same domain name. You posted the same issue to this list 4 days ago. My reply is at

[Mailman-Users] Apache does not have permission to access pipermail/listname

I am receiving an apache forbidden page when I try to access my archives after moving my lists to a new server. My old server was 2.1.8 - new server is running 2.1.9 and using the same domain name. Everything is working correctly except the archives... /etc/httpd/conf.d/mailman.conf has appropr

Re: [Mailman-Users] Apache does not have permission to accesspipermail/listname

Lars Olson wrote: >I am receiving an apache forbidden page when I try to access my archives >after moving my lists to a new server. My old server was 2.1.8 – new server >is running 2.1.9 and using the same domain name. > >Everything is working correctly except the archives... > >/etc/httpd/conf.

[Mailman-Users] Apache does not have permission to access pipermail/listname

I am receiving an apache forbidden page when I try to access my archives after moving my lists to a new server. My old server was 2.1.8 – new server is running 2.1.9 and using the same domain name. Everything is working correctly except the archives... /etc/httpd/conf.d/mailman.conf has appropr

[Mailman-Users] Apache + Suexec

All, Is it possible to install mailman (FreeBSD, from ports, with Apache + Suexec, Exim), onto a per domain basis? If so, does anyone have a ducumented procedure? -Grant -- Mailman-Users mailing list Mailman-Users@python.org http://mail.p

Re: [Mailman-Users] Apache Resource Issue

Robert Campbell wrote: > >The apache error log shows the following when I try to go to admin, >listinfo, and couple of the other cgi . > >(11)Resource temporarily unavailable: couldn't create child process: 11: >listinfo > (11)Resource temporarily unavailable: couldn't spawn child process: >/listin

[Mailman-Users] Apache Resource Issue

Ok, I had mailman working not less than 10 min ago, and now I get a 500 error. The apache error log shows the following when I try to go to admin, listinfo, and couple of the other cgi . (11)Resource temporarily unavailable: couldn't create child process: 11: listinfo (11)Resource temporarily un

Re: [Mailman-Users] Apache and pipermail 403 issues

Thank you Mark that worked perfectly. On Wed, Jul 2, 2008 at 7:51 PM, Mark Sapiro <[EMAIL PROTECTED]> wrote: > Robert Campbell wrote: > > >Currently when ever I try to get to the mailman archives for any of the > >mailing lists I revcive a 403 error. > >When I check the apache error log i see the

Re: [Mailman-Users] Apache and pipermail 403 issues

Robert Campbell wrote: >Currently when ever I try to get to the mailman archives for any of the >mailing lists I revcive a 403 error. >When I check the apache error log i see the following line: > >[Wed Jul 02 10:28:52 2008] [error] [client ] client denied by >server configuration: /archives/publi

Re: [Mailman-Users] Apache and pipermail 403 issues

Currently when ever I try to get to the mailman archives for any of the mailing lists I revcive a 403 error. When I check the apache error log i see the following line: [Wed Jul 02 10:28:52 2008] [error] [client ] client denied by server configuration: /archives/public/ The Private folder is owne

Re: [Mailman-Users] Apache,

>I do it all the time. I am using Kmail, and can configure it to reply to the >list by default. But then I get caught when something I don't want to go to >the list, goes there. It is a no-win situation. >Doug. Don't know what I am going to use to read e-mail on the Solaris 10 box. Whatever

Re: [Mailman-Users] Apache,

On Monday 30 June 2008 2:55:08 pm Brad Knowles wrote: > On 6/29/08, Vidiot wrote: > > Crap, I think I sent the last response just to you and not you and the > > list. I tend to forget to group reply. I personally prefer mail lists to > > respond to the list e-mail address and not the poster. > >

Re: [Mailman-Users] Apache,

On 6/29/08, Vidiot wrote: Crap, I think I sent the last response just to you and not you and the list. I tend to forget to group reply. I personally prefer mail lists to respond to the list e-mail address and not the poster. We really don't want to get into this argument again. -- Brad Kn

Re: [Mailman-Users] Apache,

Mark Sapiro: Crap, I think I sent the last response just to you and not you and the list. I tend to forget to group reply. I personally prefer mail lists to respond to the list e-mail address and not the poster. >It's been on my list for a long time. Obviously, I still haven't gotten >to it. My

Re: [Mailman-Users] Apache,

Vidiot wrote: > >It would be nice though if the two documents matched in their macro-naming, >to help reduce confusion and possibly misconfiguration. It's been on my list for a long time. Obviously, I still haven't gotten to it. -- Mark Sapiro <[EMAIL PROTECTED]>The highway is for gambl

Re: [Mailman-Users] Apache,

Confusion no longer reigns. Silly me, not thinking about the variables being expanded later on in the exim config file. It would be nice though if the two documents matched in their macro-naming, to help reduce confusion and possibly misconfiguration. MB -- e-mail: [EMAIL PROTECTED]

Re: [Mailman-Users] Apache,

Mark Sapiro responded: >I suggest you see which tends >to be more complete than the Exim section of the installation manual. OK, confusion reigns. The installation manual says MAILMAN_HOME, etc, while the web page says MM_HOME, etc. Which one is correc

Re: [Mailman-Users] Apache,

Vidiot wrote: > >Before you go too far, look at the exim STMP callback code example. >There are two {yes}{no}} lines in each section (warn and accept). exim >doesn't like that when doing the exim -bt test. Thanks. I've fixed that and also a couple of omissions in the router. I suggest you see

Re: [Mailman-Users] Apache,

Mark Sapiro responded: >No. 2.1.11rc2 is the latest released, but I'm in the process of >packaging the final 2.1.11 for release tomorrow. > >When I said I just fixed it for 2.1.11, I meant the final. I kinda wondered about that. Before you go too far, look at the exim STMP callback code example.

Re: [Mailman-Users] Apache,

Vidiot wrote: > >I'm confused. I installed mailman-2.1.11rc2.tgz. Mailman 2.1.11 isn't >available yet? No. 2.1.11rc2 is the latest released, but I'm in the process of packaging the final 2.1.11 for release tomorrow. When I said I just fixed it for 2.1.11, I meant the final. -- Mark Sapiro <[E

Re: [Mailman-Users] Apache,

Mark Sapiro responded: >I think that's my fault. I just fixed it for Mailman 2.1.11. (I broke >it for 2.1.11rc1.) Whew! It wasn't something I did this time. :-) I'm confused. I installed mailman-2.1.11rc2.tgz. Mailman 2.1.11 isn't available yet? >The problem is the bin/update in the tarball

Re: [Mailman-Users] Apache,

Mark Sapiro responded: >Probably not in the 2.1 branch. 3.0 will require Python 2.5 minimum and >won't try to install these codecs at all. > >I'll try to do something with configure for Mailman 2.2. Thanks, it will be appreciated. MB -- e-mail: [EMAIL PROTECTED]/

Re: [Mailman-Users] Apache,

Vidiot wrote: > >OK, did that. Gets past that now. But: > >[...] >Compiling /usr/local/mailman/Mailman/versions.py ... >sh: bin/update: not found >*** Error code 1 >The following command caused the error: >(cd /usr/local/mailman ; test -n "" || bin/update) >make: Fatal error: Command failed for t

Re: [Mailman-Users] Apache,

Vidiot wrote: > >That is what I thought I read, which is why I changed to 2.5.2, thinking >that mailman would install accordingly. Bad thinking on my part. > >Any chance this will be incorporated into future mailman configure detection >runs so that this will work cleanly? Probably not in the 2.

Re: [Mailman-Users] Apache,

Mark responded: >PACKAGES= $(EMAILPKG) OK, did that. Gets past that now. But: [...] Compiling /usr/local/mailman/Mailman/versions.py ... sh: bin/update: not found *** Error code 1 The following command caused the error: (cd /usr/local/mailman ; test -n "" || bin/update) make: Fatal error: Comm

Re: [Mailman-Users] Apache,

Mark responded: >This is not new. I tried to warn you. >. Yep, you did :-) >If you are going to be running Mailman with Python 2.5+, you don't need >the Japanese and Korean codecs anyway because they're built i

Re: [Mailman-Users] Apache,

Vidiot wrote: >Mark responded: > >>The Korean and Japanese codecs are installed by Python distutils using >>a setup.py built somewhere else. It doesn't get everything from >>configure. > >Crap, all of the modifications that I tried doing were worthless, since >the damn thing keeps installing the t

Re: [Mailman-Users] Apache,

Mark responded: >The Korean and Japanese codecs are installed by Python distutils using >a setup.py built somewhere else. It doesn't get everything from >configure. Crap, all of the modifications that I tried doing were worthless, since the damn thing keeps installing the tarball, no matter what,

Re: [Mailman-Users] Apache,

Mark responded: >I understand that. It is more subtle than that. It has to do with the >Python version that runs the Setup.py for the Korean codecs. It is getting me really pissed off. As far as I can tell, it is running the 2.5.2 version of Python. I tried --includedir with configure. Didn't

Re: [Mailman-Users] Apache,

Vidiot wrote: > >The finding of header files and the PATH environment are mutually exclusive. >Compilers do not use PATH for finding header files. I understand that. It is more subtle than that. It has to do with the Python version that runs the Setup.py for the Korean codecs. -- Mark Sapiro <

Re: [Mailman-Users] Apache,

Mark posted: >Your problem is the hangul.c file that is not compiling contains > >#include "Python.h" > >I confess, I don't fully understand the details, but Hank appears to >and he says the issue is with the order of things on your PATH. The finding of header files and the PATH environment are m

Re: [Mailman-Users] Apache,

Vidiot wrote: >I'm not sure that everyone looked at the posting that I did very clearly. >The error I posted is totally different that the error discussed in this >posting: > >http://mail.python.org/pipermail/mailman-users/2007-February/055640.html > >That was a result of the install "finding" the

Re: [Mailman-Users] Apache,

I'm not sure that everyone looked at the posting that I did very clearly. The error I posted is totally different that the error discussed in this posting: http://mail.python.org/pipermail/mailman-users/2007-February/055640.html That was a result of the install "finding" the Sun installed python.

Re: [Mailman-Users] Apache,

Hank posted: >In particular, make sure the Mailman configure script finds your local >Python build, not the (older) version included in the Solaris >distribution. This is the root of the "Korean Codec" problem that >Mark provided a google search link to. Also make sure that the configure >scrip

Re: [Mailman-Users] Apache,

On 6/26/08, Hank van Cleef wrote: I will note, and think that Brad and Mark will agree, that given the predominance of Linux and Postfix on Mailman hosts, there probably is very little interest among list subscribers for discussion of general Solaris and sendmail issues. Both systems are we

Re: [Mailman-Users] Apache,

Hank posted: >I gave the location of the actual aliases file in /etc/mail for >Solaris. /etc/aliases is provided, but is a symlink to the file in >/etc/mail. It is the symlink that I always use, same deal for the hosts file. :-) >I will note, and think that Brad and Mark will agree, that given

Re: [Mailman-Users] Apache,

The esteemed Brad Knowles has said: > > Vidiot wrote: > > > Thanks for the info, but the last time I looked, aliases was in /etc, > > not /etc/mail. > > Depends on your platform. For Solaris, the aliases have been in > /etc/mail/aliases for a very, very long time. > I gave the location of the

Re: [Mailman-Users] Apache,

Vidiot wrote: Thanks for the info, but the last time I looked, aliases was in /etc, not /etc/mail. Depends on your platform. For Solaris, the aliases have been in /etc/mail/aliases for a very, very long time. -- Brad Knowles <[EMAIL PROTECTED]> LinkedIn Profile:

Re: [Mailman-Users] Apache,

Hank van Cleef wrote: In particular, make sure the Mailman configure script finds your local Python build, not the (older) version included in the Solaris distribution. This is the root of the "Korean Codec" problem that Mark provided a google search link to. You can easily solve this during

Re: [Mailman-Users] Apache,

>The only "gimmick" specific to running Mailman with sendmail is to >include the alias pipes for Mailman in /etc/mail/aliases (and run >newaliases after changing the file). Thanks for the info, but the last time I looked, aliases was in /etc, not /etc/mail. In any event, thanks for the info. M

Re: [Mailman-Users] Apache,

The esteemed Mark Sapiro has said: > > Vidiot wrote: > > > >Thanks for pointing this out. I'll go away now and compile the source > >when I get Sol10 working. Speaking of that, do you suggest using GNU or > >Sun Studio to compile the package? > > > There are others on this list that can speak

Re: [Mailman-Users] Apache, mailman and ScriptAlias - not as documented

Stephen J. Turnbull wrote: >Brad Knowles writes: > > > Moreover, the Mailman code is written in Python, so there shouldn't > > be any need to compile anything with any C compiler. > >The CGI and MTA interface wrappers are written in C, but they're >really really simple (as anything security-criti

Re: [Mailman-Users] Apache,

>The CGI and MTA interface wrappers are written in C, but they're >really really simple (as anything security-critical should be). > >It's not going to make any difference what they're compiled with. I'll install the GNU C compiler tools. MB -- e-mail: [EMAIL PROTECTED]

Re: [Mailman-Users] Apache, mailman and ScriptAlias - not as

Brad Knowles responded: >Following our standard installation procedure works just fine for >Solaris 10. I've done it. Thanks, great news. >Moreover, the Mailman code is written in Python, so there shouldn't >be any need to compile anything with any C compiler. D'oh! >If there was anything t

Re: [Mailman-Users] Apache, mailman and ScriptAlias - not as documented

Brad Knowles writes: > Moreover, the Mailman code is written in Python, so there shouldn't > be any need to compile anything with any C compiler. The CGI and MTA interface wrappers are written in C, but they're really really simple (as anything security-critical should be). It's not going to

Re: [Mailman-Users] Apache, mailman and ScriptAlias - not as documented

>The results of > >may interest you. >Mark Sapiro <[EMAIL PROTECTED]>The highway is for gamblers, Thanks, so noted. The Solaris 10 installed. The proc temp stayed low enough to not get Solaris mad and want t

Re: [Mailman-Users] Apache, mailman and ScriptAlias - not as documented

On 6/25/08, Vidiot wrote: Thanks for pointing this out. I'll go away now and compile the source when I get Sol10 working. Speaking of that, do you suggest using GNU or Sun Studio to compile the package? Following our standard installation procedure works just fine for Solaris 10. I've d

Re: [Mailman-Users] Apache, mailman and ScriptAlias - not as documented

Vidiot wrote: > >Thanks for pointing this out. I'll go away now and compile the source >when I get Sol10 working. Speaking of that, do you suggest using GNU or >Sun Studio to compile the package? There are others on this list that can speak to Solaris installation about which I know almost noth

Re: [Mailman-Users] Apache, mailman and ScriptAlias - not as documented

>That's because you're installing a RedHat package, and the RPM already >installed /etc/httpd/conf.d/mailman.conf which contains that >ScriptAlias. Oh crap. Another reason I am going toward Solaris 10. The last thing I'd do is stick a web server confing file in another directory and include it.

Re: [Mailman-Users] Apache, mailman and ScriptAlias - not as documented

Vidiot wrote: >>Why do you think that? > >ScriptAlias /cgi-bin/ "/home/httpd/cgi-bin/" >ScriptAlias /mailman/ "/usr/lib/mailman/cgi-bin" > >mrvideo.vidiot.com.ZROOT <406> /etc/init.d/httpd restart >Stopping httpd:[ OK ] >Starting httpd: [Wed Jun

Re: [Mailman-Users] Apache, mailman and ScriptAlias - not as documented

>Why do you think that? ScriptAlias /cgi-bin/ "/home/httpd/cgi-bin/" ScriptAlias /mailman/ "/usr/lib/mailman/cgi-bin" mrvideo.vidiot.com.ZROOT <406> /etc/init.d/httpd restart Stopping httpd:[ OK ] Starting httpd: [Wed Jun 25 18:59:28 2008] [war

Re: [Mailman-Users] Apache, mailman and ScriptAlias - not as documented

Vidiot wrote: > >After doing said setting in the config file and restarting the seb server >it spits out a warning messag that it exists and that the 2nd one might not >get reached. > >I'll do it again and post the exact warning message. That's because you're installing a RedHat package, and the

Re: [Mailman-Users] Apache, mailman and ScriptAlias - not as documented

Vidiot wrote: >I've looked at the installation page over at the Wiki and there is nothing >regarding the problem I've run up against. > >See page 6 of the Installation Manual (pdf). > >It states the following should be added: > > ScriptAlias /mailman/ $prefix/cgi-bin/ > >I already have Scrip

Re: [Mailman-Users] Apache, mailman and ScriptAlias - not as documented

On 25/06/2008, at 4:52 PM, Vidiot wrote: I've looked at the installation page over at the Wiki and there is nothing regarding the problem I've run up against. See page 6 of the Installation Manual (pdf). It states the following should be added: ScriptAlias /mailman/ $prefix/cgi-bin

[Mailman-Users] Apache, mailman and ScriptAlias - not as documented

I've looked at the installation page over at the Wiki and there is nothing regarding the problem I've run up against. See page 6 of the Installation Manual (pdf). It states the following should be added: ScriptAlias /mailman/ $prefix/cgi-bin/ I already have ScriptAlias defined:

Re: [Mailman-Users] apache permissions issue

On 8/17/07, Terry wrote: >> The lists appear to be working fine. However, I cannot perform any >> administrative functions via the web interface. It does not return >> any errors when I submit and I can't see any errors in the apache >> error log for that vhost. I tried adding the apache u

Re: [Mailman-Users] apache permissions issue

Any ideas on this one? On 8/12/07, Terry <[EMAIL PROTECTED]> wrote: > Hello, > > The lists appear to be working fine. However, I cannot perform any > administrative functions via the web interface. It does not return > any errors when I submit and I can't see any errors in the apache > error log

[Mailman-Users] apache permissions issue

Hello, The lists appear to be working fine. However, I cannot perform any administrative functions via the web interface. It does not return any errors when I submit and I can't see any errors in the apache error log for that vhost. I tried adding the apache user to the mailman group with no l

[Mailman-Users] apache config issue?

Mr. Sapiro: Thank you sir, for your help. Yes, I ran check_perms with and without -f as root until I got good results. I've now added the following stanza to my vhost.conf file: Options ExecCGI SetHandler cgi-script I don't know what would have undone that. That stan

Re: [Mailman-Users] apache errors

Hi, You have to accesss http://10.0.253.82/mailman/listinfo. Without the script name in the end of URI, Apache returns error because you set "Options None." "Options ExecCGI" should not be used here for ScriptAliases is already specified. "Options Indexes" is the configuration for directory

Re: [Mailman-Users] apache errors

> Here is what I use, adjust the path to your installation: > > ScriptAlias /mailman/ /usr/lib/mailman/cgi-bin/ > > AllowOverride None > Options ExecCGI > Order allow,deny > Allow from all > Here's how it reads now after editing that file (and restarting apache). ScriptAlias /ma

Re: [Mailman-Users] apache errors

On Thu, 2005-09-29 at 14:23 -0400, John Dennis wrote: > I suspect the problem is the http configuration for the directory that > was originally posted omitted the "Options ExecCGI" which is required to > tell the http server it is permissible to execute cgi scripts in this > directory. Oh, almost

Re: [Mailman-Users] apache errors

On Thu, 2005-09-29 at 13:55 -0400, Joe Damico wrote: > Bryan: > > I had this problem myself - very recently. This was on a Solaris > implementation of Mailman. > > The values in question are: > DEFAULT_EMAIL_HOST = 'hostname' > DEFAULT_URL_HOST = 'hostname' > > I had appended these values to th

Re: [Mailman-Users] apache errors

> I had this problem myself - very recently. This was on a Solaris > implementation of Mailman. I'm on OpenBSD > The values in question are: > DEFAULT_EMAIL_HOST = 'hostname' > DEFAULT_URL_HOST = 'hostname' > > I had appended these values to the file: > /usr/local/mailman/Mailman/mm_cfg.py > > T

Re: [Mailman-Users] apache errors

age- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bryan Irvine Sent: Thursday, September 29, 2005 12:55 PM To: mailman-users@python.org Subject: [Mailman-Users] apache errors I've jsut installed mailman, and think I've done everything right so far. When I try to browse

[Mailman-Users] apache errors

I've jsut installed mailman, and think I've done everything right so far. When I try to browse to the mailman site though it doesn't seem to work properly. I've found other similar questions in the archive, but none of those had any resolution. When I browse to http://10.0.253.82/mailman/ I jus

Re: [Mailman-Users] apache and mailman

On Wed, 2005-07-27 at 15:54 -0500, roy vinner wrote: > Greetings! > > Which settings are there to tweak so that apache set > with group=apache can still run mailman? creating a group web with no > such user and mailman and apache in it did not do the job. You need to rebuild mailman using the con

[Mailman-Users] apache and mailman

Greetings! Which settings are there to tweak so that apache set with group=apache can still run mailman? creating a group web with no such user and mailman and apache in it did not do the job. Thanks for any input. Roy -- Mailman-Users mai

[Mailman-Users] Apache won't show Mailman pages after reboot

Hi, I'm running Mailman 2.1 on a Debian Woody system. It worked fine, but today I rebooted the server (after > 200 days) and now the web server (Apache) does not display mailman's web interfaces (e.g. mysite.com/mailman/listinfo as well as the other mailman pages). It shows: "Forbidden You don't

[Mailman-Users] Apache: allow which dirs? (was Re: Problems with relocating a list)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, 21 Sep 2004 23:32:25 -0600 Anthony Chavez <[EMAIL PROTECTED]> wrote: > However, Apache 2 still 403s when attempting to access > /pipermail/listname/, using either hostname My question at this point is this: what Mailman directories should

  1   2   >