Time drift in manual autoresponder

[ChristophWurst]

Steps to reproduce

1. Set up an account
2. Enable Sieve
3. Enable the autorepsonder for 2023-11-10 to 2023-11-10 (one day)

Expected behavior

Autoresponder is active 2023-11-10

Actual behavior

Autoresponder is active 2023-11-09

{"version":1,"enabled":true,"start":"2023-12-09","end":"2023-12-09","subject":"Testing","message":"This is a test."}
if allof(currentdate :value "ge" "date" "2023-12-09", currentdate :value "le" "date" "2023-12-09") {
...

Mail app version

3.5.0 RC3

Mailserver or service

No response

Operating system

No response

PHP engine version

None

Web server

None

Database

None

Additional info

No response

[ChristophWurst]

This could be related to #9077 and moving the sieve logic to the backend. We send a js date to the server and this could lead to the same issue fixed by nextcloud/server#41703.

[ChristophWurst]

Assigning high priority because until fixed, dates entered by users result in incorrect autoresponders, which we can't fix once they are stored.