This bug was fixed in the package exim4 - 4.95-4ubuntu3
---
exim4 (4.95-4ubuntu3) kinetic; urgency=medium
* d/p/lp1974214-segfault-smtp-delivery-0{1,2}.patch: Fix segfault when
there's an SMTP delivery attempt following a deferral. (LP: #1974214)
-- Sergio Durigan Junior
** Description changed:
[ Impact ]
When the user sends a message to someone, if the server responsible for
receiving this message defers it, and if there are other possible
servers (i.e., other servers listed as secondary MX) to try, exim4 will
segfault while trying to connect to the
** Description changed:
[ Impact ]
When the user sends a message to someone, if the server responsible for
receiving this message defers it, and if there are other possible
servers (i.e., other servers listed as secondary MX) to try, exim4 will
segfault while trying to connect to the
** Changed in: exim4 (Debian)
Status: Unknown => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1974214
Title:
Segfaults on verify callout, in _gnutls_trust_list_get_issuer
To
** Merge proposal linked:
https://code.launchpad.net/~sergiodj/ubuntu/+source/exim4/+git/exim4/+merge/423963
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1974214
Title:
Segfaults on verify
Launchpad has imported 48 comments from the remote bug at
http://bugs.exim.org/show_bug.cgi?id=2886.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
** Merge proposal linked:
https://code.launchpad.net/~sergiodj/ubuntu/+source/exim4/+git/exim4/+merge/423962
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1974214
Title:
Segfaults on verify
** Tags added: server-todo
** Changed in: exim4 (Ubuntu Jammy)
Status: Triaged => In Progress
** Changed in: exim4 (Ubuntu Kinetic)
Status: Triaged => In Progress
** Bug watch added: Debian Bug tracker #1004740
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004740
** Also
** Description changed:
+ [ Impact ]
+
+ When the user sends a message to someone, if the server responsible for
+ receiving this message defers it, and if there are other possible
+ servers (i.e., other servers listed as secondary MX) to try, exim4 will
+ segfault while trying to connect to the
Thank you for testing the package from the PPA and providing feedback,
Malcom and Raf.
I took some time today to try and come up with a reproducer for the bug,
since this is one of the requirements for a successful SRU to Jammy. So
far I haven't had any success, but I'll try to continue working
** Changed in: exim4 (Ubuntu Kinetic)
Assignee: (unassigned) => Sergio Durigan Junior (sergiodj)
** Changed in: exim4 (Ubuntu Jammy)
Assignee: (unassigned) => Sergio Durigan Junior (sergiodj)
** Changed in: exim4 (Ubuntu Jammy)
Importance: Medium => High
** Changed in: exim4
Previously exim would get SIGFPE on each mail delivery attempt. The PPA
version has been installed for almost 2 days and no more crashes.
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1974214
We've been running Sergio's exim 4.95-4ubuntu3~ppa2 for 27 hours so far
with no segfaults (previously it was segfaulting every few minutes) --
looks like the bug is fixed with those patches; thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
On Thursday, May 26 2022, Malcolm Scott wrote:
> Hi Sergio, unfortunately your patched package does not fix the problem
> -- we still see segfaults.
>
> From the upstream discussion, I think we may need this commit as well:
>
>
Hi Sergio, unfortunately your patched package does not fix the problem
-- we still see segfaults.
From the upstream discussion, I think we may need this commit as well:
https://git.exim.org/exim.git/commitdiff/8c74b00980bc7e3e479e8dfcd7c0008b2ac3f543
--
You received this bug notification
The corresponding commit that supposedly fixes this issue is:
https://git.exim.org/exim.git/commitdiff/5a8015582376ff3cc0c0d034d9237008b10d2164
I haven't tried to reproduce the problem, but if it's affecting Jammy
then we will need to SRU the fix, which means that we need a reproducer
first.
I
It looks like this is indeed an exim issue that was fixed in a recent
update. exim bug report can be found at:
https://bugs.exim.org/show_bug.cgi?id=2886
** Bug watch added: bugs.exim.org/ #2886
http://bugs.exim.org/show_bug.cgi?id=2886
** Changed in: exim4 (Ubuntu)
Importance: Undecided
I have forwarded this bug to upstream at
https://gitlab.com/gnutls/gnutls/-/issues/1374
** Bug watch added: gitlab.com/gnutls/gnutls/-/issues #1374
https://gitlab.com/gnutls/gnutls/-/issues/1374
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
You are right, 3.7.3-4 from jammy already contains the fix. I am
suspecting that the fix might be the cause of your segfault since this
was the last change in this part of the code and it seems to be a
regression introduced in jammy.
It looks like this bug hasn't been reported upstream yet. so we
@tobhe Thanks for looking into this. However that upstream bug was
apparently fixed in GnuTLS 3.7.4; I just tried libgnutls30
3.7.4-2ubuntu1 from kinetic and I still see these crashes in exim4.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Summary changed:
- Segfaults on sender verify callout, in _gnutls_trust_list_get_issuer
+ Segfaults on verify callout, in _gnutls_trust_list_get_issuer
** Description changed:
We are experiencing segfaults in exim since upgrading from impish
(4.94.2-7ubuntu2 with libgnutls30
21 matches
Mail list logo
