Closed Bug 277225 Opened 20 years ago Closed 19 years ago

Mailman links to nonexistant mailing list archives

Categories

(mozilla.org Graveyard :: Server Operations: Projects, task, P3)

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: justdave, Assigned: justdave)

References

Details

We just had a post on mozilla-webtools pointing out that the archives link on
the mailman listinfo pages for the mailing lists goes to the internal archives
in Mailman which were disabled shortly after we set it up because the archiving
was all done by the news server.  We need to find a way to modify the archives
links to point at the news archive instead on the affected lists.
Certainly in my version of mailman (2.1.4) there is an option on the list admin 
page to "Edit the Public HTML Pages". On the next screen, there is an option 
labelled "General list information page" where you can edit the archive link. 
You would need to do this individually for each list, though. 
Cool, that was easy. :)

mozilla-webtools is fixed.  I actually don't have admin access to any other
public lists though.
I have admin access for all of MailMan now.  I can take care of this eventually.
Priority: -- → P3
Dave: is this still worth doing, considering our upcoming server change?

Gerv
(In reply to comment #4)
> Dave: is this still worth doing, considering our upcoming server change?

Yes and no. :)  We're going to have to create all of these pages for all of the
new mailing lists anyway as we set them up on the new server.  Let's just set
them up right while we're at it. :)
Assignee: justdave → justdave
Component: Server Operations → Server Operations Projects
QA for this component is now Justin
QA Contact: myk → justin
Depends on: mailman21
Mailman on lists.mozilla.org has been hacked to supply a URL to Google Groups for the <MM-Archive-URL> replacement tag in the templates for lists that are gatewayed to a newsgroup.
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.