similar to: Problem with ldap / quotas

Hello, I am trying to switch from LDA to LMTP on a Postfix/Dovecot setup, but something is going wrong. I have followed the directions at: https://wiki.dovecot.org/HowTo/PostfixDovecotLMTP Here is a session from dovecot.log: Aug 4 12:19:42 vmail2 dovecot: lmtp(3152): Connect from local Aug 4 12:19:42 vmail2 dovecot: auth: ldap(imaptester at noa.gr): unknown user Aug 4 12:19:42 vmail2

Hi, I've upgraded from 2.0.13 to 2.1.1 and when I started the service, I got the following warning: Mar 21 10:07:23 imapserver dovecot: master: Dovecot v2.1.1 starting up (core dumps disabled) Mar 21 10:08:17 imapserverdovecot: auth: Warning: ldap: Ignoring changed user_attrs in /etc/dovecot/dovecot-passdb-ldap.conf, because userdb ldap not used. (If this is intentional, set

Hello, I would like to ask on suggested vsz_limit values. Is there any way of calculating such values? How should we determine them? I don't want to risk wrong values (and possible errors) on a production system, if I upgrade to 2.0.16 where vsz_limit values are enforced (I read release notes)! If there is no standard way of calculation, could someone please check the following info and

In our low-traffic server we have always kept the default value for IMAP mail_max_userip_connections (10). The server has been working fine! (Thank you Timo for this!) However, recently we have been having: Maximum number of connections from user+IP exceeded errors both for IMAP and webmail users. Thus, we have now changed the value to 100. The questions: 1.Might this lead to

Hello, We have one user who is complaining that he has lost mails from 3 imap folders, administered through squirrelmail. The folders suddenly appeared unregistered, and once manually registered they were empty. Has anyone observed something like this? We are running two servers (as VMs) with Dovecot v2.2.18, synced (two-way) using dsync. The configurations follow. Can you please help me

Hello, I have setup v2.2.12 to mirror mailboxes between our main mail server (vmail.example.com) and a failover server (vmail1.example.com). The problem I have is the behavior of mailboxes used on the main server (*vmail*) over POP3. I have setup an IMAP account on the failover server (*vmail1*) on such a mailbox: the mailbox is used on vmail using POP3 and the same is monitored on vmail1

Hello, I am running dovecot-2.0.13-1_128.el5 x86_64 RPM on CentOS 5.7 with the config shown below. All accounts are virtual, hosted on LDAP Server. My problem is that the quota warning mail is not sent as expected. For example, in the logs I get: Dec 12 08:42:40 vmail dovecot: lda(imaptester): Error: quota: net_connect_unix(/var/run/dovecot/quota-warning) failed: Permission denied

Hi, I have a relatively new installation with LDAP and Postfix, running smoothly on CentOS but it logs dovecot messages both in /var/log/messages and in /var/log/dovecot.log. I have configured it to log in /var/log/dovecot.log (with syslog_facility: local1 and a respective line in syslog.conf, see below) but it also logs in /var/log/messages. As a result, I would expect it to only log into

Hello, I am running v2.0.13. In my dovecot.conf I have: userdb { args = /etc/dovecot/dovecot-usrdb-ldap.conf driver = ldap } passdb { args = /etc/dovecot/dovecot-passdb-ldap.conf driver = ldap } Is it legitimate to include multiple ldap userdb's, like: userdb { args = /etc/dovecot/dovecot-usrdb-ldap1.conf driver = ldap } passdb { args =

Am 04.08.2017 um 12:06 schrieb Nikolaos Milas: > Hello, > > I am trying to switch from LDA to LMTP on a Postfix/Dovecot setup, but > something is going wrong. > > I have followed the directions at: > https://wiki.dovecot.org/HowTo/PostfixDovecotLMTP > > Here is a session from dovecot.log: > > Aug 4 12:19:42 vmail2 dovecot: lmtp(3152): Connect from local >

I am running two servers with Dovecot v2.2.12 on CentOS x86_64 (5.10 and 6.5 respectively) and users are virtual over ldap. I have setup our main internal server (vmail.example.com) with dsync replication according to the first part of http://wiki2.dovecot.org/Replication. The second one (vmail1.example.com) will be the failover server which we want to be a real-time mirror (but can be

On 5/5/2017 8:29 ??, Nikolaos Milas wrote: > I am very puzzled with "unknown filesystem". After more googling, I found this bug report with a very recent fix: https://bugzilla.redhat.com/show_bug.cgi?id=1399487 It seems to me that this may be relevant in our case. If so, may it be that this fix has not been rolled out to CentOS repos yet? What is your opinion and your

Op 8/21/2015 om 1:31 PM schreef Nikolaos Milas: > On 20/8/2015 11:09 ??, Nikolaos Milas wrote: > >> As soon as I manage to re-build Dovecot with the latest snapshot, >> I'll test it! > > Hello, > > I've built dovecot with a today snapshot from hg > (dovecot-2-2-9f815e781beb) and I am trying to enable haproxy. > > I configured as follows (lines added

Hello, I would like to compile Dovecot using custom ldap libraries, located at a particular custom system location. How should I alter the config process to specify that the include dir is "/usr/local/openldap/include" and the lib dir is "/usr/local/openldap/lib64" and not the standard ones (/usr/include/ and /usr/lib64/ respectively) on RHEL/CentOS 5 (x86_64). Note that

Hello, using dovecot 2.1 and per user mail quota via ldap is there a way to have a default quota which gets used, if the "quota" field in ldap is not set? I tried with: plugin { quota = maildir:User quota quota_rule = *:storage=3G } userdb { args = /etc/dovecot/dovecot-ldap.conf driver = ldap } and in dovecot-ldap.conf: user_attrs = dcMailQuota=quota_rule=*:storage=%$ but

Hi, I am running CentOS 7 (fully updated) on a VM. This has a mounted nfs share (via fstab) (which mounts a remote storage system) on which we have created the home directories of 2 users Here are the home directories: /mynfsmount | |--/user1 |--/user1 We want to move this whole branch from the mounted NFS share to the local disk. What is the way to do so? Would it be enough to create a

Hello, Where can I find detailed documentation on how "remote" & "local" blocks are used in protocol configuration to provide specific settings for particular IPs/Names? I've been searching around (wiki2, Google) but I found very few things. I also checked in the conf.d directory of the installation and couldn't find anything. One useful thread was here:

On 5/5/2017 1:19 ??, Gianluca Cecchi wrote: > Could you verify, if /dev/sda is your boot disk, with the command > > fdisk -l /dev/sda > ? It's /dev/vda in my case: # fdisk -l /dev/vda Disk /dev/vda: 21.5 GB, 21474836480 bytes, 41943040 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512

> -----Original Message----- > From: dovecot-bounces at dovecot.org [mailto:dovecot-bounces at dovecot.org] > On Behalf Of Burak G?RER > Sent: Thursday, May 30, 2013 10:34 AM > To: Nikolaos Milas > Cc: Dovecot Mailing List > Subject: Re: [Dovecot] Dovecot 2.2 build rpm on Centos6 > > On 27-05-2013 16:56, Nikolaos Milas wrote: > > On 27/5/2013 1:07 ??, Birta

On 20/8/2015 10:35 ??, Tim Groeneveld wrote: > # This is a list of trusted networks... ips are seperated by ", " > # default, empty > haproxy_trusted_networks = 10.1.2.0/24, 10.2.1.0/24 > > # This is the timeout... in seconds. > # default, 3 > # haproxy_timeout = 3 > > # modify your inet listener's to include haproxy=yes > inet_listener { >