On 2018-06-13 at 18:44 +0000, Emanuel Gonzalez via Exim-users wrote:
> rspamd-proxy doesn't work with Exim v4.87. Connection works etc but exim can't parse the response.
Interesting. From the rspamd log attached to your ticket against rspamd
it looks as though rspamd thinks things succeeded?
Since you have the service listening on a TCP port, could you provide a
tcpdump of the response, so we can see what text you're getting in
reply, please?
This means seeing the _actual_ reply, not just that there was a reply.
> 2018-06-13 13:45:23 1fT8te-0004kn-Pw spam acl condition: cannot parse spamd [1.2.3.4]:11332, output: 0
Our code seems to match what I can figure out from the rspamd codebase,
but I've never looked at rspamd's code before so am unfamiliar with it.
The core parsing is unchanged from the logic which rspamd supplied to
us, I believe.
> More information see this report https://github.com/vstakhov/rspamd/issues/2289
You include a tcpdump there showing that packets were exchanged, and
their sizes, but nothing about the content of the packets.
You'll want to tell tcpdump: -Xs0
The "-s 0" says "read the entire packet, not just the start" and the
"-X" says to print a dump in hex and ASCII.
We only want the actual text from the reply, we don't need all the stuff
sending the mail across. The reply probably includes the text:
RSPAMD/1.3 0 EX_OK
That packet, to the end of the connection, is the bit we need, to
compare what the server sent with what Exim expected.
Regards,
-Phil
