Re: [exim-dev] [PATCH] DMARC: fix use-after-free in dmarc_dns_lookup

Hi Lorenz, Lorenz Brun via Exim-dev (Fr 14 Okt 2022 21:02:51 CEST): > This fixes a use-after-free in dmarc_dns_lookup where the result > of dns_lookup in dnsa is freed before the required data is copied out. > > Fixes: 9258363 ("DNS: explicit alloc/free of workspace") … Thanks for the fix, it

Re: [exim-dev] Exim 4.96-RC0 released

Andreas Metzler via Exim-dev (Sa 30 Apr 2022 10:34:23 CEST): > > People upgrading directly from < 4.93 to 4.96 would still have to deal > with hard breakage on upgrades, but requirig a two step upgrade might be > considered a fair compromise. Yes, that's something I'm thinking about too. 4.95:

Re: [exim-dev] [Bug 2855] $sender_host_address doesn't work well with hybrid (v4mapped) IPv4 representation

https://bugs.exim.org/show_bug.cgi?id=2855#c4 --- a/src/src/spool_out.c +++ b/src/src/spool_out.c @@ -185,7 +185,7 @@ if (sender_helo_name) spool_var_write(fp, US"helo_name", sender_helo_name); if (sender_host_address) { if (is_tainted(sender_host_address)) putc('-', fp); - fprintf(fp,

[exim-dev] messages from this list to outlook.com and hotmail.com users

(which is hard to detect if you're affected) or if the issue seems to be solved. Thank you. Best regards from Dresden/Germany Viele Grüße aus Dresden Heiko Schlittermann -- SCHLITTERMANN.de internet & unix support - Heiko Schlittermann, Dipl.-Ing.

Re: [exim-dev] Patch on exim-4.94+fixes applied after EOL

Heiko Schlittermann via Exim-dev (Do 13 Mai 2021 10:13:31 CEST): > I merged 4.94+fixes into 4.94.2+fixes (again). Not pushed yet, it's running the testsuite locally. -- Heiko signature.asc Description: PGP signature -- ## List details at https://lists.exim.org/mailman/listinfo/exim-dev E

Re: [exim-dev] Patch on exim-4.94+fixes applied after EOL

Good morning, Andreas Metzler via Exim-dev (Mi 12 Mai 2021 20:08:52 CEST): > Thanks, seems to have happened again with > c1faf04b865465894c7ca41ab4585fb69d4a5936. How about closing this branch > e.g. with a commit deleting all files? How to "close" a branch in Git? There seem to be many ways.

Re: [exim-dev] Patch on exim-4.94+fixes applied after EOL

Andreas Metzler via Exim-dev (Mi 12 Mai 2021 20:08:52 CEST): > On 2021-05-09 Heiko Schlittermann via Exim-dev wrote: > > Thanks, seems to have happened again with > c1faf04b865465894c7ca41ab4585fb69d4a5936. How about closing this branch > e.g. with a commit deleting all files?

Re: [exim-dev] Patch on exim-4.94+fixes applied after EOL

Andreas Metzler via Exim-dev (So 09 Mai 2021 08:06:11 CEST): > Hello, > > there is a patch on exim-4.94+fixes which was applied after 4.94.2, it > is therefore missing on exim-4.94.2+fixes. > > ed64b5c2f0f44db27ae48128fc97d5ad8406a28e Fix ${ipv6norm:} Thank you, it is merged now into

Re: [exim-dev] [Bug 2594] CNAME handling can break TLS certificate verification

Viktor Dukhovni via Exim-dev (So 14 Mär 2021 14:33:21 CET): > For the record, the expectation is: > > - Absent DANE TLSA records, the literal MX hostname, which is >of course insecurely obtained from MX records, so validation >is mostly an exercise in futility. It would only mean

[exim-dev] Postponed release of Exim 4.94+

on #Exim, the mailing lists and via direct contacts. Best regards from Dresden/Germany Viele Grüße aus Dresden Heiko Schlittermann -- SCHLITTERMANN.de internet & unix support - Heiko Schlittermann, Dipl.-Ing. (TU) - {fon,fax}: +49.351.802998{1,3} - g

Re: [exim-dev] typo in doc for Ratelimit options for what is being measured

u34--- via Exim-dev (Do 10 Sep 2020 18:25:06 CEST): > http://exim.org/exim-html-current/doc/html/spec_html/ch-access_control_lists.html#ratoptmea > has the following duplication: … > The dupliaction is that acl_smtp_rcpt is mentioned twice. Thanks. Fixed. Committed. Pushed. -- Heiko

[exim-dev] compatible with c99?

Hello, I'm referring to https://bugs.exim.org/show_bug.cgi?id=2585 The -std=c99 flag causes the build to fail. Is this expected behaviour? Or should we build cleanly using this flag too? Best regards from Dresden/Germany Viele Grüße aus Dresden Heiko Schlittermann

Re: [exim-dev] [Bug 2545] New: Allow disabling autogenerated selfsigned cert warning

admin--- via Exim-dev (Do 26 Mär 2020 18:30:27 CET): > So there should be a way to disable the warning or perhaps it should not be > shown at all, or at least only once a day. I can imagine an at-startup warning if tls_advertise_hosts is non-empty and no tls_certificate/tls_privatekey is

Re: [exim-dev] SPF not working properly

> a very simple example while exim's spf.c looks more complex Exim intercepts the DNS queries made from libspf2. Best regards from Dresden/Germany Viele Grüße aus Dresden Heiko Schlittermann -- SCHLITTERMANN.de internet & unix support - Heiko Schlitt

Re: [exim-dev] Fork in readconf.c

Nick, at the following GIT URL you'll find a branch heiko/x/cpanel/pre-flight git://git.exim.org/~heiko/exim.git Please be prepared that I'may change the history of this repo without notice. This is no official repository, though it is publicly available. The branch

Re: [exim-dev] Hard to understand doc enhancement 52af44332434a2a34ae30f3d0ac3b549d512e4cc

Andreas Metzler via Exim-dev (Mo 11 Mär 2019 19:34:50 CET): > Hello, > > Thanks, the description of what to do is great, but the imho the > rationale (what breaks?) should stay. a23acfd5c4366f1c4d97e87ac61ee841f39b819a -- Heiko signature.asc Description: PGP signature -- ## List details at

Re: [exim-dev] Hard to understand doc enhancement 52af44332434a2a34ae30f3d0ac3b549d512e4cc

Andreas Metzler via Exim-dev (Sa 09 Mär 2019 17:49:28 CET): > Hello, > > 52af44332434a2a34ae30f3d0ac3b549d512e4cc and the latest commit on 4.92 > fixes adds this change to spec: > > +&*Warning 3*&: Do not use an IPv4-mapped IPv6 address for a key; use the > +IPv4. Such addresses being searched

Re: [exim-dev] Missing Colon on I= for outbound mail?

Larry, do you agree with this commit? Especially with the commit message, as it mentions your name and address. Author: Heiko Schlittermann (HS12-RIPE) Date: Fri Mar 8 18:29:20 2019 +0100 Add missing colon when logging outgoing I= Credits to Larry Rosenman

Re: [exim-dev] Missing Colon on I= for outbound mail?

l pick this. Best regards from Dresden/Germany Viele Grüße aus Dresden Heiko Schlittermann -- SCHLITTERMANN.de internet & unix support - Heiko Schlittermann, Dipl.-Ing. (TU) - {fon,fax}: +49.351.802998{1,3} - gnupg encrypted messages are welcome

Re: [exim-dev] [Bug 2376] New: log_message doesn't log if connection is interrupted (which is quite unexpected) while other rules in the same acl are applied

ost [1.7/1m max:1] Best regards from Dresden/Germany Viele Grüße aus Dresden Heiko Schlittermann -- SCHLITTERMANN.de internet & unix support - Heiko Schlittermann, Dipl.-Ing. (TU) - {fon,fax}: +49.351.802998{1,3} - gnupg encrypted messages are welcome --

[exim-dev] New release candidate 4.92-RC3

), as well as the uploaded packages, are signed with my GPG key. Best regards from Dresden/Germany Viele Grüße aus Dresden Heiko Schlittermann -- SCHLITTERMANN.de internet & unix support - Heiko Schlittermann, Dipl.-Ing. (TU) - {fon,fax}: +49.351.802998

Re: [exim-dev] [exim] Exim 4.92-RC1

Paul Hecker via Exim-dev (So 16 Dez 2018 19:52:45 CET): > Hi, > for sure, thanks! exim 4.92-RC2 should work for you, doesn't it? -- Heiko signature.asc Description: PGP signature -- ## List details at https://lists.exim.org/mailman/listinfo/exim-dev Exim details at http://www.exim.org/ ##

[exim-dev] New release candidate 4.92-RC2

to this mail. This mail and the above mentioned tarballs are signed with my GPG key, which is the same as for RC1. Best regards from Dresden/Germany Viele Grüße aus Dresden Heiko Schlittermann -- SCHLITTERMANN.de internet & unix support - Heiko Schlitter

Re: [exim-dev] [exim] Exim 4.92-RC1

Please do not cross-post to lists and private addresses. Paul Hecker (Fr 14 Dez 2018 16:24:43 CET): > can no longer compile this version with my current Makefile as there is > WITH_CONTENT_SCAN=yes > enabled and all other scanner interfaces disabled (as DISABLE_MAL_CLAM=yes, >

[exim-dev] Exim 4.92-RC1

AND attached to ** this message. Best regards from Dresden/Germany Viele Grüße aus Dresden Heiko Schlittermann -- SCHLITTERMANN.de internet & unix support - Heiko Schlittermann, Dipl.-Ing. (TU) - {fon,fax}: +49.351.802998{1,3} - gnupg encrypted mess

[exim-dev] New Release

Hi, after a short chat with Jeremy we agreed, that I'll start the release process. More than 6 months since the last release are over and there is a bunch of additions, improvements, bug fixes. If any of you has some committs not pushed yet, please integrate them into the master branch until

Re: [exim-dev] buildfarm client proposal: tests configure support

Phil Pennock via Exim-dev (Sa 22 Sep 2018 07:06:21 CEST): > > I can't reach the box right now :\ Did you do anything like reboot it? > Otherwise, it's support ticket time if it doesn't come back. No, I just pulled the changes I pushed to the branch you created. And I started the run-whatever

Re: [exim-dev] buildfarm client proposal: tests configure support

Heiko Schlittermann via Exim-dev (Mi 19 Sep 2018 11:46:52 CEST): > I'll do so this evening (roughly UTC). Almost …. I made the changes, pushed it and pulled it into macstadiums /opt/buildfarm/home/code and started ./invoke.buildfarm But I do not see how you use test_configure_

Re: [exim-dev] buildfarm client proposal: tests configure support

Phil Pennock via Exim-dev (Di 18 Sep 2018 20:31:41 CEST): > On 2018-09-16 at 12:49 +0100, Jeremy Harris via Exim-dev wrote: > > The code addition looks reasonable on the surface. Go head and > > push it to master. > > I'm going to let Heiko make his suggested improvements. I'll do so this

Re: [exim-dev] buildfarm client proposal: tests configure support

or die; system("./configure", @{$EximBuild::conf{test_configure_args}) == 0 or die; system("make") == 0 or die; exit 0; }; @makeout = <$make>; close($make) or die; Maybe I missed the point, but If you'd like, I can try implementing

Re: [exim-dev] UTF-8 and Exim string operations

Heiko Schlittermann (Sa 18 Aug 2018 09:29:50 CEST): > > This. > > > > Add new operators, or options on current ones; don't > > change how they currently work (barring bugs). > > +1 After a little bit more thinking ${astrlen:Ötzi} yields 5 ${ustrlen

Re: [exim-dev] UTF-8 and Exim string operations

Jeremy Harris via Exim-dev (Fr 17 Aug 2018 13:03:33 CEST): > On 08/17/2018 05:03 AM, Phil Pennock via Exim-dev wrote: > > Anyone have strong feelings on how Exim should handle UTF-8 with > > operators such as ${length_1:STR} ? > > > > Document that the current operators work on bytes > > This. >

Re: [exim-dev] branch exim-4_91+fixes created

Renaud Allard via Exim-dev (Di 24 Apr 2018 00:05:08 CEST): > > Do you release a downloadable tar.gz archive of that branch? This would be > interesting for maintainers which are using a "ports" system like the BSDs. Currently not. But I'm thinking about it. But please, do not

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

e these 'NULL character' log entries on our system. Best regards from Dresden/Germany Viele Grüße aus Dresden Heiko Schlittermann -- SCHLITTERMANN.de ---- internet & unix support - Heiko Schlittermann, Dipl.-Ing. (TU) - {fon,fax}: +49.351.802998{1,3}

Re: [exim-dev] [Bug 2235] New: CVE-2018-6789

Phil Pennock (Di 13 Feb 2018 00:08:50 CET): > On 2018-02-09 at 15:32 +, Vsevolod Stakhov via Exim-dev wrote: > > It seems that FreeBSD is no longer considered in CVE early disclosure, > > isn't it? > > There has been no change from Exim's side in how this was communicated. >

Re: [exim-dev] committers

Andreas Metzler (Sa 03 Feb 2018 18:57:19 CET): … > I googled in vain and experimented a bit. Using cherry-pick instead of > merge seemed to work for me to change the committer. > > instead of git merge --ff > use git cherry-pick .. Yeah, probably I did exactly

Re: [exim-dev] committers

Jeremy Harris (Sa 03 Feb 2018 18:03:18 CET): … > Previouly for commits done using content supplied by other people > we have set the Author and left the Committer saying who did > the commit. I'd like that to continue. Yes, that was my intention too, but I didn't check if the

Re: [exim-dev] committers

On 030caf2a9 it worked another way, there I'm the committer, as I'd have expected. I'm not sure anymore how I did it with 030caf2a9. -- Heiko signature.asc Description: PGP signature -- ## List details at https://lists.exim.org/mailman/listinfo/exim-dev Exim details at

Re: [exim-dev] committers

Jeremy Harris (Sa 03 Feb 2018 17:41:07 CET): > Who is "Vladimir Panteleev " > and how did he acquire commit rights? I merged his pull request from github. And I suppsed that I'll be the committer then. Doesn't seem to have worked that way. What did I

Re: [exim-dev] [Bug 2206] error messages Berkeley DB error: BDB1565 DB->pget: method not permitted

he "relevant parts" of the configuration? There are no use > of berkeley-dbs in it which are obvious to me. No 'dbm' and/or 'ratelimit' in your config? Then the only (implicit) use of DBM are the retry databases. Is it feasible to remove them (rm $spooldir/db/*) Best r

Re: [exim-dev] [Bug 2206] New: error messages Berkeley DB error: BDB1565 DB->pget: method not permitted

way to reproduce the behaviour? Can you share your configuration? Ideally the relevant parts only. Best regards from Dresden/Germany Viele Grüße aus Dresden Heiko Schlittermann -- SCHLITTERMANN.de ---- internet & unix support - Heiko Schlitt

[exim-dev] Exim 4.89.1 released

(mirrors and http://ftp.exim.org/pub/exim/exim4/), signed with my (Heiko Schlittermann) signature. Alternatively you can use Git from git://git.exim.org/, signed tag exim-4_89_1. As an alternative to installing this release you may prefer to disable the SMTP chunking option by setting

[exim-dev] CVE-2017-16943, CVE-2017-16944

the chunking extension. chunking_advertise_hosts = Distros are advised to include these commits. Best regards from Dresden/Germany Viele Grüße aus Dresden Heiko Schlittermann -- SCHLITTERMANN.de internet & unix support - Heiko Schlittermann, Dipl.

Re: [exim-dev] [patch] Typo fix "psuedo"

Andreas Metzler (Sa 28 Okt 2017 13:22:31 CEST): > Hello, > > find atached a trivial patch to fix a typo in exipick's documentation. Thankyou (5dda37a2ea959801a0836097dc1e4ba43d78170b) -- Heiko signature.asc Description: PGP signature -- ## List details at

Re: [exim-dev] feature request for exim: query DNSBL providers' DNS servers directly

t such option already). This would solve the problem with overridden resolver configuration files (resolv.conf). Best regards from Dresden/Germany Viele Grüße aus Dresden Heiko Schlittermann -- SCHLITTERMANN.de internet & unix support - Heiko Sc

Re: [exim-dev] [Bug 2144] log failed (4xx) delivery attempts

Andrew C Aitchison (Mi 05 Jul 2017 16:54:30 CEST): > On Wed, 5 Jul 2017, ad...@bugs.exim.org wrote: I reformatted the entry to match the original long lines: > 2017-07-05 14:47:13 [19866] 1dSji4-0005AQ-GR <= h...@schlittermann.de > H=(blade.schlittermann.de)

Re: [exim-dev] [SOLVED] readv/writev

Hi James, James C. McPherson (Mo 03 Jul 2017 23:34:48 CEST): … > Both readv and writev are POSIX-standard functions, so they > should be available on all UNIX and UNIX-like systems. > > http://pubs.opengroup.org/onlinepubs/9699919799/functions/readv.html >

[exim-dev] 4.89+fixes

Hi, I get the feeling that with distribution of 4.89 the pressure to release some small fixes raises. I've prepared already a exim-4_89+fixes branch on git://git.exim.org/~heiko/exim.git It should include the following fixes as recommended by Jeremy 65e061b76867fix log line corruption

[exim-dev] [SOLVED] readv/writev

Heiko Schlittermann via Exim-dev <exim-dev@exim.org> (Mi 28 Jun 2017 00:16:11 CEST): > Hi, > > I'm sitting with bug 2130 and I'm wondering if anybody knows how > portable readv(2) and writev(2) are, on the platforms we'd like to > support. pwcheck.c uses writev(2) as does m

[exim-dev] readv/writev

Hi, I'm sitting with bug 2130 and I'm wondering if anybody knows how portable readv(2) and writev(2) are, on the platforms we'd like to support. Any hints? -- Heiko signature.asc Description: PGP signature -- ## List details at https://lists.exim.org/mailman/listinfo/exim-dev Exim details

[exim-dev] [h...@schlittermann.de: Re: CVE-2017-1000369 | Exim 4.89+fixes]

to the distro packagers some days ago: - Forwarded message from Heiko Schlittermann <h...@schlittermann.de> - Date: Sun, 18 Jun 2017 10:54:04 +0200 From: Heiko Schlittermann <h...@schlittermann.de> To: Operating system distro security contacts <dist...@vs.openwall.org>

Re: [exim-dev] [Bug 2118] sendmail -be and ${run} macro security problem

il" to be shipped with Exim, replacing the current practice (having a symlink sendmail -> exim) (The reason to do so is "apache-itk", which restricts some operations, so exim's setgid calls fail.) Best regards from Dresden/Germany Viele Grüße aus Dresden Heiko Schlitterman

Re: [exim-dev] Popping '.' from @INC

Todd Rinaldo via Exim-dev (Di 14 Feb 2017 19:36:01 CET): .. > > But, that's basically the same what taint mode does, isn't it? > > So, why not add -T to the #! line? This would give us @INC cleansing > > *and* additional taint checks. > > As far as I know, -T does not remove

Re: [exim-dev] Popping '.' from @INC

Heiko Schlittermann <h...@schlittermann.de> (Di 14 Feb 2017 18:03:25 CET): … > So better approach: > > BEGIN { > @INC = grep { !/^\// } @INC; > } Oh BEGIN { @INC = grep { /^\// } @INC; } But not compatible with Win32, is it? --

Re: [exim-dev] Popping '.' from @INC

Phil Pennock <p...@exim.org> (So 12 Feb 2017 12:30:48 CET): > On 2017-02-12 at 11:30 +0100, Heiko Schlittermann wrote: > > I saw, that '.' now gets pop()ed from @INC in various Perl scripts. > > > > Is there a special reason doing so? If we'd deal with security in min

[exim-dev] Popping '.' from @INC

Hi, I saw, that '.' now gets pop()ed from @INC in various Perl scripts. Is there a special reason doing so? If we'd deal with security in mind, we should use Perl's taint mode to make the scripts more secure. -- Heiko signature.asc Description: Digital signature -- ## List details at

Re: [exim-dev] Disabling BDAT by default for upcoming Debian stable release?

"RFC 3030" "CHUNKING" The CHUNKING extension (RFC3030) will be advertised in the EHLO message to these hosts. Hosts may use the BDAT command as an alternate to DATA. +(Defaulting this option to "unset" is Debian specific. Nativ Exims +default to "*".

[exim-dev] [h...@schlittermann.de: [oss-security] CVE-2016-9963 (Was: CVE Request - Exim 4.69-4.87 - disclosure of private information)]

Hello, in case you missed this on one of the other channels: Heiko Schlittermann <h...@schlittermann.de> (Fr 16 Dez 2016 00:36:45 CET): … > Product:Exim > Versions: 4.69 -> 4.87 > Impact: Possible leak of private information to a remote attacker > Reference:

Re: [exim-dev] Bug in string expansion of exim configuration?

ere. The -dev list is more for developers/programmers But of course, you're welcome on both lists. Best regards from Dresden/Germany Viele Grüße aus Dresden Heiko Schlittermann -- SCHLITTERMANN.de internet & unix support - Heiko Schlittermann, Dipl

[exim-dev] Please do not push to git.exim.org master

ublic SSH key if I do not have it already from January this year. Best regards from Dresden/Germany Heiko -- SCHLITTERMANN.de ---- internet & unix support - Heiko Schlittermann, Dipl.-Ing. (TU) - {fon,fax}: +49.351.802998{1,3} - gnupg encrypted messages

Re: [exim-dev] DKIM not built by default, but configure.default contains control=dkim_disable_verify

ccount to bugzilla for reporting a > bug, sorry. It is currently disabled, I think. (There was some spammer) Best regards from Dresden/Germany Viele Grüße aus Dresden Heiko Schlittermann -- SCHLITTERMANN.de internet & unix support - Heiko S

Re: [exim-dev] [exim] tls_eccurve = auto (Was: Exim 4.88 RC5 uploaded)

Heiko Schlittermann <h...@schlittermann.de> (Fr 02 Dez 2016 14:40:34 CET): … > now tls_eccurve = auto is the default and should work in any OpenSSL > version. For OpenSSL < 1.0.2 it falls back to prime256v1. For more > recent OpenSSL versions it uses the librar

[exim-dev] tls_eccurve = auto (Was: Exim 4.88 RC5 uploaded)

est regards from Dresden/Germany Viele Grüße aus Dresden Heiko Schlittermann -- SCHLITTERMANN.de internet & unix support - Heiko Schlittermann, Dipl.-Ing. (TU) - {fon,fax}: +49.351.802998{1,3} - gnupg encrypted messages are welcome --- key ID: F

Re: [exim-dev] Administriva: Bugzilla spam

Nigel Metheringham (Fr 25 Nov 2016 11:44:55 CET): > Sorry, I obviously wasn't being clear (then again, in hurry). Thank you for the clarification. And the changes. -- Heiko signature.asc Description: Digital signature -- ## List details at

Re: [exim-dev] Administriva: Bugzilla spam

Nigel Metheringham (Do 24 Nov 2016 23:33:08 CET): > We have had a few cases of someone deciding to spam bugzilla with spammy > content bug reports. Bugzilla is not very good at defending against > these, and unfortunately Bugzilla feeds into the exim-dev list. > > I have put

Re: [exim-dev] [exim] Exim 4.88 RC and configuring qualify_domain

ld? What for? Yes, you got $h_to: and $h_replay-to: Best regards from Dresden/Germany Viele Grüße aus Dresden Heiko Schlittermann -- SCHLITTERMANN.de internet & unix support - Heiko Schlittermann, Dipl.-Ing. (TU) - {fon,fax}: +49.351.802998{1

[exim-dev] About 4.87+fixes

Hello, I'm about to prepare a 4.87+fixes release. Is there any important commit since the release of exim-4_87 that should make it into this "inofficial" maintenance branch? Best regards from Dresden/Germany Viele Grüße aus Dresden Heiko Schlittermann -- SCHLIT

Re: [exim-dev] Exim4 spool directory symlink local root escalation - does this apply to 4.87?

sue in my environment. As long as I can't reproduce it, I do not change anything in Exim. Best regards from Dresden/Germany Viele Grüße aus Dresden Heiko Schlittermann -- SCHLITTERMANN.de internet & unix support - Heiko Schlittermann, Dipl.-Ing. (TU) -

Re: [exim-dev] [Bug 1832] New: Log reason for disconnection, as returned by remote host

nection in response to HELO > === 1) Can you 'tcpdump' the connection? To be sure if the response was sent. 2) What's the setting of your log_selector? Best regards from Dresden/Germany Viele Grüße aus Dresden Heiko Schlittermann -- SCHLITTERMANN.de ---- in

Re: [exim-dev] Git unknotting

Nigel Metheringham (Do 07 Apr 2016 14:38:58 CEST): > Github won't let you push --force unless you unprotect the branch first... > > OK, both repos have the right version now, and the sync process between > them is working again. It could have been much worse - if there had >

Re: [exim-dev] Git unknotting

LSE, FALSE); The latter being the right one (03f68c52bd7d014304b03ad6394343350ea71b2c) Sorry for the mess. Best regards from Dresden/Germany Viele Grüße aus Dresden Heiko Schlittermann -- SCHLITTERMANN.de -------- internet & unix support - Heiko Schlittermann, Dipl.-Ing. (TU) -

Re: [exim-dev] [Bug 1811] exim -bt vs exim -bv uses different uid/gid

ser ... I'd bet, it does opening and reading the .forward file as the user, after the check_local_user precondition. Best regards from Dresden/Germany Viele Grüße aus Dresden Heiko Schlittermann -- SCHLITTERMANN.de ---- internet & unix support - Heiko Schl

Re: [exim-dev] warning on missing environment option

ept -bV). BTW the warning above indicates that you don't have the latest version, as in the latest version add_environment isn't suggested as a solution anymore (and isn't a solution anymore, only keep_environment is counted as an indication that "you got it".) Best regards from Dresde

Re: [exim-dev] warning on missing environment option

Hi Arkadiusz, Heiko Schlittermann <h...@schlittermann.de> (Do 17 Mär 2016 07:51:57 CET): > > and it does that in weird conditions like: > > > > # exim -bpc > > 0 > > (silent) > > Oh, why? Don't know. I'll investigate this. Conclusion: The warning abo

Re: [exim-dev] warning on missing environment option

Hi, Heiko Schlittermann <h...@schlittermann.de> (Do 10 Mär 2016 19:59:46 CET): > Setting keep_environment to some, even an empty value clearly indicates > the users intention. If only add_environment is there, it's not obvious > that the "default" environment is empty. In

Re: [exim-dev] warning on missing environment option

t; does not suppress > a warning) seems to be a bug as it is not documented. Yes, but I'd like to turn it the other way round: the use of add_environment doesn't influence the warnings at all. And, I can imagine that future release of Exim do not issue that warning at all anymore, beca

Re: [exim-dev] Security release for CVE-2016-1531: 4.84.2, 4.85.2, 4.86.2, 4.87 RC5]

rmany Viele Grüße aus Dresden Heiko Schlittermann -- SCHLITTERMANN.de internet & unix support - Heiko Schlittermann, Dipl.-Ing. (TU) - {fon,fax}: +49.351.802998{1,3} - gnupg encrypted messages are welcome --- key ID: F69376CE - ! key id 7C

Re: [exim-dev] Security release for CVE-2016-1531: 4.84.2, 4.85.2, 4.86.2, 4.87 RC5]

Heiko Schlittermann <h...@schlittermann.de> (Do 03 Mär 2016 00:16:58 CET): > Please attach the environment.c file and send it to me. > > > Replace: > if (unsetenv(CS name) < 0) return FALSE; > else p = USS environ; /* RESTART from the beginning */ >

Re: [exim-dev] Security release for CVE-2016-1531: 4.84.2, 4.85.2, 4.86.2, 4.87 RC5]

Please, which commit/version of the source do you use? > >int. That's another issue. Changing the if … FALSE; > >to > > unsetenv(CS name); > > > >should work. > > I still get > > gcc environment.c > environment.c: In function `cleanup_environment': > environment.c:54: void value not ignored

[exim-dev] Security release for CVE-2016-1531: 4.84.2, 4.85.2, 4.86.2, 4.87 RC5]

As written in the PM, your unsetenv() returns void, my returns int. That's another issue. Changing the if … FALSE; to unsetenv(CS name); should work. Best regards from Dresden/Germany Viele Grüße aus Dresden Heiko Schlittermann -- SCHLITTERMANN.de -

Re: [exim-dev] Cutthrough routing: data loss on client side error

Daryl Richards <da...@isletech.net> (Fr 22 Jan 2016 19:34:52 CET): … > Yes, that seems to have solved the issue. The patch is already on its way into exim-4_86+fixes Best regards from Dresden/Germany Viele Grüße aus Dresden Heiko Schlittermann -- SCHLITT

Re: [exim-dev] LDAP multiline attribute oddity

Graeme Fowler (Di 19 Jan 2016 11:51:57 CET): > On 18 Jan 2016, at 18:22, Jeremy Harris wrote: > > > > You could rewrite that "ldap_get_values()" call, for which there's > > a "deprecated" note in my (Fedora 23) include file, with > > "ldap_get_values_len()"

Re: [exim-dev] LDAP multiline attribute oddity

Jeremy Harris (Di 19 Jan 2016 12:21:28 CET): (…) > > Just for my understanding… > > the, value of the attribute starts with a '\0' byte? > > If it does - or, indeed, has embedded NULs - Exim just > isn't going to deal kindly with it/them. Exim strings > are C-style

Re: [exim-dev] LDAP multiline attribute oddity

Jeremy Harris (Di 19 Jan 2016 13:18:25 CET): … > > If > > they contain \0 after transforming to char[], then we can't use them > > anyway, can we? > > Correct. That LDAP use just isn't > supported by Exim. Got it :) Thank you for clarification. -- Heiko signature.asc

[exim-dev] Cutthrough routing: data loss on client side error

51 [10762] 1aLF8a-0002na-5D >> {zensored} R=dnslookup T=remote_smtp H=ssl.schlittermann.de [212.80.235.130] X=TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256 CV=no DN="/C=DE/ST=Sachsen/L=Dresden/O=Heiko Schlittermann/CN=ssl.schlittermann.de/emailAddress=postmas...@schlittermann.de" C=&q

Re: [exim-dev] LDAP multiline attribute oddity

? Best regards from Dresden/Germany Viele Grüße aus Dresden Heiko Schlittermann -- SCHLITTERMANN.de ---- internet & unix support - Heiko Schlittermann, Dipl.-Ing. (TU) - {fon,fax}: +49.351.802998{1,3} - gnupg encrypted messages are welcome ---

Re: [exim-dev] LDAP multiline attribute oddity

Graeme Fowler <gra...@graemef.net> (Mo 18 Jan 2016 20:30:49 CET): > On Mon, 2016-01-18 at 20:19 +0100, Heiko Schlittermann wrote: > > Thus, the the is a single value, but spread across multiple lines? > > Yes. > > > Can you show an example result from the correspon

Re: [exim-dev] LDAP multiline attribute oddity

The sed line was wrong… should read `sed signature.asc Description: Digital signature -- ## List details at https://lists.exim.org/mailman/listinfo/exim-dev Exim details at http://www.exim.org/ ##

Re: [exim-dev] Clang warnings for RC2 #3

the environment you used? Ideally it's just one of the current Linux distributions I can mimic in a docker container for testing. Best regards from Dresden/Germany Viele Grüße aus Dresden Heiko Schlittermann -- SCHLITTERMANN.de internet & unix sup

Re: [exim-dev] Next Exim release

resden/Germany Viele Grüße aus Dresden Heiko Schlittermann -- SCHLITTERMANN.de internet & unix support - Heiko Schlittermann, Dipl.-Ing. (TU) - {fon,fax}: +49.351.802998{1,3} - gnupg encrypted messages are welcome --- key ID: F69376CE - ! key i

[exim-dev] tls_advertise_hosts issues too many warnings (!?)

Dresden/Germany Viele Grüße aus Dresden Heiko Schlittermann -- SCHLITTERMANN.de internet & unix support - Heiko Schlittermann, Dipl.-Ing. (TU) - {fon,fax}: +49.351.802998{1,3} - gnupg encrypted messages are welcome --- key ID: F69376CE

Re: [exim-dev] -bP configure_file ---> -bP config_file

Heiko Schlittermann <h...@schlittermann.de> (Fr 13 Nov 2015 09:53:29 CET): > Ouoh, just after pushing it: `hide` doesn't seem to be honoured always. > I'll fix this instantly. fixed. -- Heiko signature.asc Description: Digital signature -- ## List details at https://lists.exim

[exim-dev] Maintenance branch 4_86+fixes updated

already a cloned repo: git fetch origin exim-4_86+fixes git co exim-4_86+fixes It passed the testsuite for {debian7,debian8,fedora21,opensuse}-{openssl,gnutls} with the usual failures. Best regards from Dresden/Germany Viele Grüße aus Dresden Heiko Schlittermann

Re: [exim-dev] Interesting behaviour

le Grüße aus Dresden Heiko Schlittermann -- SCHLITTERMANN.de ---- internet & unix support - Heiko Schlittermann, Dipl.-Ing. (TU) - {fon,fax}: +49.351.802998{1,3} - gnupg encrypted messages are welcome --- key ID: F69376CE - ! key id 7CBF764A and

Re: [exim-dev] Interesting behaviour

our ACL. But, I believe there is some variable containing the complete command arguments from the current SMTP command, maybe you can check this. Best regards from Dresden/Germany Viele Grüße aus Dresden Heiko Schlittermann -- SCHLITTERMANN.de internet &am

Re: [exim-dev] Dovecot auth socket correctness check

thentication socket type mismatch (connected to auth-master instead of > auth-client) I'll check that, unless some other of the developers does it. If it works (it will, I suppose) I can integrate it into the Exim source tree. Best regards from Dresden/Germany Viele Grüße aus Dresden Heiko

Re: [exim-dev] Dovecot auth socket correctness check

Hi Timo, Heiko Schlittermann <h...@schlittermann.de> (So 11 Okt 2015 18:01:41 CEST): > Hi Timo, > Timo Sirainen <t...@iki.fi> (Fr 01 Aug 2014 13:16:16 CEST): … sorry for the confusion, your message is more than one year old and your patch is already included in the sources.

Re: [exim-dev] [Bug 1684] Malformed headers which exceed length spec willingly passed to remote servers

e are some standards and that their mails have to follow that standards. (Starting with mistyped addresses that people want to have delivered anyway, continued with broken headers, long message body lines, …) Most other parts of our life do not tolerate violating some rules. Why mail should?

Re: [exim-dev] Exim 4.86 segfault on FreeBSD 10.2

git repository. Best regards from Dresden/Germany Viele Grüße aus Dresden Heiko Schlittermann -- SCHLITTERMANN.de internet & unix support - Heiko Schlittermann, Dipl.-Ing. (TU) - {fon,fax}: +49.351.802998{1,3} - gnupg encrypted messages are welcome ---

[exim-dev] Update on maintenance branch exim-4_86+fixes [c4dcf906ceb3]

,openssl} For all items covered see the ChangeLog of the commit c4dcf906ceb3a45c6b30f76476d73ca836b262cd Best regards from Dresden/Germany Viele Grüße aus Dresden Heiko Schlittermann -- SCHLITTERMANN.de internet & unix support - Heiko Schlittermann,

  1   2   3   >