On Sat, Oct 05, 2002 at 12:32:12AM -0400, Sam Varshavchik wrote: > Diego A. Puertas F. writes: > > > --Sam Varshavchik | Thursday 03 October 2002 21:58-- > >> sqwebmail cannot be used with hard filesystem quotas. In addition > >> to the above, sqwebmail also needs to build a folder index > >> database, which obviously is not going to work. > > > > Well, is there any way to tell sqwebmail to create those files, config > > files, timestamps, flags; in short, any files that are not email; in > > another path, rather that in $HOME/maildir ? > > No. > Hmmmm ... this is not good news. In a college environment where the users do not get a shell, what can be done? And that's an ugly message, can it be improved?
One method would be to make the soft quota the real quota, and use the grace period feature to give the users time to delete and purge files so as to get below quota. The hard quota would give them some borrowed room with which to operate, while still preventing runaway situations. But reaching the hard quota would still probably mean a help desk call. The good news is that if the system is also running courier imap, the user can still access the mail via imap, using any of a variety of imap clients. If there is no PC imap client available, there is at least one viable free web imap client available using the advanced features at mail2web.com . Or there are several web imap clients that can be installed on the local system. The problem would be that now the user may never go back to using sqwebmail, and it would be necessary to support imap at the help desk. So much for the KISS principle and sqwebmail as the one-stop solution that both performs well and works well. Does anyone have a better solution? I would greatly appreciate it. Philip Tejera
