On 2018-06-15 at 11:51 +0000, Emanuel Gonzalez via Exim-users wrote:
> "In fact, it is Exim who SHOULD drop fucking legacy protocol support.
> But I cannot convince its developers to do that. I have fixed this
> issue at some point in the past but I have no Exim to test that."
For the record: this is the first I've ever heard of such an issue.
I've just checked <
https://bugs.exim.org/> and there's no sign of a
tracking issue.
We're open to patches to change protocols, that's how this code was
contributed in the first place. We support open source and closed
source products both. We've no objection to changing protocols here.
I do object to finding out that there's an issue by a developer of
another project bad-mouthing us and I object to spending my time
cleaning up the mess. I've little to no incentive to go out of my way
to chase this down any further.
In the meantime, it looks like Exim just doesn't support rspam-proxy
if it's truly just ignoring configuration to speak their own protocol.
I've filed a feature request tracking issue:
https://bugs.exim.org/show_bug.cgi?id=2282
I'm going to step away now because this entire situation is leaving a
bad taste in my mouth and making me grumpy. "Feature request filing
against a project by bad-mouthing the developers and shaming them into
development" is not a model I wish to support or encourage for open
source development. This is not why I give up my own time to work on
software such as Exim. This is bullshit.
-Phil
