Timo Sirainen writes:
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?
Done for
On 19.7.2012, at 4.24, Joseph Tam wrote:
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
On 7/14/2012 11:14 PM, Robert Schetterer wrote:
1.2.11 is outdated you should upgrade 2.1.8 and try again
Thanks. I knew the version was old but I wasn't quite ready for the
upgrade. Anyway, I got ready, sat down and upgraded to 2.1.8 this
weekend and have it all running again now.
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
Am 15.07.2012 05:34, schrieb Michael Wessel:
Hi,
I'm running dovecot 1.2.11 on Centos and have the expire plugin enabled.
I've had this in place for some time but until now never actually ran
the expire-tool. I'm now trying to put this to use.
The expire plugin as such is working fine and
Hi,
I'm running dovecot 1.2.11 on Centos and have the expire plugin enabled.
I've had this in place for some time but until now never actually ran
the expire-tool. I'm now trying to put this to use.
The expire plugin as such is working fine and also the tool is working
fine - up to a point.
