https://bugs.exim.org/show_bug.cgi?id=2750
--- Comment #3 from u34 ---
My mistake. Quoting
http://exim.org/exim-html-current/doc/html/spec_html/ch-string_expansions.html#SECTexpansionitems
By default, any of these errors causes the expansion to fail. However, if
you
supply a fifth substr
https://bugs.exim.org/show_bug.cgi?id=2750
--- Comment #2 from u34 ---
Trying to clarify the description:
Suppose I want to protect against failure to write the request string.
Such a failure is explicitly mentioned in the possible errors list.
Should I use
${readsocket{/socket/name}{request
https://bugs.exim.org/show_bug.cgi?id=2745
--- Comment #2 from u34 ---
Quoting
http://exim.org/exim-html-current/doc/html/spec_html/ch-file_and_database_lookups.html#SECTpartiallookup
Partial matching is requested by adding the string âpartial-â
Not just partial, but partial-. With a hy
https://bugs.exim.org/show_bug.cgi?id=2745
Jeremy Harris changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.exim.org/show_bug.cgi?id=2750
Jeremy Harris changed:
What|Removed |Added
Resolution|--- |INVALID
Status|NEW
https://bugs.exim.org/show_bug.cgi?id=2749
Jeremy Harris changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.exim.org/show_bug.cgi?id=2750
Bug ID: 2750
Summary: Documentation: readsocket: possible errors are listed,
but matching sub strings for are not
Product: Exim
Version: 4.94
Hardware: All
URL: htt
https://bugs.exim.org/show_bug.cgi?id=2749
Bug ID: 2749
Summary: Documentation: a minor consistency issue: Title has
eol. Body has end-of-line
Product: Exim
Version: 4.94
Hardware: All
URL: http://exim.org/ex
https://bugs.exim.org/show_bug.cgi?id=2748
Bug ID: 2748
Summary: Documentation: closing, but no opening, parenthesis
in doc/doc-docbook/spec.xfpt:10534
Product: Exim
Version: 4.94
Hardware: All
URL: http://e
https://bugs.exim.org/show_bug.cgi?id=2747
Heiko Schlittermann changed:
What|Removed |Added
Assignee|unalloca...@exim.org|h...@schlittermann.de
--
You are receivin
https://bugs.exim.org/show_bug.cgi?id=2747
--- Comment #7 from Heiko Schlittermann ---
And an additional question: can you reproduce it using swaks:
swaks -f mail...@example.org -t mail...@example.org --pipe 'exim -bh
192.168.178.9'
--
You are receiving this mail because:
You are on the CC lis
https://bugs.exim.org/show_bug.cgi?id=2747
--- Comment #6 from Heiko Schlittermann ---
Even with exim4-daemon-heavy (4.94.2-1) and the configuration you provided I
can't reproduce it.
Can you please attach the test config you used to this ticket? The config line
numbers differ between my and you
https://bugs.exim.org/show_bug.cgi?id=2747
--- Comment #5 from Nico Rittner ---
(In reply to Andreas Metzler from comment #2)
> Could you doublecheck with 4.94.2-2 (or the just uploaded 4.94.2-3)
i will try 4.94.2-2 as soon as possible.
at the moment i am unable to locate 4.94.2-3 anywhere.
Ni
https://bugs.exim.org/show_bug.cgi?id=2747
--- Comment #4 from Nico Rittner ---
hi Heiko,
(In reply to Heiko Schlittermann from comment #1)
> i've set up a plain Debian11 and installed the default exim4-daemon-light
Sorry, i forgot to mention that i used exim4-daemon-heavy for comparison,
beca
https://bugs.exim.org/show_bug.cgi?id=2747
--- Comment #3 from Heiko Schlittermann ---
http://ftp.debian.org/debian/dists/bullseye/main/binary-amd64/ is still at
4.94.2-1
--
You are receiving this mail because:
You are on the CC list for the bug.
--
## List details at https://lists.exim.org/ma
https://bugs.exim.org/show_bug.cgi?id=2747
--- Comment #2 from Andreas Metzler ---
(In reply to Nico Rittner from comment #0)
[...]
> tested with version 4.94.2 of debian "bullseye"
[...]
That would be 4.94.2-1?
Could you doublecheck with 4.94.2-2 (or the just uploaded 4.94.2-3)
Gentoo's pack
https://bugs.exim.org/show_bug.cgi?id=2733
--- Comment #15 from Heiko Schlittermann ---
While I believe your observations, I can't reproduce it.
4.94.2-31-503e55a2c is the version I'm running (latest commit on
exim-4.94.2+taintwarn).
LOG_FILE_PATH is set to "/opt/exim/log". `exim -C /dev/null -b
https://bugs.exim.org/show_bug.cgi?id=2733
--- Comment #14 from Andreas Metzler ---
(In reply to Andreas Metzler from comment #13)
> (In reply to Heiko Schlittermann from comment #11)
> > please can you check if the issue goes away once you remove the call to
> > open_logs() from src/transports/a
https://bugs.exim.org/show_bug.cgi?id=2747
Heiko Schlittermann changed:
What|Removed |Added
CC||h...@schlittermann.de
--- Comment #1 from
https://bugs.exim.org/show_bug.cgi?id=2747
Bug ID: 2747
Summary: segfault in smtp-receiving process after upgrading to
4.94.2
Product: Exim
Version: 4.93
Hardware: x86-64
OS: Linux
Status: NEW
https://bugs.exim.org/show_bug.cgi?id=2747
Nico Rittner changed:
What|Removed |Added
Priority|medium |high
Version|4.93
https://bugs.exim.org/show_bug.cgi?id=2746
Bug ID: 2746
Summary: Doc: without a link, and less then usual: expansion
fails as explicit failure on a lookup
Product: Exim
Version: 4.94
Hardware: All
URL: http:/
https://bugs.exim.org/show_bug.cgi?id=2733
--- Comment #13 from Andreas Metzler ---
(In reply to Heiko Schlittermann from comment #11)
> please can you check if the issue goes away once you remove the call to
> open_logs() from src/transports/appendfile.c
>
> I did so here (based on the latest c
https://bugs.exim.org/show_bug.cgi?id=2733
--- Comment #12 from Andreas Metzler ---
(In reply to Andreas Metzler from comment #10)
[...]
> ... so my log.c is identical what you get by
> a) checking out 4.94.2+fixes
> b) git merge exim-4.94.2+taintwarn
> c) patch -p1 < /tmp/patch2.patch
I think I
https://bugs.exim.org/show_bug.cgi?id=2733
--- Comment #11 from Heiko Schlittermann ---
Hi Andreas,
please can you check if the issue goes away once you remove the call to
open_logs() from src/transports/appendfile.c
I did so here (based on the latest commit on exim-4.94.2+taintwarn) and now
lo
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 Exim
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.
I
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?
I merged 4.94+fix
28 matches
Mail list logo
