全球主机交流论坛

标题: 连接smtp发邮件会验证域名? [打印本页]
作者: wawos    时间: 2024-10-21 13:37
标题: 连接smtp发邮件会验证域名?
本帖最后由 wawos 于 2024-10-21 13:39 编辑

不是指邮件地址的域名, 这个肯定要验证的我知道,

比如smtp服务器地址是: smtp.qq.com

直接连域名+账号密码, 可以成功登录


但是改成连: smtp.qq.com的IP: 183.47.101.192 + 账号密码, 却不成功

是什么原因呢
作者: wawos    时间: 2024-10-21 13:38
smtp不是像远程桌面、SSH一样, 不具备域名验证功能的吗?

难道他也和web服务的http一样, 具有域名验证功能?
作者: sRGB    时间: 2024-10-21 13:39
你实名认证过吗，使用设备专用密码发邮件的吗
作者: iks    时间: 2024-10-21 13:39
ehlo 了解一下，，，
作者: iks    时间: 2024-10-21 13:40
wawos 发表于 2024-10-21 13:38
smtp不是像远程桌面、SSH一样, 不具备域名验证功能的吗?

难道他也和web服务的http一样, 具有域名验证功能? ...
远程桌面、SSH一样
谁告诉你的？先问是不是再问为什么，，
作者: wawos    时间: 2024-10-21 13:47
iks 发表于 2024-10-21 13:39
ehlo 了解一下，，，

ehlo后面必须要要smtp的域名吗
作者: wawos    时间: 2024-10-21 14:33
iks 发表于 2024-10-21 13:39
ehlo 了解一下，，，

胡说, 不对,  看了教程, EHLO是表明自己的身份,  后面填的是自己网站的域名

根本就不是填smtp.qq.com
作者: iks    时间: 2024-10-21 16:13
本帖最后由 iks 于 2024-10-21 16:14 编辑
wawos 发表于 2024-10-21 14:33
胡说, 不对,  看了教程, EHLO是表明自己的身份,  后面填的是自己网站的域名

根本就不是填smtp.qq.com ...


看走眼了抱歉，EHLO 确实是表明自己的身份

SMTP 只能用完全限定域名 (FQDN) 的原因是使用 SSL, TLS 或 StartTLS 的 SMTP 需要验证服务器名称

例如，尝试获得 email-smtp.us-west-1.amazonaws.com:587 的证书，执行：
# openssl s_client -connect email-smtp.us-west-1.amazonaws.com:587 -starttls smtp

可以得到：
  1. # openssl s_client -connect email-smtp.us-west-1.amazonaws.com:587 -starttls smtp
  2. CONNECTED(00000003)
  3. depth=2 C = US, O = Amazon, CN = Amazon Root CA 1
  4. verify return:1
  5. depth=1 C = US, O = Amazon, CN = Amazon RSA 2048 M01
  6. verify return:1
  7. depth=0 CN = email-smtp.us-west-1.amazonaws.com
  8. verify return:1
  9. ---
  10. Certificate chain
  11. 0 s:CN = email-smtp.us-west-1.amazonaws.com
  12.    i:C = US, O = Amazon, CN = Amazon RSA 2048 M01
  13. 1 s:C = US, O = Amazon, CN = Amazon RSA 2048 M01
  14.    i:C = US, O = Amazon, CN = Amazon Root CA 1
  15. 2 s:C = US, O = Amazon, CN = Amazon Root CA 1
  16.    i:C = US, ST = Arizona, L = Scottsdale, O = "Starfield Technologies, Inc.", CN = Starfield Services Root Certificate Authority - G2
  17. 3 s:C = US, ST = Arizona, L = Scottsdale, O = "Starfield Technologies, Inc.", CN = Starfield Services Root Certificate Authority - G2
  18.    i:C = US, O = "Starfield Technologies, Inc.", OU = Starfield Class 2 Certification Authority
  19. ---
  20. Server certificate
  21. -----BEGIN CERTIFICATE-----
  22. MIIGQjCCBSqgAwIBAgIQCaHt/BVsLHNtiqrkyyDR5zANBgkqhkiG9w0BAQsFADA8
  23. MQswCQYDVQQGEwJVUzEPMA0GA1UEChMGQW1hem9uMRwwGgYDVQQDExNBbWF6b24g
  24. UlNBIDIwNDggTTAxMB4XDTI0MDkwNDAwMDAwMFoXDTI1MDkwMzIzNTk1OVowLTEr
  25. MCkGA1UEAxMiZW1haWwtc210cC51cy13ZXN0LTEuYW1hem9uYXdzLmNvbTCCASIw
  26. DQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAKmaJ9aVXCPy8BuK8GcaWI2+uwiI
  27. Lfp1kFCtf9oTjNU6yevf3fp/vkpalix2kyBH4hAugpyCf+unTCZyLOuWatVToRr4
  28. CBu8yzDcQvwLfO00sRbe9hzf5NBuiNVLgP2x0oKFkL3RxljmutPnp00JFKLbe8ct
  29. qLNw3v8hgN0Bh4mymNky2rsQPLXhpgkiTA0ibDhQblQcWdyoZecXxAy2hTnqfqas
  30. SHqWS1xNPUpB+5CHJ7NsUz7JwnzNAYYR8i2E/x+ZP6vapcshLwDM3/Eh6FsAecZ9
  31. mnovwgsZkEPKwJqFLxFi8TLIJxg+VgZ8B1GjmJbElBwg2Wu8bixTvvQYZYMCAwEA
  32. AaOCA00wggNJMB8GA1UdIwQYMBaAFIG4DmOKiRIY5fo7O1CVn+blkBOFMB0GA1Ud
  33. DgQWBBQY257IFQMtex9fYm/npUcgwAVovzCBgQYDVR0RBHoweIInZW1haWwtc210
  34. cC1maXBzLnVzLXdlc3QtMS5hbWF6b25hd3MuY29tgikqLmVtYWlsLXNtdHAudXMt
  35. d2VzdC0xLnZwY2UuYW1hem9uYXdzLmNvbYIiZW1haWwtc210cC51cy13ZXN0LTEu
  36. YW1hem9uYXdzLmNvbTATBgNVHSAEDDAKMAgGBmeBDAECATAOBgNVHQ8BAf8EBAMC
  37. BaAwHQYDVR0lBBYwFAYIKwYBBQUHAwEGCCsGAQUFBwMCMDsGA1UdHwQ0MDIwMKAu
  38. oCyGKmh0dHA6Ly9jcmwucjJtMDEuYW1hem9udHJ1c3QuY29tL3IybTAxLmNybDB1
  39. BggrBgEFBQcBAQRpMGcwLQYIKwYBBQUHMAGGIWh0dHA6Ly9vY3NwLnIybTAxLmFt
  40. YXpvbnRydXN0LmNvbTA2BggrBgEFBQcwAoYqaHR0cDovL2NydC5yMm0wMS5hbWF6
  41. b250cnVzdC5jb20vcjJtMDEuY2VyMAwGA1UdEwEB/wQCMAAwggF7BgorBgEEAdZ5
  42. AgQCBIIBawSCAWcBZQB1AN3cyjSV1+EWBeeVMvrHn/g9HFDf2wA6FBJ2Ciysu8gq
  43. AAABkbq8Y0AAAAQDAEYwRAIgIJ3ah+QSfrN7ogIh3TF6cThNrlbHRhL8YTc9EoZN
  44. VQkCIENbP4vqCx81C7Kaf4LlvNXbAjhxQ99V5o1pRlqJDqPKAHUAfVkeEuF4Knsc
  45. YWd8Xv340IdcFKBOlZ65Ay/ZDowuebgAAAGRurxjAQAABAMARjBEAiBS8/o0JW7s
  46. rCqN6K3VjckdzBMSlQ/pxKPTw9QAJhGGyQIgfka8+F+qxfLK8C5YS7nXw4mpRtn5
  47. I6wiZdcN9pYwnYQAdQDm0jFjQHeMwRBBBtdxuc7B0kD2loSG+7qHMh39HjeOUAAA
  48. AZG6vGMbAAAEAwBGMEQCIC0/v3uCz8djCDtMMpz6I/H7mVYfSVGjoXX4SPLcTnsr
  49. AiA+DlEej6rPxGvucXdhzFC66nIQoNA4AeIuq6cffB296jANBgkqhkiG9w0BAQsF
  50. AAOCAQEAFtteDD34Btc4wTsfOQdfiSAFyxNVP6eMdvDFJwlh3n8wP80wo8761IIG
  51. de+MNhguNNJXDDxSQBSE4ZgyLU6AvjaDqC0qsAPLaz8rOsEpVWad1th4kgAuRU/S
  52. l6qbALUSD8v2nxT0mi8/RBXtsi/R36sr+XkJgbh19tRX/3HR22oe+QqXLtAatkJL
  53. 0HzWg9KXDpMPU/Dtn+**5wBw6AtwTFwcGL+eiS8Uodn0y+PvHI5i/Ax77o2aU6h
  54. OuHBeXE/yVnO/0JaTNCB/06vhQ77q08EiIR/UzS+BmDWFdRcFST5f7F+8XezOo1c
  55. DrF1GkcJAMvyJ7KKdeK43eu2ATFdSg==
  56. -----END CERTIFICATE-----
  57. subject=CN = email-smtp.us-west-1.amazonaws.com

  59. issuer=C = US, O = Amazon, CN = Amazon RSA 2048 M01

  61. ---
  62. No client certificate CA names sent
  63. Peer signing digest: SHA256
  64. Peer signature type: RSA-PSS
  65. Server Temp Key: ECDH, P-256, 256 bits
  66. ---
  67. SSL handshake has read 6135 bytes and written 903 bytes
  68. Verification: OK
  69. ---
  70. New, TLSv1.3, Cipher is TLS_AES_256_GCM_SHA384
  71. Server public key is 2048 bit
  72. Secure Renegotiation IS NOT supported
  73. Compression: NONE
  74. Expansion: NONE
  75. No ALPN negotiated
  76. Early data was not sent
  77. Verify return code: 0 (ok)
  78. ---
  79. 250 Ok
  80. ---
  81. Post-Handshake New Session Ticket arrived:
  82. SSL-Session:
  83.     Protocol  : TLSv1.3
  84.     Cipher    : TLS_AES_256_GCM_SHA384
  85.     Session-ID: F13F18778F6405D1D2864FC3078014639FC3AA9186FA64D6F725CB3198E2050D
  86.     Session-ID-ctx:
  87.     Resumption PSK: EE4CB763252AD64874D1A8B75650A16F3E08FC252517F96875052DED3B7115B35EDA13C8B958674B8235647A968C98FE
  88.     PSK identity: None
  89.     PSK identity hint: None
  90.     SRP username: None
  91.     TLS session ticket lifetime hint: 86400 (seconds)
  92.     TLS session ticket:
  93.     0000 - 3a 1c b5 42 b9 44 7e 3b-4c 73 37 5c 92 dd 1e a3   :..B.D~;Ls7\....
  94.     0010 - 44 68 bf 65 0d c9 81 6f-6d 6c 36 b8 e3 a5 aa 08   Dh.e...oml6.....

  96.     Start Time: 1729498245
  97.     Timeout   : 7200 (sec)
  98.     Verify return code: 0 (ok)
  99.     Extended master secret: no
  100.     Max Early Data: 0
  101. ---
  102. read R BLOCK
  103. 451 4.4.2 Timeout waiting for data from client.
  104. closed
复制代码


该证书的 commonName 为 email-smtp.us-west-1.amazonaws.com

如果你将 SMTP 服务器标记为 50.18.243.214 则会发生不匹配，客户端拒绝送信
作者: iks    时间: 2024-10-21 16:16
另外这种愚蠢问题为什么不去问 ChatGPT，总有一个是对的
作者: 榆木    时间: 2024-10-21 16:39
测试了，可以登陆成功啊。多半是证书不匹配的问题。可以尝试手动制定servername，或者手动在hosts里面给域名指定IP地址即可。



欢迎光临 全球主机交流论坛 (https://loc.516000.xyz/) Powered by Discuz! X3.4