https://bugs.exim.org/show_bug.cgi?id=1802
--- Comment #6 from vsevolod@??? ---
I don't understand that point: that's exactly the reason why I've opened this
ticket - exim and rspamd should be consistent in terms of protocol. Newer exim
that would be likely shipped with newer rspamd will talk to rspamd without
problmes. Older exim will be *likely* shipped with older rspamd and there will
no problem as well. In a rare case when older exim will communicate with newer
rspamd it is still possible to provide compatibility by changing the
configuration option.
On the contrary, newer exim (with shutdown removed) will be able to communicate
with both older and newer rspamd as rspamd has never ever relied on `shutdown`
unlike SA. If `shutdown` would not be removed for rspamd then *all* users of
exim would be affected after some time (6-8 months) and should enable the
workaround manually. That's why I've opened this ticket.
Why don't I like half-closed connections? It turns out that when a client
decides to close connection for some reason (timeout, not enough resources,
SMTP session failure, etc) rspamd still has to process this message despite of
the fact that nobody waits for a reply. And there is no reliable way to
distinguish half-closed connection from fully closed in BSD sockets
(
https://cr.yp.to/tcpip/twofd.html). Since rspamd never ever utilized
half-closed connections, I've decided to gradually remove their support in
honor of performance benefits and more straightforward REST-like protocol. In
fact, I have to hack HTTP protocol to support some legacy clients including
exim. And I don't like this situation.
--
You are receiving this mail because:
You are on the CC list for the bug.
