similar to: Correct permissions for base_dir??

Hello list I am testing mdbox with Dovecot from http://hg.dovecot.org/dovecot-2.0-sis/.and my MTA is Exim. It appears to crash, but I am not sure how to capture the actual crash. What I get in Exim logs is: 2010-07-28 19:55:13 1Oe9uT-000KmG-Oz ** /var/spool/virtual/ titan.co.ke/wash/Maildir <wash at titan.co.ke> R=virtual_domains T=dovecot_virtual_delivery: Child process of

Right, Changes made to dovecot-2.0.5/src/lib-master/master-service.c conn.listen_fd = l->fd; conn.fd = net_accept(l->fd, &conn.remote_ip, &conn.remote_port); i_error("conn.fd: %d",conn.fd); i_error("l->fd: %d",l->fd); i_error("&conn.remote_ip:

I am a little confused here. I have been running 2.2.34 which I installed in /opt/dovecot2.2 I installed 2.3.0.1 to /opt/dovecot23 I then used config files from /opt/dovecot2.2/etc/dovecot to /opt/dovecot2.3/etc/dovecot and all I did was sed -i.BAK 's/dovecot2.2/dovecot2.3/g'. Dovecot started and was running file. Next, I manually crafted config files for 2.3.0.1 based on the example

Hi, again. 1. Can somebody explain me about dovecot's shared mailboxes? 2. What does it do while searching shared mailboxes (debug_log cannot explain it)? What files is it looking for? 3. Need i set dovecot-shared file into directory which are shared (if i want to have separate flags for separate users)? 4. Some errors are hard to understand. For example, # pwd

Getting complaints from people about pop/imap issues. some people are getting repaeted e-mail. Other are not able to delete their e-mails from an IMAP lcient. Current configuration /usr/dovecot2/sbin/dovecot -n # 2.2.26.0 (23d1de6): /usr/dovecot2/etc/dovecot/dovecot.conf # OS: FreeBSD 11.0-RELEASE-p2 amd64 base_dir = /var/run/dovecot/ disable_plaintext_auth = no first_valid_uid = 100

Hi there, I've already asked this question on FreeBSD forums without getting any response. So, I thought it's a good idea to ask it again here. I've setup Dovecote2 (2.2.13) + Postfix + SpamAssassin on my FreeBSD 10 VPS and it works flawlessly. Though, I couldn't setup the Dovecot Antispam plugin to train SpamAssassin when I move mails to the Junk folder. I installed the

When we upgrade our kernels from 2.6.32.2 to 3.2.16 something strange has happened. On high traffic dovecot/auth looks like not responding. We found a lot of this lines at the log: dovecot: pop3-login: Error: net_connect_unix(pop3) failed: Resource temporarily unavailable (...) and clients stop authorizing Some other errors follow in the wake of: dovecot: pop3: Error: Raw backtrace:

Hi all, I'm using dovecot 2.2.13 with virtual folders and fts-solr (see attached dovecot-n.conf). At using virtual folder with fts, the dovecot crashes with following panic: Aug 20 10:49:43 imap(...): Panic: file fts-search-serialize.c: line 63 (fts_search_deserialize_add_idx): assertion failed: (*idx < buf->used) Aug 20 10:49:43 imap(test4 at india.com): Error: Raw backtrace:

On Wed, 10 Apr 2019 at 17:50, @lbutlr via dovecot <dovecot at dovecot.org> wrote: > On 10 Apr 2019, at 08:36, @lbutlr via dovecot <dovecot at dovecot.org> wrote: > > net_connect_unix(/var/run/dovecot/stats-writer) failed: Permission den)) > > One other detail: > > /var/run/dovecot/stats-writer: > 0 srw-rw---- 1 root dovecot 0 Apr 10 08:47 stats-writer

I have version 2.0.0 and upgraded to 2.0.2 and after - this is happend: Raw backtrace: /opt/dovecot2/lib/dovecot/libdovecot.so.0 [0xb7e3425e] -> /opt/dovecot2/lib/dovecot/libdovecot.so.0 [0xb7e342b5] -> /opt/dovecot2/lib/dovecot/libdovecot.so.0 [0xb7e338d6] -> /opt/dovecot2/lib/dovecot/libdovecot.so.0 [0xb7e31cb1] -> dovecot/pop3(client_handle_input+0x8e) [0x804be7e] ->

I have dovecot 2.2.33 installed. When trying to install dovecot2-pigeonhole (v 0.4.19) I get the following when it tries to install dovecot 2.2.31_1 I run portsnap fetch update daily, and I ran it again after this error, but same result. ===> Installing for dovecot2-2.2.31_1 ===> Checking if dovecot2 already installed ===> Registering installation for dovecot2-2.2.31_1 as automatic

I am seeing a rather high CPU usage with 2.2 now: last pid: 30725; load averages: 4.58, 27.36, 25.49 up 0+15:36:12 16:02:53 103 processes: 4 running, 98 sleeping, 1 zombie CPU: 34.5% user, 0.0% nice, 65.4% system, 0.2% interrupt, 0.0% idle Mem: 602M Active, 1767M Inact, 254M Wired, 6116K Cache, 112M Buf, 490M Free Swap: 5900M Total, 5900M Free PID USERNAME THR PRI NICE SIZE

FreeBSD 9.3 Dovecot 2.25 (7be1766) I'm trying to install Dovecot2-pigeonhole-0.4.14_2 from ports. Get an error: cc1: error: unrecognized command line option "-Wno-duplicate-decl-specifier" With options MAKE_JOBS_UNSAFE=yes: cc1: error: unrecognized command line option "-Wno-duplicate-decl-specifier" *** [edit-mail.lo] Error code 1 Stop in

Hi! I use dovecot 1 without any problems for years. Thanks for it! Now I try to migrate to dovecot2. I have small problem. # dovecot --version 2.0.7 # dovecot -n # 2.0.7: /usr/local/etc/dovecot/dovecot.conf # OS: FreeBSD 8.1-RELEASE i386 auth_verbose = yes disable_plaintext_auth = no first_valid_gid = 26 first_valid_uid = 26 lda_mailbox_autocreate = yes login_greeting = imap/pop mailserver

Hello, The following errors are constantly popping up for 2 accounts. I can't get it fixed, I did doveadm backup to another account, the same happens in the new account. I did doveadm force-resync, the problem persists. I'm using dovecot 2.2. 2017-08-18T11:46:12.472821881Z Aug 18 11:46:12 lmtp(ramon.lacerda at alliar.com): Warning: mdbox

V2 of dovecot has had the following releases (to recap) 2.0.0 2010-08-16 2.0.1 2010-08-24 2.0.2 2010-09-08 2.0.3 2010-09-17 2.0.4 2010-09-26 2.0.5 2010-10-01 I am on FreeBSD, and the port committers want to wait till dovecot V2 "stabilizes" prior to adding it to the FreeBSD ports base. So, my question is, respectfully, is dovecot V2.0.5 stable enough for prime-time on a busy ISP

Hi, I have a mailbox where indexing fails with the following error: # /opt/dovecot2/bin/doveadm -c /tmp/dovecot.conf -o mail_location=/tmp/skesselring index '*' doveadm(root): Panic: file charset-iconv.c: line 132 (charset_to_utf8): assertion failed: (*src_size - pos <= CHARSET_MAX_PENDING_BUF_SIZE) doveadm(root): Error: Raw backtrace:

First of all, I think dovecot is really fantastic and I have thanks for all the hard work. I think it will be the best fit for my ~5000 users when I have it setup completely. We normally have approx 500 concurrent IMAP connections during the day. I am trying to convert from courier-imap to dovecot, but I have an issue with public namespace folders that are not writable by certain users.

# portmaster mail/dovecot-sieve ===>>> The dependency for mail/dovecot seems to be handled by dovecot2-2.2.22 ===>>> Initial dependency check complete for mail/dovecot-sieve ===>>> Starting build for mail/dovecot-sieve <<<=== ===>>> All dependencies are up to date ===> Cleaning for dovecot-sieve-1.2+0.1.19_2 ===>>> Waiting on

Hi System debian 8.11 and dovecot-2.2.36.4 My webmail is roundcube with imapproxy. I have one problem. My dovecot servers is are in a cluster with keepalived like: dovecot1----VIP-IP--------dovecot2 All works fine I have a problem with imapproxy when a server dovecot1 had a problem (kernel panic sic!) Keepalived works perfecty and moved VIP to dovecot2 - all works fine for normal users but