Are you certain that you used the correct imapd binary? It is very easy to become confused and inadvertantly run the old binary if you have two imapd binaries on the system -- it happens *very* frequently.
Yes, I am sure. After your mail I deleted ALL temporary files and directories I am using to compile imapd. Then I untared original distribution, applied changes you recommended, compiled whole package from 0, checked for running imapd programs, copied just compiled imapd to test directory and ensured, that empty in /etc/inetd.conf points to this imapd (an it is actually the only one on this development system - the one I am trying to compile), sent HUP signal to inetd.
Result is same. Truss output shows, that imapd is looking for files and directories only in /home/martynas. Nothing like chdir or stat for any files/dirs in /data/mail/martynas. Actually "grep data truss_output" is empty.
So now I am a little bit confused ... Sorry for this.
Do you have any opinion about possibility to make imapd use closedBox feature and ensure, that chroot will be done to correct directory in pw_login procedure ? Are there any "bad" experiences with closedBox (user's inbox is in same /data/mail/<user> directory) ?
Thank you again for your time and support.
With best regards Martynas
