* Web Analysts :
> OSError: [Errno 40] Too many levels of symbolic links:
> '/usr/lib/mailman/archives/private/listname/listname'
Sounds like you have circular symlink somewhere around
/usr/lib/mailman/archives/private/listname/listname
--
Ralf Hildebrandt Charite Universitäts
What does this mean?
[root@zarathustra mailman]# bin/check_perms
Traceback (most recent call last):
File "bin/check_perms", line 391, in
checkall()
File "bin/check_perms", line 204, in checkall
os.path.walk(d, checkwalk, STATE)
File "/usr/lib/python2.7/posixpath.py", line 23
Noah wrote:
>
>I run check_perms with the -f switch and the program runs the program
>claims it found 100 problems and asks to run the program again. Next
>time I run it 100 problems are still found. So I did some research to
>figure out what the problems are.
>
>$ sudo ./check_perms -f
>/var/
hi there,
I run check_perms with the -f switch and the program runs the program
claims it found 100 problems and asks to run the program again. Next
time I run it 100 problems are still found. So I did some research to
figure out what the problems are.
$ sudo ./check_perms -f
/var/lib/mail
On Mon, May 25, 2009 at 08:04:39AM -0700, Mark Sapiro wrote:
> >Problems found: 1283
> >Re-run as list (or root) with -f flag to fix
>
> The most likely explanation is there are directories in Mailman's tree
> that are symlinks. check_perms looks at the permissions of the link
> itself (generally
admin2 wrote:
>
>okay I am running check_perms with the -f switch and find that the same
>Problems occur over and over. Why are they not getting fixed? I am
>running check_perms as root.
>
>
>Problems found: 1283
>Re-run as list (or root) with -f flag to fix
The most likely explanation is the
Hi,
okay I am running check_perms with the -f switch and find that the same
Problems occur over and over. Why are they not getting fixed? I am
running check_perms as root.
Problems found: 1283
Re-run as list (or root) with -f flag to fix
---
admin2 wrote:
>
>I am not clear why check_perms are failing. The error claims
>'/var/lib/mailman/archives/public/maillist' directory does not exist.
>but an 'ls' reveals it does.
>r...@enabled:/var/lib/mailman/bin# ls -l
>/var/lib/mailman/archives/public/maillist
>lrwxrwxrwx 1 80 mailman 44 Dec
Hi there,
I am not clear why check_perms are failing. The error claims
'/var/lib/mailman/archives/public/maillist' directory does not exist.
but an 'ls' reveals it does.
/var/lib/mailman/archives/public/maillist bad group (has: mailman,
expected list) (fixing)
Traceback (most recent call
Bill Christensen wrote:
>
>I'm setting up a new server with Mailman.
>
>After installing I tried
> bin/check_perms -f
>and got:
> file "bin/check_perms", line 44
> '''
> ^
>Syntax error: invalid syntax
>
>I'm running Python 2.5.1. My existing server, running Mailman
>2
Hi all,
I'm setting up a new server with Mailman.
After installing I tried
bin/check_perms -f
and got:
file "bin/check_perms", line 44
'''
^
Syntax error: invalid syntax
I'm running Python 2.5.1. My existing server, running Mailman
2.1.11/Python 2.3, has th
support <[EMAIL PROTECTED]> wrote:
>What does this all mean?
>
>Re-run as list (or root) with -f flag to fix
>[EMAIL PROTECTED]:/etc# check_perms -f
>/var/lib/mailman/templates bad group (has: root, expected list) (fixing)
>/var/lib/mailman/logs bad group (has: root, expected list) (fixing)
>/var/
What does this all mean?
Re-run as list (or root) with -f flag to fix
[EMAIL PROTECTED]:/etc# check_perms -f
/var/lib/mailman/templates bad group (has: root, expected list) (fixing)
/var/lib/mailman/logs bad group (has: root, expected list) (fixing)
/var/lib/mailman/cgi-bin bad group (has: root, e
John Fleming wrote:
>Running 2.1.9 on Debian etch (stable), lists working fine except qrunner
>silently dies and noone notices until someone realizes they haven't seen any
>mail lately. Currently worked around with cron job restarting Mailman.
>Googling around, some have suggested this might b
Running 2.1.9 on Debian etch (stable), lists working fine except qrunner
silently dies and noone notices until someone realizes they haven't seen any
mail lately. Currently worked around with cron job restarting Mailman.
Googling around, some have suggested this might be related to
permissions
faq03.014.htp
The FAQ entry says I should run check_perms so I did.
Now what? The FAQ offers nothing on which files need their permissions
changed or to what mode.
ma /usr/pkg/lib/mailman/bin# ./check_perms
Traceback (most recent call last):
File "./check_perms", line 50, in ?
MAILMAN_GID
All fixed now.
I was using the BSD port version rather than a source tarball, so I
edited the Makefile to use mailman rather than mailnull for the
groupid.
Thanks everyone for all the help :)
--
Tim DeBoer
Just once, I'd like it if someone called me "Sir".
Without adding "You're creating a scen
On Tue, 2005-08-09 at 09:30 -0600, Tim DeBoer wrote:
> timlist". Command output: Group mismatch error. Mailman expected the
> mail wrapper script to be executed as group "mailnull", but the
> system's mail server executed the mail script as group "mailman". Try
> tweaking the mail server to run t
I've managed to get my web interface to mailman working, but... when I
run check_perms I see all this.
# bin/check_perms
Traceback (most recent call last):
File "bin/check_perms", line 380, in ?
checkall()
File "bin/check_perms", line 196, in checkall
os.path.walk(d, checkwalk, STATE)
Rob Scott wrote:
>I'm fairly certain this problem was caused by my running check_perms -f when
>troubleshooting another issue, since resolved, but right after fixing that
>when attempting to access the web interface I got a 403 for everything. admin,
>listinfo, etc.
What was in your web server
I'm fairly certain this problem was caused by my running check_perms -f when
troubleshooting another issue, since resolved, but right after fixing that when
attempting to access the web interface I got a 403 for everything. admin,
listinfo, etc. I went to a backup of the site and copied the perm
I've install mailman-2.1.1-5.i386.rpm version and it seems to work fine
Thank you any way!
- Original Message -
From: "Todd" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, May 04, 2004 12:17 PM
Subject: Re: [Mailman-Users] check_perms error?
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
nikos wrote:
> Unfortunatelly there is nothing in RH errata
> Any suggestions?
Look again? :)
https://rhn.redhat.com/errata/RHSA-2004-020.html
- --
ToddOpenPGP -> KeyID: 0xD654075A | URL: www.pobox.com/~tmz/pgp
=
Unfortunatelly there is nothing in RH errata
Any suggestions?
- Original Message -
From: "Todd" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, May 04, 2004 11:06 AM
Subject: Re: [Mailman-Users] check_perms error?
> -BEGIN PGP SIGNED MESSAGE
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
nikos wrote:
> I run mailman-2.1-8 in a RH9 Linux with python-2.2.2-26.
You should apply the redhat errata to your system. The mailman
package shipped with redhat 9 was broken in several annoying ways.
- --
ToddOpenPGP -> KeyID: 0xD654075A
Hello list
This is my first try in mailman.
I run mailman-2.1-8 in a RH9 Linux with python-2.2.2-26.
Mailman installed automaticaly from redhat installer.
When I run check_perms in /var/mailman/bin/ directory the following message
shows. Is that problem and how can I solve it before continuing
T
Hi,
I installed Mailman on FreeBSD 4.9
I move the mailman directory to /home/http/admin/mailman
When I check the perm from the install dir: sh check_perms -f
I have:
Check the permissions for the Mailman installation.
Usage: %(PROGRAM)s [-f] [-v] [-h]
With no arguments, just check and report a
Joe Kirby <[EMAIL PROTECTED]> writes:
> My lists are working just fine, and all of the command line admin
> features work.
>
> When I go to http://server/mailman/admin/listname and enter my site
> password, I get an error back saying "Authorization Failed". I have
> tried setting the site passwor
Sorry! I forgot to show the problem with check_perms.
When I try to run ./check_perms :
Traceback (innermost last):
File "./check_perms", line 50, in ?
MAILMAN_GRPNAME = grp.getgrgid(MAILMAN_GID)[0]
TypeError: illegal argument type for built-in operation
--
This email is protected by a
My lists are working just fine, and all of the command line admin
features work.
When I go to http://server/mailman/admin/listname and enter my site
password, I get an error back saying "Authorization Failed". I have
tried setting the site password using mmsitepass. Everything worked fine
last mo
Hi ...
I'm having a good time setting up a replacement box for my mail and web
server, switching to postfix for MTA, and moving a lists over from my
old mailman server (2.0.6 to 2.0.8).
A couple of issues I've noticed:
1. I was surprised that the --with-mail-gid needed to be "mailman" and
not
What directory are you in when you run bin/check_perms?
> Hello. I installed Mailman on a RH7.1 box with the RPM from Rawhide
> (Mailman version 2.0.6). When I run check_perms, I'm getting the following
> error:
> Traceback (innermost last):
>File "bin/check_perms", line 50, in ?
> MA
Hello. I installed Mailman on a RH7.1 box with the RPM from Rawhide
(Mailman version 2.0.6). When I run check_perms, I'm getting the following
error:
Traceback (innermost last):
File "bin/check_perms", line 50, in ?
MAILMAN_GRPNAME = grp.getgrgid(MAILMAN_GID)[0]
TypeError: illegal argume
Hello. I installed Mailman on a RH7.1 box with the RPM from Rawhide
(Mailman version 2.0.6). When I run check_perms, I'm getting the following
error:
Traceback (innermost last):
File "bin/check_perms", line 50, in ?
MAILMAN_GRPNAME = grp.getgrgid(MAILMAN_GID)[0]
TypeError: illegal argume
34 matches
Mail list logo
