Your message dated Thu, 26 Sep 2019 19:24:25 +0200
with message-id <[email protected]>
and subject line Re: Bug#741412: exim4: process crashed with signal 11 while 
delivering
has caused the Debian Bug report #741412,
regarding exim4: process crashed with signal 11 while delivering
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
741412: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=741412
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: exim4
Version: 4.80-7
Severity: important

After upgradading debian to woody I started to get exim crashed for some
emails (a few emails for few thousand deliveries). 

Email is delivered to exim, put into the queue, and never delivered.
Running the queue gives error message: 

        queue run: process 2795 crashed with signal 11 while delivering 
1WNfPp-0000ft-T3

I have taken that email and tried to modify it to make the smallest
possible data that causes exim crashes. The file "test.txt" contains
such data (tab idented): 

        To: zbigniew grzybacz <[email protected]>, 
         =?ISO-8859-2?Q?Stanis=B3aw_Filas?= <[email protected]>, 
         [email protected], [email protected]
        Subject: test

        crash test

Command "cat -A text.txt" gives: 

        To: zbigniew grzybacz <[email protected]>, $
         =?ISO-8859-2?Q?Stanis=B3aw_Filas?= <[email protected]>, $
         [email protected], [email protected]$
        Subject: test$
        $
        crash test$

And here is output of " cat test.txt | base64": 

        
VG86IHpiaWduaWV3IGdyenliYWN6IDx6Ymlnbmlldy5ncnp5YmFjekBkdWJpZWx2aXRydW0ucGw+
        
LCAKID0/SVNPLTg4NTktMj9RP1N0YW5pcz1CM2F3X0ZpbGFzPz0gPHN0YW5pc2xhdy5maWxhc0Bk
        
dWJpZWx2aXRydW0ucGw+LCAKIHBhdGFsaXRhLm1hcmNpbkBkdWJpZWx2aXRydW0ucGwsIHBoY2JA
        ZHViaWVsdml0cnVtLnBsClN1YmplY3Q6IHRlc3QKCmNyYXNoIHRlc3QK

Now I feed this file to exim: "cat test.txt | exim -t". No errors
reported. 

Then I run "exim -qf", and get error message: 

        2014-03-12 10:25:38 queue run: process 2795 crashed with signal 11 
while delivering 1WNfPp-0000ft-T3

Command "exim -bp" shows: 

         0m   503 1WNfPp-0000ft-T3 <[email protected]>
                  [email protected]
                  [email protected]
                  [email protected]
                  [email protected]

What is STRANGE: when running queue in debugging mode "exim -d -qf"
message is DELIVERED. 
        


-- Package-specific info:
Exim version 4.80 #3 built 02-Jan-2013 19:40:22
Copyright (c) University of Cambridge, 1995 - 2012
(c) The Exim Maintainers and contributors in ACKNOWLEDGMENTS file, 2007 - 2012
Berkeley DB: Berkeley DB 5.1.29: (October 25, 2011)
Support for: crypteq iconv() IPv6 GnuTLS move_frozen_messages DKIM
Lookups (built-in): lsearch wildlsearch nwildlsearch iplsearch cdb dbm dbmjz 
dbmnz dnsdb dsearch nis nis0 passwd
Authenticators: cram_md5 plaintext
Routers: accept dnslookup ipliteral manualroute queryprogram redirect
Transports: appendfile/maildir/mailstore autoreply lmtp pipe smtp
Fixed never_users: 0
Size of off_t: 8
Configuration file is /etc/exim4/exim4.conf

-- System Information:
Debian Release: 7.4
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 3.2.0-4-686-pae (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/bash

Versions of packages exim4 depends on:
ii  debconf [debconf-2.0]  1.5.49
ii  exim4-base             4.80-7
ii  exim4-daemon-light     4.80-7

exim4 recommends no packages.

exim4 suggests no packages.

-- debconf information:
  exim4/drec:

--- End Message ---
--- Begin Message ---
On 2019-09-24 Leszek Dubiel <[email protected]> wrote:

> Since 2017 I don't get that error anymore. Please close the bug.

Thank you for the heads-up, closing.

cu Andreas

--- End Message ---

Reply via email to