当前位置: 首页 > news >正文

Java Mail腾讯企业邮箱或其他邮箱发送邮件失败bug记录

问题出现情况

  邮件发送时debug用F8逐步运行可以成功发送邮件,但是用F9或者直接运行程序却发送失败未开启mail的debug模式的报错日志是下面这个:
org.springframework.mail.MailAuthenticationException: Authentication failed; nested exception is javax.mail.AuthenticationFailedException: [EOF]at org.springframework.mail.javamail.JavaMailSenderImpl.doSend(JavaMailSenderImpl.java:440)at org.springframework.mail.javamail.JavaMailSenderImpl.send(JavaMailSenderImpl.java:361)at org.springframework.mail.javamail.JavaMailSenderImpl.send(JavaMailSenderImpl.java:356)
  开启了mail的debug日志,然后之前忘了添加超时设置,后续添加了下面超时设置
spring:#JavaMailSendermail:host: smtp.exmail.qq.comport: 587username: xxx@xxx.compassword: xxxdefault-encoding: UTF-8properties:mail.smtp.starttls.enable: truemail.smtp.timeout: 5000 # 设置连接超时(毫秒)后面加的mail.smtp.connectiontimeout: 5000 # 设置连接超时(毫秒)后面加的mail.smtp.writetimeout: 5000 # 设置写入超时(毫秒)后面加的
  之后发现是卡在了权限验证AUTH LOGIN,然后无法进行下一步,直到超时,日志如下:
DEBUG SMTP: exception reading response, THROW: 
java.net.SocketTimeoutException: Read timed outat java.net.SocketInputStream.socketRead0(Native Method)at java.net.SocketInputStream.socketRead(SocketInputStream.java:116)at java.net.SocketInputStream.read(SocketInputStream.java:171)at java.net.SocketInputStream.read(SocketInputStream.java:141)at sun.security.ssl.SSLSocketInputRecord.read(SSLSocketInputRecord.java:475)at sun.security.ssl.SSLSocketInputRecord.readHeader(SSLSocketInputRecord.java:469)at sun.security.ssl.SSLSocketInputRecord.bytesInCompletePacket(SSLSocketInputRecord.java:69)at sun.security.ssl.SSLSocketImpl.readApplicationRecord(SSLSocketImpl.java:1271)at sun.security.ssl.SSLSocketImpl.access$300(SSLSocketImpl.java:76)at sun.security.ssl.SSLSocketImpl$AppInputStream.read(SSLSocketImpl.java:948)at com.sun.mail.util.TraceInputStream.read(TraceInputStream.java:126)at java.io.BufferedInputStream.fill(BufferedInputStream.java:246)at java.io.BufferedInputStream.read(BufferedInputStream.java:265)at com.sun.mail.util.LineInputStream.readLine(LineInputStream.java:106)at com.sun.mail.smtp.SMTPTransport.readServerResponse(SMTPTransport.java:2440)at com.sun.mail.smtp.SMTPTransport.ehlo(SMTPTransport.java:1699)at com.sun.mail.smtp.SMTPTransport.protocolConnect(SMTPTransport.java:759)at javax.mail.Service.connect(Service.java:366)at org.springframework.mail.javamail.JavaMailSenderImpl.connectTransport(JavaMailSenderImpl.java:518)at org.springframework.mail.javamail.JavaMailSenderImpl.doSend(JavaMailSenderImpl.java:437)at org.springframework.mail.javamail.JavaMailSenderImpl.send(JavaMailSenderImpl.java:361)at org.springframework.mail.javamail.JavaMailSenderImpl.send(JavaMailSenderImpl.java:356)at com.example.demo.mail.MailServiceImpl.send(MailServiceImpl.java:95)at com.example.demo.mail.MailServiceImpl.send(MailServiceImpl.java:108)at com.example.demo.schedule.MyRunner.run(MyRunner.java:20)at org.springframework.boot.SpringApplication.callRunner(SpringApplication.java:781)at org.springframework.boot.SpringApplication.callRunners(SpringApplication.java:765)at org.springframework.boot.SpringApplication.run(SpringApplication.java:319)at org.springframework.boot.SpringApplication.run(SpringApplication.java:1215)at org.springframework.boot.SpringApplication.run(SpringApplication.java:1204)

问题解决过程

  在debug过程中发现是在TLS握手时超时导致的权限验证失败,在项目启动时添加:
-Djavax.net.debug=ssl:handshake

  添加后查看日志,ServerHello返回的版本是TLSv1.2,但是指定通信的版本是TLSv1.3,成功的日志指定的也是1.3,我尝试配置指定TLS版本为v1.2后发现问题成功解决:

spring:mail:host: smtp.exmail.qq.comport: 587username: xxx@xxx.compassword: xxxdefault-encoding: UTF-8properties:mail.smtp.starttls.enable: truemail.smtp.starttls.required: truemail.smtp.ssl.protocols: TLSv1.2mail.smtp.auth: truemail.smtp.timeout: 5000 # 设置连接超时(毫秒)mail.smtp.connectiontimeout: 5000 # 设置连接超时(毫秒)mail.smtp.writetimeout: 5000 # 设置写入超时(毫秒)

  后续我通过openssl命令行执行查看server的TLS版本发现是支持v1.3的:

admin@DESKTOP-0SP0F5T MINGW64 ~/Desktop
$ openssl s_client -starttls smtp -crlf -connect smtp.exmail.qq.com:587
Connecting to 119.147.6.199
CONNECTED(00000250)
depth=2 C=US, O=DigiCert Inc, OU=www.digicert.com, CN=DigiCert Global Root CA
verify return:1
depth=1 C=US, O=DigiCert Inc, CN=DigiCert Secure Site CN CA G3
verify return:1
depth=0 C=CN, ST=Guangdong Province, L=Shenzhen, O=Tencent Technology (Shenzhen) Company Limited, CN=*.exmail.qq.com
verify return:1
...省略
No client certificate CA names sent
Peer signing digest: SHA256
Peer signature type: RSA-PSS
Server Temp Key: X25519, 253 bits
---
SSL handshake has read 3871 bytes and written 446 bytes
Verification: OK
---
New, TLSv1.3, Cipher is TLS_AES_256_GCM_SHA384
...省略
---
250 8BITMIME
---
Post-Handshake New Session Ticket arrived:
SSL-Session:Protocol  : TLSv1.3Cipher    : TLS_AES_256_GCM_SHA384
...省略

  然而通过ssl-tool在线验证却发现不支持,可自行点击超链接查看
  问了chatgpt发现也是:
在这里插入图片描述
  所以最后解决方法是指定了TLS版本

最后

  哪位大佬知道这是为什么吗,最终还是没明白问题出在了哪里,望指点


http://www.mrgr.cn/news/48494.html

相关文章:

  • MySQL的基础语法-2
  • 电商新动力:SpringBoot购物推荐网站开发详解
  • 国内首个专业领域知识增强服务框架 KAG 技术报告,助力大模型落地垂直领域
  • Apple提出MM1.5:多模态大型语言模型微调的方法、分析和见解
  • Ubuntu卸载Mysql【ubuntu 24.04/mysql 8.0.39】
  • 利用Spring Boot构建医疗病历B2B平台的优势
  • yolo5快速上手训练数据集
  • 125页满分PPT | 数据架构革新顶层规划方案
  • 弧光保护装置的应用
  • 大模型完美攻略手册(从入门到专家)精选资源集,新手入门教程!
  • 在python中如何判断回文串(二)?
  • 漏洞挖掘和渗透测试的区别是什么?(非常详细),零基础入门到精通,看这一篇就够了
  • 【华为】RIP与 BFD联动
  • 给参加AI大模型秋招和实习的同学一点建议,看完这一篇就够了
  • 后端——eclipse实现前端后端的交互(1)
  • 网络舆情如何防控与管理?小马识途分享10招
  • 构建基于 阻塞队列 / 环形队列 的高效生产消费者模型系统
  • 安卓-广播
  • 高精度定位技术综合应用与注意事项
  • 长时间蓝屏的问题解决:使用ST7567控制器的LCD液晶显示模组的软件优化