libc-client has a patch in Debian
(debian/patches/10_disallow_escaping_home.diff) that sets the
restrictBox variable to maximum restriction by default.  While probably
OK in the context of uw-imapd, this patch breaks libc-client for many
other types of applications.  libc-client is a shared library, used by
uw-mailutils, mailsync, and libmail-cclient-perl, and so the added
security should (and could) be done at runtime for uw-imapd
specifically, not by patching the source of libc-client.  (pine would be
affected too if it wasn't shipped with its own copy of libc-client.)

This might sound like a minor problem, but I just spent more than six
hours trying to find out why mailutil was not working.  Not a word about
this in /usr/share/doc/libc-client2002edebian, either.