On 7/6/23 10:26 AM, Charles Buckley wrote:
In hindsight, I think this problem was more to do with the fact that I run
three lists on this server, two of which have the same list admin password, one
of which doesn't. If the developer team were thinking too pointy-headedly
while developing
:13
To: Richard Damon
Cc: mailman-users@python.org
Subject: [Mailman-Users] Re: Mailman 2.1.15 doesn't allow admin changes on
private lists
Anyway, it would be easy to check if Charles has access to mm_cfg.py.
(I don't think there's anything in config.pck that affects the URL
scheme.)
Steve
Richard Damon writes:
> One configuration error that I remember being able to cause this
> sort of issue is if the list is configured with a http:// address,
> but the server automatically forwards to https:// then it can lose
> the data for the submission.
Interesting idea. But I don't
it probably be in some DB for which there
was never any compelling need.
Ch.
-Original Message-
From: Mark Sapiro
Sent: Wednesday, 5 July 2023 22:39
To: mailman-users@python.org
Subject: [Mailman-Users] Re: Mailman 2.1.15 doesn't allow admin changes on
private lists
On 7/5/23 1:27 AM
doesn't allow admin changes on
private lists
On 7/5/23 7:51 PM, Charles Buckley wrote:
>
> Heck, if I knew where the footer data was stored, I'd be happy to go in and
> edit the file by hand, the web page be damned. I just want to get this
> delivered and out of the way. Watch
Mark Sapiro writes:
> Actually, the first 2.1 release was in December, 2002. See
> https://wiki.list.org/DOC/7%20Mailman%20history
You would
You have to admit the early 2.1 release history is extremely
confusing. I'm pretty sure I chose the tag that was exactly "2.1".
On 7/5/23 7:51 PM, Charles Buckley wrote:
Heck, if I knew where the footer data was stored, I'd be happy to go in and
edit the file by hand, the web page be damned. I just want to get this
delivered and out of the way. Watch it probably be in some DB for which there
was never any
Subject: [Mailman-Users] Re: Mailman 2.1.15 doesn't allow admin changes on
private lists
On 7/5/2023 12:54 PM, Charles Buckley wrote:
> My server is one of those shared servers, to which I do not have shell
> access. Mailman would have to be reinstalled by the sysadmins -- I
> can't do i
this
delivered and out of the way. Watch it probably be in some DB for which there
was never any compelling need.
Ch.
-Original Message-
From: Mark Sapiro
Sent: Wednesday, 5 July 2023 22:39
To: mailman-users@python.org
Subject: [Mailman-Users] Re: Mailman 2.1.15 doesn't allow admin changes
Stephen J. Turnbull wrote:
> Charles Buckley writes:
> > I saw a report of this behaviour on this mailing list from the year
> > 2000.
> If you have an URL for this post, or a timestamp, or even a precise
> date, it might be helpful. I can't find it.
It's
On 7/5/2023 12:54 PM, Charles Buckley wrote:
My server is one of those shared servers, to which I do not have shell
access. Mailman would have to be reinstalled by the sysadmins -- I
can't do it. I have involved them, but they're still coming up to
speed.
That in itself is a trifle worrying--
On 7/5/23 1:27 AM, Charles Buckley wrote:
I experimented with this a bit, and found that I could eliminate the footer on
my public (browsable) list on the same server. So I tried converting my other
private (non-browsable) list to be browsable, at which point I could eliminate
the footer,
Hello,
Thanks for answering.
If the first private list I could successfully change by making it non-private
also behaved as the 'recalcitrant list' before I did so, then I would suggest
that it's a mailman issue.
My server is one of those shared servers, to which I do not have shell
On 7/5/2023 1:27 AM, Charles Buckley wrote:
Any advice would be appreciated.
My first advice would be to upgrade to the current 2.1 mailman (.39?) and
try it again; 2.15 is -really- old and this behavior may be due to a bug
that's been fixed.
z!
14 matches
Mail list logo
