Re: [courier-users] problem with imap SELECT INBOX
Stefan Hornburg (Racke) writes: > How did you install Courier-IMAP? Did you build it from source, or install a precompiled package? > It's possible that the precompiled package gets built against libfam which is likely not to be binary ABI-compatible with gamin, > even though the .so symbols are the same. So, imapd binds with the .so, but the binary ABI incompatibility is breaking everything. This might be one explanation. > The official Debian packages are indeed build against libfam. This is likely the reason. Gamin might provide source-level compatibility with libfam, but it's unlikely to provide binary ABI-level compatibility. The package should have an explicit dependency on libfam, and not allow to be installed together with Gamin. pgpeOWWAbZTta.pgp Description: PGP signature -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] problem with imap SELECT INBOX
On 12/04/2012 12:12 AM, Sam Varshavchik wrote: > Marco van Hulten writes: > >> Op zo 02 dec 2012 18:53:03 CET schreef Sam: >> > There have been occasional reports of some kind of a problem with libfam in >> > Debian that's causing this, with the actual cause being unknown. >> > >> > Rebuilding courier-imap against Gamin, instead of FAM, usually fixes this. >> >> Thank you Sam, the problem is fixed, thanks to this hint. But a funny >> thing is that Gamin was installed and not FAM. When I did an "apt-get >> install fam libfam-dev" which automatically removed Gamin, imap worked >> again. Thus there seemed to be a problem with Gamin, while FAM works >> fine (on my system). >> >> So, for folk having trouble with reading the maildir after they managed >> to login through imap, switching from Gamin to FAM or the other way >> around is a good idea to try out! > > How did you install Courier-IMAP? Did you build it from source, or install a > precompiled package? > It's possible that the precompiled package gets built against libfam which is > likely not to be binary ABI-compatible with gamin, > even though the .so symbols are the same. So, imapd binds with the .so, but > the binary ABI incompatibility is breaking everything. This might be one > explanation. > The official Debian packages are indeed build against libfam. Regards Racke -- LinuXia Systems => http://www.linuxia.de/ Expert Interchange Consulting and System Administration ICDEVGROUP => http://www.icdevgroup.org/ Interchange Development Team -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d ___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] problem with imap SELECT INBOX
Marco van Hulten writes: Op zo 02 dec 2012 18:53:03 CET schreef Sam: > There have been occasional reports of some kind of a problem with libfam in > Debian that's causing this, with the actual cause being unknown. > > Rebuilding courier-imap against Gamin, instead of FAM, usually fixes this. Thank you Sam, the problem is fixed, thanks to this hint. But a funny thing is that Gamin was installed and not FAM. When I did an "apt-get install fam libfam-dev" which automatically removed Gamin, imap worked again. Thus there seemed to be a problem with Gamin, while FAM works fine (on my system). So, for folk having trouble with reading the maildir after they managed to login through imap, switching from Gamin to FAM or the other way around is a good idea to try out! How did you install Courier-IMAP? Did you build it from source, or install a precompiled package? It's possible that the precompiled package gets built against libfam which is likely not to be binary ABI-compatible with gamin, even though the .so symbols are the same. So, imapd binds with the .so, but the binary ABI incompatibility is breaking everything. This might be one explanation. pgpThcqUIaiOU.pgp Description: PGP signature -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] problem with imap SELECT INBOX
Op zo 02 dec 2012 18:53:03 CET schreef Sam: > There have been occasional reports of some kind of a problem with libfam in > Debian that's causing this, with the actual cause being unknown. > > Rebuilding courier-imap against Gamin, instead of FAM, usually fixes this. Thank you Sam, the problem is fixed, thanks to this hint. But a funny thing is that Gamin was installed and not FAM. When I did an "apt-get install fam libfam-dev" which automatically removed Gamin, imap worked again. Thus there seemed to be a problem with Gamin, while FAM works fine (on my system). So, for folk having trouble with reading the maildir after they managed to login through imap, switching from Gamin to FAM or the other way around is a good idea to try out! Marco signature.asc Description: PGP signature -- Keep yourself connected to Go Parallel: BUILD Helping you discover the best ways to construct your parallel projects. http://goparallel.sourceforge.net___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] problem with imap SELECT INBOX
Marco van Hulten writes: while for another, I get this: $ telnet FQDN imap Trying 145.97.230.176... Connected to FQDN. Escape character is '^]'. * OK [CAPABILITY IMAP4rev1] Courier-IMAP ready. Copyright 1998-2010 Double Precision, Inc. See COPYING for distribution information. A login USERNAME PASSWORD2 B select INBOX and then it does nothing; it hangs. I can only quit it by killing the task or say couriertcpd. The permissions of ~/Maildir/* are identical (with correct respective user and group IDs). I tried to remove ~/Maildir and recreate them with maildirmake, but even then user USERNAME is not able to do B select INBOX, while user test is (also with newly created Maildir). Any ideas are welcome. I am running Debian 6.0.6 with courier-imap 4.8.0-3. There have been occasional reports of some kind of a problem with libfam in Debian that's causing this, with the actual cause being unknown. Rebuilding courier-imap against Gamin, instead of FAM, usually fixes this. pgpxyWzSEGrmm.pgp Description: PGP signature -- Keep yourself connected to Go Parallel: DESIGN Expert tips on starting your parallel project right. http://goparallel.sourceforge.net/___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
