IMAP configuration error

The iworx courrier IMAP daemon is slightly misconfigured. By default, it wants FAM to be running. But iworx’s default config is to have FAM (and xinet) disabled.
The result is that it fills the logs with:

@40000000422e0fba06f8996c ERR: Error: Input/output error
@40000000422e0fba06f8d7ec ERR: Check for proper operation and configuration
@40000000422e0fba06f8dbd4 ERR: of the File Access Monitor daemon (famd).
@40000000422e0fba11d0729c ERR: Failed to create cache file: maildirwatch ([elided])
@40000000422e0fba11d16c9c ERR: Error: Input/output error
@40000000422e0fba11d1ab1c ERR: Check for proper operation and configuration
@40000000422e0fba11d1af04 ERR: of the File Access Monitor daemon (famd).
@40000000422e0fba24613d74 ERR: Failed to create cache file: maildirwatch ([elided])
@40000000422e0fba24621c1c ERR: Error: Input/output error
@40000000422e0fba246256b4 ERR: Check for proper operation and configuration
@40000000422e0fba24625a9c ERR: of the File Access Monitor daemon (famd).
@40000000422e0fba360b0794 ERR: Failed to create cache file: maildirwatch ([elided])
@40000000422e0fba360baf8c ERR: Error: Input/output error

etc.

The solution is to do one of two things:


# chkconfig xinetd on
# chkconfig sgi_fam on
# service xinetd start

I would prefer that this not be done, personally, fam kinda sucks, and there’s no need for the feature that requires it:

REALTIME CONCURRENT FOLDER STATUS UPDATES
Setting the IMAP_ENHANCEDIDLE to 1 in /etc/courier/imapd enables real-
time concurrent folder status updates. When relatime folder status
updates are enabled all IMAP mail clients that have the same folder
open will be immediately notified of any changes to the folder’s con-
tents.

Why on earth would that feature would be worth enabling an RPC work-alike is beyond me.

a more preferable solution is to build imap with the --disable-fam option. This probably requires a patch, and is the Hard Way.

(am I the only one using IMAP?)

We use IMAP internally as well. Next time we update IMAP we’ll compile with that --disable-fam option. That error in the log looks worse than it actually is, it doesn’t cause any problems from the user’s perspective that I’m aware of.

Paul

Thanks Paul.

Just a note, that compile option may not be available in a generic package. I believe that a patch may be available to add that option. I know it has no effect, and doesn’t hurt anything, but I hate filling logs for no reason (it reduces their usefulness).

Thanks again