Project

General

Profile

Actions

tickets #123478

open

arbitrary old archive messages give me a 404 ?

Added by pjessen over 1 year ago. Updated about 1 year ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Mailing lists
Target version:
-
Start date:
2023-01-22
Due date:
% Done:

0%

Estimated time:

Description

I was doing some research when I noticed several old archive urls (picked at random) giving me a 404:

http://lists.opensuse.org/opensuse-bugs/2006-11/msg13161.html
http://lists.opensuse.org/blinux-de/2002-03/msg00013.html
http://lists.opensuse.org/obs-tests/2019-01/msg00116.html
http://lists.opensuse.org/opensuse-buildservice/2011-04/msg00149.html

That doesn't seem right ? I can see the redirect happening.

Actions #1

Updated by pjessen over 1 year ago

  • Private changed from Yes to No
Actions #2

Updated by pjessen over 1 year ago

pjessen wrote:

http://lists.opensuse.org/opensuse-bugs/2006-11/msg13161.html
http://lists.opensuse.org/blinux-de/2002-03/msg00013.html
http://lists.opensuse.org/obs-tests/2019-01/msg00116.html
http://lists.opensuse.org/opensuse-buildservice/2011-04/msg00149.html

The redirect is wrong:

https://lists.opensuse.org/archives/lists/buildservice@lists.opensuse.org/message/D4VI3FH7EWG7LYUJIDVXAI5O3XDD5ZVW/`
                                        ^

That 's' is wrong.
For now, I have fixed it with sed -i -e 's@/archives/lists/@/archives/list/@' mails.rewritemap

Actions #3

Updated by cboltz over 1 year ago

For the records: These redirect maps are from openSUSE:infrastructure:mailman3 nginx-rewrite-lists-openSUSE, so someone will need to update this package.

That said: I'm quite sure these redirects worked in the past (when they were set up) - which leads to the question if there was a lists -> list change in mailman.

If so, this change probably also broke "new" links to the mailman archive, and we should probably setup a general redirect for lists -> list. (Note: I checked some Archived-At headers in my mail archive, and they always had list.)

Actions #4

Updated by pjessen about 1 year ago

Unfortunately, the nginx logs only go back 30 days, so the earliest I can see is 29 December 2022, still the wrong redirect.

That said: I'm quite sure these redirects worked in the past (when they were set up) - which leads to the question if there was a lists -> list change in mailman.

Agree. It looks like the latest mailman3 was installed in December:

mailman3 (lists.o.o):/var/log/nginx # rpm -qi mailman3
Name        : mailman3
Version     : 3.3.6
Release     : 85.1
Architecture: noarch
Install Date: Fri Dec 16 17:33:42 2022

mailman3 (lists.o.o):/var/log/postorius # rpm -qi python39-mailman-hyperkitty
Name        : python39-mailman-hyperkitty
Version     : 1.2.0
Release     : 20.9
Architecture: noarch
Install Date: Fri Dec 16 17:34:05 2022
Actions

Also available in: Atom PDF