[exim-dev] [Bug 2235] CVE-2018-6789

2018-02-12 Thread admin--- via Exim-dev
https://bugs.exim.org/show_bug.cgi?id=2235 Heiko Schlittermann changed: What|Removed |Added Resolution|--- |FIXED

[exim-dev] [Bug 2239] segfault when processing control = utf8_downconvert

2018-02-12 Thread admin--- via Exim-dev
https://bugs.exim.org/show_bug.cgi?id=2239 Jeremy Harris changed: What|Removed |Added Status|NEW |ASSIGNED --- Comment #2

[exim-dev] [Bug 2239] segfault when processing control = utf8_downconvert

2018-02-12 Thread admin--- via Exim-dev
https://bugs.exim.org/show_bug.cgi?id=2239 --- Comment #3 from Gedalya --- Yes. The documentation could be read as suggesting the flag is stored with the message, not with a recipient address item. Coming to think of it, it would fit better in many configurations if this

[exim-dev] [Bug 2239] segfault when processing control = utf8_downconvert

2018-02-12 Thread admin--- via Exim-dev
https://bugs.exim.org/show_bug.cgi?id=2239 Git Commit changed: What|Removed |Added CC||g...@exim.org --- Comment #4 from

[exim-dev] [Bug 2239] New: segfault when processing control = utf8_downconvert

2018-02-11 Thread admin--- via Exim-dev
https://bugs.exim.org/show_bug.cgi?id=2239 Bug ID: 2239 Summary: segfault when processing control = utf8_downconvert Product: Exim Version: 4.90 Hardware: x86-64 OS: Linux Status: NEW Severity: bug

[exim-dev] [Bug 2239] segfault when processing control = utf8_downconvert

2018-02-11 Thread admin--- via Exim-dev
https://bugs.exim.org/show_bug.cgi?id=2239 --- Comment #1 from Gedalya --- Sorry, correction. It does work when called from acl_smtp_rcpt. Looks like the acl_check() function in acl.c leaves addr as NULL unless (where==ACL_WHERE_RCPT || where==ACL_WHERE_VRFY ||

[exim-dev] [Bug 2242] exim_dbmbuild fails to open output files relative to cwd if no / in name

2018-02-14 Thread admin--- via Exim-dev
https://bugs.exim.org/show_bug.cgi?id=2242 Jeremy Harris changed: What|Removed |Added Status|NEW |ASSIGNED

[exim-dev] [Bug 2242] New: exim_dbmbuild fails to open output files relative to cwd if no / in name

2018-02-14 Thread admin--- via Exim-dev
https://bugs.exim.org/show_bug.cgi?id=2242 Bug ID: 2242 Summary: exim_dbmbuild fails to open output files relative to cwd if no / in name Product: Exim Version: 4.90 Hardware: x86 OS: Windows

[exim-dev] [Bug 2243] Noise in "exim -bV" stderr with +arguments log_selector

2018-02-19 Thread admin--- via Exim-dev
https://bugs.exim.org/show_bug.cgi?id=2243 --- Comment #5 from Phil Pennock --- (although, now that I've realized the log_testing_mode connection, I no longer see why the runtime user impacts upon the logs being written or not ... this was a bad time to give up caffeine) -- You

[exim-dev] [Bug 2243] Noise in "exim -bV" stderr with +arguments log_selector

2018-02-19 Thread admin--- via Exim-dev
https://bugs.exim.org/show_bug.cgi?id=2243 Phil Pennock changed: What|Removed |Added Status|NEW |ASSIGNED

[exim-dev] [Bug 2246] New: utf8_downconvert as a transport option

2018-02-22 Thread admin--- via Exim-dev
https://bugs.exim.org/show_bug.cgi?id=2246 Bug ID: 2246 Summary: utf8_downconvert as a transport option Product: Exim Version: 4.90 Hardware: All OS: All Status: NEW Severity: wishlist Priority:

[exim-dev] [Bug 2239] segfault when processing control = utf8_downconvert

2018-02-22 Thread admin--- via Exim-dev
https://bugs.exim.org/show_bug.cgi?id=2239 Jeremy Harris changed: What|Removed |Added Resolution|--- |FIXED

[exim-dev] [Bug 2242] exim_dbmbuild fails to open output files relative to cwd if no / in name

2018-02-22 Thread admin--- via Exim-dev
https://bugs.exim.org/show_bug.cgi?id=2242 Git Commit changed: What|Removed |Added CC||g...@exim.org --- Comment #2 from

[exim-dev] [Bug 2239] segfault when processing control = utf8_downconvert

2018-02-22 Thread admin--- via Exim-dev
https://bugs.exim.org/show_bug.cgi?id=2239 Jeremy Harris changed: What|Removed |Added See Also|

[exim-dev] [Bug 2238] Internal SPF check making too much lookups?

2018-02-22 Thread admin--- via Exim-dev
https://bugs.exim.org/show_bug.cgi?id=2238 Jeremy Harris changed: What|Removed |Added Status|NEW |RESOLVED

[exim-dev] [Bug 2246] utf8_downconvert as a transport option

2018-02-22 Thread admin--- via Exim-dev
https://bugs.exim.org/show_bug.cgi?id=2246 Jeremy Harris changed: What|Removed |Added See Also|

[exim-dev] [Bug 2239] segfault when processing control = utf8_downconvert

2018-02-22 Thread admin--- via Exim-dev
https://bugs.exim.org/show_bug.cgi?id=2239 --- Comment #5 from Jeremy Harris --- Nobody commented on the fix. Opened wishlist item 2246 for the transport option suggestion. -- You are receiving this mail because: You are on the CC list for the bug. -- ## List details at

[exim-dev] [Bug 2243] Noise in "exim -bV" stderr with +arguments log_selector

2018-02-18 Thread admin--- via Exim-dev
https://bugs.exim.org/show_bug.cgi?id=2243 Phil Pennock changed: What|Removed |Added CC||p...@exim.org --- Comment #1 from

[exim-dev] [Bug 2246] utf8_downconvert as a transport option

2018-02-24 Thread admin--- via Exim-dev
https://bugs.exim.org/show_bug.cgi?id=2246 Gedalya changed: What|Removed |Added CC||geda...@gedalya.net --- Comment

[exim-dev] [Bug 2246] utf8_downconvert as a transport option

2018-02-24 Thread admin--- via Exim-dev
https://bugs.exim.org/show_bug.cgi?id=2246 --- Comment #2 from Jeremy Harris --- Fixed; e6532c4a78. -- You are receiving this mail because: You are on the CC list for the bug. -- ## List details at https://lists.exim.org/mailman/listinfo/exim-dev Exim details at

[exim-dev] [Bug 1998] RFE: custom expansions

2018-02-16 Thread admin--- via Exim-dev
https://bugs.exim.org/show_bug.cgi?id=1998 Phil Pennock changed: What|Removed |Added Target Milestone|4.10x |Exim_4.91+ -- You are receiving

[exim-dev] [Bug 1294] SPF TYPE99 deprecation

2018-02-16 Thread admin--- via Exim-dev
https://bugs.exim.org/show_bug.cgi?id=1294 Phil Pennock changed: What|Removed |Added Target Milestone|4.10x |Exim_4.91+ -- You are receiving

[exim-dev] [Bug 2243] Noise in "exim -bV" stderr with +arguments log_selector

2018-02-19 Thread admin--- via Exim-dev
https://bugs.exim.org/show_bug.cgi?id=2243 --- Comment #2 from Andreas Metzler --- > Phil Pennock changed: [...] > That said, I'm can't see why stderr would have been empty before; I can find > one change to the logic since 4.84 was cut, and that is a macro

[exim-dev] [Bug 2243] New: Noise in "exim -bV" stderr with +arguments log_selector

2018-02-18 Thread admin--- via Exim-dev
https://bugs.exim.org/show_bug.cgi?id=2243 Bug ID: 2243 Summary: Noise in "exim -bV" stderr with +arguments log_selector Product: Exim Version: 4.90 Hardware: x86 URL: https://bugs.debian.org/890236

[exim-dev] [Bug 2243] Noise in "exim -bV" stderr with +arguments log_selector

2018-02-19 Thread admin--- via Exim-dev
https://bugs.exim.org/show_bug.cgi?id=2243 --- Comment #3 from Phil Pennock --- If I invoke Exim as non-root (user in admin_groups), then the log-line does not appear on stderr. If I invoke Exim as root, then it does. I'm still puzzling over why this is, but it does suggest that

[exim-dev] [Bug 2162] Implement Authenticated Received Chain (ARC)

2018-03-03 Thread admin--- via Exim-dev
https://bugs.exim.org/show_bug.cgi?id=2162 Git Commit changed: What|Removed |Added CC||g...@exim.org --- Comment #6 from

[exim-dev] [Bug 2162] Implement Authenticated Received Chain (ARC)

2018-03-03 Thread admin--- via Exim-dev
https://bugs.exim.org/show_bug.cgi?id=2162 Jeremy Harris changed: What|Removed |Added Status|ASSIGNED|WAIT_FIX_CONFIRMATION

[exim-dev] [Bug 2242] exim_dbmbuild fails to open output files relative to cwd if no / in name

2018-03-03 Thread admin--- via Exim-dev
https://bugs.exim.org/show_bug.cgi?id=2242 Jeremy Harris changed: What|Removed |Added Resolution|--- |FIXED

[exim-dev] [Bug 1523] DANE support under GnuTLS

2018-03-03 Thread admin--- via Exim-dev
https://bugs.exim.org/show_bug.cgi?id=1523 Jeremy Harris changed: What|Removed |Added Status|ASSIGNED|RESOLVED

[exim-dev] [Bug 1523] DANE support under GnuTLS

2018-03-04 Thread admin--- via Exim-dev
https://bugs.exim.org/show_bug.cgi?id=1523 --- Comment #6 from Jeremy Harris --- Doh, thinko. DANE was moved to mainline by c0635b6dfe and will be in 4.91 -- You are receiving this mail because: You are on the CC list for the bug. -- ## List details at

[exim-dev] [Bug 2248] New: Lightweight redis cluster redirect method

2018-03-05 Thread admin--- via Exim-dev
https://bugs.exim.org/show_bug.cgi?id=2248 Bug ID: 2248 Summary: Lightweight redis cluster redirect method Product: Exim Version: 4.90 Hardware: x86 OS: All Status: NEW Severity: wishlist

[exim-dev] [Bug 2248] Lightweight redis cluster redirect method

2018-03-06 Thread admin--- via Exim-dev
https://bugs.exim.org/show_bug.cgi?id=2248 --- Comment #3 from Graeme Fowler --- Tricky. Requires a functional and configured cluster (perhaps on a second port on localhost) and that takes some setup to create. Will see if I can create a 2701-redis-cluster test alongside

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

2018-03-08 Thread admin--- via Exim-dev
https://bugs.exim.org/show_bug.cgi?id=2250 Graeme Fowler changed: What|Removed |Added CC||gra...@graemef.net ---

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

2018-03-08 Thread admin--- via Exim-dev
https://bugs.exim.org/show_bug.cgi?id=2250 --- Comment #2 from David Carter --- > I can see a steady stream of 'NULL character' error messages > which appear to relate to remote hosts attempting to talk gibberish > (TLS perhaps?) on port 25 Yes, we still see this now that I

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

2018-03-08 Thread admin--- via Exim-dev
https://bugs.exim.org/show_bug.cgi?id=2250 --- Comment #9 from Jeremy Harris --- Depends whether the bug is deterministic for that recipient string. -- You are receiving this mail because: You are on the CC list for the bug. -- ## List details at

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

2018-03-08 Thread admin--- via Exim-dev
https://bugs.exim.org/show_bug.cgi?id=2250 --- Comment #5 from Graeme Fowler --- So in the "only the receiving end has changed", I'm not seeing anything on my MX servers which are mirroring the behaviour you're seeing. I *am* seeing occasional "??EHLO somename" commands,

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

2018-03-08 Thread admin--- via Exim-dev
https://bugs.exim.org/show_bug.cgi?id=2250 --- Comment #6 from David Carter --- > It's a puzzler. The fact that I only seem to see these errors for messages from lists.cam.ac.uk is curious. Actually, no: If I search my logs for the last 28 days I _do_ find some examples

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

2018-03-08 Thread admin--- via Exim-dev
https://bugs.exim.org/show_bug.cgi?id=2250 --- Comment #7 from Simon Arlott --- (In reply to David Carter from comment #4) > > I assume that a bisect isn't viable? > > It would be awkward. I would be willing to try a couple of subdivisions to > try and narrow

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

2018-03-08 Thread admin--- via Exim-dev
https://bugs.exim.org/show_bug.cgi?id=2250 --- Comment #10 from David Carter --- I guess I will need to try bisection with the 4xy suggestion to minimise fallout. Any obvious points between 4.89.1 and 4.90.1 that I need to avoid as they introduce nasty bugs? -- You are

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

2018-03-08 Thread admin--- via Exim-dev
https://bugs.exim.org/show_bug.cgi?id=2250 --- Comment #11 from Jeremy Harris --- I don't think there were any real howlers in that sequence. -- You are receiving this mail because: You are on the CC list for the bug. -- ## List details at

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

2018-03-08 Thread admin--- via Exim-dev
https://bugs.exim.org/show_bug.cgi?id=2250 --- Comment #3 from Jeremy Harris --- Scanning the commit log between 4.89.1 and 4.90.1 isn't flagging anything to me. I assume that a bisect isn't viable? -- You are receiving this mail because: You are on the CC list for the

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

2018-03-08 Thread admin--- via Exim-dev
https://bugs.exim.org/show_bug.cgi?id=2250 --- Comment #4 from David Carter --- > I assume that a bisect isn't viable? It would be awkward. I would be willing to try a couple of subdivisions to try and narrow things down. However I think that I would want to wait a couple of

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

2018-03-08 Thread admin--- via Exim-dev
https://bugs.exim.org/show_bug.cgi?id=2250 --- Comment #8 from David Carter --- > 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 > instances of the issue without dropping

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

2018-03-11 Thread admin--- via Exim-dev
https://bugs.exim.org/show_bug.cgi?id=2251 Git Commit changed: What|Removed |Added CC||g...@exim.org --- Comment #6 from

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

2018-03-11 Thread admin--- via Exim-dev
https://bugs.exim.org/show_bug.cgi?id=2251 Jeremy Harris changed: What|Removed |Added Status|NEW |ASSIGNED

[exim-dev] [Bug 2255] TLS/SSL issue after upgading to 4.90

2018-03-11 Thread admin--- via Exim-dev
https://bugs.exim.org/show_bug.cgi?id=2255 --- Comment #1 from Jeremy Harris --- We don't have particularly good insight into what the SSL libraries do (though I'm concerned that you managed to negotiate such a weak cipher). Was the working conn you show using 4.89 or

[exim-dev] [Bug 2255] TLS/SSL issue after upgading to 4.90

2018-03-11 Thread admin--- via Exim-dev
https://bugs.exim.org/show_bug.cgi?id=2255 --- Comment #3 from Jeremy Harris --- Either side is fine for this. -- You are receiving this mail because: You are on the CC list for the bug. -- ## List details at https://lists.exim.org/mailman/listinfo/exim-dev Exim

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

2018-03-11 Thread admin--- via Exim-dev
https://bugs.exim.org/show_bug.cgi?id=2251 --- Comment #4 from Matthew Slowe --- (In reply to Jeremy Harris from comment #3) > Thanks. Was the debug output saved, from the run first noted above? > > Alternatively could you run an "exim -d-all+lookup -be" test for that >

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

2018-03-11 Thread admin--- via Exim-dev
https://bugs.exim.org/show_bug.cgi?id=2253 Git Commit changed: What|Removed |Added CC||g...@exim.org --- Comment #1 from

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

2018-03-11 Thread admin--- via Exim-dev
https://bugs.exim.org/show_bug.cgi?id=2251 --- Comment #1 from Jeremy Harris --- Do you know which variant of LDAP library you are using? -- You are receiving this mail because: You are on the CC list for the bug. -- ## List details at

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

2018-03-11 Thread admin--- via Exim-dev
https://bugs.exim.org/show_bug.cgi?id=2253 Jeremy Harris changed: What|Removed |Added Status|NEW |ASSIGNED

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

2018-03-11 Thread admin--- via Exim-dev
https://bugs.exim.org/show_bug.cgi?id=2251 --- Comment #3 from Jeremy Harris --- Thanks. Was the debug output saved, from the run first noted above? Alternatively could you run an "exim -d-all+lookup -be" test for that expansion, where a "no result" is expected? This

[exim-dev] [Bug 2255] New: TLS/SSL issue after upgading to 4.90

2018-03-11 Thread admin--- via Exim-dev
https://bugs.exim.org/show_bug.cgi?id=2255 Bug ID: 2255 Summary: TLS/SSL issue after upgading to 4.90 Product: Exim Version: 4.90 Hardware: x86 OS: FreeBSD Status: NEW Severity: bug Priority:

[exim-dev] [Bug 2255] TLS/SSL issue after upgading to 4.90

2018-03-11 Thread admin--- via Exim-dev
https://bugs.exim.org/show_bug.cgi?id=2255 --- Comment #2 from exim@mx.zzux.com --- The both logs are on 4.90_1. Where I must to catch traffic with Wireshark - on the Windows side? -- You are receiving this mail because: You are on the CC list for the bug. -- ## List details at

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

2018-03-11 Thread admin--- via Exim-dev
https://bugs.exim.org/show_bug.cgi?id=2251 --- Comment #2 from Matthew Slowe --- (In reply to Jeremy Harris from comment #1) > Do you know which variant of LDAP library you are using? Looks like openldap... # ldd $(which exim) | grep ldap libldap-2.4.so.2 =>

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

2018-03-12 Thread admin--- via Exim-dev
https://bugs.exim.org/show_bug.cgi?id=2251 --- Comment #8 from Jeremy Harris --- Apart from by virtue of being in git? The date for the next numbered bundle release has not been set. Will you be testing it before that? -- You are receiving this mail because: You are on

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

2018-03-12 Thread admin--- via Exim-dev
https://bugs.exim.org/show_bug.cgi?id=2251 --- Comment #7 from Matthew Slowe --- Thanks Jeremy. Any idea when this might get released? -- You are receiving this mail because: You are on the CC list for the bug. -- ## List details at

[exim-dev] [Bug 2255] TLS/SSL issue after upgading to 4.90

2018-03-12 Thread admin--- via Exim-dev
https://bugs.exim.org/show_bug.cgi?id=2255 --- Comment #4 from exim@mx.zzux.com --- I was found differences between failure and success on 4.90_1 and 4.89. But I'm absolutely puzzled how to copy readable packet description from Wireshark to clipboard. Exim 4.90 is missing SessionId in server

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

2018-03-12 Thread admin--- via Exim-dev
https://bugs.exim.org/show_bug.cgi?id=2112 Heiko Schlittermann changed: What|Removed |Added Status|NEW |RESOLVED

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

2018-03-12 Thread admin--- via Exim-dev
https://bugs.exim.org/show_bug.cgi?id=2112 Git Commit changed: What|Removed |Added CC||g...@exim.org --- Comment #4 from

[exim-dev] [Bug 2255] TLS/SSL issue after upgading to 4.90

2018-03-13 Thread admin--- via Exim-dev
https://bugs.exim.org/show_bug.cgi?id=2255 Thorsten changed: What|Removed |Added CC||thorsten.ha...@freenet.ag

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

2018-03-13 Thread admin--- via Exim-dev
https://bugs.exim.org/show_bug.cgi?id=2251 --- Comment #9 from Matthew Slowe --- Hi Jeremy, Struggling a bit to test this as the EPEL SRPM appears to be significantly different. The block you've updated is at line 887 and looks a bit different: /* Terminate the dynamic

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

2018-03-13 Thread admin--- via Exim-dev
https://bugs.exim.org/show_bug.cgi?id=2251 --- Comment #10 from Jeremy Harris --- Indeed, git commits are against a git branch tip, so a distro likely will not have caught up yet. gstring_reset_unused() is just that one store_reset line. -- You are receiving this mail

[exim-dev] [Bug 2255] TLS/SSL issue after upgading to 4.90

2018-03-13 Thread admin--- via Exim-dev
https://bugs.exim.org/show_bug.cgi?id=2255 tomputer changed: What|Removed |Added CC||e...@tomputer.nl --- Comment #6

[exim-dev] [Bug 2255] TLS/SSL issue after upgading to 4.90

2018-03-13 Thread admin--- via Exim-dev
https://bugs.exim.org/show_bug.cgi?id=2255 --- Comment #8 from Jeremy Harris --- Also, given comment 5, you could try setting a nondefault openssl_options. Before 7006ee24ec it was "+no_sslv2 +single_dh_use". After: "+no_sslv2 +single_dh_use +no_ticket" -- You are

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

2018-03-13 Thread admin--- via Exim-dev
https://bugs.exim.org/show_bug.cgi?id=2251 --- Comment #11 from Matthew Slowe --- (In reply to Jeremy Harris from comment #10) > Indeed, git commits are against a git branch tip, so a distro likely will > not have caught up yet. > > gstring_reset_unused() is just that one

[exim-dev] [Bug 2255] TLS/SSL issue after upgading to 4.90

2018-03-13 Thread admin--- via Exim-dev
https://bugs.exim.org/show_bug.cgi?id=2255 --- Comment #7 from Jeremy Harris --- It might be a good idea to ask the OpenSSL mailing list: openssl-users.openssl.org -- You are receiving this mail because: You are on the CC list for the bug. -- ## List details at

[exim-dev] [Bug 2255] TLS/SSL issue after upgading to 4.90

2018-03-13 Thread admin--- via Exim-dev
https://bugs.exim.org/show_bug.cgi?id=2255 --- Comment #11 from exim@mx.zzux.com --- A day before writing this topic I was trying various combinations of "openssl_options" in Exim config, most of them were with no effect except few of them, when SSL/TLS was unavailable at all. Now I've added

[exim-dev] [Bug 2255] TLS/SSL issue after upgading to 4.90

2018-03-13 Thread admin--- via Exim-dev
https://bugs.exim.org/show_bug.cgi?id=2255 --- Comment #9 from tomputer --- Hi Jeremy, Thank you for your quick response. I changed my settings: From: openssl_options=+no_sslv2 +no_sslv3 To: openssl_options=+no_sslv2 +no_sslv3 +single_dh_use +no_ticket Sadly that didn't

[exim-dev] [Bug 2255] TLS/SSL issue after upgading to 4.90

2018-03-13 Thread admin--- via Exim-dev
https://bugs.exim.org/show_bug.cgi?id=2255 --- Comment #10 from Thorsten --- You would have to set NO_TICKET on the IMAP server, not Exim. What you could try, although I do not know whether it works, is to set -no_ticket in Exim, thus disabling the disabling of

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

2018-03-14 Thread admin--- via Exim-dev
https://bugs.exim.org/show_bug.cgi?id=2250 --- Comment #17 from David Carter --- (In reply to David Carter from comment #16) > (In reply to David Carter from comment #14) > > > I will start bisection with DKIM disabled. > > 4a5cbaff2f9addfc9b4375a97ec6669bf18ee4db (Tue Sep 19

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

2018-03-14 Thread admin--- via Exim-dev
https://bugs.exim.org/show_bug.cgi?id=2250 Jeremy Harris changed: What|Removed |Added Assignee|ni...@exim.org |jgh146...@wizmail.org

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

2018-03-14 Thread admin--- via Exim-dev
https://bugs.exim.org/show_bug.cgi?id=2251 --- Comment #12 from Matthew Slowe --- Jeremy, I brought the new binary into service for a little while and noticed that, for addresses which would have triggered the segfault before, we're now getting: Rewrite of @kent.ac.uk

[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 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 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 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 2251] Segfault when LDAP lookup does not return a result

2018-03-14 Thread admin--- via Exim-dev
https://bugs.exim.org/show_bug.cgi?id=2251 --- Comment #13 from Jeremy Harris --- I guess it depends whether people think my initial take on the return value is correct or not. The LDAP library seems to be returning one attribute, with a zero-length value. I don't know

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

2018-03-15 Thread admin--- via Exim-dev
https://bugs.exim.org/show_bug.cgi?id=2251 --- Comment #16 from Matthew Slowe --- (In reply to Jeremy Harris from comment #15) > Where you have $value, put > ${if def:value {$value}{$local_part}} That's now live with the updated config and the following patch added on top

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

2018-03-15 Thread admin--- via Exim-dev
https://bugs.exim.org/show_bug.cgi?id=2251 --- Comment #17 from Jeremy Harris --- (In reply to Matthew Slowe from comment #16) > Is there anything else you'd like me to try? No, that's good. Thanks. -- You are receiving this mail because: You are on the CC list for the

[exim-dev] [Bug 2256] New: Need class grouping of variables

2018-03-15 Thread admin--- via Exim-dev
https://bugs.exim.org/show_bug.cgi?id=2256 Bug ID: 2256 Summary: Need class grouping of variables Product: Exim Version: 4.90 Hardware: All OS: All Status: NEW Severity: wishlist Priority:

[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 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 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

[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 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

[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 #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 2248] Lightweight redis cluster redirect method

2018-03-06 Thread admin--- via Exim-dev
https://bugs.exim.org/show_bug.cgi?id=2248 Graeme Fowler changed: What|Removed |Added Assignee|ni...@exim.org |gra...@graemef.net -- You

[exim-dev] [Bug 2248] Lightweight redis cluster redirect method

2018-03-06 Thread admin--- via Exim-dev
https://bugs.exim.org/show_bug.cgi?id=2248 Graeme Fowler changed: What|Removed |Added Resolution|--- |WORKSFORME

[exim-dev] [Bug 2248] Lightweight redis cluster redirect method

2018-03-06 Thread admin--- via Exim-dev
https://bugs.exim.org/show_bug.cgi?id=2248 --- Comment #2 from Jeremy Harris --- Testsuite coverage? -- You are receiving this mail because: You are on the CC list for the bug. -- ## List details at https://lists.exim.org/mailman/listinfo/exim-dev Exim details at

[exim-dev] [Bug 2248] Lightweight redis cluster redirect method

2018-03-06 Thread admin--- via Exim-dev
https://bugs.exim.org/show_bug.cgi?id=2248 --- Comment #4 from Graeme Fowler --- Created attachment 1073 --> https://bugs.exim.org/attachment.cgi?id=1073=edit redis cluster test case Test suite case for redis cluster, demonstrating at least one MOVED response -- You are

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

2018-03-07 Thread admin--- via Exim-dev
https://bugs.exim.org/show_bug.cgi?id=2250 Bug ID: 2250 Summary: Peculiarity with SMTP delivery in Exim 4.90.1 Product: Exim Version: 4.90 Hardware: x86 OS: Linux Status: NEW Severity: bug

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

2018-03-14 Thread admin--- via Exim-dev
https://bugs.exim.org/show_bug.cgi?id=2251 --- Comment #14 from Matthew Slowe --- (In reply to Jeremy Harris from comment #13) > I guess it depends whether people think my initial take on the return value > is correct or not. The LDAP library seems to be returning one

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

2018-03-14 Thread admin--- via Exim-dev
https://bugs.exim.org/show_bug.cgi?id=2251 --- Comment #15 from Jeremy Harris --- (In reply to Matthew Slowe from comment #14) > Is there a simple way in the expansion syntax to catch this and fail anyway > in the mean time? Where you have $value, put ${if def:value

[exim-dev] [Bug 2257] New: 4.90.1+fixes branch: pipe transport ends with: Socket operation on non-socket: Error 88

2018-03-20 Thread admin--- via Exim-dev
https://bugs.exim.org/show_bug.cgi?id=2257 Bug ID: 2257 Summary: 4.90.1+fixes branch: pipe transport ends with: Socket operation on non-socket: Error 88 Product: Exim Version: N/A Hardware: x86 OS: Linux

[exim-dev] [Bug 2257] 4.90.1+fixes branch: pipe transport ends with: Socket operation on non-socket: Error 88

2018-03-20 Thread admin--- via Exim-dev
https://bugs.exim.org/show_bug.cgi?id=2257 Jeremy Harris changed: What|Removed |Added Status|NEW |ASSIGNED

[exim-dev] [Bug 2257] 4.90.1+fixes branch: pipe transport ends with: Socket operation on non-socket: Error 88

2018-03-20 Thread admin--- via Exim-dev
https://bugs.exim.org/show_bug.cgi?id=2257 Git Commit changed: What|Removed |Added CC||g...@exim.org --- Comment #1 from

  1   2   >