ietf-tools / mailarchive

IETF Mail List Archives
https://mailarchive.ietf.org
BSD 3-Clause "New" or "Revised" License
38 stars 24 forks source link

https://mailarchive.ietf.org/arch/msg/asdf/2R9GMtILTjMhaiCk7mUPoPZEe_w/ reached me with Archived-At: <https://mailarchive.ietf.org/arch/msg/asdf/6QZdZAZQ2mvqHq8VTLbJLoRTZyE> #3760

Closed cabo closed 1 month ago

cabo commented 1 month ago

And the latter doesn't seem to exist.

cabo commented 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.

cabo commented 1 month ago

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.

cabo commented 1 month ago

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>
cabo commented 1 month ago

... but not on May 8:

Archived-At: 
 <https://mailarchive.ietf.org/arch/msg/asdf/zrrAI_L4AXj3KXRBjOdkgeNgeek>

(correct).

cabo commented 1 month ago

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

rpcross commented 1 month ago

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.

cabo commented 1 month ago

Thanks! What is the release process here?

rpcross commented 1 month ago

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.

cabo commented 1 month ago

Perfect. Thank you!