作者：溜溜的情歌哆瑞咪 | 来源：互联网 | 2023-09-12 17:20
Hey, I'm back with another question. I got everything set up great, and was successful in the first wave of emails. However, we're getting ready to send out a second wave of emails, but the open tracking has stopped working. It was previously all good, opens were tracking properly in both tests and actual execution. Now I'm getting TLS handshake errors, which I can tell are linked to the opens. If I send myself a mail, and try and open it, I get an error that links back to my IP.
The following is a sample of some of the errors:
1
2
3
4
5
| 2017/06/22 09:42:13 http: TLS handshake error from IP: tls: no cipher suite supported by both client and server
2017/06/22 16:59:14 http: TLS handshake error from IP: local error: tls: bad record MAC
2017/06/22 17:23:31 http: TLS handshake error from IP: tls: oversized record received with length 29556
2017/06/22 19:31:23 http: TLS handshake error from IP: tls: unsupported SSLv2 handshake received
2017/06/22 19:31:23 http: TLS handshake error from IP: tls: client offered an unsupported, maximum protocol version of 300 |
Any help in getting this resolved is greatly appreciated. Thanks!
该提问来源于开源项目：gophish/gophish
Sorry for the delay in revisiting this. Are you still seeing these TLS errors?
If so, is it perfectly correlated to actually opening the email with an email client, or do you have a spam appliance that may be doing link checking when emails are being received?
京公网安备 11010802041100号