Closed cabo closed 1 month ago
Similar: message https://mailarchive.ietf.org/arch/msg/asdf/cJr6-Q9YhgMXxqO_FMKkYGT8Jro/ arrived with header Archived-At: https://mailarchive.ietf.org/arch/msg/asdf/X0WEL1e0ahmQluvpwCGdr-etE8c ...which again doesn't seem to exist.
Downloading the message from https://mailarchive.ietf.org/arch/msg/asdf/cJr6-Q9YhgMXxqO_FMKkYGT8Jro/ yields an .eml file with this header line:
Archived-At:
<https://mailarchive.ietf.org/arch/msg/asdf/X0WEL1e0ahmQluvpwCGdr-etE8c>
Note the conspicuous (DOS) newline.
I'm currently only seeing this in ASDF.
also for older messages (May 09): https://mailarchive.ietf.org/arch/msg/asdf/H-9qtENeHsr_OaULc7HqKcsXboY/
Archived-At:
<https://mailarchive.ietf.org/arch/msg/asdf/1ljYZFOzz6P6G4PqRu7Z8rmgwms>
... but not on May 8:
Archived-At:
<https://mailarchive.ietf.org/arch/msg/asdf/zrrAI_L4AXj3KXRBjOdkgeNgeek>
(correct).
MPLS, too:
https://mailarchive.ietf.org/arch/msg/mpls/e50u7U7jPTGVVxD8HHnGWgqJOwA/
Archived-At:
<https://mailarchive.ietf.org/arch/msg/mpls/o_IdAlk7DoGkti_mT0wDytlVop8>
Random observation: The bad ones get download file names such as "mpls_ BL3P.eml" "asdf _PAXP.eml" while the good ones get asdf_171520.eml rswg_40F0A1.eml
This issue is caused by the archive not properly handling the leading whitespace in the Message-ID header when calculating the Archived-At header. A fix is being made.
Thanks! What is the release process here?
The fix is included in Release v2.24.0 which is deployed now. The messages in question will now be found at the address in the Archive-At header.
Perfect. Thank you!
And the latter doesn't seem to exist.