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@, abu
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
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
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" \
> \(
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
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.
Expirin
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 fi
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 no
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 exp
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 fro
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
>
> mail_location =
> mbox:/var/spool/dovecotmail/%d/%n/mails:INDEX=/var/spool/dovecotmail/%d/%n/indexes
>
> in dovecot.conf, but that doesn't work w
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
ssl_key_file
On 12/12/2009, Tapio Sokura (oh2...@iki.fi) wrote:
> When I run expire-tool under strace, I can see that it is indeed
> looking for the mails in the typical autodetect locations (Maildir,
> mail, Mail) under user's home directory. So it appers that
> expire-tool takes the home directory from userdb
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 dovecot.con
On Sat, 2009-07-04 at 22:15 +0200, LEVAI Daniel wrote:
> Info: expire: No expire or expire_altmove settings - plugin disabled
That's actually intended. expire-tool doesn't need (and shouldn't even
try to use) expire plugin. Removed the log message:
http://hg.dovecot.org/dovecot-1.2/rev/dff7312629a
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/loca
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: Tr
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 124026335
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 ctim
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 s
$ /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 ad
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 patc
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 re
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-05-26 at 09:35 +0200, Andre Hübner wrote:
> > 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:
..
> --enable-debug
This is what I meant actually, the name just changed in v1.2.
What do
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 \
On Tue, 2009-05-26 at 09:20 +0200, Andre Hübner wrote:
> > That really shouldn't be happening. What dovecot version is this with?
> > Can you run it with valgrind?
>
> its version 1.1.15
>
> valgrind --trace-children=yes dovecot --exec-mail ext
> /usr/li
That really shouldn't be happening. What dovecot version is this with?
Can you run it with valgrind?
its version 1.1.15
valgrind --trace-children=yes dovecot --exec-mail ext
/usr/libexec/dovecot/expire-tool --test
==31981== Memcheck, a memory error detector.
==31981== Copyright (C)
> len = 28
> #3 0x0804a949 in auth_input (conn=0x80da350) at auth-client.c:142
> line =
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
Hello,
ulimit -c unlimited
dovecot --exec-mail ext /usr/libexec/dovecot/expire-tool --test
gdb /usr/libexec/dovecot/expire-tool core
bt full
here is the output. i am not in a hurry, for me it was just testing. But you
are surely interested...
gdb /usr/libexec/dovecot/expire-tool core
GNU
setting by returning it from userdb.
http://wiki.dovecot.org/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
doveco
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
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/li
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:
&
On Tuesday 19 May 2009 21.38.18 Timo Sirainen wrote:
> 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/dovec
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/
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 pr
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
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
Hi,
I'm having some trouble getting the expire plugin to work, and I'm not
sure where to turn for troubleshooting.
This is on 1.2rc3.
To my dovecot.conf, I've added:
mail_plugins = expire
under the protocol imap and lda sections.
I also added:
dict {
expire = mysql:/etc/dovecot/dovecot
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
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
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 old
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
>
> - dov
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 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-
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
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 for
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
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 c
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
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
55 matches
Mail list logo
