the "Mailing list discussion" link for rfcs is incorrect

[rjsparks]

The generated link into the mailarchive uses &q= where it should use /q=. The query should also look for both references to the rfc name and the name of the draft the rfc came from.

[elear]

Just a comment of no particular significance. I realize it's your namespace, but is that meant to be a query, but yet doesn't quite look like one? Would it make sense to add &q= into the mailarchive?

[jennifer-richards]

I think it's currently generating .../?email_list=<acro>?q=<docname> but should be.../?email_list=<acro>&q=<docname>

[jennifer-richards]

(i.e., what @elear asks for seems to be supported by mailarchive)

[rjsparks]

This is a data cleaning / code robustness issue:

datatracker/ietf/templates/doc/document_info.html

Line 434 in 50aa399

<a href="{{ doc.group.list_archive }}?q={{ doc.name }}">

and

>>> Group.objects.filter(list_archive__endswith="/").count()
383
>>> Group.objects.exclude(list_archive="").exclude(list_archive__endswith="/").count()
334

[rjsparks]

And I typo-ed in the original post, stimulating an unnecessary conversation - apologies.

[rjsparks]

Yet redirects at mailarchive are handling those differences already. Attempting to rediscover the document that motivated this issue.

[rjsparks]

Relocated - the issue is at /doc/rfc5280/ which links to https://mailarchive.ietf.org/arch/search/?email_list=pkix?q=rfc5280 because

>>> Group.objects.get(acronym='pkix').list_archive
'https://mailarchive.ietf.org/arch/search/?email_list=pkix'

Further:

>>> Group.objects.filter(list_archive__contains="?email_list").count()
165

We should transform those to use the shorter version of /arch/browse/<acronym>