On Wed, May 9, 2012 at 12:17 AM, Mark Sapiro m...@msapiro.net wrote:
On 5/8/2012 8:22 PM, David wrote:
On Tue, May 8, 2012 at 9:34 PM, Mark Sapiro m...@msapiro.net
mailto:m...@msapiro.net wrote:
What about newly archived messages. Presumably, those are not owned
by
David wrote:
Yes, I can access all the archived messages now, as expected. You are right
about the ownership. In checking again, I can access files from the listing
below regardless of whether the owner is www-data or list.
I did not change any permissions directly. I ran the check_perms script.
On Wed, May 9, 2012 at 12:20 PM, Mark Sapiro m...@msapiro.net wrote:
I can't diagnose what the real issue was without knowing the ownership
and permissions before the change
Thank you. This discussion has increased my understanding and better
prepared me to deal with these issues after
David writes:
apparently I missed something. The problem was simply permissions -- the
well-known Ubuntu issue.
Not just Ubuntu. I believe pretty much every system that Mailman runs
on runs into these issues every once in a while.
It's important to run bin/check_perms every time you
On Tue, May 8, 2012 at 4:48 AM, Stephen J. Turnbull step...@xemacs.orgwrote:
David writes:
apparently I missed something. The problem was simply permissions -- the
well-known Ubuntu issue.
Not just Ubuntu. I believe pretty much every system that Mailman runs
on runs into these issues
On Tue, May 8, 2012 at 11:19 AM, David d...@fiteyes.com wrote:
On Tue, May 8, 2012 at 4:48 AM, Stephen J. Turnbull step...@xemacs.orgwrote:
David writes:
apparently I missed something. The problem was simply permissions --
the
well-known Ubuntu issue.
Not just Ubuntu. I believe
On Tue, May 8, 2012 at 11:41 AM, David d...@fiteyes.com wrote:
On Tue, May 8, 2012 at 11:19 AM, David d...@fiteyes.com wrote:
On Tue, May 8, 2012 at 4:48 AM, Stephen J. Turnbull
step...@xemacs.orgwrote:
David writes:
apparently I missed something. The problem was simply permissions
On Tue, May 8, 2012 at 4:48 AM, Stephen J. Turnbull
step...@xemacs.orgwrote:
If it's not 100% clean,
then run bin/check_perms -f. Sometimes multiple runs are
necessary.
# bin/check_perms -f
No problems found
All permissions are reported as OK now. The check_perms is a very handy
On Tue, May 8, 2012 at 12:37 PM, David d...@fiteyes.com wrote:
On Tue, May 8, 2012 at 4:48 AM, Stephen J. Turnbull
step...@xemacs.orgwrote:
If it's not 100% clean,
then run bin/check_perms -f. Sometimes multiple runs are
necessary.
# bin/check_perms -f
No problems found
All
On Tue, May 8, 2012 at 8:19 PM, Mark Sapiro m...@msapiro.net wrote:
On 5/8/2012 11:16 AM, David wrote:
On Tue, May 8, 2012 at 12:37 PM, David d...@fiteyes.com wrote:
# bin/check_perms -f
No problems found
All permissions are reported as OK now. The check_perms is a very handy
On 5/8/2012 5:39 PM, David wrote:
Good guess, but no, I did not do that. All I did was run bin/check_perms
-f several times.
Permissions were left exactly as check_perms -f set them:
drwxrwsr-x
[...]
For whatever reason, it did not work even with the world readable and
searchable
On Tue, May 8, 2012 at 9:34 PM, Mark Sapiro m...@msapiro.net wrote:
What about newly archived messages. Presumably, those are not owned by
www-data. can you access them?
They are owned by www-data and I can access them. The reason they are owned
by www-data is because of the directory
On 5/8/2012 8:22 PM, David wrote:
On Tue, May 8, 2012 at 9:34 PM, Mark Sapiro m...@msapiro.net
mailto:m...@msapiro.net wrote:
What about newly archived messages. Presumably, those are not owned by
www-data. can you access them?
They are owned by www-data and I can access
What is the solution for this?
OSError: [Errno 13] Permission denied:
'/var/lib/mailman/archives/private/list/attachments'
# ls -la /var/lib/mailman/archives/private/list/attachments
ls: cannot access /var/lib/mailman/archives/private/list/attachments: No
such file or directory
Should I just
On Mon, May 7, 2012 at 5:37 PM, David d...@fiteyes.com wrote:
What is the solution for this?
OSError: [Errno 13] Permission denied:
'/var/lib/mailman/archives/private/list/attachments'
# ls -la /var/lib/mailman/archives/private/list/attachments
ls: cannot access
Ooops. If a moderator sees this, you can delete this whole thread without
sending it. The problem was permissions. I thought I had looked at that and
validated correct permissions in my very first trouble shooting step, but
apparently I missed something. The problem was simply permissions -- the
16 matches
Mail list logo
