Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.bugs.dist > #1102816
| From | Gedalya <gedalya@gedalya.net> |
|---|---|
| Newsgroups | linux.debian.bugs.dist |
| Subject | Bug#1004740: exim4: SIGSEGV (maybe attempt to write to immutable memory) when sending a mail; message frozen |
| Date | 2022-05-11 17:20 +0200 |
| Message-ID | <ElWi6-eMGS-1@gated-at.bofh.it> (permalink) |
| References | (4 earlier) <DMrC9-pt-7@gated-at.bofh.it> <Ely65-eyfa-1@gated-at.bofh.it> <ElyfL-eyiX-1@gated-at.bofh.it> <DM1HI-1iW-3@gated-at.bofh.it> <ElyfL-eyiX-1@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
[Multipart message — attachments visible in raw view] - view raw
On 5/10/22 21:30, Gedalya wrote: > I forgot to mention: google seems to be closing the connection immediately after the deferral, causing the logged TLS error lines, and this seems to be a necessary component for this issue No. That's incorrect. I've reproduced this with plain Debian-built exim4-daemon-light 4.95-5 and 4.96~RC0-1, with the remote setup being my two MX servers running exim with a simple "defer" acl verb, not closing the connection. The behavior seems quite similar with both exim versions. See attachments. I'm a little dazzled by the variety of crashes I've seen so far: smtp_setup_conn > tls_client_start > verify_certificate, and during ARC signing, but it could be just noise so I'll leave it alone for now.
Back to linux.debian.bugs.dist | Previous | Next — Next in thread | Find similar | Unroll thread
Bug#1004740: exim4: SIGSEGV (maybe attempt to write to immutable memory) when sending a mail; message frozen Gedalya <gedalya@gedalya.net> - 2022-05-11 17:20 +0200 Bug#1004740: exim4: SIGSEGV (maybe attempt to write to immutable memory) when sending a mail; message frozen Matt Corallo <rpbdbrciwe@mattcorallo.com> - 2022-05-16 07:20 +0200
csiph-web