similar to: Login/director not created

But if in the configuration of the director is stated login/director. Than I assume this socket should be in the login dir not? You have also the director activate with executable = imap-login director? -----Original Message----- Subject: Re: Login/director not created On my install the login/ dir is: drwxr-x--- 2 root dovenull 8 Nov 10 18:14:00 login/ srw-rw-rw- 1 root

Hello, Absolutely. Here is the output of doveconf -n: # doveconf -n # 2.2.31 (65cde28): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.19 (e5c7051) # OS: Linux 4.9.36-x86_64-linodexx x86_64 Arch Linux auth_mechanisms = plain login base_dir = /var/run/dovecot/ dict { expire = ldap:/etc/dovecot/dovecot-ldap.conf.ext quota = ldap:/etc/dovecot/dovecot-ldap.conf.ext } doveadm_password = #

Greetings, I'm setting up replication and am getting this error from the server where the replicated mails are being initially created: Aug 27 11:03:53 molecular dovecot: dsync-server(user at domain.org): Error: Couldn't create lock /vmail/domain.org/user/home/.dovecot-sync.lock: No such file or directory Can anyone shed some light on this? Here's the Replicator config of the

Hello, I am mosty done with the upgrade, but there is a problem that keeps me awake at night: file ownership and permissions. It would be most helpful to have the following from Aki's live system: ls -halFR /var/run/dovecot -------------- next part -------------- An HTML attachment was scrubbed... URL:

I too assume this socket should be in the login dir. I am suggesting that maybe the socket is not being created because of permissions. Therefore if you explicitly set { group = dovenull } you may fix the permissions issue. I am not running director in my setup, just pointing out what jumped out at me. On 11/11/2019 1:24 PM, Marc Roos via dovecot wrote: > > But if in the configuration

On my install the login/ dir is: drwxr-x--- 2 root dovenull 8 Nov 10 18:14:00 login/ srw-rw-rw- 1 root dovenull 0 Nov 10 18:14:00 login/dns-client= srw-rw-rw- 1 root dovenull 0 Nov 10 18:14:00 login/imap= srw------- 1 dovenull dovenull 0 Nov 10 18:14:00 login/ipc-proxy= srw-rw-rw- 1 root dovenull 0 Nov 10 18:14:00 login/login= srw-rw-rw- 1 root dovenull 0 Nov

Hi All, I can't get directory proxying of pop3 and imap working.? The director stuff appears to be OK - see below.?? The ldap authentication is working on the backend mail server.? I just get connection refused when I telnet to the proxy on the pop3 and imap ports.? Nothing appears to be running on the pop3 and imap ports despite the lines in the config below.? I am not sure what to do from

We have a Dovecot installation of several nodes that share an NFS mount for the user data. We are trying to configure Dovecot Proxy with Director in order to have Director select the appropriate IMAP server for a given user on behave of Dovecot Proxy. So far all examples I've seen on the dovecot site require the proxy to know the exact mail server to pass the user to by way of an LDAP

Hi, After upgrading to dovecot 2.1.12, I see a lot of these errors: # 2.1.12: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-279.14.1.el6.x86_64 x86_64 CentOS release 6.3 (Final) # Filesystem: ext4 with mdbox storage Dec 10 15:21:04 mail dovecot: imap(user at example.org): Error: Cached message size smaller than expected (5010 < 8192) Dec 10 15:21:04 mail dovecot: imap(user at example.org):

The conf.d files are not included. I have added !include conf.d/*.conf to director.conf and reloaded the dovecot and director services. conf.d/10-logging also has the following lines: log_path = /dovecot.log info_log_path = $log_path debug_log_path = $log_path The /dovecot.log file still shows empty. Nothing is being logged to that file. Thanks & Regards, Naveen On Thu, Dec 26, 2019 at

Hello! I tried to use imap-hibernate. But errors in maillog: Oct 19 05:14:24 server dovecot: imap(email at example.com)<67125><Lu7ndYt4n8aASO/q>: Error: kevent(-1) for notify remove failed: Bad file descriptor Oct 19 05:14:24 server dovecot: imap(email at example.com)<67125><Lu7ndYt4n8aASO/q>: Error: close(-1) for notify remove failed: Bad file descriptor Oct 19

I have migrated from dovecot 1.2 to dovecot 2.0. When I connect via telnet to 110 port of the dovecot server the client hangs: telnet 192.168.4.80 110 Trying 192.168.4.80... /Connected to 192.168.4.80. Escape character is '^]'./ In syslog I got the following error: /Jan 12 12:14:44 buzon dovecot: imap-login: Error: auth: connect(login) in directory / failed: Permission denied

> On 25/08/2020 14:35 Robert Nowotny <rnowotny at rotek.at> wrote: > > > I get ZLIB Errors after dovecot upgrade from 2.3.10.1 to 2.3.11.3 > > > Aug 21 15:27:34 lxc-imap dovecot: imap(acsida)<63870><jZk...>: Error: Mailbox Sent: UID=40826: read(zlib(/home/vmail/virtualmailboxes/acsida/storage/m.2409)) failed:

prw-rw-rw- 1 root wheel 0 Nov 1 13:09 stats-mail prw------- 1 root wheel 0 Nov 1 13:09 stats-user drwxr-x--- 2 root dovenull 4 Nov 1 13:09 token-login If something other than root is trying to write to stats-user, we found the issue. this is on 10.3-STABLE On Wed, Nov 2, 2016 at 12:13 PM, Timo Sirainen <tss at iki.fi> wrote: > On 01 Nov 2016, at 22:31,

I just noticed this error in my logs: director: Error: doveadm not compatible with this server (mixed old and new binaries?) director: Error: director(10.161.192.28:541/right): Wrong protocol in socket (director-doveadm vs director) The first error I removed by changing director_doveadm_port = 541 to director_doveadm_port = 542 Not really sure why that fixed it. The second error I

Hi everyone, short version: Is there no built in failover mechanism for the director service to handle a backend failure? Long version: I have a frontend server running the director service and two backends. Due to maintenance I had to shut down one of the backends which caused connection errors for the users being directed to this backend. I was very surprised as I expected the director to

I'm using dovecot in a multi server setup. Two directors forward pop3, imap and smtp to backend dovecots with their central storage on NFS. Yesterday I stumbled upon these log lines: 2019-11-18 20:17:51 lmtp(17274): Info: Connect from 172.22.1.6 2019-11-18 20:17:51 lmtp(17274): Panic: file smtp-client-connection.c: line 1142 (smtp_client_connection_established): assertion failed:

Hello In my installation the disable_plaintext_auth does not appear to take effect. I can see that the value is correct using doveconf -a but it doesn't change anything. Whenever attempting to log in using IMAP I get this: * BAD [ALERT] Plaintext authentication not allowed without SSL/TLS, but your client did it anyway. If anyone was listening, the password was exposed. ls NO

Yes, After I changed mode and user/group Oct 18 19:17:50 server dovecot: imap(email at example.com)<57613><VVXuZ4N4avOASO/q>: Error: kevent(-1) for notify remove fail ed: Bad file descriptor Oct 18 19:17:50 server dovecot: imap(email at example.com)<57613><VVXuZ4N4avOASO/q>: Error: close(-1) for notify remove failed: Bad file descriptor Oct 18 19:17:50 server dovecot:

hi, we are using the dovecot-rc1 version, and we are testing the director service, as there is little documentation on this service, a pair of questions.. if i'm not wrong, the proxy_maybe it's not implemented, yet? will be soon? this limitation does not allow use the same two directors servers like mail backend servers? the fairlure of one director server it's automatically