我正在使用较旧的电子邮件客户端（编辑：尤多拉7.1.0.9 在 Windows 上），似乎无法通过 Gmail 的 SMTP 服务器发送电子邮件，即使降低了每个本文。
因此，我尝试在电子邮件客户端和 Gmail 之间添加 stunnel，但仍然失败并显示相同的错误消息，告诉我阅读以下 URL 中的文章： https://support.google.com/mail/answer/14257
这是 stunnel.conf 文件：
output = stunnel.log
debug = debug
engine = capi
cert = stunnel.pem
options = NO_SSLv2
[gmail-smtp]
client = yes
accept = 127.0.0.1:25
connect = smtp.gmail.com:465
这是来自 stunnel 的日志：
2014.09.12 13:29:09 LOG7[6896]: Service [gmail-smtp] accepted (FD=440) from 127.0.0.1:56142
2014.09.12 13:29:09 LOG7[6896]: Creating a new thread
2014.09.12 13:29:09 LOG7[6896]: New thread created
2014.09.12 13:29:09 LOG7[6516]: Service [gmail-smtp] started
2014.09.12 13:29:09 LOG5[6516]: Service [gmail-smtp] accepted connection from 127.0.0.1:56142
2014.09.12 13:29:09 LOG6[6516]: s_connect: connecting 173.194.66.109:465
2014.09.12 13:29:09 LOG7[6516]: s_connect: s_poll_wait 173.194.66.109:465: waiting 10 seconds
2014.09.12 13:29:09 LOG5[6516]: s_connect: connected 173.194.66.109:465
2014.09.12 13:29:09 LOG5[6516]: Service [gmail-smtp] connected remote server from 192.168.0.12:56143
2014.09.12 13:29:09 LOG7[6516]: Remote socket (FD=524) initialized
2014.09.12 13:29:09 LOG6[6516]: SNI: sending servername: smtp.gmail.com
2014.09.12 13:29:09 LOG7[6516]: SSL state (connect): before/connect initialization
2014.09.12 13:29:09 LOG7[6516]: SSL state (connect): SSLv3 write client hello A
2014.09.12 13:29:09 LOG7[6516]: SSL state (connect): SSLv3 read server hello A
2014.09.12 13:29:09 LOG7[6516]: SSL state (connect): SSLv3 read finished A
2014.09.12 13:29:09 LOG7[6516]: SSL state (connect): SSLv3 write change cipher spec A
2014.09.12 13:29:09 LOG7[6516]: SSL state (connect): SSLv3 write finished A
2014.09.12 13:29:09 LOG7[6516]: SSL state (connect): SSLv3 flush data
2014.09.12 13:29:09 LOG7[6516]: 1 items in the session cache
2014.09.12 13:29:09 LOG7[6516]: 4 client connects (SSL_connect())
2014.09.12 13:29:09 LOG7[6516]: 4 client connects that finished
2014.09.12 13:29:09 LOG7[6516]: 0 client renegotiations requested
2014.09.12 13:29:09 LOG7[6516]: 0 server connects (SSL_accept())
2014.09.12 13:29:09 LOG7[6516]: 0 server connects that finished
2014.09.12 13:29:09 LOG7[6516]: 0 server renegotiations requested
2014.09.12 13:29:09 LOG7[6516]: 3 session cache hits
2014.09.12 13:29:09 LOG7[6516]: 0 external session cache hits
2014.09.12 13:29:09 LOG7[6516]: 0 session cache misses
2014.09.12 13:29:09 LOG7[6516]: 0 session cache timeouts
2014.09.12 13:29:09 LOG6[6516]: SSL connected: previous session reused
2014.09.12 13:29:13 LOG6[6516]: SSL socket closed (SSL_read)
2014.09.12 13:29:13 LOG7[6516]: Sent socket write shutdown
2014.09.12 13:29:13 LOG5[6516]: Connection closed: 100 byte(s) sent to SSL, 702 byte(s) sent to socket
2014.09.12 13:29:13 LOG7[6516]: Remote socket (FD=524) closed
2014.09.12 13:29:13 LOG7[6516]: Local socket (FD=440) closed
2014.09.12 13:29:13 LOG7[6516]: Service [gmail-smtp] finished (0 left)
2014.09.12 13:29:13 LOG7[6516]: str_stats: 3 block(s), 4294963962 data byte(s), 150 control byte(s)
2014.09.12 13:29:13 LOG7[6516]: str_stats: 20 byte(s) at ..\src\network.c:413
2014.09.12 13:29:13 LOG7[6516]: str_stats: 20 byte(s) at ..\src\network.c:412
2014.09.12 13:29:13 LOG7[6516]: str_stats: 20 byte(s) at ..\src\network.c:411
有任何来自 stunnel 或 SSL 专家的提示吗？
谢谢。
答案1
我使用几乎相同的 stunnel 配置从旧电子邮件客户端向 Gmail 发送电子邮件。它可以正常工作，但我不得不将我的电子邮件地址从 更改为 ，[email protected]因为我的旧电子邮件客户端发送的地址格式不符合 Gmail 的接受格式。也许您遇到了类似的问题。<[email protected]>
获取数据包转储的一种方法是使用Microsoft 网络监视器。
使用该工具（或类似的数据包捕获工具），您应该能够将 Eudora 发送的内容与另一个（成功的）电子邮件客户端发送的内容进行比较，然后调整 Eudora 以发送另一个客户端发送的内容。这就是我解决类似问题的方法。