similar to: panic when doveadm sieve put between multiple hosts

Hello, I am getting a persistent seg fault while trying to sync our server to a new location. We are on 2.2.33.2, due for an upgrade but we have used dsync successfully in the past. In fact, we used it to populate this same instance. So I hope this is just a configuration issue. My logs are being filled with these errors:: 2019-07-10T08:29:53-04:00 localhost dovecot: [ID 583609 mail.crit]

Hi! I've got dovecot 1.0.rc15. I want dovecot to listen only on localhost for imap, and on any interfaces for imaps. So I put the following into my config: protocol imap { listen = 127.0.0.1:143 ssl_listen = *:10993 .. } dovecot -n correctly reports: listen: 127.0.0.1:143 ssl_listen: *:10993 But I can still do a 'telnet MY_HOST 143' from the outside, and 'netstat -pltn |

Hello, I'm trying to configure the dovecot-antispam plugin. Now I've run into a problem: whenever I try to move/copy a message in/from the spam mailbox, Thunderbird (and also Sylpheed, haven't tried anything else) says: The current command did not succeed. The mail server responded: Failed to read mail beginning. and in the logs I get: dovecot: Aug 07 10:41:23 Error:

Hello, I've ran into problem with Dovecot and dsync replication. Everything works perfectly, including replication of sieve scripts, except fact that if user activates the 'managesieve' ruleset (I'm using currently Roundcubemail) on "mail1" host, it wouldn't be activated on "mail2" host, by creating symlink ".dovecot.sieve ->

Hi all, I need your insight. I've been testing Dovecot on an AIX 5.2 system. Compiled and running fine. We have some users on an AIX 5.1 system, so I'm working on installing it there, so we can do further testing. I'm using Dovecot 1.0 RC15 with OpenSSL 9.0.7e, configured to use port 10143 (imap) and 10993 (imaps). The error I'm seeing in the log is: dovecot: Nov 28

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

Is it possible to have multiple Listen directives in a dovecot configuration file for the same protocol? I am running dovecot-1.2.11 and I want to be able to use the "standard port" as well as a test port: protocol imap { listen = *:143 listen = *:10143 ssl_listen = *:993 ssl_listen = *:10993 for example. Or is this more preferably done by pointing

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 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 =

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

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

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 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 Everyone, I wouldlike to set up a postfix-dovecot with HA using HAproxy but im facing issues. I've followed this documentation : http://wiki2.dovecot.org/HAProxy (pour dovecot) http://blog.haproxy.com/2012/06/30/efficient-smtp-relay-infrastructure-with-postfix-and-load-balancers/ (pour postfix) Package's version : dovecot : 2:2.2.19 (>= 2.2.19 pour proxy protocol)