Your message dated Thu, 24 Feb 2005 18:53:36 +0000
with message-id <[EMAIL PROTECTED]>
and subject line Bug#296784: exim: some error messages live infinitely
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--------------------------------------
Received: (at submit) by bugs.debian.org; 24 Feb 2005 16:44:27 +0000
>From [EMAIL PROTECTED] Thu Feb 24 08:44:27 2005
Return-path: <[EMAIL PROTECTED]>
Received: from 169-249-2s.infos.ru (bilbo.gorod-spb.ru) [212.176.249.169]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1D4M6F-0007Bi-00; Thu, 24 Feb 2005 08:44:27 -0800
Received: from amavis by bilbo.gorod-spb.ru with scanned-ok (Exim 3.35 #1
(Debian))
id 1D4M6C-0003UC-00
for <[EMAIL PROTECTED]>; Thu, 24 Feb 2005 19:44:24 +0300
Received: from bilbo.gorod-spb.ru ([127.0.0.1])
by localhost (bilbo [127.0.0.1]) (amavisd-new, port 10024) with ESMTP
id 12819-03 for <[EMAIL PROTECTED]>;
Thu, 24 Feb 2005 19:44:21 +0300 (MSK)
Received: from al by bilbo.gorod-spb.ru with local (Exim 3.35 #1 (Debian))
id 1D4M69-0003U5-00; Thu, 24 Feb 2005 19:44:21 +0300
From: Al Nikolov <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: exim: some error messages live infinitely
X-Mailer: reportbug 1.50
Date: Thu, 24 Feb 2005 19:44:21 +0300
Message-Id: <[EMAIL PROTECTED]>
X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at gorod-spb.ru
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE
autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level:
Package: exim
Version: 3.35-1woody4
Severity: normal
I believe, that's a bug. In exim.conf i have following directives:
timeout_frozen_after = 7d
ignore_errmsg_errors_after = 3d
and _usually_ they work. But i see some aged messages in the queue (exim
-bp):
50d 4.6K 1CmKa0-0005UJ-00 <> *** frozen ***
[EMAIL PROTECTED]
38d 4.1K 1CqXUZ-0002AJ-00 <> *** frozen ***
[EMAIL PROTECTED]
29d 15K 1Ctq3D-0003Fs-00 <> *** frozen ***
[EMAIL PROTECTED]
28d 23K 1CuFF4-0001GA-00 <> *** frozen ***
[EMAIL PROTECTED]
28d 3.7K 1CuGhH-0001w8-00 <> *** frozen ***
[EMAIL PROTECTED]
24d 4.7K 1CvW6g-0005UP-00 <> *** frozen ***
[EMAIL PROTECTED]
24d 22K 1Cvj3n-0004UR-00 <> *** frozen ***
[EMAIL PROTECTED]
21d 2.6K 1Cwojo-00044C-00 <> *** frozen ***
[EMAIL PROTECTED]
21d 2.4K 1CwvUM-0007ez-00 <> *** frozen ***
[EMAIL PROTECTED]
17d 5.9K 1CyHbs-0001M2-00 <> *** frozen ***
[EMAIL PROTECTED]
17d 8.0K 1CyIvY-00028S-00 <> *** frozen ***
[EMAIL PROTECTED]
12d 92K 1Czpj2-0000Ky-00 <> *** frozen ***
[EMAIL PROTECTED]
-- System Information
Debian Release: 3.0
Architecture: i386
Kernel: Linux bilbo 2.4.18 #1 SMP Sat Nov 27 18:45:31 MSK 2004 i686
Locale: LANG=ru_RU.KOI8-R, LC_CTYPE=ru_RU.KOI8-R
Versions of packages exim depends on:
ii cron 3.0pl1-72 management of regular background p
ii libc6 2.2.5-11.8 GNU C Library: Shared libraries an
ii libdb2 2:2.7.7.0-7 The Berkeley database routines (ru
ii libident 0.22-2 simple RFC1413 client library - ru
ii libldap2 2.0.23-6.3 OpenLDAP libraries.
ii libpam0g 0.72-35 Pluggable Authentication Modules l
ii libpcre3 3.4-1.1 Philip Hazel's Perl Compatible Reg
---------------------------------------
Received: (at 296784-done) by bugs.debian.org; 24 Feb 2005 18:53:45 +0000
>From [EMAIL PROTECTED] Thu Feb 24 10:53:45 2005
Return-path: <[EMAIL PROTECTED]>
Received: from p4-7014.uk2net.com [213.232.95.15] (Debian-exim)
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1D4O7N-0000FL-00; Thu, 24 Feb 2005 10:53:45 -0800
Received: from cpc2-lock1-4-0-cust161.cos2.cable.ntl.com ([81.108.253.161]
helo=[10.36.0.103])
by p4-7014.uk2net.com with asmtp (TLS-1.0:DHE_RSA_AES_128_CBC_SHA:16)
(Exim 4.34)
id 1D4O7F-0003U8-RA; Thu, 24 Feb 2005 18:53:44 +0000
Message-ID: <[EMAIL PROTECTED]>
Date: Thu, 24 Feb 2005 18:53:36 +0000
From: Mark Baker <[EMAIL PROTECTED]>
User-Agent: Mozilla Thunderbird 1.0 (Macintosh/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Al Nikolov <[EMAIL PROTECTED]>, [EMAIL PROTECTED]
CC: [EMAIL PROTECTED]
References: <[EMAIL PROTECTED]>
In-Reply-To: <[EMAIL PROTECTED]>
X-SA-Exim-Connect-IP: 81.108.253.161
X-SA-Exim-Mail-From: [EMAIL PROTECTED]
Subject: Re: Bug#296784: exim: some error messages live infinitely
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-SA-Exim-Version: 4.1 (built Tue, 17 Aug 2004 11:06:07 +0200)
X-SA-Exim-Scanned: Yes (on p4-7014.uk2net.com)
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER
autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level:
X-CrossAssassin-Score: 2
Al Nikolov wrote:
>I believe, that's a bug. In exim.conf i have following directives:
>
>timeout_frozen_after = 7d
>ignore_errmsg_errors_after = 3d
>
>and _usually_ they work. But i see some aged messages in the queue (exim
>-bp):
>
>50d 4.6K 1CmKa0-0005UJ-00 <> *** frozen ***
> [EMAIL PROTECTED]
>
>
>
Yes, that does look like a bug to me. Actually frozen messages will only
be deleted at the next queue run after they time out, but if you weren't
getting regular queue runs I'm sure you'd be worried about more
important things than frozen messages not being deleted, so I assume
that that isn't the cause.
Try doing "exim -d9 -q" to do a queue run with debug turned on. You'll
get pages of output, so you probably want to redirect it to a file. Look
through this for the message ID, and see what it says about it. This
should suggest what the problem is.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
