similar to: Dovecot replication not picking up new mail in maildir

I've got a basic dovecot master-master replication setup between two servers (imap1 and imap2). Actions such as deleting messages or moving them between folders are replicated correctly and quickly. However, when new mail is delivered by postfix, replication does not occur until something else triggers it, such as one of the delete/move actions mentioned earlier. A search suggested this

> On 27/10/2020 14:49 Justin Ridge <jayare-dcml at outlook.com> wrote: > > > On 26/10/2020 19:25, John Fawcett wrote: > > On 25/10/2020 17:19, jayare~dcml at videocoding.org wrote: > >> I've got a basic dovecot master-master replication setup between two > >> servers (imap1 and imap2). Actions such as deleting messages or moving > >> them

Hello. 1. I have two identically hosts 2. I have set up replication between two hosts 3. I have 'Y' AS proxy_maybe in password_query. 4. password_query returns one of this one hosts 5. I set this parameters in dovecot config: disable_plaintext_auth = yes ssl = yes auth_mechanisms = plain login for enforce use encrypted connections by client programs.

v2.1 supports now multiple LDAP fields in a template e.g.: user_attrs = \ homeDirectory=home, \ uidNumber=uid, \ gidNumber=gid, \ =mail=%{ldap:mailboxFormat}:%{ldap:homeDirectory} which is the same as: user_attrs = \ =home=%{ldap:homeDirectory}, \ =uid=%{ldap:uidNumber}, \ =gid=%{ldap:gidNumber}, \ =mail=%{ldap:mailboxFormat}:%{ldap:homeDirectory} I was also thinking about

Hi, first of all, many thanks for a great piece of software. Today I updated one of our 2 IMAP/POP3 proxies from version 2.2.15.17-1 to 2.2.23.1-1 (both are enterprise editions). After the update I now see randomly the following errors in the log file on my first proxy: ... Apr 15 10:28:54 imap1 dovecot: pop3-login: Error: SSL: Stacked error: error:1408F119:SSL

Hello, Following Jan-Frode's advise I am trying this configuration: {postfix} ---lmtp---> {director} ---lmtp---> {dovecot} so I have two dovecot instances for director/proxy and lmtp delivery on ports 1024 and 24 respectively. whilst for imap connections I can specify a pool of imap backend servers via 'director_mail_servers' it seems is not possible with lmtp. Sep 12

Hello, I spend a couple of days configurating a new installation of dovecot 2.0.14 with virtual accounts and NFS storage for maildir home/mail directories. At this point I need shared mailboxes but since user mail/home locations are ldap attributes, how is it supposed I must configure this for shared mailboxes? for the users' mail/home directories I set this line: user_attrs =

What syntax is needed to make this work? The 2.0 wiki recomendations don't work - I can see the inboxes or the folders but not both at once and there are lots of error messages about prefix clashes if I simply use the existing 2.0.20 conf file on 2.1.6 The layout I have is: Inboxes in mbox format - /var/spool/mail/%u Folders in maildir format - /var/spool/imap/%u/Maildir/ Control and

http://dovecot.org/releases/2.2/dovecot-2.2.16.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.16.tar.gz.sig A few fixes and some imapc improvements since the release candidate. * dbox: Resyncing (e.g. doveadm force-resync) no longer deletes dovecot.index.cache file. The cache file was rarely the problem so this just caused unnecessary slowness. * Mailbox name limits changed during

http://dovecot.org/releases/2.2/dovecot-2.2.16.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.16.tar.gz.sig A few fixes and some imapc improvements since the release candidate. * dbox: Resyncing (e.g. doveadm force-resync) no longer deletes dovecot.index.cache file. The cache file was rarely the problem so this just caused unnecessary slowness. * Mailbox name limits changed during

We had this this morning: Oct 25 12:36:34 msslat dovecot: imap(keh2): Error: user keh2: Initialization failed: Namespace '#mbox/': mkdir(/stage/mail/imap1/keh2/mail) failed: Permission denied (euid=2291(keh2) egid=101(luci) missing +w perm: /stage/mail/imap1, euid is not dir owner) Oct 25 12:36:34 msslat dovecot: imap(keh2): Error: Invalid user settings. Refer to server log for more

hi, mutt -f imap://max at test.local@127.0.0.1 Could not connect to 127.0.0.1 (Connection refused). lsof -i dovecot 20200 root 5u IPv4 233361 TCP localhost:imap2 (LISTEN) imap-logi 20204 dovecot 0u IPv4 233361 TCP localhost:imap2 (LISTEN) imap-logi 20205 dovecot 0u IPv4 233361 TCP localhost:imap2 (LISTEN) imap-logi 20206 dovecot 0u IPv4 233361 TCP

Hi, I am a long-time dovecot user/admin for my family mail server, but I had ventured into configuring replication only recently and I am not sure about how it should work and what are the good practices. My intent for replication was to have another instance to switch to in a short time if something fails. I have daily backups, but it will take much more time to rebuild and restore than just to

Hello, I have a question about the way Dovecot limits file system access. Currently we're using Dovecot 1.0.5 (Solaris 10). In some cases users have a symbolic link like "z: -> /" in their mail directory. As a result there are log entries like Jan 25 13:30:31 imap1 dovecot: [ID 107833 mail.error] IMAP(xyz):

Hi, I would like to have two seperate imap listeners, with different authentication settings, but the mailstore and userbase etc will be identical. I know I can do this: > service imap-login { > inet_listener imap { > port = 143 > } > inet_listener imap2 { > port = 144 > } > } But I'm unsure how to configure imap/143 with "driver =

Hello, I run Dovecot?2.3.2.1 and I keep separate index / control files: mail_location = maildir:~/Maildir:INDEX=/liveindexes/indexes/%d/%n:CONTROL=/liveindexes/control/%d/%n When I try to set an ACL on a folder, I get this error: Dec 26 17:35:56 imap2 dovecot: imap(user at domain.com): Error: file_dotlock_open(/home/vpopmail/domains/domain.com/user/Maildir/.Test/dovecot-acl) failed: Resource

Alright, but do you know why the error happens ? On Thursday, 27-12-2018 at 2:51 Aki Tuomi wrote: > On 27 December 2018 at 00:55 Qmail Dev wrote: > > > Hello, > > I run Dovecot?2.3.2.1 and I keep separate index / control files: > > > mail_location = > maildir:~/Maildir:INDEX=/liveindexes/indexes/%d/%n:CONTROL=/liveindexes/control/%d/%n > > When I try

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

I'm getting lots of errors like this (possibly on every message delivery): imap2 dovecot: lmtp(rlaager at wiktel.com): Error: OU02K+gQmFhUAwAAVtfydQ : sieve: binary save: failed to create temporary file: open(/var/lib/dovecot/sieve/junk-mail.svbin.ima p2.852.) failed: Permission denied (euid=500(vmail) egid=500(vmail) missing +w perm: /var/lib/dovecot/ sieve, dir owned by 0:0 mode=0755)

Hi, I think I'm having a problem with simultaneous pop3 connections on the same mailbox with one connection deleting a message. Jan 29 14:36:30 imap1 dovecot: pop3-login: Login: user=<riki at domain.com>, method=PLAIN, rip=82.xx.xx.xx, lip=-----, pip=------, mpid=7703, secured, session=<1A+8DiHxfABSUCCH> Jan 29 14:36:30 imap1 dovecot: pop3-login: Login: user=<riki at