dovecot - May 2009 - Can expire-tool skip folders with "expire time in future" errors?

Hi folks,

when I run expire-tool, I often see messages like the following:

  # dovecot --exec-mail ext /usr/libexec/dovecot/expire-tool
  Info: user/Trash: stop, expire time in future: Fri May 22 17:42:23 2009

the server's dovecot.conf contains the following line:

  expire = Trash 2 Junk 7 */News 30 */Reports 7
>From what I observe, an error of "expire time in future" in one of
the
Trash folders stops expire-tool alltogether, meaning that remaining
folders like News or Reports don't get processed at all?

Is this interpretation correct? If so, can I convince expire-tool to
skip errors and continue processing other folders?

-R

On Wed, 2009-05-20 at 18:53 +0200, Ralph Seichter wrote:
> Hi folks,
> 
> when I run expire-tool, I often see messages like the following:
> 
>   # dovecot --exec-mail ext /usr/libexec/dovecot/expire-tool
>   Info: user/Trash: stop, expire time in future: Fri May 22 17:42:23 2009
It should log that only when you use --test parameter. If it happens
also without --test, what dovecot version are you using?

Anyway it's not an error. It just means that all the rest of the
mailboxes have future timestamps, and expire-tool has finished its work.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part
URL:
<http://dovecot.org/pipermail/dovecot/attachments/20090525/7738e80f/attachment-0002.bin>

Timo Sirainen wrote:
> > Info: user/Trash: stop, expire time in future: [...]
>
> It should log that only when you use --test parameter.
You're right, I've used the --test parameter to see what's going on.
> Anyway it's not an error. It just means that all the rest of the
> mailboxes have future timestamps, and expire-tool has finished its
> work.
I have folders containing messages which have been moved there -- either
by the sieve plugin or manually in Thunderbird -- days or even weeks ago.
The messages are not removed even with an expire time of "somefolder
1".

So far, I thought that the expire plugin stops when the first "expire
time in future" ist detected, but if I understand you correctly, this
message implicitely means that there are no more messages at all to be
expired?

What can I do to find out why some folders don't seem to be processed by
the expire plugin? Is there any debugging/logging data I can look into?

-R

Timo Sirainen wrote:
> Anyway it's not an error. It just means that all the rest of the
> mailboxes have future timestamps, and expire-tool has finished its work.
I upgraded to Dovecot 1.1.15, but expire still gives me trouble. I keep
seeing the following error repeatedly now:

  dict: db(secondary, ): unable to allocate space from the buffer cache
  dict: sdb.open() failed: Cannot allocate memory
  dict:
  dict: db(/var/lib/dovecot/expire.db) open failed
  dict: Failed to initialize dictionary 'expire'

When I run the expire-tool manually or by cron job, it dies with a
segmentation fault, so effectively I currently cannot use expire at all.

-R