cyr_expire and messages where Date: is in the future?

[Mike Eggleston]

On Wed, 09 Jan 2008, David Carter might have said:

> On Wed, 9 Jan 2008, Mike Eggleston wrote:
> 
> >Using spam assassin and sieve I have messages flagged as spam filed into
> >user.*.spam folders. I also have a 'cyr_expire -E 1 -X 1' job running
> >each morning and a 'cyradm mboxcfg expire user.*.spam expire 2' set on all
> >spam folders. One of the oddities I'm seeing is where a spam message has a
> >header of 'Date: Fri, 28 Mar 2008 00:16:17 -0800'. These messages are not
> >expiring even though the messages may physically be months or a year old.
> 
> I believe that ipurge is the problem here, not cyr_expire. ipurge uses the 
> Date: header unless you use the -X flag. Consequently a message with:
> 
>   Date: Fri, 28 Mar 2008 00:16:17 -0800
> 
> wouldn't be expunged until March.

I tried and experiment that worked using 'ipurge -d 1 -X user.$user.spam'.
The delete flags were set properly. I guess I still need to run a cyr_expire
to expunge the messages?

I want to \Delete all messages in user.*.spam and user.*.backup. Can I use
those patterns with ipurge?

Mike