courier-imap: CLOSE failed

Bug #6903 reported by Debian Bug Importer
34
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://bugs.debian.org/253304

Revision history for this message
In , Roger Leigh (rleigh) wrote : Re: [Bug #253304] courier-imap: CLOSE failed
Download full text (5.0 KiB)

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,OU=Automatically-generated IMAP SSL key,CN=localhost,<email address hidden>
 # Issuer's DN: C=US,ST=NY,L=New York,O=Courier Mail Server,OU=Automatically-generated IMAP SSL key,CN=localhost,<email address hidden>

- 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.
1 CAPABILITY
* CAPABILITY IMAP4rev1 UIDPLUS CHILDREN NAMESPACE THREAD=ORDEREDSUBJECT THREAD=REFERENCES SORT QUOTA IDLE AUTH=PLAIN ACL ACL2=UNION
1 OK CAPABILITY completed
2 LOGIN "roger" "karma79"
2 OK LOGIN Ok.
3 STATUS "INBOX.linux.fsfe-uk" (uidvalidity uidnext unseen)
4 STATUS "INBOX.net.purchasing" (uidvalidity uidnext unseen)
5 STATUS "INBOX.debian.printing" (uidvalidity uidnext unseen)
6 STATUS "INBOX.devel.groff" (uidvalidity uidnext unseen)
7 STATUS "INBOX.devel.gtkmm" (uidvalidity uidnext unseen)
8 STATUS "INBOX.devel.gimp-print.bugs" (uidvalidity uidnext unseen)
9 STATUS "INBOX.debian.libpqxx" (uidvalidity uidnext unseen)
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.system.hardware" (uidvalidity uidnext unseen)
15 STATUS "INBOX.york.ben-lairig" (uidvalidity uidnext unseen)
16 STATUS "INBOX.lug.york" (uidvalidity uidnext unseen)
17 STATUS "INBOX.lug.wylug.help" (uidvalidity uidnext unseen)
18 STATUS "INBOX.lug.wylug.discuss" (uidvalidity uidnext unseen)
19 STATUS "INBOX.lug.wylug.announce" (uidvalidity uidnext unseen)
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.linux.hardware" (uidvalidity uidnext unseen)
24 STATUS "INBOX.linux.development" (uidvalidity uidnext unseen)
25 STATUS "INBOX.linux.bugs" (uidvalidity uidnext unseen)
26 STATUS "INBOX.devel.inkjet" (uidvalidity uidnext unseen)
27 STATUS "INBOX.devel.gtk" (uidvalidity uidnext unseen)
28 STATUS "INBOX.devel.gimp-print.private" (uidvalidity uidnext un...

Read more...

Revision history for this message
In , Roger Leigh (rleigh) 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-authdaemon_0.45.4-1_i386.deb courier-imap-ssl_3.0.3-1_i386.deb
courier-base_0.45.4-1_i386.deb courier-imap_3.0.3-1_i386.deb
courier-doc_0.45.4-1_all.deb courier-ssl_0.45.4-1_i386.deb

has rectified the problem. Perhaps something has broken in -2 or -3
revision of the Debian diff?

Regards,
Roger

--
Roger Leigh

                Printing on GNU/Linux? http://gimp-print.sourceforge.net/
                GPG Public Key: 0x25BFB848. Please sign and encrypt your mail.

Revision history for this message
In , Stefan Hornburg (Racke) (racke) wrote : Re: Bug#253304: [Bug #253304] courier-imap: CLOSE failed

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-authdaemon_0.45.4-1_i386.deb courier-imap-ssl_3.0.3-1_i386.deb
> courier-base_0.45.4-1_i386.deb courier-imap_3.0.3-1_i386.deb
> courier-doc_0.45.4-1_all.deb courier-ssl_0.45.4-1_i386.deb
>
> 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://www.linuxtag.org/)
Perlworkshop 2004, 30. Juni: Entwicklung großer Perlanwendungen
am Beispiel von Interchange (http://www.perlworkshop.de/)

Revision history for this message
In , Roger Leigh (roger-whinlatter) 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-authdaemon_0.45.4-1_i386.deb courier-imap-ssl_3.0.3-1_i386.deb
>> courier-base_0.45.4-1_i386.deb courier-imap_3.0.3-1_i386.deb
>> courier-doc_0.45.4-1_all.deb courier-ssl_0.45.4-1_i386.deb
>>
>> 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

                Printing on GNU/Linux? http://gimp-print.sourceforge.net/
                GPG Public Key: 0x25BFB848. Please sign and encrypt your mail.

Revision history for this message
In , Roger Leigh (roger-whinlatter) 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-authdaemon_0.45.4-1_i386.deb courier-imap-ssl_3.0.3-1_i386.deb
>> courier-base_0.45.4-1_i386.deb courier-imap_3.0.3-1_i386.deb
>> courier-doc_0.45.4-1_all.deb courier-ssl_0.45.4-1_i386.deb
>>
>> 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

                Printing on GNU/Linux? http://gimp-print.sourceforge.net/
                GPG Public Key: 0x25BFB848. Please sign and encrypt your mail.

Revision history for this message
In , Stefan Hornburg (Racke) (racke) wrote :

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-authdaemon_0.45.4-1_i386.deb courier-imap-ssl_3.0.3-1_i386.deb
> >> courier-base_0.45.4-1_i386.deb courier-imap_3.0.3-1_i386.deb
> >> courier-doc_0.45.4-1_all.deb courier-ssl_0.45.4-1_i386.deb
> >>
> >> 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://www.linuxtag.org/)
Perlworkshop 2004, 30. Juni: Entwicklung großer Perlanwendungen
am Beispiel von Interchange (http://www.perlworkshop.de/)

Revision history for this message
In , Roger Leigh (roger-whinlatter) wrote :

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

                Printing on GNU/Linux? http://gimp-print.sourceforge.net/
                GPG Public Key: 0x25BFB848. Please sign and encrypt your mail.

Revision history for this message
In , Stefan Hornburg (Racke) (racke) wrote : 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

--
Upcoming Talks and Presentations:
Perlworkshop 2004, 30. Juni: Entwicklung großer Perlanwendungen
am Beispiel von Interchange (http://www.perlworkshop.de/)

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Automatically imported from Debian bug report #253304 http://bugs.debian.org/253304

Revision history for this message
Debian Bug Importer (debzilla) wrote :

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-imap/testing, the problem goes away.
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-imap/moveconfig: true

Revision history for this message
Debian Bug Importer (debzilla) wrote :
Download full text (5.3 KiB)

Message-ID: <20040609221341.GA5680@wrynose>
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,OU=Automatically-generated IMAP SSL key,CN=localhost,<email address hidden>
 # Issuer's DN: C=US,ST=NY,L=New York,O=Courier Mail Server,OU=Automatically-generated IMAP SSL key,CN=localhost,<email address hidden>

- 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.
1 CAPABILITY
* CAPABILITY IMAP4rev1 UIDPLUS CHILDREN NAMESPACE THREAD=ORDEREDSUBJECT THREAD=REFERENCES SORT QUOTA IDLE AUTH=PLAIN ACL ACL2=UNION
1 OK CAPABILITY completed
2 LOGIN "roger" "karma79"
2 OK LOGIN Ok.
3 STATUS "INBOX.linux.fsfe-uk" (uidvalidity uidnext unseen)
4 STATUS "INBOX.net.purchasing" (uidvalidity uidnext unseen)
5 STATUS "INBOX.debian.printing" (uidvalidity uidnext unseen)
6 STATUS "INBOX.devel.groff" (uidvalidity uidnext unseen)
7 STATUS "INBOX.devel.gtkmm" (uidvalidity uidnext unseen)
8 STATUS "INBOX.devel.gimp-print.bugs" (uidvalidity uidnext unseen)
9 STATUS "INBOX.debian.libpqxx" (uidvalidity uidnext unseen)
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.system.hardware" (uidvalidity uidnext unseen)
15 STATUS "INBOX.york.ben-lairig" (uidvalidity uidnext unseen)
16 STATUS "INBOX.lug.york" (uidvalidity uidnext unseen)
17 STATUS "INBOX.lug.wylug.help" (uidvalidity uidnext unseen)
18 STATUS "INBOX.lug.wylug.discuss" (uidvalidity uidnext unseen)
19 STATUS "INBOX.lug.wylug.announce" (uidvalidity uidnext unseen)
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.linux.hardware" (uidvalidity uidnext unseen)
24 STATUS "INBOX.linux.development"...

Read more...

Revision history for this message
Debian Bug Importer (debzilla) wrote :

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-authdaemon_0.45.4-1_i386.deb courier-imap-ssl_3.0.3-1_i386.deb
courier-base_0.45.4-1_i386.deb courier-imap_3.0.3-1_i386.deb
courier-doc_0.45.4-1_all.deb courier-ssl_0.45.4-1_i386.deb

has rectified the problem. Perhaps something has broken in -2 or -3
revision of the Debian diff?

Regards,
Roger

--
Roger Leigh

                Printing on GNU/Linux? http://gimp-print.sourceforge.net/
                GPG Public Key: 0x25BFB848. Please sign and encrypt your mail.

Revision history for this message
Debian Bug Importer (debzilla) wrote :
Download full text (4.9 KiB)

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_Fri__11_Jun_2004_15:18:48_+0200_08548510
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

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-authdaemon_0.45.4-1_i386.deb courier-imap-ssl_3.0.3-1_i386.deb
> courier-base_0.45.4-1_i386.deb courier-imap_3.0.3-1_i386.deb
> courier-doc_0.45.4-1_all.deb courier-ssl_0.45.4-1_i386.deb
>=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://www.linuxtag.org/)
Perlworkshop 2004, 30. Juni: Entwicklung gro=DFer Perlanwendungen=20
am Beispiel von Interchange (http://www.perlworkshop.de/)

--Multipart_Fri__11_Jun_2004_15:18:48_+0200_08548510
Content-Type: application/octet-stream;
 name="famfail.patch"
Content-Disposition: attachment;
 filename="famfail.patch"
Content-Transfer-Encoding: base64

LS0tIGNvdXJpZXItMC40NS40Lm9yaWcvbWFpbGRpci9tYWlsZGlyd2F0Y2guYworKysgY291cmll
ci0wLjQ1LjQvbWFpbGRpci9tYWlsZGlyd2F0Y2guYwpAQCAtNjgsMTQgKzY4LDcgQEAKIAkJfQog
CX0KIAotCWlmICghbWFpbGRpcndhdGNoX2N1cnJlbnRmYW0pCi0JewotCQlmcmVlKHctPm1haWxk
aXIpOwotCQlmcmVlKHcpOwotCQl3PU5VTEw7Ci0JfQotCWVsc2UKLQl7CisJaWYgKG1haWxkaXJ3
YXRjaF9jdXJyZW50ZmFtKSB7CiAJCXctPmZhbT1tYWlsZGlyd2F0Y2hfY3VycmVudGZhbTsKIAkJ
Kyt3LT5mYW0tPnJlZmNudDsKIAl9CkBAIC04NiwyMyArNzksMjUgQEAKIHZvaWQgbWFpbGRpcndh
dGNoX2ZyZWUoc3RydWN0IG1haWxkaXJ3YXRjaCAqdykKIHsKICNpZiBIQVZFX0ZBTQotCWlmICgt
LXctPmZhbS0+cmVmY250ID09IDApCi0JewotCQl3LT5mYW0tPmJyb2tlbj0xOwotCQlpZiAobWFp
bGRpcndhdGNoX2N1cnJlbnRmYW0gJiYKLQkJICAgIG1haWxkaXJ3YXRjaF9jdXJyZW50ZmFtLT5i
cm9rZW4pCisJaWYgKHctPmZhbSkgeworCQlpZiAoLS13LT5mYW0tPnJlZmNudCA9PSAwKQogCQl7
Ci0JCQkvKgotCQkJKiogTGFzdCByZWZlcmVuY2UgdG8gdGhlIGN1cnJlbnQgRkFNIGNvbm5lY3Rp
b24sCi0JCQkqKiBrZWVwIGl0IGFjdGl2ZS4KLQkJCSovCisJCQl3LT5mYW0tPmJyb2tlbj0xOwor
CQkJaWYgKG1haWxkaXJ3YXRjaF9jdXJyZW50ZmFtICYmCisJCQkgICAgbWFpbGRpcndhdGNoX2N1
cnJlbnRmYW0tPmJyb2tlbikKKwkJCXsKKwkJCQkvKgorCQkJCSoqIExhc3QgcmVmZXJlbmNlIHRv
IHRoZSBjdXJyZW50IEZBTSBjb25uZWN0aW9uLAorCQkJCSoqIGtlZXAgaXQgYWN0aXZlLgorCQkJ
CSovCiAKLQkJCXctPmZhbS0+YnJva2VuPTA7Ci0JCX0KLQkJZWxzZSAvKiBTb21lIG90aGVyIGNv
bm5lY3Rpb24sIHdpdGggbm8gbW9yZSByZWZzICovCi0JCXsKLQkJCUZBTUNsb3NlKCZ3LT5mYW0t
PmZjKTsKLQkJCWZyZWUody0+ZmFtKTsKKwkJCQl3LT5mYW0tPmJyb2tlbj0wOworCQkJfQorCQkJ
ZWxzZSAvKiBTb21lIG90aGVyIGNvbm5lY3Rpb...

Read more...

Revision history for this message
Debian Bug Importer (debzilla) wrote :

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-authdaemon_0.45.4-1_i386.deb courier-imap-ssl_3.0.3-1_i386.deb
>> courier-base_0.45.4-1_i386.deb courier-imap_3.0.3-1_i386.deb
>> courier-doc_0.45.4-1_all.deb courier-ssl_0.45.4-1_i386.deb
>>
>> 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

                Printing on GNU/Linux? http://gimp-print.sourceforge.net/
                GPG Public Key: 0x25BFB848. Please sign and encrypt your mail.

Revision history for this message
Debian Bug Importer (debzilla) wrote :

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-authdaemon_0.45.4-1_i386.deb courier-imap-ssl_3.0.3-1_i386.deb
>> courier-base_0.45.4-1_i386.deb courier-imap_3.0.3-1_i386.deb
>> courier-doc_0.45.4-1_all.deb courier-ssl_0.45.4-1_i386.deb
>>
>> 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

                Printing on GNU/Linux? http://gimp-print.sourceforge.net/
                GPG Public Key: 0x25BFB848. Please sign and encrypt your mail.

Revision history for this message
Debian Bug Importer (debzilla) wrote :

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-authdaemon_0.45.4-1_i386.deb courier-imap-ssl_3.0.3-1_i386.deb
> >> courier-base_0.45.4-1_i386.deb courier-imap_3.0.3-1_i386.deb
> >> courier-doc_0.45.4-1_all.deb courier-ssl_0.45.4-1_i386.deb
> >>=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://www.linuxtag.org/)
Perlworkshop 2004, 30. Juni: Entwicklung gro=DFer Perlanwendungen=20
am Beispiel von Interchange (http://www.perlworkshop.de/)

Revision history for this message
Debian Bug Importer (debzilla) wrote :

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

                Printing on GNU/Linux? http://gimp-print.sourceforge.net/
                GPG Public Key: 0x25BFB848. Please sign and encrypt your mail.

Revision history for this message
Debian Bug Importer (debzilla) wrote :

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://www.perlworkshop.de/)

Revision history for this message
Matt Zimmerman (mdz) wrote :

*** Bug 6904 has been marked as a duplicate of this bug. ***

Revision history for this message
Matt Zimmerman (mdz) wrote :

*** Bug 6905 has been marked as a duplicate of this bug. ***

Revision history for this message
Matt Zimmerman (mdz) wrote :

*** Bug 6906 has been marked as a duplicate of this bug. ***

Revision history for this message
Matt Zimmerman (mdz) wrote :

*** Bug 6907 has been marked as a duplicate of this bug. ***

Revision history for this message
In , Kelly Byrd (kbyrd-debian) wrote : 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

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-ID: <7797.65.113.40.130.1088712839.squirrel@65.113.40.130>
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

Revision history for this message
Matt Zimmerman (mdz) wrote :

Remove myself from all these CCs now that we have the warty-bugs mailing list

Revision history for this message
In , Stefan Hornburg (Racke) (racke) wrote :

severity 258445 serious
merge 253304 258445
thanks

--
LinuXia Systems => http://www.linuxia.de/
Expert Interchange Consulting and System Administration
ICDEVGROUP => http://www.icdevgroup.org/
Interchange Development Team

Revision history for this message
Debian Bug Importer (debzilla) wrote :

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://www.linuxia.de/
Expert Interchange Consulting and System Administration
ICDEVGROUP => http://www.icdevgroup.org/
Interchange Development Team

Revision history for this message
Debian Bug Importer (debzilla) wrote :

*** Bug 6996 has been marked as a duplicate of this bug. ***

Revision history for this message
In , Stefan Hornburg (Racke) (racke) wrote : Courier Debian Packaging Problem (IMAP + FAM)

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_info_imap_find (info=0xbfffb2ac, path=0x81872e0 "INBOX.Trash",
    myId=0xbffffebe "<email address hidden>") at maildirinfo.c:179
#3 0x0804d02b in decode_valid_mailbox (p=0x81872e0 "INBOX.Trash", autosubscribe=1) at imapd.c:327
#4 0x0804d651 in parse_mailbox_error (tag=0xbfffb5b8 "19", curtoken=0x8182780, ok_hierarchy=0,
    autosubscribe=1) at imapd.c:572
#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://www.linuxia.de/
Expert Interchange Consulting and System Administration
ICDEVGROUP => http://www.icdevgroup.org/
Interchange Development Team

Revision history for this message
Debian Bug Importer (debzilla) wrote :
Download full text (6.5 KiB)

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=_Sun__11_Jul_2004_12_35_48_+0200_o6OBYd=gyCWXBfy5
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

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_info_imap_find (info=0xbfffb2ac, path=0x81872e0 "INBOX.Trash",
    myId=0xbffffebe "<email address hidden>") at maildirinfo.c:179
#3 0x0804d02b in decode_valid_mailbox (p=0x81872e0 "INBOX.Trash", autosubscribe=1) at imapd.c:327
#4 0x0804d651 in parse_mailbox_error (tag=0xbfffb5b8 "19", curtoken=0x8182780, ok_hierarchy=0,
    autosubscribe=1) at imapd.c:572
#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://www.linuxia.de/
Expert Interchange Consulting and System Administration
ICDEVGROUP => http://www.icdevgroup.org/
Interchange Development Team

--Multipart=_Sun__11_...

Read more...

Revision history for this message
In , Stefan Hornburg (Racke) (racke) wrote : Bug#253304: fixed in courier 0.45.6-1
Download full text (7.1 KiB)

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-authdaemon_0.45.6-1_i386.deb
  to pool/main/c/courier/courier-authdaemon_0.45.6-1_i386.deb
courier-authmysql_0.45.6-1_i386.deb
  to pool/main/c/courier/courier-authmysql_0.45.6-1_i386.deb
courier-authpostgresql_0.45.6-1_i386.deb
  to pool/main/c/courier/courier-authpostgresql_0.45.6-1_i386.deb
courier-base_0.45.6-1_i386.deb
  to pool/main/c/courier/courier-base_0.45.6-1_i386.deb
courier-doc_0.45.6-1_all.deb
  to pool/main/c/courier/courier-doc_0.45.6-1_all.deb
courier-faxmail_0.45.6-1_i386.deb
  to pool/main/c/courier/courier-faxmail_0.45.6-1_i386.deb
courier-imap-ssl_3.0.5-1_i386.deb
  to pool/main/c/courier/courier-imap-ssl_3.0.5-1_i386.deb
courier-imap_3.0.5-1_i386.deb
  to pool/main/c/courier/courier-imap_3.0.5-1_i386.deb
courier-ldap_0.45.6-1_i386.deb
  to pool/main/c/courier/courier-ldap_0.45.6-1_i386.deb
courier-maildrop_0.45.6-1_i386.deb
  to pool/main/c/courier/courier-maildrop_0.45.6-1_i386.deb
courier-mlm_0.45.6-1_i386.deb
  to pool/main/c/courier/courier-mlm_0.45.6-1_i386.deb
courier-mta-ssl_0.45.6-1_i386.deb
  to pool/main/c/courier/courier-mta-ssl_0.45.6-1_i386.deb
courier-mta_0.45.6-1_i386.deb
  to pool/main/c/courier/courier-mta_0.45.6-1_i386.deb
courier-pcp_0.45.6-1_i386.deb
  to pool/main/c/courier/courier-pcp_0.45.6-1_i386.deb
courier-pop-ssl_0.45.6-1_i386.deb
  to pool/main/c/courier/courier-pop-ssl_0.45.6-1_i386.deb
courier-pop_0.45.6-1_i386.deb
  to pool/main/c/courier/courier-pop_0.45.6-1_i386.deb
courier-ssl_0.45.6-1_i386.deb
  to pool/main/c/courier/courier-ssl_0.45.6-1_i386.deb
courier-webadmin_0.45.6-1_i386.deb
  to pool/main/c/courier/courier-webadmin_0.45.6-1_i386.deb
courier_0.45.6-1.diff.gz
  to pool/main/c/courier/courier_0.45.6-1.diff.gz
courier_0.45.6-1.dsc
  to pool/main/c/courier/courier_0.45.6-1.dsc
courier_0.45.6.orig.tar.gz
  to pool/main/c/courier/courier_0.45.6.orig.tar.gz
sqwebmail_0.45.6-1_i386.deb
  to pool/main/c/courier/sqwebmail_0.45.6-1_i386.deb

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-authpostgresql courier-ldap courier-faxmail courier-pcp courier-authmysql courier-imap courier-authdaemon courier-base sqwebmail courier-ssl courier-pop courier-mta courier-webadmin courier-imap-ssl courier-doc courier-mlm courier-maildrop courier-mta-ssl courier-pop-ssl
Architecture: source i386 all
Version: 0.45.6-1
Distribution: unstable
Urgency: low
Maintain...

Read more...

Revision history for this message
Debian Bug Importer (debzilla) wrote :
Download full text (7.3 KiB)

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-authdaemon_0.45.6-1_i386.deb
  to pool/main/c/courier/courier-authdaemon_0.45.6-1_i386.deb
courier-authmysql_0.45.6-1_i386.deb
  to pool/main/c/courier/courier-authmysql_0.45.6-1_i386.deb
courier-authpostgresql_0.45.6-1_i386.deb
  to pool/main/c/courier/courier-authpostgresql_0.45.6-1_i386.deb
courier-base_0.45.6-1_i386.deb
  to pool/main/c/courier/courier-base_0.45.6-1_i386.deb
courier-doc_0.45.6-1_all.deb
  to pool/main/c/courier/courier-doc_0.45.6-1_all.deb
courier-faxmail_0.45.6-1_i386.deb
  to pool/main/c/courier/courier-faxmail_0.45.6-1_i386.deb
courier-imap-ssl_3.0.5-1_i386.deb
  to pool/main/c/courier/courier-imap-ssl_3.0.5-1_i386.deb
courier-imap_3.0.5-1_i386.deb
  to pool/main/c/courier/courier-imap_3.0.5-1_i386.deb
courier-ldap_0.45.6-1_i386.deb
  to pool/main/c/courier/courier-ldap_0.45.6-1_i386.deb
courier-maildrop_0.45.6-1_i386.deb
  to pool/main/c/courier/courier-maildrop_0.45.6-1_i386.deb
courier-mlm_0.45.6-1_i386.deb
  to pool/main/c/courier/courier-mlm_0.45.6-1_i386.deb
courier-mta-ssl_0.45.6-1_i386.deb
  to pool/main/c/courier/courier-mta-ssl_0.45.6-1_i386.deb
courier-mta_0.45.6-1_i386.deb
  to pool/main/c/courier/courier-mta_0.45.6-1_i386.deb
courier-pcp_0.45.6-1_i386.deb
  to pool/main/c/courier/courier-pcp_0.45.6-1_i386.deb
courier-pop-ssl_0.45.6-1_i386.deb
  to pool/main/c/courier/courier-pop-ssl_0.45.6-1_i386.deb
courier-pop_0.45.6-1_i386.deb
  to pool/main/c/courier/courier-pop_0.45.6-1_i386.deb
courier-ssl_0.45.6-1_i386.deb
  to pool/main/c/courier/courier-ssl_0.45.6-1_i386.deb
courier-webadmin_0.45.6-1_i386.deb
  to pool/main/c/courier/courier-webadmin_0.45.6-1_i386.deb
courier_0.45.6-1.diff.gz
  to pool/main/c/courier/courier_0.45.6-1.diff.gz
courier_0.45.6-1.dsc
  to pool/main/c/courier/courier_0.45.6-1.dsc
courier_0.45.6.orig.tar.gz
  to pool/main/c/courier/courier_0.45.6.orig.tar.gz
sqwebmail_0.45.6-1_i386.deb
  to pool/main/c/courier/sqwebmail_0.45.6-1_i386.deb

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-authpostgresql courier-ldap courier-faxmail courier-pcp courier-authmysql courier-imap courier-authdaemon courier-base sqwebmail courier-ssl cour...

Read more...

Revision history for this message
Matt Zimmerman (mdz) wrote :

Fixed via sync of 0.45.6-1

Changed in courier:
status: Unknown → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.