Thank you very much!
Gedalya wrote on 12/03/2016 06:30:
Add %k to login_log_format_elements (in conf.d/10-logging.conf)
for example
login_log_format_elements = user=<%u> method=%m rip=%r lip=%l mpid=%e %c %k
session=<%{session}>
On 03/12/2016 12:20 AM, Luigi Rosa wrote:
Hi,
could it be poss
Forgot the important part, sorry
http://wiki.dovecot.org/Variables
On 03/12/2016 12:30 AM, Gedalya wrote:
Add %k to login_log_format_elements (in conf.d/10-logging.conf)
for example
login_log_format_elements = user=<%u> method=%m rip=%r lip=%l mpid=%e
%c %k session=<%{session}>
On 03/12/20
Add %k to login_log_format_elements (in conf.d/10-logging.conf)
for example
login_log_format_elements = user=<%u> method=%m rip=%r lip=%l mpid=%e %c
%k session=<%{session}>
On 03/12/2016 12:20 AM, Luigi Rosa wrote:
Hi,
could it be possible to log the TLS cipher suite as Postfix does?
This i
Hi,
could it be possible to log the TLS cipher suite as Postfix does?
This is a typical TLS Dovecot log line:
imap-login: Login: user=, method=DIGEST-MD5, rip=1.2.3.4,
lip=4.3.2.1, mpid=19671, TLS, session=
This is the Postfix equivalent
postfix/smtp[59723]: Anonymous TLS connection establis
On 3/10/2016 7:56 PM, Timo Sirainen wrote:
>> On 11 Mar 2016, at 02:37, Charles Marcus wrote:
>>
>> On 3/9/2016 9:02 PM, Timo Sirainen wrote:
>>> On 08 Mar 2016, at 01:50, Pavel Stano wrote:
sis attachment deduplication is broken in 2.2.16 upwards.
It is caused by this commit.
ht
On 11 Mar 2016, at 04:15, Gordon Grubert
wrote:
>
> But I found another interesting fact: The openldap client on debian 8
> can handle hard communication interrupts correctly. I've added
>
> NETWORK_TIMEOUT 5
> TIMEOUT 5
>
> to ldap.conf because man 5 ldap.conf says:
>
> NETWORK_TIMEO
On 03/11/2016 03:30 PM, Gordon Grubert wrote:
Of course, such a WORKAROUND could be used and I'm sure that this
works. But Timo says, dovecot is using the LDAP API. The openldap
client can handle network timeouts. Therefore, dovecot has to be able
to use these timeouts, too, like described in l
Rich Wales wrote:
> I am syncing two Dovecot sites using the dsync function.
If you are referring to replication ...
> I would like to be able to run some sort of periodic health check to
> confirm that dsync is (or is not) running properly between the two
> sites, and alert me if dsync is fail
I am syncing two Dovecot sites using the dsync function.
I would like to be able to run some sort of periodic health check to
confirm that dsync is (or is not) running properly between the two
sites, and alert me if dsync is failing or lagging excessively.
Does anyone know of a tool to do this?
On Fri, 11 Mar 2016 11:58:00 -0300
Juan Bernhard wrote:
>
> El 11/03/2016 a las 11:22 a.m., Alessio Cecchi escribió:
> > Hi,
> >
> > I'm evaluating to switch from NetApp to a ZFS appliance (like Qsan). Our
> > setup is Dovecot, Maildir for email storage and NFS to share mailboxes
> > (more than
El 11/03/2016 a las 12:04 p.m., Charles Marcus escribió:
On 3/11/2016 9:58 AM, Juan Bernhard wrote:
Be careful to no do any synchronous writes under ZFS. Every sync write
can take up to 3 seconds of latency (under freebsd, I didnt test ZFS in
linux). Im using it in a 3k user environment and wo
On 3/11/2016 9:58 AM, Juan Bernhard wrote:
> Be careful to no do any synchronous writes under ZFS. Every sync write
> can take up to 3 seconds of latency (under freebsd, I didnt test ZFS in
> linux). Im using it in a 3k user environment and works great with a 4TB
> raid 10, and dovecot cache fi
El 11/03/2016 a las 11:22 a.m., Alessio Cecchi escribió:
Hi,
I'm evaluating to switch from NetApp to a ZFS appliance (like Qsan). Our
setup is Dovecot, Maildir for email storage and NFS to share mailboxes
(more than 30k users) across POP/IMAP and MX servers.
NetApp NFS works fine also under hi
On 11.03.2016 10:10, mj wrote:
Hi,
We're now running with ldap via haproxy, as was suggested in this thread
by Timo. So far, so good: it seems to work very well.
Of course, such a WORKAROUND could be used and I'm sure that this
works. But Timo says, dovecot is using the LDAP API. The openldap
Hi,
I'm evaluating to switch from NetApp to a ZFS appliance (like Qsan). Our
setup is Dovecot, Maildir for email storage and NFS to share mailboxes
(more than 30k users) across POP/IMAP and MX servers.
NetApp NFS works fine also under high load but have some limitation for
inode numbers per
Hello.
I want to use second ldap server for failover. So, i add a second
section for userdb/passdb. My question is: what connection timeout,
after that dovecot will be try to connectd another ldap server? Can i
change it?
Thanks.
Am 11.03.2016 um 01:56 schrieb Timo Sirainen:
On 11 Mar 2016, at 02:37, Charles Marcus wrote:
On 3/9/2016 9:02 PM, Timo Sirainen wrote:
On 08 Mar 2016, at 01:50, Pavel Stano wrote:
sis attachment deduplication is broken in 2.2.16 upwards.
It is caused by this commit.
https://github.com/d
Hi,
We're now running with ldap via haproxy, as was suggested in this thread
by Timo. So far, so good: it seems to work very well.
MJ
On 03/10/2016 04:15 PM, Gordon Grubert wrote:
Hi Timo,
On 01.03.2016 22:51, Timo Sirainen wrote:
On 29 Feb 2016, at 17:18, Gordon Grubert
wrote:
Hi,
we
On 11.03.2016 01:18, Nick Bright wrote:
On 3/10/2016 3:50 PM, Andrew McGlashan wrote:
If they are using POP to download messages from any client, make sure
the client does a leave on server for at least long enough for other
client devices to download the messages.
Cheers
A.
Yes, that's the wh
El vie., 11 mar. 2016 a las 2:08, Timo Sirainen () escribió:
> On 11 Mar 2016, at 03:48, Luis Ugalde wrote:
> >
> > Hi,
> >
> > I'm starting to see, on a pretty standard Debian Jessie installation,
> some
> > error messages that are apparently related to the ETOOMANYREFS errno.
> >
> > Firstly, t
20 matches
Mail list logo
