--> David Woodfall <[email protected]> [2013-02-04 01:27:32 +0000]:
> I'm still no closer to solving this. It seems that mutt just ignores
> folder format for IMAP completely.
Hi David,
I'm not absolutely clear what your setup is but seems like you may
be using a similar setup to mine - reading mail on the server which
receives mail and also using imap to remotely read the mail on that
server, however, in case you are using a similar set up to me perhaps
if I describe it, it might help you.
I generally read my mail on the mx host server which also has Dovecot
imap setup. When I'm reading mail using mutt on the server, I don't
bother using imap to the localhost, the imap server is purely for
when I'm reading mail using mutt on another machine. So, I have to
setup my mailboxes for mutt on the server in a slightly different
way because Dovecot LDA creates my mailboxes with a leading '.' in
~/.maildir. This appears to me to be how your mailboxes are created?
I've also set up the imap server to automatically allow/make MUA's
subscribe to the mailboxes, so I don't need to put $check_imap_subscribed
in my muttrc file.
So I've set the $MAIL environment variable to ~/.maildir in my
shell's configuration file ( OpenBSD's version of ksh ), then I've
set $folder in my muttrc as $MAIL:
set folder=$MAIL
set mask=.
...
... and my mailboxes are set up like so:
mailboxes !
mailboxes =.foo
mailboxes =.bar
...
Note, this is only when using mutt with direct Maildir++ access on
the server
When using imap, I use pretty much the normal method for accessing
imap folders:
set tunnel="ssh -q -C kontrol '/usr/local/libexec/dovecot/imap'"
set folder=imaps://kontrol.kode5.net/
set spoolfile=+inbox
set header_cache=~/.header_cache
...
Obviously, you needn't use the tunnel method. I find it helps,
though, when I'm accessing mail from another computer in my LAN as
there's not much point in letting mutt find the server through the
internet and setting $folder to imaps://hostname or using the
internal ip makes mutt complain about the ssl cert which of course
has been created using the FQDN.
Jamie
--
Primary Key: 4096R/1D31DC38 2011-12-03
Key Fingerprint: A4B9 E875 A18C 6E11 F46D B788 BEE6 1251 1D31 DC38
