On 18/10/2025 20:25 EEST Philip Bondi via dovecot <dovecot@dovecot.org> wrote:

Hello to all:

Would someone be able to comment on the correct method to specify timezone?

[243] $ doveadm search -u user@domain.ca MAILBOX hover/INBOX-hover.mbx SENTSINCE "2024-01-01" SENTBEFORE "01-Jan-2025" fa6bc10562ee846855141f00d09efc50 4092 fa6bc10562ee846855141f00d09efc50 4093 fa6bc10562ee846855141f00d09efc50 4094 fa6bc10562ee846855141f00d09efc50 4095 fa6bc10562ee846855141f00d09efc50 4096 fa6bc10562ee846855141f00d09efc50 4097

[244] $ doveadm search -u user@domain.ca MAILBOX hover/INBOX-hover.mbx SENTSINCE "2024-01-01" SENTBEFORE "01-Jan-2025 00:00:00 -0400" Fatal: Invalid search date parameter: 01-Jan-2025 00:00:00 -0400

It worked with 2.4.1, what version are you using?

Aki

SENTSINCE and SENTBEFORE are "Date" inputs (day-month-year) per RFC 3501. No timezone is allowed.

See, e.g., RFC 3501[6.4.4]:

"Messages whose [RFC-2822] Date: header (disregarding time and timezone) is within or later than the specified date."

doveadm search is just proxying IMAP compliant search strings, so it uses the RFC syntax requirements.

michael

On 10/18/2025 11:25 AM MDT Philip Bondi via dovecot <dovecot@dovecot.org> wrote:

Hello to all:

Would someone be able to comment on the correct method to specify timezone?

[243] $ doveadm search -u user@domain.ca MAILBOX hover/INBOX-hover.mbx SENTSINCE "2024-01-01" SENTBEFORE "01-Jan-2025" fa6bc10562ee846855141f00d09efc50 4092 fa6bc10562ee846855141f00d09efc50 4093 fa6bc10562ee846855141f00d09efc50 4094 fa6bc10562ee846855141f00d09efc50 4095 fa6bc10562ee846855141f00d09efc50 4096 fa6bc10562ee846855141f00d09efc50 4097

[244] $ doveadm search -u user@domain.ca MAILBOX hover/INBOX-hover.mbx SENTSINCE "2024-01-01" SENTBEFORE "01-Jan-2025 00:00:00 -0400" Fatal: Invalid search date parameter: 01-Jan-2025 00:00:00 -0400

---

dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-leave@dovecot.org