What you describe seems to be a good indication that it isn't an imapd
issue, but rather some inetd issue. The fact that inetd answers the port
seems to indicate that it is having trouble invoking imapd.
Since this isn't an imapd issue, you'll probably be better off getting a
local UNIX expert to look at your system configuration.
However, I strongly recommend getting the imap-2007 version from
ftp://ftp.cac.washington.edu/mail/imap.tar.Z
and rebuilding both imapd and ipop3d to be based upon that version.
-- Mark --
http://panda.com/mrc
Democracy is two wolves and a sheep deciding what to eat for lunch.
Liberty is a well-armed sheep contesting the vote.
_______________________________________________
Imap-uw mailing list
Imap-uw@u.washington.edu
https://mailman1.u.washington.edu/mailman/listinfo/imap-uw
