Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

220-hostname Unexpected response after connect #113

Open
LangeSebastian opened this issue Nov 8, 2024 · 1 comment
Open

220-hostname Unexpected response after connect #113

LangeSebastian opened this issue Nov 8, 2024 · 1 comment

Comments

@LangeSebastian
Copy link
Contributor

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)

@dantti
Copy link
Member

dantti commented Nov 8, 2024

please try git bisect since old versions worked

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants