IP addresses and Host names can be added to the STARTTLS Whitelist. MDaemon staff members may participate in theįorums periodically but please recognize that this is not the official These forums are provided by MDaemon Technologies for user-to-user If the recipient server is forcing TLS, the session will fail and it'll be logged in MDaemon. If the SMTP session is successful when not using STARTTLS, the problem definitely lies with the secure handshake and/or certificate. The certificate MDaemon is using can be inspected in the menu below.Īnother test to perform is adding the problem host(s) to the STARTTLS Whitelist. Is MDaemon using a self signed certificate or a certificate using outdated protocols (TLS 1.0 or 1.1) or a SHA1 certificate type? Normally if there is a SSL/TLS protocol error, it would be recorded in the logs, but that does not rule out this being a cause of the issue. Perhaps the disconnect is coming from here. I would recommend reviewing any firewalls and/or security hardware/software that could be monitoring SMTP traffic. As MDaemon is not terminating the session, the first steps for trouble shooting this lie outside of MDaemon. The primary issue is what is disconnecting the initial two connections. (- 451 Could not load DRD for domain (XXX.com) rcpt online for this response shows this is a response from MXLogic's servers and it is rejecting the message for one reason or another. When connecting to the remaining hosts, it is rejected by the recipient servers. Socket connection closed by the other side (how rude!) MDaemon reports either the recipient server or something in between MDaemon and the recipient server severed the connection. MDaemon issues a STARTTLS command to open a secure connection and the handshake never completes. MDaemon connects to the first two servers without issue. The log shows MDaemon attempting to connect to the 5 records reported by the DNS server in order of preference.
0 kommentar(er)
