* Timo Sirainen :
> On 1.6.2012, at 23.58, Patrick Ben Koetter wrote:
>
> > Besides pulling together all the data we also think it would be useful to
> > have
> > an SNMP interface to access the stats.
>
> I had thought about SNMP before also, but for the current kind of stats that
> are exporte
I forgot to include this config info:
> # 1.0.15: /etc/dovecot/dovecot.conf
> log_timestamp: %Y-%m-%d %H:%M:%S
> protocols: imap pop3
> ssl_listen: *
> ssl_disable: yes
> disable_plaintext_auth: no
> login_dir: /var/run/dovecot/login
> login_executable(default): /usr/lib/dovecot/imap-login
> logi
On 1.6.2012, at 23.58, Patrick Ben Koetter wrote:
> Besides pulling together all the data we also think it would be useful to have
> an SNMP interface to access the stats.
I had thought about SNMP before also, but for the current kind of stats that
are exported I couldn't think of any reasonable
Debian Lenny, Dovecot v 1.0.15.
I'm getting a lot of what I think is a local socket asking
dovecot:auth to verify username/passwords:
> May 31 09:00:54 server dovecot-auth: pam_unix(dovecot:auth): authentication
> failure; logname= uid=0 euid=0 tty=dovecot ruser=admin rhost=
Note the empty 'r
Timo,
following our discussion on dovecot stats at the LinuxTag 2012 my team and I
sat down and put together a list of stat items we think to be useful in daily
dovecot usage.
Besides pulling together all the data we also think it would be useful to have
an SNMP interface to access the stats. Our
Hi folks,
I'm setting up a dovecot server with managesieve support. I'd like to
offer spamfiltering through a Sieve script to my users by default,
but still allow them to modify the filtering rules through Managesieve.
I found the sieve_global_path configuration option, which seems perfect
for wh
Hi,
I am seeing inconsistencies in search results (finding 2 emails when only 1
exists, finding the email when it has been moved to another folder, etc).
I figured I should run force-resync to fix any issues. I ran the following:
doveadm -v force-resync -u and I got some worrysome logs.
- I s
On 31.5.2012, at 16.58, henrixd wrote:
> Why commenting out "inet_listener imaps {}" won't stop dovecot to listen port
> 993? I think this would be expected behavior. Just curious, finally got it
> working with port = 0. :)
When you comment out something, Dovecot uses the default settings for i