当 Gmail 以编程方式用作 POP3 服务器时,它会表现出哪些非标准行为特征?
我正在尝试准备一份完整的 Gmail POP3 行为列表,您通常不会想到在 POP3 服务器中会发现这些行为。
例如,Gmail 似乎会忽略来自 POP3 客户端的 DELE(删除)命令。相反,它实施自己的删除和归档策略。
准备列表的目的是避免开发人员针对 Gmail POP3 服务器测试 POP3 客户端,然后假设所有 POP3 服务器的行为方式相同。
谁能提供更完整的非标准行为列表?
I am trying to prepare a complete list of behaviour that Gmail POP3 exhibits, that you wouldn’t expect to generally find in a POP3 server.
For example, Gmail appears to ignore the DELE (delete) command from a POP3 client. Instead, it implements its own delete and archive strategy.
The purpose of preparing a list is to avoid developers testing a POP3 client against the Gmail POP3 server and then assuming that all POP3 servers behave in the same way.
Can anyone provide a more complete list of non-standard behaviour?
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(1)
我无法提供完整的列表,但我可以提供我所知道的信息:
更准确地说:我发现只有 RETR 命令才会发生这种情况。不是 TOP 命令。我还注意到,如果在发出 RETR 命令后未发送 QUIT 命令,则消息将保留在服务器上以供以后的会话使用。因此,可以获取消息并关闭连接,并且 gmail 将使消息在下一个会话中保持可见。
这是我所知道的有关 gmail pop3 服务的唯一非标准行为。这些信息大部分是我在作为 OpenPop.NET 的开发人员时收集的。
可能有用的参考:
I cannot come with a complete list, but I can come with what I know of:
To be more precise: I found out that this happens with the RETR command only. Not the TOP command. I also noticed that if the QUIT command is not sent after issuing RETR commands, the messages are kept on the server for later sessions. It is therefore possible to fetch the messages and just close the connection, and gmail will keep the messages visible for the next session.
Those are the only non-standard behaviour I know about the gmail pop3 service. Most of this information I have gathered while being a developer for OpenPop.NET.
References that might be of use: