[exim-dev] [Bug 2112] Avast scanner does not work when options specified

2018-03-09 Thread admin--- via Exim-dev
https://bugs.exim.org/show_bug.cgi?id=2112 --- Comment #3 from Heiko Schlittermann --- Created attachment 1076 --> https://bugs.exim.org/attachment.cgi?id=1076=edit patch for avast 2.2.0 protocol The attached patch may(!) fix that issue. Needs to be tested in

[exim-dev] [Bug 2112] Avast scanner does not work when options specified

2018-03-09 Thread admin--- via Exim-dev
https://bugs.exim.org/show_bug.cgi?id=2112 --- Comment #2 from Heiko Schlittermann --- https://mta.org.ua/exim/patches/exim-4.90.1-fix-avast-option-support/patch-src__exim-4.90.1-fix-avast-option-support.patch Seems to solve it. Working on it. -- You are receiving this

[exim-dev] [Bug 2112] Avast scanner does not work when options specified

2018-03-09 Thread admin--- via Exim-dev
https://bugs.exim.org/show_bug.cgi?id=2112 --- Comment #1 from Heiko Schlittermann --- *** Bug 2252 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are on the CC list for the bug. -- ## List details at

[exim-dev] [Bug 2252] Improve the error message when connecting to closed avast tcp socket

2018-03-09 Thread admin--- via Exim-dev
https://bugs.exim.org/show_bug.cgi?id=2252 Heiko Schlittermann changed: What|Removed |Added Resolution|--- |DUPLICATE

[exim-dev] [Bug 2250] Peculiarity with SMTP delivery in Exim 4.90.1

2018-03-09 Thread admin--- via Exim-dev
https://bugs.exim.org/show_bug.cgi?id=2250 --- Comment #16 from David Carter --- (In reply to David Carter from comment #14) > I will start bisection with DKIM disabled. 4a5cbaff2f9addfc9b4375a97ec6669bf18ee4db (Tue Sep 19 21:57:30 2017 +0100) has the problem. That predates

[exim-dev] [Bug 2250] Peculiarity with SMTP delivery in Exim 4.90.1

2018-03-09 Thread admin--- via Exim-dev
https://bugs.exim.org/show_bug.cgi?id=2250 --- Comment #15 from David Carter --- (In reply to David Carter from comment #13) > That patch doesn't apply cleanly to "80a47a2c96". It looks like quite a long > has changed since then, so I'm going to need some help applying the same

[exim-dev] [Bug 2250] Peculiarity with SMTP delivery in Exim 4.90.1

2018-03-09 Thread admin--- via Exim-dev
https://bugs.exim.org/show_bug.cgi?id=2250 --- Comment #14 from David Carter --- (In reply to David Carter from comment #13) > (In reply to David Carter from comment #12) > > > I am currently running ae06ddc47aa43bb5e2dcbe2643e41649d1947a9d (latest > > available commit from

Re: [exim-dev] [Bug 2250] Peculiarity with SMTP delivery in Exim 4.90.1

2018-03-09 Thread Jeremy Harris via Exim-dev
On 09/03/18 13:25, admin--- via Exim-dev wrote: > That patch doesn't apply cleanly to "80a47a2c96". It looks like quite a long > has changed since then, so I'm going to need some help applying the same fix > to > intermediate versions. 80a47a2c96 was 2006; you're only looking for problems

[exim-dev] [Bug 2250] Peculiarity with SMTP delivery in Exim 4.90.1

2018-03-09 Thread admin--- via Exim-dev
https://bugs.exim.org/show_bug.cgi?id=2250 --- Comment #13 from David Carter --- (In reply to David Carter from comment #12) > I am currently running ae06ddc47aa43bb5e2dcbe2643e41649d1947a9d (latest > available commit from origin/exim-4_90+fixes), and that still has the >

[exim-dev] [Bug 2253] New: When using PRDR with the SMTP transport, the overall response message is not logged

2018-03-09 Thread admin--- via Exim-dev
https://bugs.exim.org/show_bug.cgi?id=2253 Bug ID: 2253 Summary: When using PRDR with the SMTP transport, the overall response message is not logged Product: Exim Version: 4.90 Hardware: All OS: All

[exim-dev] [Bug 2250] Peculiarity with SMTP delivery in Exim 4.90.1

2018-03-09 Thread admin--- via Exim-dev
https://bugs.exim.org/show_bug.cgi?id=2250 --- Comment #12 from David Carter --- (In reply to David Carter from comment #8) > > I suggest modifying Exim so that it doesn't return 5xx on NULL characters. > > Return 4xx instead so that it will retry? That way you can collect more

[exim-dev] [Bug 2252] Improve the error message when connecting to closed avast tcp socket

2018-03-09 Thread admin--- via Exim-dev
https://bugs.exim.org/show_bug.cgi?id=2252 Heiko Schlittermann changed: What|Removed |Added Assignee|t...@duncanthrax.net

[exim-dev] [Bug 2252] New: Improve the error message when connecting to closed avast tcp socket

2018-03-09 Thread admin--- via Exim-dev
https://bugs.exim.org/show_bug.cgi?id=2252 Bug ID: 2252 Summary: Improve the error message when connecting to closed avast tcp socket Product: Exim Version: 4.90 Hardware: x86 OS: Linux Status:

[exim-dev] [Bug 2251] New: Segfault when LDAP lookup does not return a result

2018-03-09 Thread admin--- via Exim-dev
https://bugs.exim.org/show_bug.cgi?id=2251 Bug ID: 2251 Summary: Segfault when LDAP lookup does not return a result Product: Exim Version: 4.90 Hardware: x86 OS: Linux Status: NEW Severity: bug