2 Dec
2009
2 Dec
'09
12:31 p.m.
On November 29, 2009 10:15:55 AM -0800 Frank Cusack <fcusack@fcusack.com> wrote:
Easy enough for me to patch the sieve code which is likely what I'll do.
Here it is. I decided to store the timestamp (dup) info even though it isn't used when deciding to send a response, because
- it saves the addresses that vacation replies were sent to, so that when disabling vacation the user can get a report of those recipients
- if the user changes the vacation :days the dup database already exists and doesn't have to start fresh -- just like happens if they change it from (e.g.) :1 to :2
If you want to use this patch, you might want to consider using a magic number (e.g. 999) for :days instead of 0, so that users unaware of the magic number can't easily send unthrottled vacation responses. Just change the
if ( ctx->days && senv->duplicate_check != NULL ) {
part to be
if ( ctx->days != 999 && senv->duplicate_check != NULL ) {
-frank