Daniel Kasak writes:
Sam Varshavchik wrote:
Daniel Kasak writes:
<snipped>
Sep 13 16:29:56 [imapd-ssl] /etc/courier-imap/shared/index: No such file or directory
This message is harmless. This is a new configuration file, and this diagnostic is issued as a reminder. You can make it a zero-length file to get rid of the warning.
Yeah I did that, and yeah it stopped the warnings.
Sep 13 16:29:56 [imapd-ssl] shared-folders/clients/522.52280 Tress Cocks and Maddox/tmp/1095056996.M481233P26440_sync.screamer.nusconsulting.com.au:
What the heck is that period doing in there? Periods are used as hierarchy delimiters, and are forbidden in folder names.
The period IS a hierarchy delimiter. Under the folder 'clients' we have a set of folders with the 1st 3 digits of the file's ID ( eg 522 ) and then under that we have a folder per file ( eg 52280 Tress Cocks Maddox )
The problem is probably shared subfolders.
Should the '522' folder be an actual folder in the server's filesystem? It's always worked perfectly the way we've had it. I've just checked the man page for maildirmake to see if I got it wrong. It states:
Folders cannot be created directly within other folders. Running maildirmake -f Urgent mail/Maildir/.Drafts will not work. Instead, the period character is designated as a hierarchy separator, run maildirmake -f Drafts.Urgent mail/Maildir instead.
This is for regular folders only. Shared folders is a different beast.
For experimental purposes try replacing the period with a space, and see what happens.
pgpMQUTKHHke1.pgp
Description: PGP signature
