I've got about 30 domains hosted on this machine with qmail/vpopmail/courier-imap. Not a single problem; this system works excellent and until now I've had nary a problem.
Courier-IMAP version 0.32 (? no --version option, this was from an unstripped binary) vpopmail version 4.9.10 I've been running across a *very* strange bug. one user on one domain can no longer get into his IMAP folder; imaplogin says that the folder is locked. Now normally that just means the +t bit is set. However this is not the case. he can check his mail perfectly via POP3 and mail can be delivered to his folder without trouble. There's nothing unusual about the name: jcole. the domain is equally uninteresting: overnightradio.com. I've asked this in the vpopmail list but haven't received any responses. I'm pretty sure it's not a vpopmail problem, since I can grab email via POP3 and delivery to the Maildirs works fine. This would not be the case if the +t bit actually was set on the Maildir. It seems to be some kind of interaction between vchkpw and imaplogin. What I have tried: - vdeluser'ing the guy and vadduser'ing him back. I verified that his directory disappeared and that trying to check his mail via IMAP returns a "user not found" instead of "LOCKED" -- check, but still get a "LOCKED" after adding him back (the directory was obliterated, so any +t bit should have been gone) - creating a new user in that domain and checking mail via IMAP - no problem. - deleting vpasswd.cdb and rerunning vpasswd on the user - no change. - renaming the user's directory to "asdf" and changing the login name/home dir to "asdf" in vpasswd (and deleting the cdb and recreate with vpasswd) -- user can now check mail as asdf@domain!?! - renaming the user's directory back to his username and modifying the user's home directory (keeping username "asdf" in vpasswd (and updating the cdb)) -- user can still check mail without problem as asdf@domain. - changing username back to normal in vpasswd (and running vpasswd to update the cdb) -- this returns the vpasswd file back to what it normally is -- user can no longer check email (LOCKED returned from imaplogin) ?! It is very very strange; it's like imaplogin has kept state for this particular user NAME and refuses to let go. I've stopped and restarted courier-imap a half dozen times and searched around for some kind of state file but I haven't been successful in finding one. I also tried wrapping imaplogin in a shell script so I could strace it but courier-imap doesn't seem to like that. :-) I scanned my entire system for sticky-bitted directories. only /tmp and /usr/tmp have the +t bit set. Similar results for +t'd files: nothing interesting. As I said, the user can check email via POP3 without issue and none of the other users in any of the domains (including this one) have trouble -- it's just with this particular username, which has worked for many months before this. I haven't upgraded vpopmail or imap in this time either. Anyone? I'm not sure what to try next. Courier-imap has shit-for-logging capability (well the imaplogin module anyway) and I'm running out of ideas short of trying to do a total courier-imap upgrade which should not be necessary. Regards, Andrew _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
