| Summary | Vacation with Start/End dates triggered a month later near midnight |
| Queue | Ingo |
| Queue Version | 3.1.2 |
| Type | Bug |
| State | No Feedback |
| Priority | 1. Low |
| Owners | Horde Developers (at) |
| Requester | delrio (at) mie (dot) utoronto (dot) ca |
| Created | 11/04/2013 (4320 days ago) |
| Due | |
| Updated | 02/01/2017 (3135 days ago) |
| Assigned | 10/10/2016 (3249 days ago) |
| Resolved | 02/01/2017 (3135 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
State ⇒ Feedback
bug #14486fixed this too.For example, save the (first) Received header in a variable and
compare only against that variable, but it would require the Sieve
Variables extension.
(my own workaround was to modify the sieve script to check for
"Received" "by our.server.example.com")
Assigned to
Priority ⇒ 1. Low
Type ⇒ Bug
Summary ⇒ Vacation with Start/End dates triggered a month later near midnight
Queue ⇒ Ingo
Milestone ⇒
Patch ⇒ No
State ⇒ Unconfirmed
Autoreply got triggered again near midnight on Nov 1 (a month later)
for certain senders on a different timezone.
The emails that triggered the late autoreply had "Received" headers on
different timezones, e.g.
Received: ... Nov 1 (local timezone)
Received: ... Oct 31 (remote timezone)
The part of the sieve script that checks for Oct. 01-02 match is (simplified):
if header :regex "Received" "^.*(Oct)... {
if header :regex "Received" "^.*([0 ]1|[0 ]2)... {
vacation ...
}
}
but this also matches emails on Nov 01 that have at least one Received
header on Oct 31.