Hello,
I'm running mutt on Cygwin (v. 1.5). I'm using the standard packages
version supplied by Cygwin, 1.4.2.2i. My mail directory is Maildir,
mounted on a managed mount to cope with the naming convention.
The mount entry is (note: line may get wrapped):
C:\Documents and Settings\username\Maildir on /home/username/Maildir type
system (binmode,managed)
My mailboxes command is supplied absolute paths:
find ~/Maildir -type d -name cur -printf '%h '
My Windows system is XP.
My maildir hierarchy has a reasonably involved tree structure, but each
actual directory is a leaf so they only have tmp, new & cur directories.
The mail is delivered by procmail.
The new mail is marked within the folders, eg if new mail arrives in
the current directory, it gets marked as new and mutt tells me it's
there. New mail in other folders is marked as new when I visit them,
but the folder is not marked in folder view, and none of the switch
to folders with new mail commands work.
I've done a lot of searching on this and not yet found any answer.
Though I've seen others with similar issues, I've not yet seen anything
that resolves mine.
I sent an email to the mutt list and Rocco there very kindly helped me
check some stuff. Mutt looks for files in the "new" dir that do not
have ":2" in the name or a "T" after the comma. Using ls confirmed that
none of the files in "new" did so. We also checked the mailcheck
settings and they seemed okay.
So, I'm wondering if this is to do with the managed mount, but I don't
know how to check this, or whether there's something else that I'm
missing.
Is anyone else using this set-up or know what issues or settings to
look at? From searching the list archives, I know that some people did
use Maildir & managed mount, but there may not be (m)any who still do.
cheers,
Adam
--
"...one cannot be angry when one looks at a penguin."
- John Ruskin
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
