courier-imap: CLOSE failed
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
courier (Debian) |
Fix Released
|
Unknown
|
|||
courier (Ubuntu) |
Fix Released
|
Medium
|
Thom May |
Bug Description
Automatically imported from Debian bug report #253304 http://
In Debian Bug tracker #253304, Roger Leigh (rleigh) wrote : Re: [Bug #253304] courier-imap: CLOSE failed | #1 |
In Debian Bug tracker #253304, Roger Leigh (rleigh) wrote : | #2 |
Roger Leigh <email address hidden> writes:
> I can also reproduce this with current sid, with both mutt and
> Emacs21/Gnus as mail clients.
>
> In addition, the connection is broken abruptly after about 10s after
> logging in. For example, logging a Gnus imap session:
Downgrading from 0.45.4-3 to 0.45.4-1 (testing) versions of:
courier-
courier-
courier-
has rectified the problem. Perhaps something has broken in -2 or -3
revision of the Debian diff?
Regards,
Roger
--
Roger Leigh
GPG Public Key: 0x25BFB848. Please sign and encrypt your mail.
In Debian Bug tracker #253304, Stefan Hornburg (Racke) (racke) wrote : Re: Bug#253304: [Bug #253304] courier-imap: CLOSE failed | #3 |
On Fri, 11 Jun 2004 00:16:27 +0100
Roger Leigh <email address hidden> wrote:
> Roger Leigh <email address hidden> writes:
>
> > I can also reproduce this with current sid, with both mutt and
> > Emacs21/Gnus as mail clients.
> >
> > In addition, the connection is broken abruptly after about 10s after
> > logging in. For example, logging a Gnus imap session:
>
> Downgrading from 0.45.4-3 to 0.45.4-1 (testing) versions of:
>
> courier-
> courier-
> courier-
>
> has rectified the problem. Perhaps something has broken in -2 or -3
> revision of the Debian diff?
If this downgrade fixes your problem, the FAM message patch attached to
this message might be the culprit. Is FAM installed and running on your
system ?
Thanks
Racke
--
Upcoming Talks and Presentations:
Linuxtag 2004, 25. Juni: Courier Mail Server (http://
Perlworkshop 2004, 30. Juni: Entwicklung großer Perlanwendungen
am Beispiel von Interchange (http://
In Debian Bug tracker #253304, Roger Leigh (roger-whinlatter) wrote : | #4 |
Stefan Hornburg <email address hidden> writes:
> On Fri, 11 Jun 2004 00:16:27 +0100
> Roger Leigh <email address hidden> wrote:
>
>> Roger Leigh <email address hidden> writes:
>>
>> > I can also reproduce this with current sid, with both mutt and
>> > Emacs21/Gnus as mail clients.
>> >
>> > In addition, the connection is broken abruptly after about 10s after
>> > logging in. For example, logging a Gnus imap session:
>>
>> Downgrading from 0.45.4-3 to 0.45.4-1 (testing) versions of:
>>
>> courier-
>> courier-
>> courier-
>>
>> has rectified the problem. Perhaps something has broken in -2 or -3
>> revision of the Debian diff?
>
> If this downgrade fixes your problem, the FAM message patch attached to
> this message might be the culprit. Is FAM installed and running on your
> system ?
No. I have "libfam0c102" installed, but "fam" is not.
Regards,
Roger
--
Roger Leigh
GPG Public Key: 0x25BFB848. Please sign and encrypt your mail.
In Debian Bug tracker #253304, Roger Leigh (roger-whinlatter) wrote : | #5 |
Stefan Hornburg <email address hidden> writes:
> On Fri, 11 Jun 2004 00:16:27 +0100
> Roger Leigh <email address hidden> wrote:
>
>> Roger Leigh <email address hidden> writes:
>>
>> > I can also reproduce this with current sid, with both mutt and
>> > Emacs21/Gnus as mail clients.
>> >
>> > In addition, the connection is broken abruptly after about 10s after
>> > logging in. For example, logging a Gnus imap session:
>>
>> Downgrading from 0.45.4-3 to 0.45.4-1 (testing) versions of:
>>
>> courier-
>> courier-
>> courier-
>>
>> has rectified the problem. Perhaps something has broken in -2 or -3
>> revision of the Debian diff?
>
> If this downgrade fixes your problem, the FAM message patch attached to
> this message might be the culprit. Is FAM installed and running on your
> system ?
I've done a bit more testing. The problem is in the courier-imap
package. All of the 0.45.4-3 packages work apart from that one.
However, if I install fam it all seems to work OK again.
Does the patch you attached want to be applied or backed out of the
0.45.4-3 release? I can try rebuilding it if that would help.
Regards,
Roger
--
Roger Leigh
GPG Public Key: 0x25BFB848. Please sign and encrypt your mail.
In Debian Bug tracker #253304, Stefan Hornburg (Racke) (racke) wrote : | #6 |
On Sat, 19 Jun 2004 16:18:19 +0100
Roger Leigh <email address hidden> wrote:
> Stefan Hornburg <email address hidden> writes:
>
> > On Fri, 11 Jun 2004 00:16:27 +0100
> > Roger Leigh <email address hidden> wrote:
> >
> >> Roger Leigh <email address hidden> writes:
> >>
> >> > I can also reproduce this with current sid, with both mutt and
> >> > Emacs21/Gnus as mail clients.
> >> >
> >> > In addition, the connection is broken abruptly after about 10s after
> >> > logging in. For example, logging a Gnus imap session:
> >>
> >> Downgrading from 0.45.4-3 to 0.45.4-1 (testing) versions of:
> >>
> >> courier-
> >> courier-
> >> courier-
> >>
> >> has rectified the problem. Perhaps something has broken in -2 or -3
> >> revision of the Debian diff?
> >
> > If this downgrade fixes your problem, the FAM message patch attached to
> > this message might be the culprit. Is FAM installed and running on your
> > system ?
>
> I've done a bit more testing. The problem is in the courier-imap
> package. All of the 0.45.4-3 packages work apart from that one.
> However, if I install fam it all seems to work OK again.
>
> Does the patch you attached want to be applied or backed out of the
> 0.45.4-3 release? I can try rebuilding it if that would help.
This patch has been applied to 0.45.4-2 and 0.45.4-3. Now I'm building
0.45.6 packages because this upstream release has much better debugging
support and then trace this bug down.
Bye
Racke
--
Upcoming Talks and Presentations:
Linuxtag 2004, 25. Juni: Courier Mail Server (http://
Perlworkshop 2004, 30. Juni: Entwicklung großer Perlanwendungen
am Beispiel von Interchange (http://
In Debian Bug tracker #253304, Roger Leigh (roger-whinlatter) wrote : | #7 |
Stefan Hornburg <email address hidden> writes:
> On Sat, 19 Jun 2004 16:18:19 +0100
> Roger Leigh <email address hidden> wrote:
>
>> I've done a bit more testing. The problem is in the courier-imap
>> package. All of the 0.45.4-3 packages work apart from that one.
>> However, if I install fam it all seems to work OK again.
>>
>> Does the patch you attached want to be applied or backed out of the
>> 0.45.4-3 release? I can try rebuilding it if that would help.
>
> This patch has been applied to 0.45.4-2 and 0.45.4-3. Now I'm building
> 0.45.6 packages because this upstream release has much better debugging
> support and then trace this bug down.
OK. If you want any help testing, I'll be happy to oblige.
--
Roger Leigh
GPG Public Key: 0x25BFB848. Please sign and encrypt your mail.
In Debian Bug tracker #253304, Stefan Hornburg (Racke) (racke) wrote : Severe problems with Courier-IMAP | #8 |
severity 254731 serious
severity 257006 serious
tags 257006 + sid
severity 256460 serious
tags 256460 + sid
severity 255069 serious
tags 253304 + sid
severity 253304 serious
merge 256460 257006 254731 255069 253304
thanks
--
Upcoming Talks and Presentations:
Perlworkshop 2004, 30. Juni: Entwicklung großer Perlanwendungen
am Beispiel von Interchange (http://
Debian Bug Importer (debzilla) wrote : | #9 |
Automatically imported from Debian bug report #253304 http://
Debian Bug Importer (debzilla) wrote : | #10 |
Message-Id: <email address hidden>
Date: Tue, 08 Jun 2004 10:19:59 -0400
From: Mark Horn <email address hidden>
To: Debian Bug Tracking System <email address hidden>
Subject: courier-imap: CLOSE failed
Package: courier-imap
Version: 3.0.3-2
Severity: normal
I'm having trouble with the recent version of courier-imap in 'sid'. I use
mutt as an imap client, and whenever I try to quit mutt, I get a "CLOSE
failed" error message. I've downgraded to mutt/testing and the problem
persists. If I downgrade to courier-
Based on this, I would conclude that the upgrade to courier-imap is the
source of the problem.
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.4.20mh04
Locale: LANG=C, LC_CTYPE=C
Versions of packages courier-imap depends on:
ii courier-authdaemon 0.45.4-2 Courier Mail Server - Authenticati
ii courier-base 0.45.4-2 Courier Mail Server - Base system
ii libc6 2.3.2.ds1-13 GNU C Library: Shared libraries an
ii libfam0c102 2.7.0-5 client library to control the FAM
ii libgdbm3 1.8.3-2 GNU dbm database routines (runtime
ii postfix [mail-transport-age 2.1.1-3 A high-performance mail transport
-- debconf information:
courier-
Debian Bug Importer (debzilla) wrote : | #11 |
Message-ID: <20040609221341
Date: Wed, 9 Jun 2004 23:13:43 +0100
From: Roger Leigh <email address hidden>
To: <email address hidden>
Cc: Mark Horn <email address hidden>, Stefan Hornburg <email address hidden>
Subject: Re: [Bug #253304] courier-imap: CLOSE failed
I can also reproduce this with current sid, with both mutt and
Emacs21/Gnus as mail clients.
In addition, the connection is broken abruptly after about 10s after
logging in. For example, logging a Gnus imap session:
Connecting to '127.0.0.1:993'...
Resolving 'localhost'...
- Certificate type: X.509
- Got a certificate list of 1 certificates.
- Certificate[0] info:
# The hostname in the certificate matches 'localhost'.
# valid since: Fri Oct 24 17:15:00 BST 2003
# expires at: Sat Oct 23 17:15:00 BST 2004
# serial number: 00
# fingerprint: 9c 14 9a e5 11 39 70 ca f3 58 9d f7 74 70 c9 f4
# version: #3
# public key algorithm: RSA
# Modulus: 1024 bits
# Subject's DN: C=US,ST=NY,L=New York,O=Courier Mail Server,
# Issuer's DN: C=US,ST=NY,L=New York,O=Courier Mail Server,
- Peer's certificate issuer is unknown
- Peer's certificate is NOT trusted
- Version: TLS 1.0
- Key Exchange: RSA
- Cipher: ARCFOUR 128
- MAC: SHA
- Compression: NULL
- Handshake was completed
- Simple Client Mode:
* OK [CAPABILITY IMAP4rev1 UIDPLUS CHILDREN NAMESPACE THREAD=
1 CAPABILITY
* CAPABILITY IMAP4rev1 UIDPLUS CHILDREN NAMESPACE THREAD=
1 OK CAPABILITY completed
2 LOGIN "roger" "karma79"
2 OK LOGIN Ok.
3 STATUS "INBOX.
4 STATUS "INBOX.
5 STATUS "INBOX.
6 STATUS "INBOX.devel.groff" (uidvalidity uidnext unseen)
7 STATUS "INBOX.devel.gtkmm" (uidvalidity uidnext unseen)
8 STATUS "INBOX.
9 STATUS "INBOX.
10 STATUS "INBOX.misc" (uidvalidity uidnext unseen)
11 STATUS "INBOX.friends" (uidvalidity uidnext unseen)
12 STATUS "INBOX.net.uklinux" (uidvalidity uidnext unseen)
13 STATUS "INBOX.net.admin" (uidvalidity uidnext unseen)
14 STATUS "INBOX.
15 STATUS "INBOX.
16 STATUS "INBOX.lug.york" (uidvalidity uidnext unseen)
17 STATUS "INBOX.
18 STATUS "INBOX.
19 STATUS "INBOX.
20 STATUS "INBOX.lug.ukuug" (uidvalidity uidnext unseen)
21 STATUS "INBOX.linux.misc" (uidvalidity uidnext unseen)
22 STATUS "INBOX.linux.help" (uidvalidity uidnext unseen)
23 STATUS "INBOX.
24 STATUS "INBOX.
Debian Bug Importer (debzilla) wrote : | #12 |
Message-ID: <email address hidden>
Date: Fri, 11 Jun 2004 00:16:27 +0100
From: Roger Leigh <email address hidden>
To: <email address hidden>
Cc: Mark Horn <email address hidden>, Stefan Hornburg <email address hidden>
Subject: Re: [Bug #253304] courier-imap: CLOSE failed
Roger Leigh <email address hidden> writes:
> I can also reproduce this with current sid, with both mutt and
> Emacs21/Gnus as mail clients.
>
> In addition, the connection is broken abruptly after about 10s after
> logging in. For example, logging a Gnus imap session:
Downgrading from 0.45.4-3 to 0.45.4-1 (testing) versions of:
courier-
courier-
courier-
has rectified the problem. Perhaps something has broken in -2 or -3
revision of the Debian diff?
Regards,
Roger
--
Roger Leigh
GPG Public Key: 0x25BFB848. Please sign and encrypt your mail.
Debian Bug Importer (debzilla) wrote : | #13 |
Message-Id: <email address hidden>
Date: Fri, 11 Jun 2004 15:18:48 +0200
From: Stefan Hornburg <email address hidden>
To: Roger Leigh <email address hidden>, <email address hidden>
Subject: Re: Bug#253304: [Bug #253304] courier-imap: CLOSE failed
--Multipart_
Content-Type: text/plain; charset=ISO-8859-1
Content-
On Fri, 11 Jun 2004 00:16:27 +0100
Roger Leigh <email address hidden> wrote:
> Roger Leigh <email address hidden> writes:
>=20
> > I can also reproduce this with current sid, with both mutt and
> > Emacs21/Gnus as mail clients.
> >
> > In addition, the connection is broken abruptly after about 10s after
> > logging in. For example, logging a Gnus imap session:
>=20
> Downgrading from 0.45.4-3 to 0.45.4-1 (testing) versions of:
>=20
> courier-
> courier-
> courier-
>=20
> has rectified the problem. Perhaps something has broken in -2 or -3
> revision of the Debian diff?
If this downgrade fixes your problem, the FAM message patch attached to
this message might be the culprit. Is FAM installed and running on your
system ?
Thanks
Racke
--=20
Upcoming Talks and Presentations:
Linuxtag 2004, 25. Juni: Courier Mail Server (http://
Perlworkshop 2004, 30. Juni: Entwicklung gro=DFer Perlanwendungen=20
am Beispiel von Interchange (http://
--Multipart_
Content-Type: application/
name="
Content-
filename=
Content-
LS0tIGNvdXJpZXI
ci0wLjQ1LjQvbWF
CX0KIAotCWlmICg
aXIpOwotCQlmcmV
YXRjaF9jdXJyZW5
Kyt3LT5mYW0tPnJ
dGNoX2ZyZWUoc3R
LXctPmZhbS0+
bGRpcndhdGNoX2N
cm9rZW4pCisJaWY
Ci0JCQkvKgotCQk
b24sCi0JCQkqKiB
CQkJaWYgKG1haWx
cnJlbnRmYW0tPmJ
IHRoZSBjdXJyZW5
CSovCiAKLQkJCXc
bm5lY3Rpb24sIHd
PmZjKTsKLQkJCWZ
ZWxzZSAvKiBTb21
Debian Bug Importer (debzilla) wrote : | #14 |
Message-ID: <email address hidden>
Date: Sat, 12 Jun 2004 00:10:45 +0100
From: Roger Leigh <email address hidden>
To: Stefan Hornburg <email address hidden>
Cc: <email address hidden>
Subject: Re: Bug#253304: [Bug #253304] courier-imap: CLOSE failed
Stefan Hornburg <email address hidden> writes:
> On Fri, 11 Jun 2004 00:16:27 +0100
> Roger Leigh <email address hidden> wrote:
>
>> Roger Leigh <email address hidden> writes:
>>
>> > I can also reproduce this with current sid, with both mutt and
>> > Emacs21/Gnus as mail clients.
>> >
>> > In addition, the connection is broken abruptly after about 10s after
>> > logging in. For example, logging a Gnus imap session:
>>
>> Downgrading from 0.45.4-3 to 0.45.4-1 (testing) versions of:
>>
>> courier-
>> courier-
>> courier-
>>
>> has rectified the problem. Perhaps something has broken in -2 or -3
>> revision of the Debian diff?
>
> If this downgrade fixes your problem, the FAM message patch attached to
> this message might be the culprit. Is FAM installed and running on your
> system ?
No. I have "libfam0c102" installed, but "fam" is not.
Regards,
Roger
--
Roger Leigh
GPG Public Key: 0x25BFB848. Please sign and encrypt your mail.
Debian Bug Importer (debzilla) wrote : | #15 |
Message-ID: <email address hidden>
Date: Sat, 19 Jun 2004 16:18:19 +0100
From: Roger Leigh <email address hidden>
To: Stefan Hornburg <email address hidden>
Cc: <email address hidden>
Subject: Re: Bug#253304: [Bug #253304] courier-imap: CLOSE failed
Stefan Hornburg <email address hidden> writes:
> On Fri, 11 Jun 2004 00:16:27 +0100
> Roger Leigh <email address hidden> wrote:
>
>> Roger Leigh <email address hidden> writes:
>>
>> > I can also reproduce this with current sid, with both mutt and
>> > Emacs21/Gnus as mail clients.
>> >
>> > In addition, the connection is broken abruptly after about 10s after
>> > logging in. For example, logging a Gnus imap session:
>>
>> Downgrading from 0.45.4-3 to 0.45.4-1 (testing) versions of:
>>
>> courier-
>> courier-
>> courier-
>>
>> has rectified the problem. Perhaps something has broken in -2 or -3
>> revision of the Debian diff?
>
> If this downgrade fixes your problem, the FAM message patch attached to
> this message might be the culprit. Is FAM installed and running on your
> system ?
I've done a bit more testing. The problem is in the courier-imap
package. All of the 0.45.4-3 packages work apart from that one.
However, if I install fam it all seems to work OK again.
Does the patch you attached want to be applied or backed out of the
0.45.4-3 release? I can try rebuilding it if that would help.
Regards,
Roger
--
Roger Leigh
GPG Public Key: 0x25BFB848. Please sign and encrypt your mail.
Debian Bug Importer (debzilla) wrote : | #16 |
Message-Id: <email address hidden>
Date: Sat, 19 Jun 2004 18:12:33 +0200
From: Stefan Hornburg <email address hidden>
To: Roger Leigh <email address hidden>, <email address hidden>
Subject: Re: Bug#253304: [Bug #253304] courier-imap: CLOSE failed
On Sat, 19 Jun 2004 16:18:19 +0100
Roger Leigh <email address hidden> wrote:
> Stefan Hornburg <email address hidden> writes:
>=20
> > On Fri, 11 Jun 2004 00:16:27 +0100
> > Roger Leigh <email address hidden> wrote:
> >
> >> Roger Leigh <email address hidden> writes:
> >>=20
> >> > I can also reproduce this with current sid, with both mutt and
> >> > Emacs21/Gnus as mail clients.
> >> >
> >> > In addition, the connection is broken abruptly after about 10s after
> >> > logging in. For example, logging a Gnus imap session:
> >>=20
> >> Downgrading from 0.45.4-3 to 0.45.4-1 (testing) versions of:
> >>=20
> >> courier-
> >> courier-
> >> courier-
> >>=20
> >> has rectified the problem. Perhaps something has broken in -2 or -3
> >> revision of the Debian diff?
> >
> > If this downgrade fixes your problem, the FAM message patch attached to
> > this message might be the culprit. Is FAM installed and running on your
> > system ?
>=20
> I've done a bit more testing. The problem is in the courier-imap
> package. All of the 0.45.4-3 packages work apart from that one.
> However, if I install fam it all seems to work OK again.
>=20
> Does the patch you attached want to be applied or backed out of the
> 0.45.4-3 release? I can try rebuilding it if that would help.
This patch has been applied to 0.45.4-2 and 0.45.4-3. Now I'm building
0.45.6 packages because this upstream release has much better debugging
support and then trace this bug down.
Bye
Racke
--=20
Upcoming Talks and Presentations:
Linuxtag 2004, 25. Juni: Courier Mail Server (http://
Perlworkshop 2004, 30. Juni: Entwicklung gro=DFer Perlanwendungen=20
am Beispiel von Interchange (http://
Debian Bug Importer (debzilla) wrote : | #17 |
Message-ID: <email address hidden>
Date: Sat, 19 Jun 2004 22:11:35 +0100
From: Roger Leigh <email address hidden>
To: Stefan Hornburg <email address hidden>
Cc: <email address hidden>
Subject: Re: Bug#253304: [Bug #253304] courier-imap: CLOSE failed
Stefan Hornburg <email address hidden> writes:
> On Sat, 19 Jun 2004 16:18:19 +0100
> Roger Leigh <email address hidden> wrote:
>
>> I've done a bit more testing. The problem is in the courier-imap
>> package. All of the 0.45.4-3 packages work apart from that one.
>> However, if I install fam it all seems to work OK again.
>>
>> Does the patch you attached want to be applied or backed out of the
>> 0.45.4-3 release? I can try rebuilding it if that would help.
>
> This patch has been applied to 0.45.4-2 and 0.45.4-3. Now I'm building
> 0.45.6 packages because this upstream release has much better debugging
> support and then trace this bug down.
OK. If you want any help testing, I'll be happy to oblige.
--
Roger Leigh
GPG Public Key: 0x25BFB848. Please sign and encrypt your mail.
Debian Bug Importer (debzilla) wrote : | #18 |
Message-Id: <email address hidden>
Date: Wed, 30 Jun 2004 14:59:33 +0200
From: Stefan Hornburg <email address hidden>
To: <email address hidden>
Subject: Severe problems with Courier-IMAP
severity 254731 serious
severity 257006 serious
tags 257006 + sid
severity 256460 serious
tags 256460 + sid
severity 255069 serious
tags 253304 + sid
severity 253304 serious
merge 256460 257006 254731 255069 253304
thanks
--=20
Upcoming Talks and Presentations:
Perlworkshop 2004, 30. Juni: Entwicklung gro=DFer Perlanwendungen=20
am Beispiel von Interchange (http://
Matt Zimmerman (mdz) wrote : | #19 |
*** Bug 6904 has been marked as a duplicate of this bug. ***
Matt Zimmerman (mdz) wrote : | #20 |
*** Bug 6905 has been marked as a duplicate of this bug. ***
Matt Zimmerman (mdz) wrote : | #21 |
*** Bug 6906 has been marked as a duplicate of this bug. ***
Matt Zimmerman (mdz) wrote : | #22 |
*** Bug 6907 has been marked as a duplicate of this bug. ***
In Debian Bug tracker #253304, Kelly Byrd (kbyrd-debian) wrote : consistent dropped connection with courier-imap | #23 |
I believe I'm hitting the same problem. It first showed up in squirrelmail,
specifically with squirrelmail trying to do a bunch of "STATUS (UNSEEN)"
commands. But, I can trigger it easily from telnet
I telnet to localhost:143, and login.
I then do "A STATUS INBOX.Sent (UNSEEN)", twice. On the second command
I get a disconnect. I ran with IMAPDEBUGFILE, and it shows recieveing
the first command along with a successful WRITE and OK response, for
the second it show several READS including the EOF but never any WRITE
or other indication that the command was proccessed.
I have not checked all of my folders, but so far INBOX.Sent triggers
it everytime, and other folders do not.
KB
Debian Bug Importer (debzilla) wrote : | #24 |
Message-ID: <7797.65.
Date: Thu, 1 Jul 2004 13:13:59 -0700 (PDT)
From: "Kelly Byrd" <email address hidden>
To: <email address hidden>
Subject: consistent dropped connection with courier-imap
I believe I'm hitting the same problem. It first showed up in squirrelmail,
specifically with squirrelmail trying to do a bunch of "STATUS (UNSEEN)"
commands. But, I can trigger it easily from telnet
I telnet to localhost:143, and login.
I then do "A STATUS INBOX.Sent (UNSEEN)", twice. On the second command
I get a disconnect. I ran with IMAPDEBUGFILE, and it shows recieveing
the first command along with a successful WRITE and OK response, for
the second it show several READS including the EOF but never any WRITE
or other indication that the command was proccessed.
I have not checked all of my folders, but so far INBOX.Sent triggers
it everytime, and other folders do not.
KB
Matt Zimmerman (mdz) wrote : | #25 |
Remove myself from all these CCs now that we have the warty-bugs mailing list
In Debian Bug tracker #253304, Stefan Hornburg (Racke) (racke) wrote : | #26 |
severity 258445 serious
merge 253304 258445
thanks
--
LinuXia Systems => http://
Expert Interchange Consulting and System Administration
ICDEVGROUP => http://
Interchange Development Team
Debian Bug Importer (debzilla) wrote : | #27 |
Message-Id: <email address hidden>
Date: Sat, 10 Jul 2004 14:59:56 +0200
From: Stefan Hornburg <email address hidden>
To: <email address hidden>
severity 258445 serious
merge 253304 258445
thanks
--
LinuXia Systems => http://
Expert Interchange Consulting and System Administration
ICDEVGROUP => http://
Interchange Development Team
Debian Bug Importer (debzilla) wrote : | #28 |
*** Bug 6996 has been marked as a duplicate of this bug. ***
In Debian Bug tracker #253304, Stefan Hornburg (Racke) (racke) wrote : Courier Debian Packaging Problem (IMAP + FAM) | #29 |
Hello,
I need your help and advice for the courier packaging problem described
below. Please read on.
Situation:
Courier can be compiled with or without FAM support. If FAM support is
included but FAM isn't running, this message is repeatedly written to
syslog:
Jul 10 23:31:44 turtle imaplogin: Failed to create cache file: maildirwatch (<email address hidden>)
Jul 10 23:31:44 turtle imaplogin: Error: Input/output error
Jul 10 23:31:44 turtle imaplogin: Check for proper operation and configuration
Jul 10 23:31:44 turtle imaplogin: of the File Access Monitor daemon (famd).
This is fine for source builds, but leads to problems for packagers.
Either we need to depend on the FAM daemon package or logs get filled
with the messages above. Both scenarios doesn't have a great appeal to me
(see also Debian bugs #191007, #204405, #206626, #238990, #242837
for reference).
Steve Langasek was so kind to write a patch to cope with this situation,
but unfortunately this patch leads to memory corruption like that:
Program received signal SIGSEGV, Segmentation fault.
0x400d2219 in malloc () from /lib/libc.so.6
(gdb) backtrace
#0 0x400d2219 in malloc () from /lib/libc.so.6
#1 0x400d2074 in malloc () from /lib/libc.so.6
#2 0x0806cd0a in maildir_
myId=0xbffffebe "<email address hidden>") at maildirinfo.c:179
#3 0x0804d02b in decode_
#4 0x0804d651 in parse_mailbox_error (tag=0xbfffb5b8 "19", curtoken=0x8182780, ok_hierarchy=0,
autosubscri
#5 0x080538d2 in do_imap_command (tag=0xbfffb5b8 "19") at imapd.c:4773
#6 0x0805eae3 in mainloop () at mainloop.c:93
#7 0x08056516 in main (argc=2, argv=0xbffff6a4) at imapd.c:6354
See Debian bugs #253304, #254731, #255069, #256460, #257006, #258445 for reference.
Solution:
1. Resolve the memory corruption in the patch (see attachment). If you want to
compile for debugging with the debian/rules file,
change CFLAGS=-lcrypt to LDFLAGS=-lcrypt and uncomment dh_strip
2. New scenario to solve the problem:
* test whether FAM is available in the courier-imap init script
and set an environment variable accordingly (like FAMIGNORE)
* change the source code to test this environment variable and
skip FAM access if environment variable if set
Any advice or further help would be appreciated immensely.
With regards
Racke
--
LinuXia Systems => http://
Expert Interchange Consulting and System Administration
ICDEVGROUP => http://
Interchange Development Team
Debian Bug Importer (debzilla) wrote : | #30 |
Message-Id: <email address hidden>
Date: Sun, 11 Jul 2004 12:35:48 +0200
From: Stefan Hornburg <email address hidden>
To: <email address hidden>, <email address hidden>, <email address hidden>,
<email address hidden>, <email address hidden>, <email address hidden>
Cc: <email address hidden>, <email address hidden>
Subject: Courier Debian Packaging Problem (IMAP + FAM)
--Multipart=
Content-Type: text/plain; charset=US-ASCII
Content-
Hello,
I need your help and advice for the courier packaging problem described
below. Please read on.
Situation:
Courier can be compiled with or without FAM support. If FAM support is
included but FAM isn't running, this message is repeatedly written to
syslog:
Jul 10 23:31:44 turtle imaplogin: Failed to create cache file: maildirwatch (<email address hidden>)
Jul 10 23:31:44 turtle imaplogin: Error: Input/output error
Jul 10 23:31:44 turtle imaplogin: Check for proper operation and configuration
Jul 10 23:31:44 turtle imaplogin: of the File Access Monitor daemon (famd).
This is fine for source builds, but leads to problems for packagers.
Either we need to depend on the FAM daemon package or logs get filled
with the messages above. Both scenarios doesn't have a great appeal to me
(see also Debian bugs #191007, #204405, #206626, #238990, #242837
for reference).
Steve Langasek was so kind to write a patch to cope with this situation,
but unfortunately this patch leads to memory corruption like that:
Program received signal SIGSEGV, Segmentation fault.
0x400d2219 in malloc () from /lib/libc.so.6
(gdb) backtrace
#0 0x400d2219 in malloc () from /lib/libc.so.6
#1 0x400d2074 in malloc () from /lib/libc.so.6
#2 0x0806cd0a in maildir_
myId=0xbffffebe "<email address hidden>") at maildirinfo.c:179
#3 0x0804d02b in decode_
#4 0x0804d651 in parse_mailbox_error (tag=0xbfffb5b8 "19", curtoken=0x8182780, ok_hierarchy=0,
autosubscri
#5 0x080538d2 in do_imap_command (tag=0xbfffb5b8 "19") at imapd.c:4773
#6 0x0805eae3 in mainloop () at mainloop.c:93
#7 0x08056516 in main (argc=2, argv=0xbffff6a4) at imapd.c:6354
See Debian bugs #253304, #254731, #255069, #256460, #257006, #258445 for reference.
Solution:
1. Resolve the memory corruption in the patch (see attachment). If you want to
compile for debugging with the debian/rules file,
change CFLAGS=-lcrypt to LDFLAGS=-lcrypt and uncomment dh_strip
2. New scenario to solve the problem:
* test whether FAM is available in the courier-imap init script
and set an environment variable accordingly (like FAMIGNORE)
* change the source code to test this environment variable and
skip FAM access if environment variable if set
Any advice or further help would be appreciated immensely.
With regards
Racke
--
LinuXia Systems => http://
Expert Interchange Consulting and System Administration
ICDEVGROUP => http://
Interchange Development Team
--Multipart=
In Debian Bug tracker #253304, Stefan Hornburg (Racke) (racke) wrote : Bug#253304: fixed in courier 0.45.6-1 | #31 |
Source: courier
Source-Version: 0.45.6-1
We believe that the bug you reported is fixed in the latest version of
courier, which is due to be installed in the Debian FTP archive:
courier-
to pool/main/
courier-
to pool/main/
courier-
to pool/main/
courier-
to pool/main/
courier-
to pool/main/
courier-
to pool/main/
courier-
to pool/main/
courier-
to pool/main/
courier-
to pool/main/
courier-
to pool/main/
courier-
to pool/main/
courier-
to pool/main/
courier-
to pool/main/
courier-
to pool/main/
courier-
to pool/main/
courier-
to pool/main/
courier-
to pool/main/
courier-
to pool/main/
courier_
to pool/main/
courier_
to pool/main/
courier_
to pool/main/
sqwebmail_
to pool/main/
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to <email address hidden>,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Stefan Hornburg (Racke) <email address hidden> (supplier of updated courier package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing <email address hidden>)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.7
Date: Mon, 12 Jul 2004 00:14:44 +0200
Source: courier
Binary: courier-
Architecture: source i386 all
Version: 0.45.6-1
Distribution: unstable
Urgency: low
Maintain...
Debian Bug Importer (debzilla) wrote : | #32 |
Message-Id: <email address hidden>
Date: Mon, 12 Jul 2004 10:32:07 -0400
From: Stefan Hornburg (Racke) <email address hidden>
To: <email address hidden>
Subject: Bug#253304: fixed in courier 0.45.6-1
Source: courier
Source-Version: 0.45.6-1
We believe that the bug you reported is fixed in the latest version of
courier, which is due to be installed in the Debian FTP archive:
courier-
to pool/main/
courier-
to pool/main/
courier-
to pool/main/
courier-
to pool/main/
courier-
to pool/main/
courier-
to pool/main/
courier-
to pool/main/
courier-
to pool/main/
courier-
to pool/main/
courier-
to pool/main/
courier-
to pool/main/
courier-
to pool/main/
courier-
to pool/main/
courier-
to pool/main/
courier-
to pool/main/
courier-
to pool/main/
courier-
to pool/main/
courier-
to pool/main/
courier_
to pool/main/
courier_
to pool/main/
courier_
to pool/main/
sqwebmail_
to pool/main/
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to <email address hidden>,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Stefan Hornburg (Racke) <email address hidden> (supplier of updated courier package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing <email address hidden>)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.7
Date: Mon, 12 Jul 2004 00:14:44 +0200
Source: courier
Binary: courier-
Matt Zimmerman (mdz) wrote : | #33 |
Fixed via sync of 0.45.6-1
Changed in courier: | |
status: | Unknown → Fix Released |
I can also reproduce this with current sid, with both mutt and
Emacs21/Gnus as mail clients.
In addition, the connection is broken abruptly after about 10s after
logging in. For example, logging a Gnus imap session:
Connecting to '127.0.0.1:993'...
Resolving 'localhost'...
- Certificate type: X.509
- Got a certificate list of 1 certificates.
- Certificate[0] info: OU=Automaticall y-generated IMAP SSL key,CN= localhost, <email address hidden> OU=Automaticall y-generated IMAP SSL key,CN= localhost, <email address hidden>
# The hostname in the certificate matches 'localhost'.
# valid since: Fri Oct 24 17:15:00 BST 2003
# expires at: Sat Oct 23 17:15:00 BST 2004
# serial number: 00
# fingerprint: 9c 14 9a e5 11 39 70 ca f3 58 9d f7 74 70 c9 f4
# version: #3
# public key algorithm: RSA
# Modulus: 1024 bits
# Subject's DN: C=US,ST=NY,L=New York,O=Courier Mail Server,
# Issuer's DN: C=US,ST=NY,L=New York,O=Courier Mail Server,
- Peer's certificate issuer is unknown
- Peer's certificate is NOT trusted
- Version: TLS 1.0
- Key Exchange: RSA
- Cipher: ARCFOUR 128
- MAC: SHA
- Compression: NULL
- Handshake was completed
- Simple Client Mode:
* OK [CAPABILITY IMAP4rev1 UIDPLUS CHILDREN NAMESPACE THREAD= ORDEREDSUBJECT THREAD=REFERENCES SORT QUOTA IDLE AUTH=PLAIN ACL ACL2=UNION] Courier-IMAP ready. Copyright 1998-2004 Double Precision, Inc. See COPYING for distribution information. ORDEREDSUBJECT THREAD=REFERENCES SORT QUOTA IDLE AUTH=PLAIN ACL ACL2=UNION linux.fsfe- uk" (uidvalidity uidnext unseen) net.purchasing" (uidvalidity uidnext unseen) debian. printing" (uidvalidity uidnext unseen) devel.gimp- print.bugs" (uidvalidity uidnext unseen) debian. libpqxx" (uidvalidity uidnext unseen) system. hardware" (uidvalidity uidnext unseen) york.ben- lairig" (uidvalidity uidnext unseen) lug.wylug. help" (uidvalidity uidnext unseen) lug.wylug. discuss" (uidvalidity uidnext unseen) lug.wylug. announce" (uidvalidity uidnext unseen) linux.hardware" (uidvalidity uidnext unseen) linux.developme nt" (uidvalidity uidnext unseen) devel.inkjet" (uidvalidity uidnext unseen) devel.gimp- print.private" (uidvalidity uidnext un...
1 CAPABILITY
* CAPABILITY IMAP4rev1 UIDPLUS CHILDREN NAMESPACE THREAD=
1 OK CAPABILITY completed
2 LOGIN "roger" "karma79"
2 OK LOGIN Ok.
3 STATUS "INBOX.
4 STATUS "INBOX.
5 STATUS "INBOX.
6 STATUS "INBOX.devel.groff" (uidvalidity uidnext unseen)
7 STATUS "INBOX.devel.gtkmm" (uidvalidity uidnext unseen)
8 STATUS "INBOX.
9 STATUS "INBOX.
10 STATUS "INBOX.misc" (uidvalidity uidnext unseen)
11 STATUS "INBOX.friends" (uidvalidity uidnext unseen)
12 STATUS "INBOX.net.uklinux" (uidvalidity uidnext unseen)
13 STATUS "INBOX.net.admin" (uidvalidity uidnext unseen)
14 STATUS "INBOX.
15 STATUS "INBOX.
16 STATUS "INBOX.lug.york" (uidvalidity uidnext unseen)
17 STATUS "INBOX.
18 STATUS "INBOX.
19 STATUS "INBOX.
20 STATUS "INBOX.lug.ukuug" (uidvalidity uidnext unseen)
21 STATUS "INBOX.linux.misc" (uidvalidity uidnext unseen)
22 STATUS "INBOX.linux.help" (uidvalidity uidnext unseen)
23 STATUS "INBOX.
24 STATUS "INBOX.
25 STATUS "INBOX.linux.bugs" (uidvalidity uidnext unseen)
26 STATUS "INBOX.
27 STATUS "INBOX.devel.gtk" (uidvalidity uidnext unseen)
28 STATUS "INBOX.