I was thinking... how about some kind of timer instead of the low watermark? It would expire say every 5 or 10 minutes (a tunable parameter), and re-read the on-disk queue, giving a chance for courier to find those old messages. The re-reading of the disk queue could depend on time, rather than the number of messages. A high watermark would still exist, to limit the size of the in-memory queue cache.
This would stop courier going back to disk after every delivery, and still make sure that old messages would not get neglected for too long.
That's a possibility for the next major release...
-------------------------------------------------------
This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger for complex code. Debugging C/C++ programs can leave you feeling lost and disoriented. TotalView can help you find your way. Available on major UNIX and Linux platforms. Try it free. www.etnus.com
_______________________________________________
courier-users mailing list
[EMAIL PROTECTED]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
