similar to: Namespace issues & duplicate maiboxes

> On 17. Jul 2020, at 22.32, Antonio Leding <tech at leding.net> wrote: > > Hello, > > I am seeing duplicate mailboxes when I perform the ?doveadm mailbox list? command?the output is as follows: > > ================= > > INBOX > INBOX.Drafts > INBOX.Trash > INBOX.Sent These are the folders that your configuration has autocreated for the user. >

Not sure if this matters but the prompt when attempting the ?doveadm backup? command shows it to be a ?production" server? [root at production1 <https://dovecot.org/mailman/listinfo/dovecot> test.org.com]# doveadm backup -R -u kishore at test.org.com <https://dovecot.org/mailman/listinfo/dovecot> remote:vmail at production2.baplc.com

Fair enough but the command snippet I posted was taken directly from your earlier post dated Mon Jul 27 23:11:06 EEST 2020 and it does say ?production1??I just double-checked as well... FWIW?the server order in the command you just pasted is the exact reverse from the Jul 27th post I mentioned above? Here you appear to be exec?ing the command on prod2 and trying to pull from the remote of prod

Well that option set still doesn?t look correct? Here is the doveadm option set from my 2.2.2 server which is several weeks\months before 2.2.36? [Jul-27 @ 15:25:09 ] > dovecot --version 2.2.2 [Jul-27 @ 15:26:53 ] > ls -l /usr/local/bin/doveadm -rwxr-xr-x 1 root root 1379203 May 22 2013 /usr/local/bin/doveadm [Jul-27 @ 15:25:12 ] > doveadm usage: doveadm [-Dv] [-f

I seem to recall a post a while back where, due to the age of the remote end, the remote side command had to be entered in the command executed on the local side. Do you have dsync on the 2.0.9 machine? > On Jul 27, 2020, at 4:16 PM, Kishore Potnuru <kishore.reachme at gmail.com> wrote: > > This is what my understanding. May be I am also wrong here. > > Backup option

Hi! Kishore, you got the command wrong.. `doveadm backup -R -u username-goes-here imapc:` for this to work, you need to configure following things: imapc_host = old-host-name imapc_password = master-password imapc_master_user = master-user-name and on the old host you need passdb { args = /etc/dovecot/passwd.masterusers driver = passwd-file master = yes pass = yes } This should

On 8 Aug 2019, at 13:03, Amir Caspi <cepheid at 3phase.com> wrote: > IMHO the setting should apply regardless of protocol, but is that actually the case in practice? It seems to be broken. I have namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { autoexpunge = 14 days auto = subscribe special_use = \Junk } ? } and I have messages in my

dovecot 2.2.33.2 (d6601f4ec) on Ubuntu 18.04 The recent announcement that expunge is going to be deprecated and that autoexpunge should be used instead reminded me that my recent switch over to autoexpunge is not working. There has been an active discussion today about getting expunge working so I thought I'd use the commands suggested there to figure out why autoexpunge might not be doing

I'm trying to diagnose a really strange situation where certain emails, when submitted to the mailbox by Postfix, are not considered to be unseen by Dovecot. During testing, I've shut down anything else on the server that might want to access the mailbox. I submit the email to the local postfix instance which then says it has delivered it to the mailbox: Dec 23 09:51:35 ip-10-35-194-108

Cit?t Sami Ketola <sami.ketola at dovecot.fi>: >> On 14 Aug 2017, at 11.10, zyrixx <zyrixx at gmx.net> wrote: >> >> mail_plugins = $mail_plugins mailbox_alias >> >> plugin { >> mailbox_alias_old = Trash >> mailbox_alias_new = Deleted >> mailbox_alias_old2 = Sent >> mailbox_alias_new2 = Sendet >> mailbox_alias_old3 =

I have noticed that the name of my private server running dovecot appears in email headers rather than the public-friendly name of my server. Is there a method to specify an alternate server name for the dovecot server to use for itself in the dovecot configuration files? I performed a few Google searches and was not able to find the answer to my question. ------- user at server1:~$ dovecot

Well, I tried setting the following in /etc/environment and restarting the server: DOVECOT_HOSTDOMAIN="mail.domain.test" After doing so, I verified that the command "dovecot --hostdomain" returned "mail.domain.test" and not "appserver4.domain.com"; however, the email received header still shows: Received: from mail.domain.test by appserver4.domain.com

Hello, Thanks for the advice, I have made that change now but the server is still doing the same fail with no logs thing it was before. # 2.2.27 (c0f36b0): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.16 (fed8554) # OS: Linux 4.9.0-8-amd64 x86_64 Debian 9.6 auth_debug = yes auth_mechanisms = plain login auth_verbose = yes disable_plaintext_auth = no login_greeting = Welcome to easyMail.

Am 04.09.2018 um 17:18 schrieb Sami Ketola: > > >> On 4 Sep 2018, at 18.00, Robert Schetterer <rs at sys4.de> wrote: >> >> Am 04.09.2018 um 16:52 schrieb Sami Ketola: >>> >>> >>>> On 4 Sep 2018, at 17.47, Robert Schetterer <rs at sys4.de> wrote: >>>> >>>> Am 04.09.2018 um 09:41 schrieb Sami Ketola:

Hello there, Everything was working fine on Dovecot 2.2.10 (on CentOS 7), but after updating to version 2.2.36, our director servers are not able to proxy LMTP. We are sending mail from exim to the local Dovecot LMTP socket, which then used to send it to our internal mail servers on port 24. Besides the update, nothing has changed in the config files. The configuration has been working great

Hi, mail_max_userip_connections is only enforced at the backend level. The setting has no effect on proxy. If you want to force the limit then you can only do it in the backend. Sami > On 9 Mar 2017, at 12.05, Adi Pircalabu <adi at ddns.com.au> wrote: > > Quick follow-up: updated the proxies to 2.2.28, but I still couldn't find a way to limit the inbound IMAP connections per

Hello, I also have issues using Dovecot Backup. I am trying to Backup (or possibly Sync - one way) a single user IMAP account from a remote server, unknown type, to my own server. For that purpose, I defined the following parameters : imapc_host = <host name> imapc_user = <user name> imapc_password = <password> imapc_features = rfc822.size (<user name> has format:

Hello, I'm hosting a few customers on a dovecot Server. Most users speak german and have german as their main language. I configured the IMAP Foldernames in a Dovecot configuration file like this: ##### root at srv04:~# cat /etc/dovecot/conf.d/105-mailboxes.conf imap_capability = +XLIST namespace inbox { inbox = yes location = separator = / mailbox "Entw?rfe" { auto

Hello, I inadvertently made an error re: the namespace prefix when setting up a few accounts and several messages have been saved in the Sent\Deleted folders under the incorrect namespace. Can I simply copy these messages to the relevant folder in the proper namespace? Or do I need to export\import these? Some other procedure? Thanks in advance for any feedback?

Someone who have mailbox in different directory than indexes, can confirm if doveadm can recreate index (after deleting dovecot.index* files) or these files can be created only by connecting with IMAP client? ?r., 4 gru 2019 o 15:45 Sami Ketola <sami.ketola at dovecot.fi> napisa?(a): > > > > On 4 Dec 2019, at 11.48, Tomek Lutelmowski via dovecot < > dovecot at