Hi,
On Tue, 07 Dec 2021, Paul Wise wrote:
> Not necessarily, there are several options for this that would make it
> a very generic feature, some ideas:
>
> When the List-Archive header exists and contains a URL, the link could
> be to that URL. This works for Debian lists and mailman lists and
> probably other types of lists too.
The tracker doesn't receive emails via mailing lists, it gets sent a
direct copy from the various services.
> distro-tracker could have a list of domains that are known to have
> Message-ID search URLs and then map the List-Id to those URLs.
What's the "domain" of an email message? The one from the sender?
> For domains that have no Message-ID search URLs but do have archive
> links for the Maintainer field, the link could be to just the top-level
> archive link used for the Maintainer field.
I don't see how this can be helpful if you have to look up the message on
your own.
> Once #1001254 is implemented, then the link could be to the DPT
> Message-ID search, in a similar way to how lists.d.o links to its
> Message-ID search from the Message-ID field in its archives.
This, however, is something that is clearly more in line with the logic
of distro tracker. I agree that a query to lookup a message-id could be
useful.
(And actually I am interested in tracking message-id of everything that
went through distro-tracker to be able to drop duplicates easily and/or
present other summary views to the respective maintainers)
> I think the options I presented above are generic enough to have a low
> enough cost. For cases not covered by them I think as a compromise, it
> would be reasonable to just show the Message-ID header with no link.
This is also reasonable, indeed.
Cheers,
--
⢀⣴⠾⠻⢶⣦⠀ Raphaël Hertzog
⣾⠁⢠⠒⠀⣿⡁
⢿⡄⠘⠷⠚⠋The Debian Handbook: https://debian-handbook.info/get/
⠈⠳⣄ Debian Long Term Support: https://deb.li/LTS
signature.asc
Description: PGP signature