On 21/04/2010, at 9:48 AM, Ozgur Kazancci wrote: > Hi, > > I've a strange problem; > > I installed an OpenBSD mail server last day with Postfix, Courier-Imap..etc > > Everything was working fine, until i wanted to re-create an e-mail account. > > Now, when i'm trying to make user's directory, > (as root) /usr/local/bin/maildirmake -q 10000000S /var/vmail/domain.com/user > > Maildirmake does not response the command. It just waits for forever, > cursor waits, no output (just like when you simply run 'cat' without pointing to a file) > till i interrupt with CTRL+C. > Seems to be a common thing with Courier (never used it myself.)
Googled for "Maildirmake quota hangs" and find a few results ... http://www.mail-archive.com/courier-i...@lists.sourceforge.net/msg03319.html <quote>This means that Maildir is not a valid maildir.</quote> And try searching on the Courier lists for "maildirmake quota hangs" ... http://markmail.org/browse/net.sourceforge.lists.courier-users And an answer (from 2002) is there ... might even be the right answer ... HTH. > I thought its maybe because of the permissions, > But neither chown -R vmail:vmail /var/vmail did not solve that. > > details: > > OpenBSD 4.6-stable > > #which maildirmake > /usr/local/bin/maildirmake > > # ls -al /usr/local/bin/maildirmake > -r-xr-xr-x 1 root bin 30504 Jul 2 2009 /usr/local/bin/maildirmake > > i've created a ktrace.out file with ktrace -p $maildirmakepid while maildirmake was waiting, > kdump'd the ktrace.out file, got such messages: > > 14969 maildirmake NAMI "/var/vmail/domain.com/info/tmp/1271783205.14969_NeWmAiLdIrSiZe.hostname.serv er.com" > 14969 maildirmake RET stat -1 errno 2 No such file or directory > 14969 maildirmake CALL open(0x80b30600,0x20e,0x1a4) > 14969 maildirmake NAMI "/var/vmail/domain.com/info/tmp/1271783205.14969_NeWmAiLdIrSiZe.hostname.serv er.com" > 4969 maildirmake RET open -1 errno 2 No such file or directory > ... > > Of course, there is no such 'domain.com' or 'domain.com/user' directory in /var/vmail. > > maildirmake creates them, just like how it did last day. > > Same command, same permissions, same path, not working. > > Any idea? > > Thanks.
