On 2010-12-30 4:52 PM, Tanstaafl wrote:
After the change to the DocRoot, now when I go to either one I get only
one error:
mod_mime_magic: can't read `/usr/lib64/mailman/cgi-bin/admin'
Forgot to ask - any other ideas on this error message? I'm looking into
it from the apache angle, but not
Tanstaafl writes:
On 2010-12-30 4:52 PM, Tanstaafl wrote:
After the change to the DocRoot, now when I go to either one I get only
one error:
mod_mime_magic: can't read `/usr/lib64/mailman/cgi-bin/admin'
Forgot to ask - any other ideas on this error message? I'm looking into
On 2010-12-31 10:24 AM, Stephen J. Turnbull wrote:
Tanstaafl writes:
On 2010-12-30 4:52 PM, Tanstaafl wrote:
After the change to the DocRoot, now when I go to either one I get only
one error:
mod_mime_magic: can't read `/usr/lib64/mailman/cgi-bin/admin'
Forgot to ask - any other ideas on
Tanstaafl wrote:
On 2010-12-31 10:24 AM, Stephen J. Turnbull wrote:
What are the owner, group, and permissions for that file?
Same as all the rest in cgi-bin:
-rwxr-s--x 1 mailman mailman 10448 Dec 5 13:37 admin
There's the issue. Apache can execute the wrappers, but mod_magic can't
read
On 2010-12-29 9:07 PM, Mark Sapiro wrote:
snip
This might be related to the DocumentRoot. I don't know. I would change
the DocumentRoot for the reasons I indicate above.
Done, and thanks...
That probably won't change these errors, and if it doesn't, and the
Mailman web interface continues
Tanstaafl wrote:
Ok... but what do I point the DocumentRoot and/or the directory to?
Hmmm... maybe /usr/lib64/mailman/cgi-bin/ ?
Yes... it works now! Cool... thanks for your patience Mark...
It really doesn't matter because Apache isn't serving any documents
except those public archive
On 2010-12-23 3:48 PM, Mark Sapiro wrote:
Tanstaafl wrote:
Mark wisely pointed out:
If you haven't told Apache to listen on the port you're redirecting to,
that would explain a lot. You don't necessarily need a VirtualHost
block for that IP and port, but you do need to tell Apache to listen.
Tanstaafl writes:
Is there some kind of .conf parser for apache that will show the current
configs it is using, similar to 'postconf -n' for postfix?
Not that I know of.
Too bad, it would sure come in handy when troubleshooting apache
problems, especially in complex
On 2010-12-27 7:54 AM, Stephen J. Turnbull wrote:
Tanstaafl writes:
Is there some kind of .conf parser for apache that will show the current
configs it is using, similar to 'postconf -n' for postfix?
Mark replied:
Not that I know of.
Too bad, it would sure come in handy when troubleshooting
Tanstaafl wrote:
Where do I specify the server crt/key pair for the lists.example.com
vhost if I don't have a full blown vhost config file for it? Or can I
just go ahead and create one (vhost config file pointing to the correct
dir)?
You need to have a VirtualHost block for this host:port.
Tanstaafl wrote:
I'm trying to get things working on a non-standard port along the lines
of the How-To found here:
http://www.wesayso.net
(I know, I know, this is not ideal, but it does work well for all of the
other sites I've set up, now I'd just like to transition my mailman
install over to
On 2010-12-23 2:08 PM, Mark Sapiro wrote:
I set:
DEFAULT_URL_PATTERN = 'https://%s:#/mailman/'
Where # is the 5 digit port I set it to, then I ran:
# ./withlist -l -a -r fix_url
snip
I also added the redirect for the non-ssl host to the ssl host per the
instructions at the above
Tanstaafl wrote:
I meant I don't have a specific apache2 listener for mailman, like I do
for my other websites, I've only been (tryingto) add the rewrite rule (I
keep my rewrite rules in one .conf file, and the vhosts in individual
files per host)... maybe I need to create one that is listening
13 matches
Mail list logo
