Bug#669146: courier-imap: Since last update (20' ago) I can't connect anymore
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=[:::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.comforum_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 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#669146: courier-imap: Since last update (20' ago) I can't
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
Bug#669146: courier-imap: Since last update (20' ago) I can't connect anymore
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 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#669146: courier-imap: Since last update (20' ago) I can't connect anymore
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=[:::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.
Bug#669146: courier-imap: Since last update (20' ago) I can't connect anymore
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 = je...@opendreams.net # Page = page-je...@opendreams.net # Cell = 1.602.323.7608 # Web = http://www.opendreams.net/jesse/ -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#669146: courier-imap: Since last update (20' ago) I can't connect anymore
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 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#669146: courier-imap: Since last update (20' ago) I can't connect anymore
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) ra...@linuxia.dewrote: 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
Bug#669146: courier-imap: Since last update (20' ago) I can't connect anymore
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 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#669146: courier-imap: Since last update (20' ago) I can't connect anymore
On Wed, Apr 18, 2012 at 2:51 PM, Stefan Hornburg (Racke) ra...@linuxia.dewrote: 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..
Bug#669146: courier-imap: Since last update (20' ago) I can't connect anymore
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 = je...@opendreams.net # Page = page-je...@opendreams.net # Cell = 1.602.323.7608 # Web = http://www.opendreams.net/jesse/ -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#669146: courier-imap: Since last update (20' ago) I can't connect anymore
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-base0.67.0-1 ii debconf 1.5.42 ii libc6 2.13-27 ii libgamin0 [libfam0] 0.1.10-4 ii libgdbm31.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 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#669146: courier-imap: Since last update (20' ago) I can't connect anymore
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 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
