similar to: Doveadm client/server possible?

Recently updated to 2.2.25. Noticed a migration script I've been previously running fine started giving me the errors below. Remove server doesn't log any failure. doveconf -n attached. + /bin/doveadm -o mail_fsync=never backup -R -u user at domain.com imapc: dsync(user at domain.com): Panic: file mdbox-save.c: line 337: unreached dsync(user at domain.com): Error: Raw backtrace:

Hi! I test dsync through tcp. In a log error: dsync-remote (): Error: doveadm client: No command given All are synchronized. The error is shown by rand for the user and on that server where it is synchronized # 2.2.rc2 (976bf9e69367): /usr/local/etc/dovecot/dovecot.conf # OS: Linux 2.6.32-5-686 i686 Debian 6.0.6 ext3 auth_mechanisms = plain login digest-md5 auth_username_format = %Ln@%Ld

Hi doveadm search -u user at example.org -S localhost:19000 all produces the following error in the logs: dovecot: doveadm: Error: doveadm client attempted non-PLAIN authentication What am I missing? * tcpdump of tcp communication on port 19000 is attached * dovecot.conf is attached Regards Daniel -------------- next part -------------- A non-text attachment was scrubbed... Name: dump Type:

Very minor bug; not specifying the user mask with 'doveadm replicator replicate -f' causes a segfault: server:~# doveadm replicator replicate -f Segmentation fault server:~# doveadm replicator replicate -f '*' 123 users updated server:~# gdb /usr/bin/doveadm core.2418 GNU gdb (GDB) Red Hat Enterprise Linux 7.6.1-100.el7 This GDB was configured as

Hi, I know that a lot of work has been done regarding doveadm server, but I'm still experiencing easily reproducible segfault crashes of doveadm-server with 2.1.16 when running the following command in a 4 node director/mailbox cluster: /usr/bin/doveadm -c /etc/dovecot-director/dovecot-director.conf -D purge -A The dovecot-error.log shows the following errors (addresses anonymized): Apr

Hi folks, Not sure how much extra information I'll be able to provide on this, but I'm experiencing a consistent, reproducible dsync backup error with a single, specific account I'm trying to migrate from UW-IMAP / Panda (mix mailbox) to a Dovecot 2.2.32 cluster. Didn't spot any core files laying around. Doveadm backup output, dovecot --version and dovecot -n below:

Hi, we have configured userdb and passdb in the director and try to iterate all users and pass the "purge" command via doveadm proxy to port 19000 on the correct director backend host. A single purge -u username at example.org via doveadm-proxy works correctly, but iterating over some users with -A fails. Note: users/domains have been anonymized in output:

Hi, I'm trying to migrate IMAP mails from dovecot 1.1.20apple0.5 (osx) to dovecot 2.2.33.2 (ubuntu). I'm using "doveadm backup" to migrate my data. It works fine for all subfolders, but the root INBOX stay empty on the new server. I suspect a problem related with hierarchy separator ("." on previous server, "/" on new) or with the namespace prefix (set to

Hello, I want to open a socket for connecting doveadm using tcps. I do the following: service doveadm { inet_listener { port = 5001 ssl = yes } } At the same time, I would like to verify client certificates for connections goes to port 5001. I am trying to do the following, but it doesn't work: protocol doveadm { ssl_require_crl =

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

Hi, we have a problem with our director proxy configuration. When we run on proxy server the doveadm command with -A switch, fails with the error: # doveadm -D quota get -A doveadm(user1): Debug: auth input: user=user1 proxy starttls=any-cert doveadm(user1): Error: Proxy is missing destination host doveadm: Error: Failed to iterate through some users If we execute the command with a single

Hi I'm migrating some mailboxes from an old dovecot system where mailboxes are stored maildir uncompressed. I enabled zlib on the new system and migrated an account: doveadm -o mail_fsync=never backup -R -u tonyg imapc: when the account connects to the new system after a while i'm seeing the following error and the mailbox is no longer functioning: Jan 15 13:58:06 S611 dovecot:

Hi All, I am running Dovecot 1:2.2.9-1~bpo70+1 on Debian Wheezy. I have just started getting the error below when I do a do a list of proxied users. The list of users appears OK afterwards. # doveadm director map doveadm(root): Error: User listing returned failure doveadm(root): Error: user listing failed user mail server ip expire time . . . My director config is below. Thanks

Does anyone have an Idea how to fix this? Regards, -- Tom me at tdiehl.org On Mon, 22 Jul 2019, Tom Diehl via dovecot wrote: > Hi, > > I am running dovecot-2.2.36-3.el7.x86_64 on a Centos 7 machine. I keep seeing > the following errors in the dovecot.log: > Jul 22 12:52:04 vmail2 dovecot: doveadm: Error: open(/proc/self/io) failed: > Permission denied > > Dovecot -n

Hi ? I recently extendend my IPsec tunnel between two mail servers to deal with IPv4 addresses in addition to IPv6 ones. (No specific reason for that.) I ran into an issue worth reporting. This is Dovecot v2.2.27 (c0f36b0) at FreeBSD STABLE-11. Previously: dovecot.conf: plugin { mail_replica = tcp:remote.test } service doveadm { inet_listener { address = [::] } } |

Hi Aki, On 4/4/20 8:12 PM, Aki Tuomi wrote: > Can you provide doveconf -n and try turning on mail_debug=yes on both ends and try doveadm -Dv expunge .... mail_debug=yes is on on both ends and dovecot was restarted but anyway nothing is logged when I issue "doveadm -Dv expunge " In the shell where I issue the "expunge" I see the following: # /usr/bin/doveadm -Dv expunge

It's fixed in head. Sorry. ---Aki TuomiDovecot oy -------- Alkuper?inen viesti --------L?hett?j?: Eric <ebroch at whitehorsetc.com> P?iv?m??r?: 31.3.2016 18.05 (GMT+02:00) Saaja: dovecot at dovecot.org Aihe: Re: v2.2.23 released Yes. I concur. On 3/31/2016 7:44 AM, Leon Kyneur wrote: > 2.2.23 seems to have broken doveadm backup, was previously working > fine on 2.2.22 >

Hello, I'm testing Dovecot 2.0. I plan to use Dovecot 2.0 with thousands of domains per server. My user base is under virtual MySQL. When I run `quota doveadm recalc`, Dovecot sets quota to zero: ################################################################################ root at server:# doveadm -v quota get -u username Quota name Type Value Limit % User

Hello. I have problems with duplicate emails when using replication and configured message filters on the client. Looks like when letter comes, it processed by replication and immediately after this processed by filter on client and moved to another folder. When it arrives to slave server into INBOX, it replicated back to master into INBOX and only after that - slave receives MOVE command. The

Hello! I'm trying move to dovecot2 (centos 5.5, dovecot 2.0.8, dovecot compiled/packaged via edited dovecot2.spec from fedora git). Almost all fine, I can login via imap/pop3 and work with mail. I get segfault error with "doveadm quota get -u user" Here backtrace and other info: # gdb `which doveadm` core.5202 GNU gdb (GDB) Red Hat Enterprise Linux (7.0.1-23.el5_5.2) Copyright