[Tickets #1664] Delete Vacation DB on Disable

[bugs@bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/?id=1664
-----------------------------------------------------------------------
 Ticket             | 1664
 Updated By         | Ben Chavet <ben at horde.org>
 Summary            | Delete Vacation DB on Disable
 Queue              | Ingo
 Version            | 1.0.1
 State              | Feedback
 Priority           | 2. Medium
 Type               | Enhancement
 Owners             | Ben Chavet
-----------------------------------------------------------------------


Ben Chavet <ben at horde.org> (2005-05-22 20:34) wrote:

Ah, I see what you are saying now.  The following lines of the generated
script handle deleting an old database:

  5:   FILEDATE=`ls -lcn --time-style=+%s 'vacation.test at ben.chavet.net' |
awk '{ print $6 + (604800) }'`
  6:   DATE=`date +%s`
  7:   DUMMY=`test $FILEDATE -le $DATE && rm
'vacation.test at ben.chavet.net'`

The database is deleted if it was created more than X days ago, where X is
the user-defined "Number of days between vacation replies" on the vacation
form.  So, re-enabling the vacation script will result in a new database if
it has been more than X days since it was created.

So, this functionality isn't exactly obvous from the user's perspective. But
if we hide the database files, it should just be a transparent thing that
"just works" for the user.

The only potential problem I can see with this is if the user chooses some
insanely large number of days to keep the database.