Hi,
Am 26.06.2018 um 21:50 schrieb Andrew Lewis via Exim-users:
>> If it is correct that rspamd (in current versions) not longer operates
>> with Exim then we should cease claiming it does (until and if
>> someone develops new support), and may as well remove the nonfunctional
>> code.
>
>
Andrew Lewis via Exim-users (Di 26 Jun 2018 21:50:31
CEST):
…
> Can we revive Rspamd support please? I expect a non-trivial amount of people
> are actively using it.
I'm more than happy if we can continue (native) rspamd support.
As long as rspamd supports the legacy SpamAssassin-derived
Hi,
I'm sorry about breaking the thread, I was not on the list.
If it is correct that rspamd (in current versions) not longer operates
with Exim then we should cease claiming it does (until and if
someone develops new support), and may as well remove the nonfunctional
code.
That's not
On Wed, Jun 27, 2018 at 10:00 AM, Heiko Schlittermann via Exim-users <
exim-users@exim.org> wrote:
>
> Personally I'd like to see rspamd support in Exim, but currently my
> ressources are limited (ressources hack the support into Exim), and I do
> not feel comfortable with bloating Exim by
Hi,
Emanuel Gonzalez via Exim-users (Fr 15 Jun 2018 13:51:19
CEST):
> i talk with the rspamd develop, they say this:
>
>
> "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
On 06/16/2018 02:27 PM, Jeremy Harris via Exim-users wrote:
> On 06/15/2018 01:28 PM, Andrew C Aitchison via Exim-users wrote:
>> Hmm; rspamd used to use the spamassassin protocol.
>> At some point rspamd switched to a new protocol which the developer had
>> a reasonable reason for prefering
On 06/15/2018 01:28 PM, Andrew C Aitchison via Exim-users wrote:
> Hmm; rspamd used to use the spamassassin protocol.
> At some point rspamd switched to a new protocol which the developer had
> a reasonable reason for prefering (theoretically cleaner and IIRC
> better performance under some
On 2018-06-15 at 17:26 -0400, Phil Pennock via Exim-users wrote:
> On 2018-06-15 at 11:51 +, 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
On 2018-06-15 at 11:51 +, 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:
rspamd develop reply:
No, that's not correct. Rspamd started the own protocol based on SA protocol
long ago. Then there was a workaround to support SA clients. However, long time
ago, Rspamd has switched from own protocol to the standard HTTP (using JSON to
produce results). Hence, if Exim
On Fri, 15 Jun 2018, Emanuel Gonzalez via Exim-users wrote:
i talk with the rspamd develop, they say this:
"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
I'm in contact with the rspamd developers and they tell me this
I've told them for years* already that HTTP is the only format that should be
used when communicating with Rspamd. They just refuses to do that: Exim is the
only MTA that still uses protocol that has been deprecated for 5 years
i talk with the rspamd develop, they say this:
"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."
please give me a help.
--
## List details
On 2018-06-14 at 18:31 +, Emanuel Gonzalez via Exim-users wrote:
> Here the log:
>
> https://github.com/vstakhov/rspamd/files/2102038/rspamdserver.log
The rspamd proxy is replying with an HTTP response, not an RSPAM
protocol response.
Since I saw logic in the proxy source-code to handle
Here the log:
https://github.com/vstakhov/rspamd/files/2102038/rspamdserver.log
Thanks.!!
--
## List details at https://lists.exim.org/mailman/listinfo/exim-users
## Exim details at http://www.exim.org/
## Please use the Wiki with this list - http://wiki.exim.org/
I try to attach a .log file but my answer is not published in the thread.
--
## List details at https://lists.exim.org/mailman/listinfo/exim-users
## Exim details at http://www.exim.org/
## Please use the Wiki with this list - http://wiki.exim.org/
On 2018-06-13 at 18:44 +, 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?
/vstakhov/rspamd/issues/2289>
Rspamd-Proxy error with exim · Issue #2289 ·
vstakhov/rspamd<https://github.com/vstakhov/rspamd/issues/2289>
github.com
Classification (Please choose one option): [] Crash/Hang/Data loss
WebUI/Usability Serious bug Other bug Feature Enhancement Reproducib
18 matches
Mail list logo
