similar to: How to connect to a remote server and execute eg a search

Is there a page that explains how to connect to a remote server? What is the syntax of socket_path? doveadm search -S XXXXXXX -u testuser mailbox INBOX ALL

Hi Martin, I feel a bit like an idiot, but I have been trying with copy, so I do not lose any message when testing. But I can't get them to copy. I do indeed have same uid and gid. [@~]# doveadm mailbox status -S 192.168.10.43:542 -u testuser -t messages test messages=43 [@~]# doveadm mailbox status -u testuser -t messages INBOX/test2 messages=16 [@~]# doveadm -v copy -S

This pulls over the whole test mailbox, but I need it to be stored in a different mailbox, of course that is now possible to move from the local test to the local INBOX/test2. But then I might aswell scp the mbox in the first place. Should we conclude that it is not possible with a single doveadm command to move messages from RemoteServerA/usertest/mailboxA/messagesof2017 to

> On 17 Jan 2019, at 14.19, Marc Roos <M.Roos at f1-outsourcing.eu> wrote: > > > Same ip, connection, session happens after a few seconds, all on local > test network. Sorry I mistakenly overlooked at the ip:s. But anyway that is multiple connections and seems that PAM has some concurrency limit and refuses the third connection Thunderbird opens. so you probably have

On 23 Sep 2020, at 14:07, Marc Roos <M.Roos at f1-outsourcing.eu> wrote: > It is just a sieve rule. > > 1. > On disk default file .dovecot.sieve > > 2. I am using roundcube webmail for that. > > 3. with if false # true > # rule:[Out of Office] > if true > { > vacation :days 1 :subject "Test" "test test"; > } Is there a way

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

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

Hi , I have tried the below command from the new server. But I am getting an error. Anything is missing here? ======== [root at production1 test.org.com]# doveadm backup -R -u kishore at test.org.com remote:vmail at production2.baplc.com vmail at production1.baplc.com's password: usage: doveadm [-Dv] [-f <formatter>] <command> [<args>] altmove [-u <user>|-A]

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

you should ask your ip provider to set a proper reverse lookup for you. If I would get a lot of spam from upcloud.host ips, I would also consider blocking upcloud.host reverse dns lookups. If it is your ip, it is an easy request to have it changed. -----Original Message----- From: Sami Ketola [mailto:sami at ketola.io] Sent: Monday, October 26, 2020 11:22 AM To: lists Cc: Arjen de Korte;

No, it is still old sendmail to /var/spool/mail/ -----Original Message----- From: Sami Ketola [mailto:sami.ketola at dovecot.fi] Sent: vrijdag 27 september 2019 15:17 To: dovecot Cc: Marc Roos Subject: Re: Mail received but not indexed? > On 27 Sep 2019, at 16.06, Marc Roos via dovecot <dovecot at dovecot.org> wrote: > CentOS Linux release 7.6.1810 (Core) >

Can anyone share the proper config to get wrappers working in dovecot on FreeBSD? The dovecot examples do not seem to work, and I thought perhaps FBSD needs slightly different configs. I've compiled with: -DHAVE_LIBWRAP which I presume is the first step. The example for dovecot.conf in uncommenting: login_access_sockets = tcpwrap merely causes a log error of "imap-login: Error:

It works ! It was THAT easy ! Can you suggest how to replace the hair I pulled out ? :-) On 2016-12-29 5:27 PM, Larry Rosenman wrote: > login_access_sockets = tcpwrap > > service tcpwrap { > unix_listener login/tcpwrap { > group = $default_login_user > mode = 0600 > user = $default_login_user > } > } > > > > On Thu, Dec 29, 2016 at

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

My query? Is dovecot not getting this field automatically? -----Original Message----- Subject: Re: Dovecot proxy with ldap, complains about 'host not given' On 23 Nov 2019, at 16:11, Marc Roos <M.Roos at f1-outsourcing.eu> wrote: > It looks like the dovecot proxy can authenticate correctly but fails > then on with this message > > Nov 23 23:33:33 test2 dovecot:

I added this: passdb { driver = passwd skip = authenticated } Which enables indeed local delivery, I also noticed this. Maybe the password field check shoud not be done, when you enable skip authentication? Dec 16 10:26:37 svr1 dovecot: auth-worker(12046): Debug: passwd(test): lookup Dec 16 10:26:37 svr1 dovecot: auth-worker(12046): passwd(test): invalid password field '*'

I receive a local mail when I do a 'mail test' on a backend svr1 with this[0] configuration. However when I just add only one configuration change 'lmtp_proxy = yes' I am getting these errors[1]. I would expect this email to still be delivered locally, should this be working or do I misunderstand the lmtp proxy functionality? [0] passdb { args = auth_verbose = default

This is what my understanding. May be I am also wrong here. Backup option is there in my new server, production2. When I use the command with -R option from new server, it is connecting to old server, Production1 and giving the output of the doveadm backup command in old server to get the data. If you see the command and error I posted, it shows the same. Sorry just incase if I am wrong.

Hey Kishore? I believe this is the thread I mentioned earlier. It is quite long and spans a monthly barrier (Feb\Mar 2012) so if you use the ?Next\Previous message? links, you need to be sure to pick up the thread in each monthly archive. I have provided links to the first post of the thread in each archive here: https://dovecot.org/list/dovecot/2012-February/133718.html