Hello,
> Thanks. Looks like it was a simple mdbox-specific bug. Fixed:
> http://hg.dovecot.org/dovecot-2.0/rev/2269cea521b6
Yes, that was it. Expunging works fine now.
Regards
Christoph
Hello,
>> I have attached a file with the output of yesterday's cron job's
>> execution. As
>> you can see, after expunging there are still messages in the Trash
>> folder,
>> though expunge itself says that it has removed the first message.
>
> Thanks. Looks like it was a simple mdbox-specific bu
On Sun, 2011-04-10 at 09:11 +0200, Christoph Pleger wrote:
> I have attached a file with the output of yesterday's cron job's execution.
> As
> you can see, after expunging there are still messages in the Trash folder,
> though expunge itself says that it has removed the first message.
Thanks.
Hello,
Timo Sirainen wrote:
> > Is there any solution in sight for this? Is there some additional
> > information I can give you for solving that problem?
>
> Well, the weird thing is that the logs say it's expunging everything and
> you say it's not.. What about if you change the cronjob to do:
On Sat, 2011-04-02 at 11:21 +0200, Christoph Pleger wrote:
> Hello,
>
> > It looks like it expunged all the messages from Trash. Did you check if
> > that happened? Did it expunge too many messages?
> >
> > > Mar 18 09:50:28 joseph dovecot: imap(christoph): Debug: expire: Saving
> > > first messag
Hello,
> It looks like it expunged all the messages from Trash. Did you check if
> that happened? Did it expunge too many messages?
>
> > Mar 18 09:50:28 joseph dovecot: imap(christoph): Debug: expire: Saving
> > first message to Trash, updating timestamp to 1300438228
>
> This happens, because it
Hello,
>> Today, the daily cronjob expired some messages. I have attached the
>> output of
>> the job.
> It looks like it expunged all the messages from Trash. Did you check if
> that happened? Did it expunge too many messages?
No, after expunging, there still were messages in the Trash folder.
On Fri, 2011-03-18 at 10:02 +0100, Christoph Pleger wrote:
> Today, the daily cronjob expired some messages. I have attached the output of
> the job.
It looks like it expunged all the messages from Trash. Did you check if
that happened? Did it expunge too many messages?
> Mar 18 09:50:28 joseph
Hello,
> > Big surprise: Something bad must have happened after the messages were
> > deleted from Trash; now all messages are zero days old.
>
> Are you using maildir? Did you run with those patches + mail_debug=yes?
Today, the daily cronjob expired some messages. I have attached the output of
Hello,
> > Big surprise: Something bad must have happened after the messages were
> > deleted from Trash; now all messages are zero days old.
>
> Are you using maildir? Did you run with those patches + mail_debug=yes?
Today, the daily cronjob expired some messages. I have attached the output of
Hello,
Timo Sirainen wrote:
> > > It seems to work now. Message were expunged today and 'doveadm search
> > > -A mailbox Trash savedbefore d' still shows me messages that are
> > > four days old or younger.
> >
> > Big surprise: Something bad must have happened after the messages were
> > delete
On Sat, 2011-03-12 at 15:54 +0100, Christoph Pleger wrote:
> > > So it's as if the timestamp keeps changing to the newest deleted
> > > message.. Maybe mail_debug=yes shows something helpful with these
> > > patches:
> > >
> > > http://hg.dovecot.org/dovecot-2.0/rev/eac54c2dc98b
> > > http://hg.do
Hello,
I wrote:
> > So it's as if the timestamp keeps changing to the newest deleted
> > message.. Maybe mail_debug=yes shows something helpful with these
> > patches:
> >
> > http://hg.dovecot.org/dovecot-2.0/rev/eac54c2dc98b
> > http://hg.dovecot.org/dovecot-2.0/rev/63ed0d3f4f52
> > http://hg.d
Hello,
Timo Sirainen wrote:
> > Does anyone have an idea what is going wrong with the timestamps?
>
> So it's as if the timestamp keeps changing to the newest deleted
> message.. Maybe mail_debug=yes shows something helpful with these
> patches:
>
> http://hg.dovecot.org/dovecot-2.0/rev/eac54c2dc
On Sun, 2011-03-06 at 22:23 +0100, Christoph Pleger wrote:
> Today, messages from Trash have been expunged again.
>
> The only timestamp in the database is Sun Mar 6 08:37:55 UTC 2011. This is
> obviously not the time from when the oldest message in the Trash mailbox was
> moved into that mai
Hello,
Timo Sirainen wrote:
> Are the timestamps wrong in the database? They should contain the
> timestamp of the oldest save-date of message in the mailbox.
Today, messages from Trash have been expunged again.
The only timestamp in the database is Sun Mar 6 08:37:55 UTC 2011. This is
obvio
On 2/28/2011 1:56 PM, Christoph Pleger wrote:
Hello,
How can I look at the timestamps? By opening my database with sqlite3 and then
enter "select * from expires;"? I did that and it showed:
christoph|Trash|1298917682
How can I check if this timestamp is correct? It is not really human readable
Hello,
How can I look at the timestamps? By opening my database with sqlite3 and then
enter "select * from expires;"? I did that and it showed:
christoph|Trash|1298917682
How can I check if this timestamp is correct? It is not really human readable.
> doveadm fetch -u user@domain date.saved ma
Hello,
> Are the timestamps wrong in the database? They should contain the
> timestamp of the oldest save-date of message in the mailbox.
How can I look at the timestamps and check them? I opened my database with
sqlite3 and entered "select * from expires;" this showed only one line:
christoph|
On Sat, 2011-02-19 at 10:10 +0100, Christoph Pleger wrote:
> I started to use the expire plugin about one month ago. Since then,
> using "doveadm search -A mailbox Trash savedbefore " with different
> values for , I could see every day how the messages were getting older.
>
> Yesterday was th
Hello,
I am running dovecot 2.0.9 with expire plugin, using the sqlite backend. The
following command is executed every day by cron:
doveadm expunge -A mailbox Trash savedbefore 30d
I started to use the expire plugin about one month ago. Since then,
using "doveadm search -A mailbox Trash save
21 matches
Mail list logo
