Trying to implement expire plugin.
expire-tool works fine. This delete expunged messages but not all of them.
I have duplicate messages in appropriate folder. These messages are from
expanding postfix aliases (e.g. postmaster@, hostmaster@, abuse@ etc.
points to same mailbox and spam often sent to
On 17.8.2012, at 14.24, Oleksii Krykun wrote:
Trying to implement expire plugin.
expire-tool works fine. This delete expunged messages but not all of them.
I have duplicate messages in appropriate folder. These messages are from
expanding postfix aliases (e.g. postmaster@, hostmaster@, abuse@
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.
On Mon, 2011-04-18 at 14:45 -0500, Alex Reinhart wrote:
I resolved this issue by deleting some messages from my Junk mailbox which
had Date headers long in the past and future, despite being very old. It
appears to me that expire-tool quit when a message had a Date header forged
to be
I resolved this issue by deleting some messages from my Junk mailbox which had
Date headers long in the past and future, despite being very old. It appears to
me that expire-tool quit when a message had a Date header forged to be
non-expired, despite the message being old enough to have been
Hello,
I have dovecot set up with expire-tool to nuke Junk messages greater than 30
days old. On a server with many user accounts, it seems to work on most of them.
However, on my user account, expire-tool skips my Junk folder entirely, despite
it containing messages from January of this year.
Timo Sirainen wrote:
On Sat, 2009-12-12 at 13:46 +0200, Tapio Sokura wrote:
I'm having problems with expire-tool in Dovecot 1.2.6 not finding the
mailboxes. I had
Here's a simple way that should work:
mail_location = mbox:~/mails:INDEX=~/indexes
and then you can also drop the mail field
Hello,
I'm having problems with expire-tool in Dovecot 1.2.6 not finding the
mailboxes. I had
mail_location =
mbox:/var/spool/dovecotmail/%d/%n/mails:INDEX=/var/spool/dovecotmail/%d/%n/indexes
in dovecot.conf, but that doesn't work with expire-tool. So I commented
that out from
Charles Marcus wrote:
You forgot dovecot -n output...
# 1.2.6: /usr/local/dovecot/etc/dovecot.conf
# OS: Linux 2.6.18-164.6.1.el5 x86_64 CentOS release 5.4 (Final)
base_dir: /var/run/dovecot/
protocols: imap imaps pop3 pop3s managesieve
ssl_cert_file: /etc/pki/tls/certs/dovecot.crt
Hi!
I've upgrade from 1.1 to 1.2, and one thing I noticed, that when running
expire-tool, I get this error:
# /usr/local/sbin/dovecot --exec-mail ext /usr/local/libexec/dovecot/expire-
tool
Info: Loading modules from directory: /usr/local/lib/dovecot/imap
Info: Module loaded: /usr/local/lib
Timo Sirainen schrieb:
On Sat, 2009-06-06 at 15:35 +0200, e-frog wrote:
$ /usr/sbin/dovecot --exec-mail ext expire-tool --test
Info: Trash: timestamp 1243963680 (Tue Jun 2 19:28:00 2009
) - 1244307774 (Tue Jun 2 19:28:00 2009
)
Both human readable timestamps are equal as ctime() returns a
On Tue, 2009-06-16 at 20:39 +0200, e-frog wrote:
Thanks. I fixed it a bit differently:
http://hg.dovecot.org/dovecot-1.2/rev/1d343780e009
Thanks Timo! The timestamps are ok now, however there are still the newlines.
Just cosmetic though :-)
Info: Trash: timestamp 1240263356 (Mon Apr
Timo Sirainen schrieb:
On Tue, 2009-06-16 at 20:39 +0200, e-frog wrote:
Thanks. I fixed it a bit differently:
http://hg.dovecot.org/dovecot-1.2/rev/1d343780e009
Thanks Timo! The timestamps are ok now, however there are still the newlines.
Just cosmetic though :-)
Info: Trash: timestamp
On Sat, 2009-06-06 at 15:35 +0200, e-frog wrote:
$ /usr/sbin/dovecot --exec-mail ext expire-tool --test
Info: Trash: timestamp 1243963680 (Tue Jun 2 19:28:00 2009
) - 1244307774 (Tue Jun 2 19:28:00 2009
)
Both human readable timestamps are equal as ctime() returns a pointer
to a static
$ /usr/sbin/dovecot --exec-mail ext expire-tool --test
Info: Trash: timestamp 1243963680 (Tue Jun 2 19:28:00 2009
) - 1244307774 (Tue Jun 2 19:28:00 2009
)
Both human readable timestamps are equal as ctime() returns a pointer
to a static buffer. In addition there are some newline characters
Hello,
The patch shouldn't really have changed anything.
in 1.1.16 it works without the patch.
And I didn't fix anything in 1.1.16 either. Maybe it was some weird
compiling issue or something..
i do not have an explanation, but effect is the same. i repackaged 1.1.15
with and without
This is what I meant actually, the name just changed in v1.2.
What do you get with the attached patch?
patch fixes the problem in both cases. it does not care if --enable-debug
is enabled or disabled.
in 1.1.16 it works without the patch.
Thanks,
Andre
On Tue, 2009-06-02 at 20:21 +0200, Andre Hübner wrote:
This is what I meant actually, the name just changed in v1.2.
What do you get with the attached patch?
patch fixes the problem in both cases. it does not care if --enable-debug
is enabled or disabled.
The patch shouldn't really
line = value optimized out
That really shouldn't be happening. What dovecot version is this with?
Can you run it with valgrind?
valgrind --trace-children=yes dovecot --exec-mail ext
/usr/libexec/dovecot/expire-tool --test
signature.asc
Description: This is a digitally signed message part
Does the problem go away if you don't configure Dovecot with
--enable-devel-checks?
no, its not included in my configure-line. This is it:
./configure \
--prefix=/usr \
--sysconfdir=/etc \
--localstatedir=/var \
--mandir=/usr/share/man \
--with-ssl=openssl \
--with-storages=mbox,maildir,raw
to debug this if i get
seg.faults when running
dovecot --exec-mail ext /usr/libexec/dovecot/expire-tool --test ?
basically connect to mysql/dbd is working. if is expire-timestamp in future
i get correct results.
problem occurs when a folder is expired and action is required.
how can i debug
/UserDatabase/ExtraFields
second question is much more importend. how to debug this if i get
seg.faults when running
dovecot --exec-mail ext /usr/libexec/dovecot/expire-tool --test ?
ulimit -c unlimited
dovecot --exec-mail ext /usr/libexec/dovecot/expire-tool --test
gdb /usr/libexec/dovecot
On Tuesday 19 May 2009 22.01.42 Timo Sirainen wrote:
On Tue, 2009-05-19 at 21:53 +0200, LEVAI Daniel wrote:
This won't really work. Instead when you ran the expire-tool, it said
it dumped core, so run:
gdb /usr/local/libexec/dovecot/expire-tool core
bt full
Okay thanks:)
So
Hi!
I'm using Dovecot 1.1.15 on OpenBSD 4.4.
How can I debug this?
# /usr/local/sbin/dovecot --exec-mail ext /usr/local/libexec/dovecot/expire-
tool
Segmentation fault (core dumped)
# gdb /usr/local/sbin/dovecot
(gdb) run --exec-mail ext /usr/local/libexec/dovecot/expire-tool
Starting program
On Tue, 2009-05-19 at 21:32 +0200, LEVAI Daniel wrote:
I'm using Dovecot 1.1.15 on OpenBSD 4.4.
How can I debug this?
# /usr/local/sbin/dovecot --exec-mail ext /usr/local/libexec/dovecot/expire-
tool
Segmentation fault (core dumped)
# gdb /usr/local/sbin/dovecot
(gdb) run --exec-mail ext
On Tue, 2009-05-19 at 21:53 +0200, LEVAI Daniel wrote:
This won't really work. Instead when you ran the expire-tool, it said it
dumped core, so run:
gdb /usr/local/libexec/dovecot/expire-tool core
bt full
Okay thanks:)
So:
#2 0x1c002482 in auth_parse_input (conn=0x7fd98140
On Thu, 2009-04-23 at 08:52 +0200, Andre Hübner wrote:
is the expire plugin usable to delete mails with different settings for each
individual user?
If i view sample config at http://wiki.dovecot.org/Plugins/Expire it looks
like expire-data are related to foldernames.
Is it possible to let
Hello,
is the expire plugin usable to delete mails with different settings for each
individual user?
If i view sample config at http://wiki.dovecot.org/Plugins/Expire it looks
like expire-data are related to foldernames.
Is it possible to let each user activate the expire-plugin for different
On Wed, 2009-04-22 at 16:03 -0600, Jeff Rice wrote:
A couple questions:
First, the mailboxes to expire are stored as u...@domain/.INBOX.Trash.
How should I list them in the conf file?
You configured them correctly.
Also, is there any way to have
the system come up to date since older
On 3/15/2009 6:26 AM, Harry Lachanas wrote:
I am on dovecot 1.1.11 trying to figure out the expire tool
The thing is that when I had confed the exp tool there where a bunch
of mails inside the mail boxes. Thus it seems as if the database is
not updated about them. Is there a way to
On Mar 16, 2009, at 6:38 AM, Charles Marcus wrote:
On 3/15/2009 6:26 AM, Harry Lachanas wrote:
I am on dovecot 1.1.11 trying to figure out the expire tool
The thing is that when I had confed the exp tool there where a bunch
of mails inside the mail boxes. Thus it seems as if the database
Hi,
I am on dovecot 1.1.11 trying to figure out the expire tool
The thing is that when I had confed the exp tool there where a bunch of
mails inside the mail boxes.
Thus it seems as if the database is not updated about them.
Is there a way to update it from command line to include the
Maybe you'll find this thread useful:
http://dovecot.org/list/dovecot/2008-October/034747.html
I already saw this. Unfortunately I do not understand the complete
reasoning.
If I'm right the thread basically says
- dovecot-expire should log something with mail-debug=yes.
(it doesn't in my
On Thursday 27 November 2008 20.15.21 Jakob Curdes wrote:
Maybe you'll find this thread useful:
http://dovecot.org/list/dovecot/2008-October/034747.html
I already saw this. Unfortunately I do not understand the complete
reasoning.
If I'm right the thread basically says
- dovecot-expire
Hi, I try to get expire working, with the BDB backend and mbox mailboxes.
If I try to invoke the expire-tool like
/usr/local/sbin/dovecot --exec-mail ext
/usr/local/libexec/dovecot/expire-tool --test
I get
[EMAIL PROTECTED] ~]# /usr/local/sbin/dovecot --exec-mail ext
/usr/local/libexec
I myself wrote:
Hi, I try to get expire working, with the BDB backend and mbox mailboxes.
(...)
[EMAIL PROTECTED] ~]# /usr/local/sbin/dovecot --exec-mail ext
/usr/local/libexec/dovecot/expire-tool --test
Error: read(/var/run/dovecot/dict-server) failed: Remote disconnected
Hmm. I searched
On Wed, 2008-11-26 at 20:57 +0100, Jakob Curdes wrote:
My first finding is that I need to enable db when doing ./configure. Now
I see a berkeley database tree in the /var/run/dovecot/ directory.
However this has the timestamp of the last restart and does not change
even when I access one of
On Wednesday 26 November 2008 20.57.10 Jakob Curdes wrote:
I myself wrote:
Hi, I try to get expire working, with the BDB backend and mbox
mailboxes. (...)
[EMAIL PROTECTED] ~]# /usr/local/sbin/dovecot --exec-mail ext
/usr/local/libexec/dovecot/expire-tool --test
Error: read(/var/run
On Tue, 2008-11-04 at 17:36 +0100, Thorsten Vollmer wrote:
Hi Timo,
not long ago you fixed a bug regarding the expansion of ~/ in
mail_location that prevented expire-tool from working correctly. A
similar problem exists if mail_location contains %h: expire-tool will
use the wrong path to
On Fri, 2008-11-21 at 22:26 +0200, Timo Sirainen wrote:
On Tue, 2008-11-04 at 17:36 +0100, Thorsten Vollmer wrote:
not long ago you fixed a bug regarding the expansion of ~/ in
mail_location that prevented expire-tool from working correctly. A
similar problem exists if mail_location
Hi Timo,
not long ago you fixed a bug regarding the expansion of ~/ in
mail_location that prevented expire-tool from working correctly. A
similar problem exists if mail_location contains %h: expire-tool will
use the wrong path to access the mailbox. After replacing %h with ~,
expire-tool works as
46 matches
Mail list logo
