blocks|key|1782617|text|我刚刚对此做了一些测试，它看起来是可能的，实际上也很容易。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1782618|我使用了Mail.php扩展来实现这一点(不过，这并不重要)。我在发送消息之前添加了一个额外的报头("Trevor“=>+"My+Test")。我在Gmail中收到了这条消息，并做了一个"Show+Original“，它包含了标题。|1782619|然后我拉下这条消息(也是通过PHP)，标题包含我输入的自定义行。|1782620|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

I just did a little testing on this, and it looks possible and actually pretty easy.

I used the Mail.php extension to make this happen (shouldn't matter, though). I added an extra header before I sent the message ("Trevor" => "My Test"). I received the message in Gmail and did a "Show Original" and it contains the header.

I then pulled this message down (also via PHP) and the header contains the custom line I entered.

blocks|key|860232|text|通常，MTA将保留您引入的任何邮件标头。中继MTA是+to+do+so|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|860233|如6.4节所述，中继|860234|不需要检查消息数据的报头部分或正文，也不能这样做，除非添加它自己的"Received:“报头字段(4.4节)，并且可选地尝试检测邮件系统中的循环(参见第6.3节)。当然，此禁令也适用于对这些标题字段或文本的任何修改(另请参见第7.9节)。|blockquote|860235|860236|860237|并且一般而言，接收MTA还将仅添加与消息接收、垃圾邮件检查、循环检测等相关的其它报头。所以，是的，无论您使用哪个目标SMTP服务器，GMail或其他方式，您几乎肯定会是安全的。|860238|如果ID确实是唯一的，那么您可能需要考虑将它们用作your+Message-ID+header+value的一部分。使用Message-ID实现此目的好处在于，当用户回复您的邮件时，他们通常会在其In-Reply-To和/或References标头中包含Message-ID值：|style|CODE|860239|860240|+"+message+-ID:“字段提供引用特定消息的特定版本的唯一消息标识符。消息标识符的唯一性由生成它的主机保证(见下文)。此消息标识符旨在是机器可读的，并且不一定对人类有意义。消息标识符恰好属于特定消息的一个版本；消息的后续修订每一个都接收新的消息标识符。|860241|860242|"In-+reply+-+to+:“和"References:”字段在创建对消息的回复时使用。它们保存原始消息的消息标识符和其他消息的消息标识符(例如，在回复本身是回复的消息的情况下)。"In-+reply+-+to+:“字段可用于标识新消息作为答复的消息(或多个消息)，而"References:”字段可用于标识对话的“主题”。|860243|entityMap|0|LINK|mutability|MUTABLE|url|https://www.rfc-editor.org/rfc/rfc5321#section-3.6.3|1|https://www.rfc-editor.org/rfc/rfc5322#section-3.6.4^0|Q|9|0|0|0|0|0|0|0|U|A|1O|A|2Q|B|34|A|3J|A|P|S|1|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|16|8|@]|9|@$A|17|B|18|1|19]]|C|$]]|$1|D|3|E|5|6|7|1A|8|@]|9|@]|C|$]]|$1|F|3|G|5|H|7|1B|8|@]|9|@]|C|$]]|$1|I|3|-4|5|6|7|1C|8|@]|9|@]|C|$]]|$1|J|3|-4|5|6|7|1D|8|@]|9|@]|C|$]]|$1|K|3|L|5|6|7|1E|8|@]|9|@]|C|$]]|$1|M|3|N|5|6|7|1F|8|@$A|1G|B|1H|O|P]|$A|1I|B|1J|O|P]|$A|1K|B|1L|O|P]|$A|1M|B|1N|O|P]|$A|1O|B|1P|O|P]]|9|@$A|1Q|B|1R|1|1S]]|C|$]]|$1|Q|3|-4|5|6|7|1T|8|@]|9|@]|C|$]]|$1|R|3|S|5|H|7|1U|8|@]|9|@]|C|$]]|$1|T|3|-4|5|6|7|1V|8|@]|9|@]|C|$]]|$1|U|3|V|5|6|7|1W|8|@]|9|@]|C|$]]|$1|W|3|-4|5|6|7|1X|8|@]|9|@]|C|$]]]|X|$Y|$5|Z|10|11|C|$12|13]]|14|$5|Z|10|11|C|$12|15]]]]

In general, MTAs will preserve whatever message headers you introduce. Relaying MTAs are <a href="https://www.rfc-editor.org/rfc/rfc5321#section-3.6.3" rel="nofollow noreferrer">required to do so</a>:
<blockquote>
As discussed in Section 6.4, a relay SMTP has no need to inspect or
act upon the header section or body of the message data and MUST NOT
do so except to add its own &quot;Received:&quot; header field (Section 4.4)
and, optionally, to attempt to detect looping in the mail system (see
Section 6.3). Of course, this prohibition also applies to any
modifications of these header fields or text (see also Section 7.9).
</blockquote>
And in general the receiving MTA will also just add further headers related to message receipt, spam checking, loop detection, and the like. So yes, you're almost certainly going to be safe regardless of which destination SMTP server you use, GMail or otherwise.
If the IDs truly are unique, you may want to consider using them as part of <a href="https://www.rfc-editor.org/rfc/rfc5322#section-3.6.4" rel="nofollow noreferrer">your <code>Message-ID</code> header value</a>. The benefit of using <code>Message-ID</code> for this purpose is that when users reply to your message, they will generally include that <code>Message-ID</code> value in their <code>In-Reply-To</code> and/or <code>References</code> header:
<blockquote>
The &quot;Message-ID:&quot; field provides a unique message identifier that
refers to a particular version of a particular message. The
uniqueness of the message identifier is guaranteed by the host that
generates it (see below). This message identifier is intended to be
machine readable and not necessarily meaningful to humans. A message
identifier pertains to exactly one version of a particular message;
subsequent revisions to the message each receive new message
identifiers.
The &quot;In-Reply-To:&quot; and &quot;References:&quot; fields are used when creating a
reply to a message. They hold the message identifier of the original
message and the message identifiers of other messages (for example,
in the case of a reply to a message that was itself a reply). The
&quot;In-Reply-To:&quot; field may be used to identify the message (or
messages) to which the new message is a reply, while the
&quot;References:&quot; field may be used to identify a &quot;thread&quot; of
conversation.
</blockquote>

good day! 
sorry for so "clear" question, let me explain. In my "program", i'm sending some emails, through (for example) gmail SMTP server. Let's pretend that every email, which i've sent, contains some unique ID (generated by me) in header. Is there any chance, after retrieving that messages from gmail (for example, with python imaplib), i will get that unique ID (in header) again? thanks

send message through SMTP with guarantee ID

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

日安！很抱歉问了这么清楚的问题，让我解释一下。在我的“程序”中，我正在通过(例如) gmail SMTP服务器发送一些电子邮件。让我们假设我发送的每一封电子邮件在标题中都包含一些唯一的ID (由我生成)。有没有可能，在从gmail (例如，使用python imaplib)检索到该消息后，我会再次获得该唯一ID (在h...

问使用保修ID通过SMTP发送消息
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问使用保修ID通过SMTP发送消息EN