You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Unexpected server response "220-myhost.nodomain.io ESMTP Exim 4.98 #2 Wed, 30 Oct 2024 09:48:43 +0000" 220
Hi again,
we found an issue within the latest 2.99 and 3.x versions not being able to connect to some hosts on not correctly interpreting the response from servers. We confirmed this is working with older simplemail 2.x (not 2.99) and we are currently not sure what causes this in newer versions.
As mentioned we have it running in multiple systems and it works normally very well. Just some server responses seem to have issue on interpreting the 220 correctly. Same setup, just switching simplemail 2.3 with 3.1 and updating our interface will break the libraries functionality in this case, whereas mentioned most servers work fine.
The bulk email error is not displayed all times and connection can abort before too. We first thought we would require an earlier authentication but simplemail2 does the same order and it just works (tested on same machine with same settings).
Please notify us if we can help on analyzing any further.
2024-10-30T09:48:43 Warning :0():Unexpected server response "220-myhost.nodomain.io ESMTP Exim 4.98 #2 Wed, 30 Oct 2024 09:48:43 +0000" 220
2024-10-30T09:48:43 Debug :0():readyRead 100
2024-10-30T09:52:03 Debug :0():SocketError QAbstractSocket::SocketError(20) "220-We do not authorize the use of this system to transport unsolicited, \r\n220 and/or bulk e-mail.\r\n"
Unexpected server response "220-myhost.nodomain.io ESMTP Exim 4.98 #2 Wed, 30 Oct 2024 09:48:43 +0000" 220
Hi again,
we found an issue within the latest 2.99 and 3.x versions not being able to connect to some hosts on not correctly interpreting the response from servers. We confirmed this is working with older simplemail 2.x (not 2.99) and we are currently not sure what causes this in newer versions.
As mentioned we have it running in multiple systems and it works normally very well. Just some server responses seem to have issue on interpreting the 220 correctly. Same setup, just switching simplemail 2.3 with 3.1 and updating our interface will break the libraries functionality in this case, whereas mentioned most servers work fine.
The bulk email error is not displayed all times and connection can abort before too. We first thought we would require an earlier authentication but simplemail2 does the same order and it just works (tested on same machine with same settings).
Please notify us if we can help on analyzing any further.
`2024-10-30T09:45:13 Debug :0():Got response "220-myhost.nodomain.io ESMTP Exim 4.98 #2 Wed, 30 Oct 2024 09:45:13 +0000" expected 220
2024-10-30T09:45:13 Warning :0():Unexpected server response "220-myhost.nodomain.io ESMTP Exim 4.98 #2 Wed, 30 Oct 2024 09:45:13 +0000" 220
2024-10-30T09:45:13 Debug :0():readyRead 100
2024-10-30T09:45:43 Debug :0():Connecting to host encrypted "" 465
2024-10-30T09:45:43 Debug :0():stateChanged QAbstractSocket::HostLookupState ""
2024-10-30T09:45:43 Debug :0():stateChanged QAbstractSocket::ConnectingState ""
2024-10-30T09:45:43 Debug :0():stateChanged QAbstractSocket::ConnectedState ""
2024-10-30T09:45:43 Debug :0():connected 2 ""
2024-10-30T09:45:43 Debug :0():SocketError QAbstractSocket::SocketError(13) ""
2024-10-30T09:45:43 Debug :0():stateChanged QAbstractSocket::ClosingState ""
2024-10-30T09:45:43 Debug :0():stateChanged QAbstractSocket::UnconnectedState ""
2024-10-30T09:48:43 Debug :0():Connecting to host encrypted "http://myhost.nodomain.io/ " 465
2024-10-30T09:48:43 Debug :0():stateChanged QAbstractSocket::HostLookupState ""
2024-10-30T09:48:43 Debug :0():stateChanged QAbstractSocket::ConnectingState ""
2024-10-30T09:48:43 Debug :0():stateChanged QAbstractSocket::ConnectedState ""
2024-10-30T09:48:43 Debug :0():connected 2 ""
2024-10-30T09:48:43 Debug :0():readyRead 176
2024-10-30T09:48:43 Debug :0():Got response "220-myhost.nodomain.io ESMTP Exim 4.98 #2 Wed, 30 Oct 2024 09:48:43 +0000" expected 220
2024-10-30T09:48:43 Warning :0():Unexpected server response "220-myhost.nodomain.io ESMTP Exim 4.98 #2 Wed, 30 Oct 2024 09:48:43 +0000" 220
2024-10-30T09:48:43 Debug :0():readyRead 100
2024-10-30T09:52:03 Debug :0():SocketError QAbstractSocket::SocketError(20) "220-We do not authorize the use of this system to transport unsolicited, \r\n220 and/or bulk e-mail.\r\n"
2024-10-30T09:52:03 Debug :0():SocketError QAbstractSocket::RemoteHostClosedError ""
2024-10-30T09:52:03 Debug :0():stateChanged QAbstractSocket::ClosingState ""
2024-10-30T09:52:03 Debug :0():stateChanged QAbstractSocket::UnconnectedState ""`
(sorry for the strange formatting, it just would not accept the newlines and become unreadable)
The text was updated successfully, but these errors were encountered: