Sean Whitton writes ("Bug#1127618: tag2upload web pages should link to email
reports"):
> Ian Jackson [10/Feb 3:24pm GMT] wrote:
...
> > 2a. The Manager could generate a Message-ID for the user report, and
> > tell it to the Oracle via the o2m protocol.
..
> > 3. The Oracle email-generation code could explicitly generate and set
> > a Message-ID for every message and, for the case of the to-user
> > final email, report that to the Manager.
> >
> > I think I would like to do 2a or 3.
...
> (2a) seems slightly cleaner for future debugging because then msgid
> generation always happens on the Manager, instead of possibly happening
> in two places?
Usual email practice is for any system that generates an email to
generate its own Message-ID. We have two places that generate the
emails (this shared responsibility being a consequence of our
privsep). They currently generate their own Message-IDs (leaving it
to the MTA). So I'm not sure I agree that (2a) is cleaner than (3).
> I guess for (3) we could include the message-id as a new field in the
> existing 'email reported' line of the protocol.
Right. I think whichever way we do it, the necessary protocol change
will be small and obvious.
Ian.
--
Ian Jackson <[email protected]> These opinions are my own.
Pronouns: they/he. If I emailed you from @fyvzl.net or @evade.org.uk,
that is a private address which bypasses my fierce spamfilter.
