-
Notifications
You must be signed in to change notification settings - Fork 110
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
发送给 gmail.com的时候,会失败! #46
Comments
怎么复现呢,我发给我自己的gmail邮箱是正常的呢 |
我就是下载的发布版程序, 运行在服务器上( centos-7.9.2009 ), 没有绑定域名, IP访问的. |
https://github.com/Jinnrry/PMail/releases/tag/v2.3.3 试下这个版本呢,这里面我加了MessageId |
还是一样的.,这是日志,
|
https://github.com/Jinnrry/PMail/releases/tag/v2.3.3 我加了个日志,再帮忙试一下呢 |
日志来了
|
我看到他们是这样子格式的 腾讯的: |
官方说明是这样子, 示例应该是 :user@example.com 的格式把.
|
The message identifier (msg-id) itself MUST be a globally unique identifier for a message. The generator of the message identifier MUST guarantee that the msg-id is unique. There are several algorithms that can be used to accomplish this. Since the msg-id has a similar syntax to addr-spec (identical except that quoted strings, comments, and folding white space are not allowed), a good method is to put the domain name (or a domain literal IP address) of the host on which the message identifier was created on the right-hand side of the "@" (since domain names and IP addresses are normally unique), and put a combination of the current absolute date and time along with some other currently unique (perhaps sequential) identifier available on the system (for example, a process id number) on the left-hand side. Though other algorithms will work, it is RECOMMENDED that the right-hand side contain some domain identifier (either of the host itself or otherwise) such that the generator of the message identifier can guarantee the uniqueness of the left-hand side within the scope of that domain. 嗯,RFC是这样描述的,我又改了一版,你再试试呢 |
日志来了
|
没问题了,SPF和DKIM报错是你域名配置有问题。这两个都需要你设置域名的解析记录 |
嗯,应该是可以了,我是用的IP,没配置域名,
|
被占用的时候 |
嗯,谢谢啦 |
,QQ接收是正常的,
但是gmail会有如下错误:
The text was updated successfully, but these errors were encountered: