Debian Bug report logs - #669146
courier-imap: Since last update (20' ago) I can't connect anymore

Package: courier-imap; Maintainer for courier-imap is Markus Wanner <markus@bluegap.ch>; Source for courier-imap is src:courier (PTS, buildd, popcon).

Reported by: Jean-Yves Barbier <lazyvirus@gmx.com>

Date: Tue, 17 Apr 2012 18:54:02 UTC

Severity: important

Tags: upstream

Found in version courier/0.67.0-1

Fixed in versions 0.73.1-1.6, 0.75.0-1

Done: Ondřej Surý <ondrej@sury.org>

Bug is archived. No further changes may be made.

Toggle useless messages

View this report as an mbox folder, status mbox, maintainer mbox

Report forwarded to debian-bugs-dist@lists.debian.org, Stefan Hornburg (Racke) <racke@linuxia.de>:
Bug#669146; Package courier-imap. (Tue, 17 Apr 2012 18:54:04 GMT) (full text, mbox, link).

Acknowledgement sent to Jean-Yves Barbier <lazyvirus@gmx.com>:
New Bug report received and forwarded. Copy sent to Stefan Hornburg (Racke) <racke@linuxia.de>. (Tue, 17 Apr 2012 18:54:04 GMT) (full text, mbox, link).

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

Package: courier-imap
Version: 4.10.0-1
Severity: grave
Tags: upstream
Justification: renders package unusable

Dear Maintainer,

   * What led up to the situation?
An update.

   * What exactly did you do (or not do) that was effective (or
     ineffective)?
I just updated.

   * What was the outcome of this action?
Even after restarting courier-imap & courier-authdaemon I can't connect anymore
to courier-imap.

   * What outcome did you expect instead?
Being able to conect and send/receive emails after update, as it always worked
out of the box.



-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 3.2.0-2-686-pae (SMP w/1 CPU core)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages courier-imap depends on:
ii  courier-authlib                 0.63.0-6
ii  courier-base                    0.67.0-1
ii  debconf                         1.5.42
ii  libc6                           2.13-27
ii  libgamin0 [libfam0]             0.1.10-4
ii  libgdbm3                        1.8.3-10
ii  postfix [mail-transport-agent]  2.9.1-4

courier-imap recommends no packages.

Versions of packages courier-imap suggests:
ii  claws-mail [imap-client]  3.8.0-1
ii  courier-doc               <none>
ii  courier-imap-ssl          <none>
ii  iceape [imap-client]      2.7.3-2
ii  mutt [imap-client]        1.5.21-5+b1
ii  opera [imap-client]       11.62.1347

-- no debconf information

Information forwarded to debian-bugs-dist@lists.debian.org, Stefan Hornburg (Racke) <racke@linuxia.de>:
Bug#669146; Package courier-imap. (Tue, 17 Apr 2012 20:03:03 GMT) (full text, mbox, link).

Acknowledgement sent to "Stefan Hornburg (Racke)" <racke@linuxia.de>:
Extra info received and forwarded to list. Copy sent to Stefan Hornburg (Racke) <racke@linuxia.de>. (Tue, 17 Apr 2012 20:03:03 GMT) (full text, mbox, link).

Message #10 received at submit@bugs.debian.org (full text, mbox, reply):

On 04/17/2012 08:50 PM, Jean-Yves Barbier wrote:
> Package: courier-imap
> Version: 4.10.0-1
> Severity: grave
> Tags: upstream
> Justification: renders package unusable
>
> Dear Maintainer,
>
>     * What led up to the situation?
> An update.
>
>     * What exactly did you do (or not do) that was effective (or
>       ineffective)?
> I just updated.
>
>     * What was the outcome of this action?
> Even after restarting courier-imap&  courier-authdaemon I can't connect anymore
> to courier-imap.
>
>     * What outcome did you expect instead?
> Being able to conect and send/receive emails after update, as it always worked
> out of the box.
>

Please check your logfiles for messages (mail.log, messages). Are the daemons
running (ps aux | grep courier)?

Regards
         Racke

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

Information forwarded to debian-bugs-dist@lists.debian.org, Stefan Hornburg (Racke) <racke@linuxia.de>:
Bug#669146; Package courier-imap. (Wed, 18 Apr 2012 08:30:11 GMT) (full text, mbox, link).

Acknowledgement sent to "Stefan Hornburg (Racke)" <racke@linuxia.de>:
Extra info received and forwarded to list. Copy sent to Stefan Hornburg (Racke) <racke@linuxia.de>. (Wed, 18 Apr 2012 08:30:12 GMT) (full text, mbox, link).

Message #20 received at submit@bugs.debian.org (full text, mbox, reply):

On 04/17/2012 08:50 PM, Jean-Yves Barbier wrote:
> Package: courier-imap
> Version: 4.10.0-1
> Severity: grave
> Tags: upstream
> Justification: renders package unusable
>
> Dear Maintainer,
>
>     * What led up to the situation?
> An update.
>
>     * What exactly did you do (or not do) that was effective (or
>       ineffective)?
> I just updated.
>
>     * What was the outcome of this action?
> Even after restarting courier-imap&  courier-authdaemon I can't connect anymore
> to courier-imap.
>
>     * What outcome did you expect instead?
> Being able to conect and send/receive emails after update, as it always worked
> out of the box.
>

Please test your IMAP server through telnet, e.g. as described here:

http://documents.made-it.com/imapcmd.html

Maybe you have the following problem:

* OK [ALERT] Filesystem notification initialization error -- contact your mail administrator (check for configuration errors with the FAM/Gamin library)
c OK LOGIN Ok.

Regards
        Racke


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

Acknowledgement sent to "Stefan Hornburg (Racke)" <racke@linuxia.de>:
Extra info received and forwarded to list. Copy sent to Stefan Hornburg (Racke) <racke@linuxia.de>. (Wed, 18 Apr 2012 08:30:33 GMT) (full text, mbox, link).

Acknowledgement sent to Alberto Serrano <alb.serrano@gmail.com>:
Extra info received and forwarded to list. Copy sent to Stefan Hornburg (Racke) <racke@linuxia.de>. (Wed, 18 Apr 2012 09:42:42 GMT) (full text, mbox, link).

Message #30 received at 669146@bugs.debian.org (full text, mbox, reply):

[Message part 1 (text/plain, inline)]

Hi Racke,

We have been experiencing the same issue since upgrade to 0.67.0 (yesterday
at 19:00 GMT+2 approx.). Imap server connections don't work properly
anymore.

In /var/log/syslog, the imap log entries stop after initial connection:
     Apr 18 06:45:02 server imapd: Connection, ip=[::ffff:X.X.X.X]

Before, log entries showed information regarding the login user:  … imapd:
LOGIN, user=…

When testing imapd via telnet:

$ telnet server 143
* OK [CAPABILITY IMAP4rev1 UIDPLUS CHILDREN NAMESPACE THREAD=ORDEREDSUBJECT
THREAD=REFERENCES SORT QUOTA IDLE ACL ACL2=UNION STARTTLS] Courier-IMAP
ready. Copyright 1998-2011 Double Precision, Inc.  See COPYING for
distribution information.
01 LOGIN user password

After introducing the LOGIN command, there is no further output and seconds
later the connection is lost.

So it seems the issue is related to the login process. When using other
commands via telnet, the imapd server complains as expected:
* OK [CAPABILITY IMAP4rev1 UIDPLUS CHILDREN NAMESPACE THREAD=ORDEREDSUBJECT
THREAD=REFERENCES SORT QUOTA IDLE ACL ACL2=UNION STARTTLS] Courier-IMAP
ready. Copyright 1998-2011 Double Precision, Inc.  See COPYING for
distribution information.
foo
foo NO Error in IMAP command received by server.

Curiously, after downgrading all courier packages to 0.66.3-4,  and imap,
imap-ssl to 4.9.3-4 the problem persists.

Regards,

Alberto.

[Message part 2 (text/html, inline)]

Acknowledgement sent to Jesse Molina <jesse@opendreams.net>:
Extra info received and forwarded to list. Copy sent to Stefan Hornburg (Racke) <racke@linuxia.de>. (Wed, 18 Apr 2012 11:33:14 GMT) (full text, mbox, link).

Message #35 received at 669146@bugs.debian.org (full text, mbox, reply):

Here an FYI of a problem I had recently. I doubt this is the same issue, 
but I'll write it up anyway for posterity.

I had a similar issue about a week ago when I updated some courier 
related packages.

The issue turned out to be some kind of problem with gamin.  I switched 
from using gamin to fam and the problem went away. Gamin and fam are 
used in relation to the Enhanced IDLE functionality in Courier IMAP.

Ironically, I was using gamin because I had issues with fam a couple of 
years ago, switched, and had been happy since then. Maybe in a few years 
I'll switch back to gamin the next time fam gives me trouble.

The only indication of a problem was that occasionally, in my mail.err 
file, I would see something like;

Apr  8 09:03:41 myhostname imapd-ssl: FAMPending: timeout

Otherwise, there was almost no indication of a problem.

If you have gamin installed, look for a process running as your user, 
try killing it, and see if things magically start to work again. If so, 
that could be your problem.




-- 
# Jesse Molina
# Mail = jesse@opendreams.net
# Page = page-jesse@opendreams.net
# Cell = 1.602.323.7608
# Web  = http://www.opendreams.net/jesse/

Acknowledgement sent to "Stefan Hornburg (Racke)" <racke@linuxia.de>:
Extra info received and forwarded to list. Copy sent to Stefan Hornburg (Racke) <racke@linuxia.de>. (Wed, 18 Apr 2012 12:06:51 GMT) (full text, mbox, link).

Message #40 received at 669146@bugs.debian.org (full text, mbox, reply):

On 04/18/2012 01:25 PM, Jesse Molina wrote:
>
> Here an FYI of a problem I had recently. I doubt this is the same issue, but I'll write it up anyway for posterity.
>
> I had a similar issue about a week ago when I updated some courier related packages.
>
> The issue turned out to be some kind of problem with gamin. I switched from using gamin to fam and the problem went away. Gamin and fam are used in relation to the Enhanced IDLE functionality in Courier IMAP.
>
> Ironically, I was using gamin because I had issues with fam a couple of years ago, switched, and had been happy since then. Maybe in a few years I'll switch back to gamin the next time fam gives me trouble.
>
> The only indication of a problem was that occasionally, in my mail.err file, I would see something like;
>
> Apr 8 09:03:41 myhostname imapd-ssl: FAMPending: timeout
>
> Otherwise, there was almost no indication of a problem.
>
> If you have gamin installed, look for a process running as your user, try killing it, and see if things magically start to work again. If so, that could be your problem.
>

Yes, that could be an explanation for the problem.

Regards
        Racke


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

Message #45 received at 669146@bugs.debian.org (full text, mbox, reply):

[Message part 1 (text/plain, inline)]

Confirmed. After installing fam, the problem is solved:

# apt-get install fam libfam0

So it was probably related to the recent upgrade of libgamin0 0.1.10-4.

Thanks again,

Alberto.

PS: To those applying this workaround. Do not install only libfam0,
otherwise you will experience the problem Racke mentioned before:


* OK [ALERT] Filesystem notification initialization error -- contact
your mail administrator (check for configuration errors with the
FAM/Gamin library)

libfam0 requires fam daemon to do the real file monitoring work.


On Wed, Apr 18, 2012 at 2:01 PM, Stefan Hornburg (Racke)
<racke@linuxia.de>wrote:

> On 04/18/2012 01:25 PM, Jesse Molina wrote:
>
>>
>> Here an FYI of a problem I had recently. I doubt this is the same issue,
>> but I'll write it up anyway for posterity.
>>
>> I had a similar issue about a week ago when I updated some courier
>> related packages.
>>
>> The issue turned out to be some kind of problem with gamin. I switched
>> from using gamin to fam and the problem went away. Gamin and fam are used
>> in relation to the Enhanced IDLE functionality in Courier IMAP.
>>
>> Ironically, I was using gamin because I had issues with fam a couple of
>> years ago, switched, and had been happy since then. Maybe in a few years
>> I'll switch back to gamin the next time fam gives me trouble.
>>
>> The only indication of a problem was that occasionally, in my mail.err
>> file, I would see something like;
>>
>> Apr 8 09:03:41 myhostname imapd-ssl: FAMPending: timeout
>>
>> Otherwise, there was almost no indication of a problem.
>>
>> If you have gamin installed, look for a process running as your user, try
>> killing it, and see if things magically start to work again. If so, that
>> could be your problem.
>>
>>
> Yes, that could be an explanation for the problem.
>
> Regards
>        Racke
>
>
> --
> LinuXia Systems => http://www.linuxia.de/
> Expert Interchange Consulting and System Administration
> ICDEVGROUP => http://www.icdevgroup.org/
> Interchange Development Team
>
>

[Message part 2 (text/html, inline)]

Acknowledgement sent to "Stefan Hornburg (Racke)" <racke@linuxia.de>:
Extra info received and forwarded to list. Copy sent to Stefan Hornburg (Racke) <racke@linuxia.de>. (Wed, 18 Apr 2012 12:54:03 GMT) (full text, mbox, link).

Message #50 received at 669146@bugs.debian.org (full text, mbox, reply):

On 04/18/2012 02:15 PM, Alberto Serrano wrote:
> Confirmed. After installing fam, the problem is solved:
>
> # apt-get install fam libfam0
>
> So it was probably related to the recent upgrade of libgamin0 0.1.10-4.
>
> Thanks again,
>
> Alberto.
>
> PS: To those applying this workaround. Do not install only libfam0,
> otherwise you will experience the problem Racke mentioned before:
>
>
> * OK [ALERT] Filesystem notification initialization error -- contact
> your mail administrator (check for configuration errors with the
> FAM/Gamin library)
>
> libfam0 requires fam daemon to do the real file monitoring work.
>

Unfortunately, I cannot reproduce the problem with libgamin0 (0.1.10-4).
I'm running wheezy/testing on my machine.

Regards
          Racke


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

Message #55 received at 669146@bugs.debian.org (full text, mbox, reply):

[Message part 1 (text/plain, inline)]

On Wed, Apr 18, 2012 at 2:51 PM, Stefan Hornburg (Racke)
<racke@linuxia.de>wrote:

> Unfortunately, I cannot reproduce the problem with libgamin0 (0.1.10-4).
> I'm running wheezy/testing on my machine.
>
>
I have a cloned testing environment where I can still reproduce
it. Anything I can do?

Regards.

PS: A bit off-topic, but upgrading again courier in the testing env
reminded me of a minor inconvenience when configuring courier-mta in the
0.66.3-4 to 0.67.0-1 upgrade process. When choosing to keep the existing
customized version of the /etc/courier/smtpaccess/default configuration
file, the packaged configuration file is created as default.dpkg-dist, as
expected. However, the courier-mta.postinst runs makesmtpaccess, which
complains because of a duplicate record in default and default.dpkg-dist
with the message "Cannot store record for 127.0.0.1 - duplicate or out of
disk space.".

[Message part 2 (text/html, inline)]

Message #60 received at 669146@bugs.debian.org (full text, mbox, reply):

FYI, when I had my problem, it is notable that neither gamin, nor 
courier-imap packages were upgraded, though the problem was seen 
immediately after the upgrade.  Gamin was definitely the problem, but 
something else seems to be involved.  It was a very troublesome bug to 
figure out and the source cause wasn't obvious, which is why I went with 
fam instead of trying to downgrade packages.

If you want a full log of my upgrade, let me know and I can provide 
that. This happened back on the 8th of March.

Stefan Hornburg (Racke) wrote:
>>
>
> Unfortunately, I cannot reproduce the problem with libgamin0 (0.1.10-4).
> I'm running wheezy/testing on my machine.

-- 
# Jesse Molina
# Mail = jesse@opendreams.net
# Page = page-jesse@opendreams.net
# Cell = 1.602.323.7608
# Web  = http://www.opendreams.net/jesse/

Information forwarded to debian-bugs-dist@lists.debian.org, Stefan Hornburg (Racke) <racke@linuxia.de>:
Bug#669146; Package courier-imap. (Tue, 01 May 2012 19:30:09 GMT) (full text, mbox, link).

Acknowledgement sent to "Phil Lavin" <phil@lavin.me.uk>:
Extra info received and forwarded to list. Copy sent to Stefan Hornburg (Racke) <racke@linuxia.de>. (Tue, 01 May 2012 19:30:09 GMT) (full text, mbox, link).

Message #65 received at 669146@bugs.debian.org (full text, mbox, reply):

[Message part 1 (text/plain, inline)]

Further confirmed that installing fam and libfam0 solves the problem:

 

apt-get install fam libfam0

 

I have previously also experienced the "check for configuration errors with
the FAM/Gamin library" bug which does not seem to have reoccurred after
installing fam.

 

 

Phil

[Message part 2 (text/html, inline)]

Information forwarded to debian-bugs-dist@lists.debian.org, Stefan Hornburg (Racke) <racke@linuxia.de>:
Bug#669146; Package courier-imap. (Wed, 02 May 2012 06:33:03 GMT) (full text, mbox, link).

Acknowledgement sent to "Stefan Hornburg (Racke)" <racke@linuxia.de>:
Extra info received and forwarded to list. Copy sent to Stefan Hornburg (Racke) <racke@linuxia.de>. (Wed, 02 May 2012 06:33:03 GMT) (full text, mbox, link).

Message #70 received at 669146@bugs.debian.org (full text, mbox, reply):

On 04/18/2012 11:40 AM, Alberto Serrano wrote:
> Hi Racke,
>
> We have been experiencing the same issue since upgrade to 0.67.0 (yesterday
> at 19:00 GMT+2 approx.). Imap server connections don't work properly
> anymore.
>
> In /var/log/syslog, the imap log entries stop after initial connection:
>       Apr 18 06:45:02 server imapd: Connection, ip=[::ffff:X.X.X.X]
>
> Before, log entries showed information regarding the login user:  Â… imapd:
> LOGIN, user=Â…
>
> When testing imapd via telnet:
>
> $ telnet server 143
> * OK [CAPABILITY IMAP4rev1 UIDPLUS CHILDREN NAMESPACE THREAD=ORDEREDSUBJECT
> THREAD=REFERENCES SORT QUOTA IDLE ACL ACL2=UNION STARTTLS] Courier-IMAP
> ready. Copyright 1998-2011 Double Precision, Inc.  See COPYING for
> distribution information.
> 01 LOGIN user password
>
> After introducing the LOGIN command, there is no further output and seconds
> later the connection is lost.
>
> So it seems the issue is related to the login process. When using other
> commands via telnet, the imapd server complains as expected:
> * OK [CAPABILITY IMAP4rev1 UIDPLUS CHILDREN NAMESPACE THREAD=ORDEREDSUBJECT
> THREAD=REFERENCES SORT QUOTA IDLE ACL ACL2=UNION STARTTLS] Courier-IMAP
> ready. Copyright 1998-2011 Double Precision, Inc.  See COPYING for
> distribution information.
> foo
> foo NO Error in IMAP command received by server.
>
> Curiously, after downgrading all courier packages to 0.66.3-4,  and imap,
> imap-ssl to 4.9.3-4 the problem persists.
>

The upstream author offers two possible explanations for the stalled login:

http://sourceforge.net/mailarchive/forum.php?thread_name=cone.1335910949.185798.18151.1000%40monster.email-scan.com&forum_name=courier-imap

Regards
        Racke


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

Severity set to 'important' from 'grave' Request was from "Stefan Hornburg (Racke)" <racke@linuxia.de> to control@bugs.debian.org. (Wed, 02 May 2012 06:36:03 GMT) (full text, mbox, link).

Information forwarded to debian-bugs-dist@lists.debian.org, Stefan Hornburg (Racke) <racke@linuxia.de>:
Bug#669146; Package courier-imap. (Thu, 31 May 2012 00:33:03 GMT) (full text, mbox, link).

Acknowledgement sent to Uli Luckas <luckas@musoft.de>:
Extra info received and forwarded to list. Copy sent to Stefan Hornburg (Racke) <racke@linuxia.de>. (Thu, 31 May 2012 00:33:03 GMT) (full text, mbox, link).

Message #77 received at 669146@bugs.debian.org (full text, mbox, reply):

Hi all,
I can reproduce the problem and tried looking with strace into it.
The relevant lines of the trace seem to be these:

[pid 18269] socket(PF_FILE, SOCK_STREAM, 0) = 5
[pid 18269] connect(5, {sa_family=AF_FILE, path=@"/tmp/fam-luckas-"},
110) = ? ERESTARTSYS (To be restarted)
[pid 18269] --- SIGALRM (Alarm clock) @ 0 (0) ---

Looks like gam_server is not accepting the connection and courier not
handling that issue well.
At leat for the courier part, this information might help the developer
to fix the issue.

Why gam_server stops accepting connections is another issue to be
researched seperately.

Thanks to http://www.noah.org/wiki/Courier_IMAP_and_FAM I also did a
"netstat -np|grep /tmp/fam-" which showed quite a few connections in the
CONNECTING state. But I guess this is expected given the above strace :-)

Hope this helps resolving the issue.

Regrds,
Uli

Acknowledgement sent to Jesse Molina <jesse@opendreams.net>:
Extra info received and forwarded to list. Copy sent to Stefan Hornburg (Racke) <racke@linuxia.de>. (Thu, 31 May 2012 02:45:02 GMT) (full text, mbox, link).

Message #82 received at 669146@bugs.debian.org (full text, mbox, reply):

I filed a bug related to courier and gamin a month or three back.  Look 
for it.  Same issue, sounds like.



Uli Luckas wrote:
> Hi all,
> I can reproduce the problem and tried looking with strace into it.
> The relevant lines of the trace seem to be these:
>
> [pid 18269] socket(PF_FILE, SOCK_STREAM, 0) = 5
> [pid 18269] connect(5, {sa_family=AF_FILE, path=@"/tmp/fam-luckas-"},
> 110) = ? ERESTARTSYS (To be restarted)
> [pid 18269] --- SIGALRM (Alarm clock) @ 0 (0) ---
>
> Looks like gam_server is not accepting the connection and courier not
> handling that issue well.
> At leat for the courier part, this information might help the developer
> to fix the issue.
>
> Why gam_server stops accepting connections is another issue to be
> researched seperately.
>
> Thanks to http://www.noah.org/wiki/Courier_IMAP_and_FAM I also did a
> "netstat -np|grep /tmp/fam-" which showed quite a few connections in the
> CONNECTING state. But I guess this is expected given the above strace :-)
>
> Hope this helps resolving the issue.
>
> Regrds,
> Uli

-- 
# Jesse Molina
# Mail = jesse@opendreams.net
# Page = page-jesse@opendreams.net
# Cell = 1.602.323.7608
# Web  = http://www.opendreams.net/jesse/

Reply sent to Ondřej Surý <ondrej@sury.org>:
You have taken responsibility. (Wed, 16 Mar 2016 15:07:16 GMT) (full text, mbox, link).

Notification sent to Jean-Yves Barbier <lazyvirus@gmx.com>:
Bug acknowledged by developer. (Wed, 16 Mar 2016 15:07:16 GMT) (full text, mbox, link).

Message #87 received at 669146-done@bugs.debian.org (full text, mbox, reply):

To: 630166-done@bugs.debian.org, 669146-done@bugs.debian.org, 594847-done@bugs.debian.org, 647467-done@bugs.debian.org, 536253-done@bugs.debian.org, 502361-done@bugs.debian.org, 482127-done@bugs.debian.org, 460888-done@bugs.debian.org, 457066-done@bugs.debian.org, 450435-done@bugs.debian.org, 241299-done@bugs.debian.org, 255687-done@bugs.debian.org, 291325-done@bugs.debian.org, 294656-done@bugs.debian.org, 310839-done@bugs.debian.org, 317942-done@bugs.debian.org, 360246-done@bugs.debian.org, 394959-done@bugs.debian.org, 406877-done@bugs.debian.org, 427756-done@bugs.debian.org, 430166-done@bugs.debian.org, 438993-done@bugs.debian.org, 226141-done@bugs.debian.org, 379806-done@bugs.debian.org, 703570-done@bugs.debian.org, 100646-done@bugs.debian.org, 198880-done@bugs.debian.org, 218148-done@bugs.debian.org, 250817-done@bugs.debian.org, 296039-done@bugs.debian.org, 315636-done@bugs.debian.org, 495194-done@bugs.debian.org, 589225-done@bugs.debian.org, 273259-done@bugs.debian.org

Version: 0.73.1-1.6

I am closing all pre-wheezy bug reports and non-critical wheezy bug
reports. If you can reproduce the issue using jessie (or even better
current unstable), feel free to reopen the bug.

Cheers,
-- 
Ondřej Surý <ondrej@sury.org>
Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server

Marked as fixed in versions 0.75.0-1. Request was from Andreas Beckmann <anbe@debian.org> to control@bugs.debian.org. (Tue, 14 Jun 2016 22:00:04 GMT) (full text, mbox, link).

Bug archived. Request was from Debbugs Internal Request <owner@bugs.debian.org> to internal_control@bugs.debian.org. (Wed, 13 Jul 2016 07:30:54 GMT) (full text, mbox, link).

Send a report that this bug log contains spam.

Debian bug tracking system administrator <owner@bugs.debian.org>. Last modified: Wed Jul 24 03:24:04 2024; Machine Name: buxtehude

Debian Bug tracking system

Debbugs is free software and licensed under the terms of the GNU Public License version 2. The current version can be obtained from https://bugs.debian.org/debbugs-source/.

Debian Bug report logs - #669146 courier-imap: Since last update (20' ago) I can't connect anymore

Debian Bug report logs - #669146
courier-imap: Since last update (20' ago) I can't connect anymore