I was testing ISO date strings like 2026-06-11T12:00:00 in after: queries against /api/v1/search, which are supported by dateparse. These get dropped as invalid by mailpit and all messages are returned.
This is likely because mailpit first uses cleanString on the date, which is then rejected as invalid by dateparse because of the lowercase t.
Transparency note: I found the probable cause with GPT-5.5 in my pi-coding-agent harness. No LLM generated text has reached this issue though :)
I was testing ISO date strings like
2026-06-11T12:00:00inafter:queries against/api/v1/search, which are supported bydateparse. These get dropped as invalid bymailpitand all messages are returned.This is likely because mailpit first uses
cleanStringon the date, which is then rejected as invalid bydateparsebecause of the lowercaset.Transparency note: I found the probable cause with
GPT-5.5in mypi-coding-agentharness. No LLM generated text has reached this issue though :)