I have a Dovecot server that gets some old sessions. One back-end server has 5/224 sessions open since September and another 14 from this month that are more than 2 days old. A total of 8.5% of sessions are more than 2 days old. This isn't necessarily a problem on it's own, none of the servers have enough load that 8.5% more or less will matter. But it becomes a problem when a user accumulates enough open and possibly dead sessions over a month that the limit of open sessions is reached and they open a support ticket. It's documented that some MUAs have problems with sessions getting killed, the problems in question can't be that great because no Internet connection is 100% reliable and a significant portion of the user-base doesn't have persistent IP addresses. In my own testing the most I've been able to do is generate a warning message about a session being closed. Is there any reason for not killing the sessions? If there is no good reason not to kill them then is there a way of making Dovecot or Perdition kill a session after it's been IDLE for a couple of days? Otherwise I guess I'll have to use a cron job that kills them. -- My Main Blog http://etbe.coker.com.au/ My Documents Blog http://doc.coker.com.au/