Red Hat Bugzilla – Bug 162892
courier-imap folder prefix settings wrong
Last modified: 2007-11-30 17:11:09 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4
Description of problem:
If i try to configure squirrelmail with courier-imap (installed from source) a cannot create maildir error is given when logged in to squirrelmail. Squirrelmail in configured using the default courier-imap settings that are supplied by squirrelmail.
This error happens because the fedora squirrelmail installation overrides the default_folder_prefix to make squirrelmail work with dovecot. Removing the overridden prefix makes it work.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Install and configure courier-imap
2.Install and configure squirrelmail to use courier-imap
3.Login to squirrelmail
Actual Results: The mail overview is shown, the folders overview not.
Squirrelmail 1.5 has default settings for dovecot that can be selected during squirrelmail configuration. Perhaps it is possible to backport these changes?
We can't have it both ways. We had to set it to our preferred IMAP server,
which is dovecot. Sorry if this inconveniences you, but you can easily fix it
for your own install.
Setting it to the preferred IMAP server makes sense, but what about using the
squirrelmail 1.5 settings for dovecot? That way there is no need for the
overridden configuration file. Selecting the correct imap server isn't a problem
Or am I missing something in my assumptions?
We ship it so it requires no configuration to work with our preferred IMAP
server, which we also ship. We do not ship courier-imap anymore in Core, but
you are free to download it from Extras and reconfigure squirrelmail to use it.
However... Bug #162568 indicates that you probably don't want to use FC4
squirrelmail at all since it is incompatible with the PHP. We can't ship the
unstable CVS version in the distribution, so we're stuck at the moment with no
OK thx for the info. Concerning bug 162568, i did not yet find any problems. But
i'm setting up a new system, so did not test it very good yet.
I do hope the 1.5 version will be released any time soon... been in development
for over a year now :(.
Again thx for the quick replies.