[exim-dev] [Bug 2346] unseen in system_filter works randomly
https://bugs.exim.org/show_bug.cgi?id=2346 --- Comment #2 from remikk --- (In reply to Jeremy Harris from comment #1) > Show a debug run for such a mail. Preferably without obfuscating it as that > makes it harder to tell what is going on. I apologize for reporting this too quickly as a bug, but the problem is probably with the add-on called blockcracking, which is added to the exim configuration by Directadmin. I reported it to them. -- 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 http://www.exim.org/ ##
[exim-dev] [Bug 2224] DKIM: validation error: RSA_LONG_LINE
https://bugs.exim.org/show_bug.cgi?id=2224 --- Comment #9 from Bjoern Jacke --- it might be worth mentioning that the section 4.5.3.1.6 which was mentioned in comment 1 also contains the sentence "This number may be increased by the use of SMTP Service Extensions." This means long lines are not generally disallowed. >From my understanding BINARYMIME from RFC 3030 also allows arbitrary lenghts here as long as the chunksize is not exceeded. Also RFC 7103 says in section 6 that for binary mode SMTP (BINARYMIME) CRLF is not a line separator. This means that for SMTP connections using the chunking extension this is actually a valid bug in exim. Recent Postfix releases for example can send such messages that trigger this DKIM signing bug in exim. A workaround for this problem is to set chunking_advertise_hosts = in the exim configuration. It would be a pitty if this bug stays a wontfix. -- 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 http://www.exim.org/ ##
[exim-dev] [Bug 2348] New: 4.92-RC1 M treated as G in check_spool_space and check_log_space
https://bugs.exim.org/show_bug.cgi?id=2348 Bug ID: 2348 Summary: 4.92-RC1 M treated as G in check_spool_space and check_log_space Product: Exim Version: N/A Hardware: x86-64 OS: OpenBSD Status: NEW Severity: bug Priority: medium Component: General execution Assignee: ni...@exim.org Reporter: exim-b...@km.krot.org CC: exim-dev@exim.org In 4.92-RC1, when configuration file sets check_spool_space and check_log_space, Exim treats M as G. Below is example configuration file with just four lines: km@build ~/src/exim-git $ cat /etc/exim/configure check_spool_space = 10M check_log_space = 10M message_size_limit = 50M bounce_return_size_limit = 100K When exim -bP is run to print values of the options, the first and second are no longer Megabytes, but Gigabytes: km@build ~/src/exim-git $ ./src/build-OpenBSD-amd64/exim -bP check_spool_space check_log_space message_size_limit bounce_return_size_limit check_spool_space = 10G check_log_space = 10G message_size_limit = 50M bounce_return_size_limit = 100K -- 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 http://www.exim.org/ ##
[exim-dev] [Bug 2348] 4.92-RC1 M treated as G in check_spool_space and check_log_space
https://bugs.exim.org/show_bug.cgi?id=2348 exim-b...@km.krot.org changed: What|Removed |Added Assignee|ni...@exim.org |h...@schlittermann.de --- Comment #1 from exim-b...@km.krot.org --- 11:47 < jgh_> that's down to hs12 - he's doing the work this time around -- 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 http://www.exim.org/ ##
[exim-dev] [Bug 2348] 4.92-RC1 M treated as G in check_spool_space and check_log_space
https://bugs.exim.org/show_bug.cgi?id=2348 Jeremy Harris changed: What|Removed |Added Status|NEW |ASSIGNED Assignee|h...@schlittermann.de |jgh146...@wizmail.org -- 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 http://www.exim.org/ ##
[exim-dev] [Bug 2348] 4.92-RC1 M treated as G in check_spool_space and check_log_space
https://bugs.exim.org/show_bug.cgi?id=2348 --- Comment #2 from exim-b...@km.krot.org --- 13:39 < jgh_> unfair comment #1 there; that was about the issuance of RC1, not the cause of this bug 13:40 < km_> ah, sorry - I thought I'd explain why I assigned to hs12 13:43 < km_> my understanding was that he could have a look at this (for some reason) - not because of the cause, but for some reason 13:44 < km_> I'll add a comment about this for record :) -- 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 http://www.exim.org/ ##
[exim-dev] [Bug 2350] New: OCSP Problem for outgoing mails
https://bugs.exim.org/show_bug.cgi?id=2350 Bug ID: 2350 Summary: OCSP Problem for outgoing mails Product: Exim Version: 4.91 Hardware: x86 OS: Linux Status: NEW Severity: bug Priority: medium Component: TLS Assignee: jgh146...@wizmail.org Reporter: tors...@tributh.net CC: exim-dev@exim.org Hi, when I use OCSP-Must-Stable certificates with the OID setting: 1.3.6.1.5.5.7.1.24=DER:30:03:02:01:05 for the CSR to get a certificate, I must use later use tls_certificate tls_privatekey and tls_ocsp_file settings. If I have not got a valid tls_ocsp_file than the stapling fails and an increasing amount of mailclients can't connect to the SMTP port, because of failing TLS verification. So there is no problem for the incoming way (if you take care of having a valid staple-file), but what happens when I connect to another SMTP Server and I am requested to show my certificate? In the remote_smtp transport section, I am not able to enable stapling. I get option "tls_ocsp_file" unknown So, I show an OCSP-Must-Staple Certificate, but the OCSP stapled part is missing. In a way I show an invalid cert. Actually it didn't show any problem, but that could change fast, during the increasing deployment of safer TLS implementations. Torsten -- 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 http://www.exim.org/ ##
[exim-dev] [Bug 2349] New: Add SCRAM-SHA-1/256 Authentication Methods in Client mode
https://bugs.exim.org/show_bug.cgi?id=2349 Bug ID: 2349 Summary: Add SCRAM-SHA-1/256 Authentication Methods in Client mode Product: Exim Version: N/A Hardware: x86-64 OS: Linux Status: NEW Severity: wishlist Priority: medium Component: SMTP Authentication Assignee: jgh146...@wizmail.org Reporter: tors...@tributh.net CC: exim-dev@exim.org When I run exim on a satellite System to send mails only to a smarthost with authentication, I find no way to use SCRAM-SHA-1 as a client setting. When I check the gsasl code I can only find the settings for the server version. To prevend the exposure of a plaintext password when for whatever reasons DNS/TLS could be redirected to a malicious system. If SCRAM-SHA-1 could be added, the changes to add also SCRAM-SHA-256 should be small. Torsten -- 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 http://www.exim.org/ ##
[exim-dev] [Bug 2348] 4.92-RC1 M treated as G in check_spool_space and check_log_space
https://bugs.exim.org/show_bug.cgi?id=2348 Git Commit changed: What|Removed |Added CC||g...@exim.org --- Comment #3 from Git Commit --- Git commit: https://git.exim.org/exim.git/commitdiff/fa792e2ce96b4d6f9e39e350ec967ccb833277a7 commit fa792e2ce96b4d6f9e39e350ec967ccb833277a7 Author: Jeremy Harris AuthorDate: Fri Dec 14 14:03:18 2018 + Commit: Jeremy Harris CommitDate: Fri Dec 14 14:07:29 2018 + fix parsing of option type kint (integer, stored in k). bug 2348 broken-by: a45431fa71 src/src/readconf.c | 13 ++--- test/paniclog/0415 | 2 +- test/scripts/-Basic/0415 | 2 +- test/stderr/0415 | 2 +- test/stdout/0415 | 2 +- 5 files changed, 10 insertions(+), 11 deletions(-) -- 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 http://www.exim.org/ ##
