similar to: 2.0.3 Bug - hanging issue

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

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

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

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):

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

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.

Hello. With dovecot ver. from 20130211 I have a segfault on doveadm when sync. There are messages from server: 2013-02-14T12:42:35.508031+04:00 imap1 kernel: [870542.927083] doveadm-server[9483]: segfault at 4 ip 00000074b228bc24 sp 000003f30b8e61b0 error 4 in doveadm-server[74b226b000+3a000] or 2013-02-14T12:47:39.850942+04:00 imap1 kernel: [870847.279513] doveadm[9513]: segfault at 4 ip

Dovecot version: 2.2.25 (7be1766) I?m looking into an issue we?re having with a new setup. We have one fronted host with two backend hosts, and we?re attempting to use doveadm to allow us to administer sieve on the frontend and have it replicated to the backend hosts. When I attempt to use doveadm sieve put on the frontend host, i get the following on the frontend host: frontend-machine $ cat

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 between folders are replicated correctly and quickly. >> >> However, when new mail is delivered by postfix,

Hi, now, I'm working with the last version of dovecot and pigeonhole sieve, and when apply a sieve filter on a new message, and it try to move this mail to a folder with special character like accent give me the error 'mailbox name not utf-8: ...' >Aug 17 09:22:40 imap1 dovecot: lmtp(19629,miel): Error: kea6K484akytTAAAJBW4rA: sieve: msgid=

Hi, we have upgraded from v2.0.1 to v2.0.3 yesterday, trying to solve the "dovecot-uidlist: Duplicate file entry" errors. Now, at the moment, we don't get these errors, but when I try to expunge mails from my trash folder I get a lot of errors: Sep 23 14:24:51 imap1 dovecot: imap(user): Error: Mailbox Trash: Expunged GUID mismatch for UID 20193: 442b5ef0c3d3bf3cf4cb619944dce8e4

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 =

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

Hello all, why I can run whis command: imap1:~ # doveadm user user001 userdb: user001 ? mail????? : maildir:/var/maildir/vol04/4/46/user001 ? home????? : /var/mailfilter/vol04/4/46/user001 ? quota_rule: *:bytes=100000000 but not this one: imap1:~ # doveadm quota get -u user001 doveadm(user001): Error: user user001: Auth PASS lookup failed doveadm(user001): Fatal: passdb lookup failed what

This happened after upgrading to 2.2.16. Running on Debian wheezy amd64. We never had such a crash on this server before. However, this too was a single incident. All accounts use Maildir. Mar 21 09:32:02 imap1 dovecot: imap(---- at ---.com): Error: Log synchronization error at seq=0,offset=0 for /stor/mail/domains/----/----/Maildir/dovecot.index: Append with UID 6684, but next_uid = 6685

Fun, fun. I suggest checking the corresponding MTA configuration :) Return-Path: <David.Bear@asu.edu> Delivered-To: rohrbach@mail.webmonster.de Received: (qmail 56434 invoked by uid 801); 24 Sep 2004 15:51:37 -0000 Delivered-To: vrohrbach-karsten@rohrbach.de Received: (qmail 56429 invoked from network); 24 Sep 2004 15:51:36 -0000 Received: from post5.inre.asu.edu (129.219.110.120) by

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 all, today I got this crash from dovecot (2.0.14) Sep 29 14:09:32 imap1 dovecot: lmtp(17693): Panic: file lmtp-proxy.c: line 370 (lmtp_proxy_output_timeout): assertion failed: (proxy->data_input->eof) Sep 29 14:09:32 imap1 dovecot: lmtp(17693): Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0(+0x3f9aa)? [0x7f18f10299aa] -> /usr/lib64/dovecot/libdovecot.so.0(+0x3f9f6)