On Sun, Aug 06, 2006 at 15:37:46 -0700, Chris Frost wrote: > I agree with your suggestion that watch_maildirs should not error on such > directories. And in fact, this is what it is supposed to do. > (Except that it actually watches the dir to see if it later becomes a > maildir.) > > The assert occured because watch_maildirs sees a folder named ".INBOX", > which would have the imap name "INBOX", and then detects a name collision > with "~/Maildir/" which also has the imap name "INBOX". > > The attached patch should correct this problem; it changes watch_maildirs > to ignore any subdirectory named ".INBOX". Can you double check that > this works correctly?
Now it seems to do the right thing. But I'm not sure what local Maildir layout is expected. Currently, mbsync produces this layout here: ~/mail/<folder>/(new|cur|tmp) The folders include a folder named "INBOX", so mswatch doesn't recognize mail as a maildir: ~/mail/INBOX/ ~/mail/foo/ ~/mail/bar/ ...etc. I created a ~/Maildir with cur, new and tmp symlinks pointing to ~/mail/INBOX/(cur|new|tmp). This seems to work. However, I don't know what local layout mswatch expects for the other folders. At least a maildir named ~/Maildir/.foo, pointing to ~/mail/foo, isn't synced. Or does it need a special mbsync configuration? Regards, Tino ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ isync-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/isync-devel
