Michael Wessel writes:
When I run for example:
doveadm -D search -A mailbox Trash savedbefore 60d > /tmp/discard
I previously observed that the "date.saved" field (tested by savedbefore) seems to be clustered around particular timestamps.
Dumping out this field using
doveadm -ftab fetch -A \
"mailbox date.saved" \
\( mailbox Trash OR mailbox Junk OR mailbox "Deleted Items" \)it seems the timestamps do not actually correspond to when the client moves messages to their trash folder, but rather, to the time I query for it i.e. a query instantiates this value. This timestamp is then retained.
In practice, if this query is done on a periodic interval (e.g. daily), the date.saved will be roughly correct, and is usable as an age test for expungement.
Is there a way to force this value to be cached when the client actually saves or moves a message?
Joseph Tam jtam.home@gmail.com