Yep, I copied the config from my Mandriva installation thinking they
would be compatible. I was wrong and restoring the default fixed it. Thanks.
On 5/9/2012 7:36 PM, Mark Sapiro wrote:
> Dennis Putnam wrote:
>> mailman.conf
>>
>> ---
Dennis Putnam wrote:
>
>mailman.conf
>
>-=
>-
># Directives for the mailman web interface
>
>Alias /pipermail/ "/var/lib/mailman/archives/public/"
>ScriptAliasMatch ^/mailman/([^/]*)(
Thanks for the reply. I think you'll it pretty much vanilla.
mm_py.cfg
---
# -*- python -*-
# Copyright (C) 1998,1999,2000,2001,2002 by the Free Software
Foundation, Inc.
#
Dennis Putnam wrote:
>
>I've made the decision to abandon Mandriva and migrate to Centos. I have
>mailman up an running (sort of) but now have the opposite problem. This
>is a vanilla install of Apache so the only config file is mailman.conf
>at this time. The cgi extension does not exist, in cgi-b
On Wed, May 9, 2012 at 10:48 AM, Dennis Putnam wrote:
> I've made the decision to abandon Mandriva and migrate to Centos.
If you wanted to migrate to Ubuntu 12.04, I could give you all the steps
for getting Mailman up and running easily. But someone else will probably
be able to help you with A
I've made the decision to abandon Mandriva and migrate to Centos. I have
mailman up an running (sort of) but now have the opposite problem. This
is a vanilla install of Apache so the only config file is mailman.conf
at this time. The cgi extension does not exist, in cgi-bin, on this
installation of
Dennis Putnam wrote:
>
>Thanks. The cgi scripts do have the cgi extension on them. I put CGIEXT
>= '' in mm_cfg.py which, of course fixed the problem.
It may have fixed the problem for the moment, but it is the wrong way
to do it.
If the cgi-bin/* wrappers have .cgi extensions, the proper value
Thanks. The cgi scripts do have the cgi extension on them. I put CGIEXT
= '' in mm_cfg.py which, of course fixed the problem.
On 5/3/2012 5:10 PM, Mark Sapiro wrote:
> Dennis Putnam wrote:
>> Thanks for the reply. You are correct in that it does not exist in
>> mm_cfg.py. However, in Defaults.py i
Dennis Putnam wrote:
>
>Thanks for the reply. You are correct in that it does not exist in
>mm_cfg.py. However, in Defaults.py it is set to
>
>CGIEXT = '.cgi'
>
>The question then becomes, where should I fix it (presumably in
>mm_cfg-py). Leave it to Mandriva to change what is normal for everyone e
Thanks for the reply. You are correct in that it does not exist in
mm_cfg.py. However, in Defaults.py it is set to
CGIEXT = '.cgi'
The question then becomes, where should I fix it (presumably in
mm_cfg-py). Leave it to Mandriva to change what is normal for everyone else.
On 5/2/2012 7:44 PM, Mar
Dennis Putnam wrote:
>
>I seem to recall seeing this problem before but I can't find it in any
>of my archives.
>
>[Wed May 02 13:14:20 2012] [error] [client 74.176.153.13] script not
>found or unable to stat: /usr/lib/mailman/cgi-bin/admin.cgi.cgi,
>referer: https://dap002.dyndns-ip.com/mailman/ad
I seem to recall seeing this problem before but I can't find it in any
of my archives.
[Wed May 02 13:14:20 2012] [error] [client 74.176.153.13] script not
found or unable to stat: /usr/lib/mailman/cgi-bin/admin.cgi.cgi,
referer: https://dap002.dyndns-ip.com/mailman/admin
Obviously the double cgi
Dennis Putnam wrote:
>All the cgi files are present. It appears to me that my web server
>config was unaffected by the botched upgrade attempt. However, I don't
>know if the mailman or python installs did something. What should I
>look
>for in the httpd configuration?
check your web server erro
All the cgi files are present. It appears to me that my web server
config was unaffected by the botched upgrade attempt. However, I don't
know if the mailman or python installs did something. What should I look
for in the httpd configuration?
On 5/2/2012 11:14 AM, Mark Sapiro wrote:
> Dennis Putna
Dennis Putnam wrote:
>
>I am making progress (I think). When I uninstalled and reinstalled
>python, it seems to have taken mailman with it. I did a reinstall of
>mailman and now the daemon and the qrunners start. I can also now access
>the initial web page with my lists shown. However, when I try t
I am making progress (I think). When I uninstalled and reinstalled
python, it seems to have taken mailman with it. I did a reinstall of
mailman and now the daemon and the qrunners start. I can also now access
the initial web page with my lists shown. However, when I try to access
the management pag
Actually I think python itself may be hosed. I am uninstalling it and
reinstalling to see if that fixes it. If not then I will try your
suggestion.
On 5/2/2012 10:06 AM, Mark Sapiro wrote:
> Mark Sapiro wrote:
>> It appears your system Python is now different from the one that
>> compiled all the
Dennis Putnam wrote:
>
>On to the next layer of the onion. :-(
>
>Traceback (most recent call last):
> File "/usr/sbin/mailmanctl", line 106, in
>from Mailman import mm_cfg
>ImportError: cannot import name mm_cfg
Did you remove *.py files too? If so, restore and try again removing
only *.py
Mark Sapiro wrote:
>
>It appears your system Python is now different from the one that
>compiled all the .pyc files. Just do
>
>
> rm -r /path/to/Mailman/*.pyc
I responded without really thinking. I don't think that will work
completely. It will remove the .pyc files immediately subordinate the
On to the next layer of the onion. :-(
Traceback (most recent call last):
File "/usr/sbin/mailmanctl", line 106, in
from Mailman import mm_cfg
ImportError: cannot import name mm_cfg
On 5/2/2012 9:48 AM, Mark Sapiro wrote:
> Dennis Putnam wrote:
>> Of course I did not expect this to be eas
Dennis Putnam wrote:
>
>Of course I did not expect this to be easy. After restoring the Mailman
>directory as suggested, mailman will not start:
>
>Traceback (most recent call last):
> File "/usr/sbin/mailmanctl", line 106, in
>from Mailman import mm_cfg
>ImportError: Bad magic number in /usr
Of course I did not expect this to be easy. After restoring the Mailman
directory as suggested, mailman will not start:
Traceback (most recent call last):
File "/usr/sbin/mailmanctl", line 106, in
from Mailman import mm_cfg
ImportError: Bad magic number in /usr/lib/mailman/Mailman/mm_cfg.py
On 4/28/2012 3:02 PM, Dennis Putnam wrote:
> On 4/28/2012 4:57 PM, Mark Sapiro wrote:
>> On 4/28/2012 1:24 PM, Dennis Putnam wrote:
>>> As usual my attempt to update Mandriva has destroyed Mailman. This time
>>> the update failed and rather than move forward, I reverted back to the
>>> working vers
On 4/28/2012 4:57 PM, Mark Sapiro wrote:
> On 4/28/2012 1:24 PM, Dennis Putnam wrote:
>> As usual my attempt to update Mandriva has destroyed Mailman. This time
>> the update failed and rather than move forward, I reverted back to the
>> working version (2010.2). However, I must have missed somethi
On 4/28/2012 1:24 PM, Dennis Putnam wrote:
> As usual my attempt to update Mandriva has destroyed Mailman. This time
> the update failed and rather than move forward, I reverted back to the
> working version (2010.2). However, I must have missed something because
> I am getting the following error
As usual my attempt to update Mandriva has destroyed Mailman. This time
the update failed and rather than move forward, I reverted back to the
working version (2010.2). However, I must have missed something because
I am getting the following error when I try to access Mailman web:
Apr 28 16:07:42
26 matches
Mail list logo
