On 01/28/2015 07:15 PM, Bill Christensen wrote:
> Well, I had it all working on Monday night.
>
> I got a report today that someone was getting "Forbidden" again.
>
> The owner of the list in question (and only that one list, not any of
> the other publicly archived lists - which have not seen a
On 1/26/15 11:27 PM, Mark Sapiro wrote:
On 01/26/2015 09:12 PM, Bill Christensen wrote:
All the archives work when in private state. But I had to manually
change the owner of all the publicly available list archives to _www in
private in order for them to be readable. Otherwise they get a big
On 01/26/2015 09:12 PM, Bill Christensen wrote:
>
> All the archives work when in private state. But I had to manually
> change the owner of all the publicly available list archives to _www in
> private in order for them to be readable. Otherwise they get a big
> "Forbidden" message. Should *al
On 1/26/15 9:32 PM, Mark Sapiro wrote:
On 01/26/2015 06:08 PM, Mark Sapiro wrote:
You weren't supposed to remove/move archives/private, just the
subordinate listname directories.
And once again, I misspoke (mistyped). I again meant the subordinate
listname directories under archives/public, no
On 01/26/2015 06:08 PM, Mark Sapiro wrote:
>
> You weren't supposed to remove/move archives/private, just the
> subordinate listname directories.
And once again, I misspoke (mistyped). I again meant the subordinate
listname directories under archives/public, not archives/private.
Mailman expect
On 01/26/2015 06:00 PM, Bill Christensen wrote:
> Ok, I removed the public archives. I didn't rm -r, just copied them
> elsewhere in case this didn't work.
...
> The public archive folder didn't rebuild.
>
> Tail on the error log says:
>
> mlist.Save()
>
> File "/opt/local/share/mailman/Ma
On 1/25/15 7:27 PM, Mark Sapiro wrote:
On 01/25/2015 05:21 PM, Stephen J. Turnbull wrote:
Mark Sapiro writes:
> The solution is simple:
>
> rm -r archives/private/*
You mean "rm -r archives/public/*", don't you? As given it erases all
the data, no?
Oh My yes! Absolutely! I hope nobody
On 01/25/2015 05:21 PM, Stephen J. Turnbull wrote:
> Mark Sapiro writes:
>
> > The solution is simple:
> >
> > rm -r archives/private/*
>
> You mean "rm -r archives/public/*", don't you? As given it erases all
> the data, no?
Oh My yes! Absolutely! I hope nobody does the former. Thanks for
Mark Sapiro writes:
> The solution is simple:
>
> rm -r archives/private/*
You mean "rm -r archives/public/*", don't you? As given it erases all
the data, no?
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org
On 01/25/2015 03:45 PM, Bill Christensen wrote:
>
> I was able to bring most of the archives up to date manually, but one
> fairly active one with public archives is still only showing through
> October 2014. When I run that manually it shows that it's processing
> posts beyond the last one seen
Hi folks,
I recently discovered that all my lists stopped archiving back in
October. I have no clear idea as to what caused that, but I suspect
that it may have occurred as part of some hardware and software upgrades
I did around that time.
I'm still stuck back at Mailman 2.1.13 because the
Hi,
After upgrading to mailman 2.0 we experienced the following problem: The web
interface for the archives doesn't work. The mbox is still accessible and
contains all the messages, but the summary is not generated. The older
version of the summary is still there. Creating a new mailing list
12 matches
Mail list logo
