[Tickets #12520] Date range in Sieve-based Vacation responder does not work for some mail servers

[noreply at bugs.horde.org]

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

Ticket URL: http://bugs.horde.org/ticket/12520
------------------------------------------------------------------------------
  Ticket             | 12520
  Created By         | stuart at ruby.naifeh.org
  Summary            | Date range in Sieve-based Vacation responder does not
                     | work for some mail servers
  Queue              | Ingo
  Version            | Git master
  Type               | Bug
  State              | Unconfirmed
  Priority           | 1. Low
  Milestone          |
  Patch              | 1
  Owners             |
------------------------------------------------------------------------------


stuart at ruby.naifeh.org (2013-07-31 21:26) wrote:

I have Ingo set up to use a sieve backend with dovecot/sieve as the  
underlying mail/sieve server.  I can create a vacation responder on  
Horde, and it successfully generates the script, but if I set a date  
range for the vacation responder, the script does not fire for mail  
coming from or to systems that either do not add or remove the  
Received header (as some systems to to protect information about  
internal networks or sender ip address) or that use X-Received instead  
of Received (as gmail apparently does).

The issue is that Ingo assumes the relevant date will be in a Received  
header. On systems that strip the Received header or use the  
X-Received header, the sieve header function does not find a header to  
check, and the vacation responder therefore does not fire.

The attached patch replaces the regex/header match with a date  
comparison using the sieve Date and Relational extensions.  Rather  
than comparing the date in the Received header, it uses the current  
system date at the time the filter is fired to determine whether the  
reply should be sent.