在发送电子邮件时,Gmail API会覆盖自定义的Message-ID标头 [英] Gmail API is overwriting the custom Message-ID header while sending emails

查看:148
本文介绍了在发送电子邮件时,Gmail API会覆盖自定义的Message-ID标头的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我们正在使用Gmail API代表我们应用程序的用户发送电子邮件.在通过Gmail API发送的电子邮件的标题上,我们正在设置自定义的Message-ID.

We are using the Gmail API to send emails on behalf of the users of our App. On the header of the emails we send via the Gmail API, we are setting a custom Message-ID.

尽管如此,Gmail仍会覆盖我们使用其他ID设置的Message-ID.以下是我们尝试过的一些Message-ID:

Nevertheless Gmail is overwriting the Message-ID we set with a different one . The following are some Message-IDs that we have tried:

< 8368110f-6ffc-46f8-8e67-7ebf0e1a1d83 @ domain>

<8368110f-6ffc-46f8-8e67-7ebf0e1a1d83@domain>

< 4fb7a8b7013099c524f70906e009b46218461fff0b2dc0f8b794eb2df26e93d7 @ domain>

<4fb7a8b7013099c524f70906e009b46218461fff0b2dc0f8b794eb2df26e93d7@domain>

您知道为什么会发生此ID覆盖吗?

Any idea why this ID overwriting is happening ?

我将非常感谢您的帮助

预先感谢

推荐答案

您可以在'@'左侧之前使用.(点)尝试自定义ID. 它为我工作.

You can try custom id with .(dot) before left side of '@'. It worked for me.

有关更多详细信息,请参考以下RFC.这些对于创建自定义message-id的语法确实很有帮助.

For more details, Please refer the following RFC's. These are really helpful for creating syntax for Custom message-id.

1) RFC 2822
2) RFC 5322

1) RFC 2822
2) RFC 5322

希望这对您也有用.

这篇关于在发送电子邮件时,Gmail API会覆盖自定义的Message-ID标头的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆