At 3:21 PM +0000 3/9/06, Hugh Sasse wrote:
Enabling server mode is not possible given some types of client (from
my reading of the docs). I don't know all the clients people use, so
I must err on the side of caution. Or is that paranoid in 2006?
Caching requires server mode....
Server mode (and caching) should be fine as long as people access
their mail using any POP client.
If you have any users who have shell accounts, and access their mail
directly, disable server mode for those users. You can enable and
disable server mode on a per-user and/or per-group basis.
You might also want to think about using the fast-io option, which
renames the temp-drop to the spool instead of copying it. This only
works if the temp drop and spool are on the same filesystem.
You might also want to think about setting update-status-headers to
false. This is a trickier option, because some clients use the
'Status:' header, and some don't. It also trades I/O for CPU.
See the Performance section of the GUIDE, and also the descriptions
of the options.
One thing I've been trying to find time to do is take caching to the
next step, which is maintaining the cache when new mail has arrived
since the last mail check. That would make a big difference when
users leave mail on the server.
There are scripts that have been posted in the past that let you cull
old mail. Something else to think about.
--
Randall Gellens
Opinions are personal; facts are suspect; I speak for myself only
-------------- Randomly-selected tag: ---------------
A long-forgotten loved one will appear soon. Buy the negatives
at any price.
