Re: [Mailman-Users] moved lists and now they don't work
Hi,
I'm still having trouble...
I removed everything in /private/var/mailman/archives/public/ but
Mailman didn't replace the symlinks and when I tried to create the
symlinks, Mailman got really confused. My lists are down and I don't
know how to recover them.
corp-admin2:/private/var/mailman/archives/public root# ls -l corp-admin2:/private/var/mailman/archives/public root#
I've run check permissions dozen's of times:
corp-admin2:/private/var/mailman/archives/public root# /usr/share/ mailman/bin/check_perms -f No problems found corp-admin2:/private/var/mailman/archives/public root#
yet my error logs show permission errors. I've tried changing owners
from mailman:mailman to root:mailman and back again - I've made
directories world readable but I still get these errors...
Jun 26 19:13:08 2007 (10311) SHUNTING: 1182910388.3509221 +37c9faaaa7ce90d565375941efb6b3a61c9ad826 Jun 26 19:13:28 2007 (10311) Archive file access failure: /private/var/mailman/archives/private/customer-us.mbox/ customer-us.mbox [Errno 13] Permission denied: '/private/var/mailman/ archives/private/customer-us.mbox/customer-us.mbox'
corp-admin2:/private/var/mailman/archives/private root# cd customer-us
corp-admin2:/private/var/mailman/archives/private/customer-us root# ls -l total 5200 drwxrwsr-x 8 root mailman 272 Jun 26 14:33 2007-June -rw-rw-r-- 1 root mailman 2654504 Jun 26 14:33 2007-June.txt drw-rw---- 2 root mailman 68 Jun 26 14:33 database -rw-rw-r-- 1 root mailman 479 Jun 18 13:30 index.html
Jun 26 19:13:28 2007 (10311) Uncaught runner exception: [Errno 13]
Permission denied: '/private/var/mailman/archives/private/customer-
us.mbox/customer-us.mbox'
Jun 26 19:13:28 2007 (10311) Traceback (most recent call last):
File "/usr/share/mailman/Mailman/Queue/Runner.py", line 111, in
_oneloop
self._onefile(msg, msgdata)
File "/usr/share/mailman/Mailman/Queue/Runner.py", line 167, in
_onefile
keepqueued = self._dispose(mlist, msg, msgdata)
File "/usr/share/mailman/Mailman/Queue/ArchRunner.py", line 73, in
_dispose
mlist.ArchiveMail(msg)
File "/usr/share/mailman/Mailman/Archiver/Archiver.py", line 199,
in ArchiveMail
self.__archive_to_mbox(msg)
File "/usr/share/mailman/Mailman/Archiver/Archiver.py", line 168,
in __archive_to_mbox
mbox = self.__archive_file(afn)
File "/usr/share/mailman/Mailman/Archiver/Archiver.py", line 156,
in __archive_file
return Mailbox.Mailbox(open(afn, 'a+'))
IOError: [Errno 13] Permission denied: '/private/var/mailman/archives/
private/customer-us.mbox/customer-us.mbox'
Jun 26 19:23:03 2007 (10314) SHUNTING: 1182910982.1765511
+4636bcd0509b8d4fc66200d2a26b32dc929f0e06
Jun 26 19:23:13 2007 (10314) Uncaught runner exception: [Errno 13]
Permission denied: '/private/var/mailman/archives/private/ops'
Jun 26 19:23:13 2007 (10314) Traceback (most recent call last):
File "/usr/share/mailman/Mailman/Queue/Runner.py", line 111, in
_oneloop
self._onefile(msg, msgdata)
File "/usr/share/mailman/Mailman/Queue/Runner.py", line 167, in
_onefile
keepqueued = self._dispose(mlist, msg, msgdata)
File "/usr/share/mailman/Mailman/Queue/IncomingRunner.py", line
130, in _dispose
more = self._dopipeline(mlist, msg, msgdata, pipeline)
File "/usr/share/mailman/Mailman/Queue/IncomingRunner.py", line
153, in _dopipeline
sys.modules[modname].process(mlist, msg, msgdata)
File "/usr/share/mailman/Mailman/Handlers/ToDigest.py", line 91,
in process
send_digests(mlist, mboxfp)
File "/usr/share/mailman/Mailman/Handlers/ToDigest.py", line 132,
in send_digests
send_i18n_digests(mlist, mboxfp)
File "/usr/share/mailman/Mailman/Handlers/ToDigest.py", line 306,
in send_i18n_digests
msg = scrubber(mlist, msg)
File "/usr/share/mailman/Mailman/Handlers/Scrubber.py", line 227,
in process
url = save_attachment(mlist, part, dir, filter_html=False)
File "/usr/share/mailman/Mailman/Handlers/Scrubber.py", line 352,
in save_attachment
makedirs(fsdir)
File "/usr/share/mailman/Mailman/Handlers/Scrubber.py", line 339,
in makedirs
os.makedirs(dir, 02775)
File "/System/Library/Frameworks/Python.framework/Versions/2.3/lib/
python2.3/os.py", line 153, in makedirs
File "/System/Library/Frameworks/Python.framework/Versions/2.3/lib/
python2.3/os.py", line 153, in makedirs
File "/System/Library/Frameworks/Python.framework/Versions/2.3/lib/
python2.3/os.py", line 153, in makedirs
File "/System/Library/Frameworks/Python.framework/Versions/2.3/lib/
python2.3/os.py", line 154, in makedirs
OSError: [Errno 13] Permission denied: '/private/var/mailman/archives/
private/ops'
Jun 26 19:23:13 2007 (10314) SHUNTING: 1182910992.721427 +d396922f361992f9d2b65e96d4763591331f5010
drwxrwsr-x 9 root mailman 306 Jun 26 18:49 ops
drwxrwsr-x 3 root mailman 102 Jun 18 13:30 ops.mbox
corp-admin2:/private/var/mailman/archives/private/ops root# ls -l
total 40
drwxrwxrwx 23 root mailman 782 Jun 18 13:30 2006-April
-rwxrwxrwx 1 root mailman 6277 Jun 18 13:30 2006-April.txt
-rwxrwxrwx 1 root mailman 1444 Jun 18 13:30 2006-April.txt.gz
drwxrwxrwx 8 mailman mailman 272 Jun 25 18:53 attachments
drwxrwxrwx 7 root mailman 238 Jun 18 13:30 database
-rwxrwxrwx 1 root mailman 1040 Jun 18 13:30 index.html
-rwxrwxrwx 1 root mailman 864 Jun 18 13:30 pipermail.pckIts funny, I was more worried about moving postfix and everyone's
mailboxes....I thought mailman would be a piece of cake. If anyone
understands what happening here - I'd really appreciate it.
On Jun 18, 2007, at 10:08 PM, Mark Sapiro wrote:
carconni wrote:
Are you running SeLinux or some other kind of security policy that is denying access?
And what if you
cd customer-us.mbox ls -la
Assuming the mailman group has sufficient permission on the whole path, I think it is likely some security policy that is denying access.
-- Mark Sapiro <msapiro@value.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Hi,
I know you guys aren't excited to hear this but it's running on an
xserve. I think there may have been an error in how I was told to
move mailman...
does this look right?
corp-admin2:/private/var/mailman/archives/private root# ls -la ops.mbox/ total 80 drwxrwsr-x 3 root mailman 102 Jun 18 13:30 . drw-rw---- 736 root mailman 25024 Jun 26 19:55 .. -rw-rw-r-- 1 root mailman 37806 Jun 18 13:30 ops.mbox
corp-admin2:/private/var/mailman/archives/private root# ls -la ops total 8 drwxrwsr-x 3 root mailman 102 Jun 26 19:56 . drw-rw---- 736 root mailman 25024 Jun 26 19:55 .. -rw-rw-r-- 1 root mailman 1040 Jun 26 19:55 index.html
On Jun 26, 2007, at 8:55 PM, Mark Sapiro wrote:
carconni wrote:
This is the permission on /private/var/mailman/archives/private. You need g+sx. Also, in order for public archive access to work, you probably need o+x.
If you look again at <http://mail.python.org/pipermail/mailman-users/2007-June/057421.html>, you will see
[msapiro at sb7 var]$ ls -ld mailman/archives/private drwxrws--x 74 root mailman 4096 May 4 09:30 mailman/archives/private/
-- Mark Sapiro <msapiro@value.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Mark Sapiro wrote:
It looks like there is a bug in check_perms. check_perms checks archives/private to be sure it isn't o+r and also warns if it is o+x although on most systems, it has to be for public archives to work, but check_perms doesn't check for any user or group permissions on archives/private nor does it even check to make sure it is o-w.
Sorry for all the trouble.
-- Mark Sapiro <msapiro@value.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
carconni wrote:
Are you running SeLinux or some other kind of security policy that is denying access?
And what if you
cd customer-us.mbox ls -la
Assuming the mailman group has sufficient permission on the whole path, I think it is likely some security policy that is denying access.
-- Mark Sapiro <msapiro@value.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Hi,
I know you guys aren't excited to hear this but it's running on an
xserve. I think there may have been an error in how I was told to
move mailman...
does this look right?
corp-admin2:/private/var/mailman/archives/private root# ls -la ops.mbox/ total 80 drwxrwsr-x 3 root mailman 102 Jun 18 13:30 . drw-rw---- 736 root mailman 25024 Jun 26 19:55 .. -rw-rw-r-- 1 root mailman 37806 Jun 18 13:30 ops.mbox
corp-admin2:/private/var/mailman/archives/private root# ls -la ops total 8 drwxrwsr-x 3 root mailman 102 Jun 26 19:56 . drw-rw---- 736 root mailman 25024 Jun 26 19:55 .. -rw-rw-r-- 1 root mailman 1040 Jun 26 19:55 index.html
On Jun 26, 2007, at 8:55 PM, Mark Sapiro wrote:
carconni wrote:
This is the permission on /private/var/mailman/archives/private. You need g+sx. Also, in order for public archive access to work, you probably need o+x.
If you look again at <http://mail.python.org/pipermail/mailman-users/2007-June/057421.html>, you will see
[msapiro at sb7 var]$ ls -ld mailman/archives/private drwxrws--x 74 root mailman 4096 May 4 09:30 mailman/archives/private/
-- Mark Sapiro <msapiro@value.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Mark Sapiro wrote:
It looks like there is a bug in check_perms. check_perms checks archives/private to be sure it isn't o+r and also warns if it is o+x although on most systems, it has to be for public archives to work, but check_perms doesn't check for any user or group permissions on archives/private nor does it even check to make sure it is o-w.
Sorry for all the trouble.
-- Mark Sapiro <msapiro@value.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (2)
-
carconni -
Mark Sapiro