电子邮件线程中自定义标头的持久性 [英] Persistence of custom headers within an email thread

问题描述

我可能是一个奇怪的问题，但我以为我会去问问。说，我通过特殊的客户端发送电子邮件，使用 IMAP SMTP。该客户端在发送邮件之前，将一些自定义标头添加到电子邮件中。收件人收到这封电子邮件并直接回复（也可能是CC的几个人）。

I this is probably a strange question, but I thought I'd go ahead and ask. Say, I send an email, using IMAP SMTP, through a special client. This client adds a few custom headers to the email message before sending it on its way. The recipient receives this email and responds to me directly (and maybe CC's a few people as well).

我的问题是：给出上面的例子，头衔在线程内的所有新消息中都会持续存在？

My question is this: Given the above example, would these X-headers persist throughout all the new messages within the thread?

我可以想到的一件事是客户端会发现它发送的原始电子邮件。对此电子邮件的所有后续响应将具有回复标题，其值等于之前的电子邮件的消息标识。我不明白为什么我无法抓取这些线程的回复，直到我得到客户端发送的原始消息，从而导出原始的自定义标题。

One thing I can think of is the client would be aware of the original email message it sent. All subsequent responses to this email would have a "Reply-To" header whose value equals the "Message-Id" of the previous email. I don't see why I couldn't crawl up these thread of replies until I get to the original message sent by the client, thereby deriving the original custom headers.

也许我过分的想这个。有什么建议么？ ：）

Maybe I'm over-thinking this. Any suggestions? :)

推荐答案

消息回复不一定包含任何原始消息。 MUA很可能会建议修改（例如，添加Re：）版本的原始主题，显然地址也被用于适当的默认值。消息的其他内容都不构成回复的一部分（除非发件人故意包含它，如引用或转发）。您的邮件中的任何X标题一定不会包含在回复中（除非您对该MUA有所控制）。

A message reply does not necessarily contain anything of the original message. The MUA is likely to suggest a modified (e.g. prepended with "Re:") version of the original subject, and obviously the addresses are utilised for appropriate defaults as well. None of the other content of the message forms part of the reply (unless the sender deliberately includes it, as with quoting or forwarding). Any X- headers that you have in your message will certainly not be included in the reply (unless you have control over that MUA).

但是，您的跟踪计划原始信息当然可行：参见 RFC 5322 第3.6.4节。每个消息应该（不一定）有一个Message-ID标题，并且在适当的时候应该有In-Reply-To和References标头。

However, your plan of tracking the original message is certainly feasible: see Section 3.6.4 of RFC 5322. Every message should (not must) have a Message-ID header, and should have In-Reply-To and References headers when appropriate.

Message-ID：字段包含一个唯一的消息标识符。 参考文献：和应答到：字段各自包含一个或多个唯一消息标识符，可选地由[空格]分隔。

The "Message-ID:" field contains a single unique message identifier. The "References:" and "In-Reply-To:" fields each contain one or more unique message identifiers, optionally separated by [whitespace].

In-Reply-To是提及识别正被回覆的消息（或消息），而引用标识整个会话线程。参考标题旨在包含要回复的消息的引用标题的全部内容，因此您只需要最后一条消息来标识整个线程。

In-Reply-To is mention to identify the message (or messages) that is (are) being replied to, while References identifies the entire thread of conversation. The References header is meant to contain the entire contents of the References header of the message being replied to, so you only need the last message to identify the entire thread.

注意 In-Reply-To 和 Reply-To 不一样（后者指定发件人希望回复的地址发送到）。

Note that In-Reply-To and Reply-To are not the same thing (the latter specifies the address that the sender wishes replies to be sent to).

假设您有原始邮件，那么您应该可以使用任何回复的References标头来标识原始邮件。不是每个MUA都将正确地处理参考文献或In-Reply-To，但大多数将会。

Assuming that you have the original message, then you should be able to use the References header of any reply to identify the original message. Not every MUA will handle References or In-Reply-To correctly, but most will.

这篇关于电子邮件线程中自定义标头的持久性的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！