s from the example, than
> > searching for events fields etc creating your own.
> > >
> > >
> > >[1]
> > >https://doc.dovecot.org/configuration_manual/stats/openmetrics/
> > >
> >
> > Point is to use some external tool for that. Dovecot p
or
> >
> >It should be on this page, because I do not see it there?
> >https://doc.dovecot.org/admin_manual/list_of_events/#list-of-events
> >
> >I wonder even if this is correct, because from the event name I would
> assume this metric is calculate
he page is now updated.
>
>I did not even know, I just picked the first one from the example to search for
>
>It should be on this page, because I do not see it there?
>https://doc.dovecot.org/admin_manual/list_of_events/#list-of-events
>
>I wonder even if this is correct, because f
st one from the example to search for
It should be on this page, because I do not see it there?
https://doc.dovecot.org/admin_manual/list_of_events/#list-of-events
I wonder even if this is correct, because from the event name I would assume
this metric is calculated when a client disconnects. When I use t
On 07/10/2021 22:19, Marc wrote:
I also do not see where this client_connection_finished is described.
Thanks for pointing it out. It was indeed a documentation error as there
is no such event. The page is now updated.
vecot.org/configuration_manual/stats/openmetrics/
Yes thanks I have these, but if I see this list[1] and what configurations
options exists, it could be little longer example. I also do not see where this
client_connection_finished is described.
[1]
https://doc.dovecot.org/admin_manual/list_of_events/#list-of-events
On 07/10/2021 20:27, Marc wrote:
I am struggling a bit with getting some basic metrics into prometheus. Is there
some sample metrics file that has most common metrics configured?
This page has sample configurations and the corresponding exports:
I am struggling a bit with getting some basic metrics into prometheus. Is there
some sample metrics file that has most common metrics configured?
[@ conf.d]# cat 05-metrics.conf
# https://doc.dovecot.org/admin_manual/event_design/#event-design
metric imap_command {
filter =
nl>
> > <mailto:step...@rename-it.nl <mailto:step...@rename-it.nl>>> wrote:
> > >
> > >
> > >
> > > On 08/09/2020 18:01, bobby wrote:
> > > > I am going through my maillog file, and noticed these
> >
20 at 12:42 PM Stephan Bosch > <step...@rename-it.nl <mailto:step...@rename-it.nl> <mailto:step...@rename-it.nl <mailto:step...@rename-it.nl>>> wrote: > > > > On 08/09/2020 18:01, bobby wrote: > > I am going through m
lt;mailto:step...@rename-it.nl>>> wrote:
>
>
>
> On 08/09/2020 18:01, bobby wrote:
> > I am going through my maillog file, and noticed these
events:
> >
> > Sep 8 15:56:17 mail dovecot[294462]: lmtp(391257):
>
> > On 08/09/2020 18:01, bobby wrote:
> > > I am going through my maillog file, and noticed these events:
> > >
> > > Sep 8 15:56:17 mail dovecot[294462]: lmtp(391257): Warning:
> > Event
> > > 0x5
...@rename-it.nl>> wrote:
On 08/09/2020 18:01, bobby wrote:
> I am going through my maillog file, and noticed these events:
>
> Sep 8 15:56:17 mail dovecot[294462]: lmtp(391257): Warning:
Event
> 0x55db5bc41200 leaked (par
Is this an affected version of the bug?
> 2.3.8 (9df20d2db)
>
> On Tue, Sep 8, 2020 at 12:42 PM Stephan Bosch
> wrote:
>
>>
>>
>> On 08/09/2020 18:01, bobby wrote:
>> > I am going through my maillog file, and noticed these events:
>> >
>
On 08/09/2020 18:01, bobby wrote:
I am going through my maillog file, and noticed these events:
Sep 8 15:56:17 mail dovecot[294462]: lmtp(391257): Warning: Event
0x55db5bc41200 leaked (parent=0x55db5bc3b830): mail-storage-service.c:1325
Sep 8 15:56:17 mail dovecot[294462]: lmtp(391257
I am going through my maillog file, and noticed these events:
Sep 8 15:56:17 mail dovecot[294462]: lmtp(391257): Warning: Event
0x55db5bc41200 leaked (parent=0x55db5bc3b830): mail-storage-service.c:1325
Sep 8 15:56:17 mail dovecot[294462]: lmtp(391257): Warning: Event
0x55db5bc3b830 leaked
Hi there,
There seem to be a race condition in IMAP NOTIFY: when two events for
the SELECTED mailbox are received soon after one another, sometimes only
the first one is being reported to clients that enabled IMAP NOTIFY. On
closer look it seems like this is most often reproducible when
On 28.10.2015 19:11, Alessio Cecchi wrote:
> Il 26.10.2015 12:04 Teemu Huovila ha scritto:
>> On 26.10.2015 12:44, Frederik Bosch | Genkgo wrote:
>>> Teemu,
>>>
>>> If just need the http request, I will need something like the following
>>> configuration, right? So no meta data plugin, but with
Il 26.10.2015 12:04 Teemu Huovila ha scritto:
On 26.10.2015 12:44, Frederik Bosch | Genkgo wrote:
Teemu,
If just need the http request, I will need something like the
following configuration, right? So no meta data plugin, but with
notify and push_notification?
protocol lmtp {
On 26.10.2015 09:45, Frederik Bosch | Genkgo wrote:
> Ah fantastic. Now I guess I can use notify plugin without push_notification
> metadata plugins, right?
Im not sure I understand the question correctly. I understood from the thread
that you would be writing a driver for the
On 26.10.2015 12:44, Frederik Bosch | Genkgo wrote:
> Teemu,
>
> If just need the http request, I will need something like the following
> configuration, right? So no meta data plugin, but with notify and
> push_notification?
>
> protocol lmtp {
> mail_plugins = $mail_plugins notify
Teemu,
If just need the http request, I will need something like the following
configuration, right? So no meta data plugin, but with notify and
push_notification?
protocol lmtp {
mail_plugins = $mail_plugins notify push_notification
}
plugin {
push_notification_driver =
Thanks again. Final question: how do I configure this plugin?
On 23-10-15 16:12, Michael M Slusarz wrote:
On 10/22/2015 12:46 AM, Frederik Bosch | Genkgo wrote:
Thanks a lot! After looking at the source, I guess the ox driver will
do. Maybe, when other people find this thread, you could
On 26.10.2015 08:59, Frederik Bosch | Genkgo wrote:
> Thanks again. Final question: how do I configure this plugin?
As the only existing driver at the moment is the OX one, the plugin is
documented in OX wiki at
http://oxpedia.org/wiki/index.php?title=AppSuite:OX_Mail#Setup_of_the_Dovecot_Push
Ah fantastic. Now I guess I can use notify plugin without
push_notification metadata plugins, right?
On 26-10-15 08:36, Teemu Huovila wrote:
On 26.10.2015 08:59, Frederik Bosch | Genkgo wrote:
Thanks again. Final question: how do I configure this plugin?
As the only existing driver at the
Teemu,
After having another look at the source code, it seems that you are
right. Thanks for making this clear.
Regards,
Frederik
On 26-10-15 12:04, Teemu Huovila wrote:
On 26.10.2015 12:44, Frederik Bosch | Genkgo wrote:
Teemu,
If just need the http request, I will need something like
On 10/22/2015 12:46 AM, Frederik Bosch | Genkgo wrote:
Thanks a lot! After looking at the source, I guess the ox driver will
do. Maybe, when other people find this thread, you could tell what dlog
is. Because I do not know it, and googling came up with little results.
"dlog" is nothing more
Michael,
Thanks a lot! After looking at the source, I guess the ox driver will
do. Maybe, when other people find this thread, you could tell what dlog
is. Because I do not know it, and googling came up with little results.
Regards,
Frederik
On 21-10-15 23:33, Michael M Slusarz wrote:
On
Hello,
We want to trigger a script after certain actions by the user (event).
This script inserts the action into message queue (e.g. Rabbit MQ)
accompanied with some data. Then one or more workers picks up the action
from the message queue and do something with it. The question is: how
can
On 10/21/2015 9:07 AM, Frederik Bosch | Genkgo wrote:
We want to trigger a script after certain actions by the user (event).
This script inserts the action into message queue (e.g. Rabbit MQ)
accompanied with some data. Then one or more workers picks up the action
from the message queue and do
Fixed:
http://hg.dovecot.org/dovecot-2.2/rev/fa979ccfa34c
http://hg.dovecot.org/dovecot-2.2/rev/f600285c3df2
On 07/26/2015 06:50 PM, Guilhem Moulin wrote:
> Here is an example with APPEND
>
> $ /usr/lib/dovecot/imap
> S1: * PREAUTH [CAPABILITY IMAP4rev1 … MOVE NOTIFY SPECIAL-USE] Logged
Here is an example with APPEND
$ /usr/lib/dovecot/imap
S1: * PREAUTH [CAPABILITY IMAP4rev1 … MOVE NOTIFY SPECIAL-USE] Logged in as
guilhem
C1: a1 NOTIFY SET (INBOXES (MessageNew MessageExpunge FlagChange))
S1: a1 OK NOTIFY completed (0.000 secs)
$ /usr/lib/dovecot/imap
but how to log who exactly triggered
particular event? For example 5 users from 5 IP addresses uses single
imap user/mailbox.
One of them deletes email and I'm logging delete related events. The
only logged thing is:
dovecot: imap(user): delete: box=INBOX, uid=673287,
msgid=some@thing
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, 4 Feb 2014, Arkadiusz Miśkiewicz wrote:
Date: Tue, 4 Feb 2014 13:09:15 +0100
From: Arkadiusz Miśkiewicz ar...@maven.pl
To: dovecot@dovecot.org
Subject: Re: [Dovecot] mail_log_events,
but who exactly triggered events? [feature request
On Tuesday 04 of February 2014, Steffen Kaiser wrote:
On Tue, 4 Feb 2014, Arkadiusz Miśkiewicz wrote:
Date: Tue, 4 Feb 2014 13:09:15 +0100
From: Arkadiusz Miśkiewicz ar...@maven.pl
To: dovecot@dovecot.org
Subject: Re: [Dovecot] mail_log_events,
but who exactly triggered events
Hi.
mail_log_events is nice addition but how to log who exactly triggered
particular event? For example 5 users from 5 IP addresses uses single imap
user/mailbox.
One of them deletes email and I'm logging delete related events. The only
logged thing is:
dovecot: imap(user): delete: box
Am 30.01.2014 10:50, schrieb Arkadiusz Miśkiewicz:
mail_log_events is nice addition but how to log who exactly triggered
particular event? For example 5 users from 5 IP addresses uses single imap
user/mailbox.
One of them deletes email and I'm logging delete related events. The only
email and I'm logging delete related events. The only
logged thing is:
dovecot: imap(user): delete: box=INBOX, uid=673287, msgid=some@thing,
size=1230
which tells me nothing about who triggered it actually (note all 5 users
were logged in at deletion time)
How to solve this problem
single
imap user/mailbox.
One of them deletes email and I'm logging delete related events. The only
logged thing is:
dovecot: imap(user): delete: box=INBOX, uid=673287, msgid=some@thing,
size=1230
which tells me nothing about who triggered it actually (note all 5 users
were logged
who exactly triggered
particular event? For example 5 users from 5 IP addresses uses single
imap user/mailbox.
One of them deletes email and I'm logging delete related events. The only
logged thing is:
dovecot: imap(user): delete: box=INBOX, uid=673287, msgid=some@thing,
size=1230
which tells me
in between them, I get EXISTS events for
each message as expected.
However, when I store a bunch of messages at once (via tag + mass copy
in mutt on a fast-ish connection), I get a few EXISTS events (sometimes
one, sometimes two) even though I copied a lot of new messages over.
I expected to get an EXISTS
messages
arrive with some time interval in between them, I get EXISTS events for
each message as expected.
However, when I store a bunch of messages at once (via tag + mass copy
in mutt on a fast-ish connection), I get a few EXISTS events (sometimes
one, sometimes two) even though I copied a lot of new
?
Somewhat rarer are events like
2007-12-06 19:36:44.114294500 dovecot: Info: POP3(): Disconnected:
Storage error during logout. top=1/1723, retr=1/4665462, del=27/61,
size=17280696
It should have logged the actual storage error before this.
and rarely we got
2007-11-24 12:10
: Error: IMAP(): FETCH for mailbox
UCE-TMP UID 1545 got too little data: 7582 vs 7590
2007-12-06 16:00:27.445497500 dovecot: Error: IMAP(): FETCH for mailbox
UCE-TMP UID 1545 got too little data: 7582 vs 7590
Somewhat rarer are events like
2007-12-06 19:36:44.114294500 dovecot
?
That is possible. We have a direct access webmail system in place.
I'll check there.
Are you using NFS or other shared
filesystem?
None of that.
Somewhat rarer are events like
2007-12-06 19:36:44.114294500 dovecot: Info: POP3(): Disconnected:
Storage error during logout. top=1
On Sat, 2007-12-08 at 22:20 +0100, Jost Krieger wrote:
On Sat, Dec 08, 2007 at 11:20:12AM +0200, Timo Sirainen wrote:
On Fri, 2007-12-07 at 21:08 +0100, Jost Krieger wrote:
The most common event is:
2007-12-06 16:00:17.837654500 dovecot: Error: IMAP(): FETCH for
mailbox
46 matches
Mail list logo
