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 =
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
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
> wrote:
>
> This is what my
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.
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
Oh, I am extremely sorry. I was confused when typing the issue. Please help
me in fixing the issue. Production1 is my old server. Production2 is my new
server. Typing here correctly. Ignore all previous one's.
The new version is:
[root@production2 ~]# dovecot --version
2.2.36
Also, FWIW...your doveadm command is missing quite a few options…here is mine…
[Jul-27 @ 15:11:57] > dovecot —version
2.3.10.1 (a3d0e1171)
[Jul-27 @ 15:22:39] > ls -l /usr/bin/doveadm
-rwxr-xr-x. 1 root root 2949584 May 19 02:09 /usr/bin/doveadm
[Jul-27 @ 15:21:31] > doveadm
usage: doveadm
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
I am executing the command from the new server. I was executing the command
from production2 server only. It has the backup option, but whereas
production1 doesn't have it. Though I am executing from production2, I am
seeing the below error. Is it becasue production1 server doesn't have that
> On 28. Jul 2020, at 0.10, Kishore Potnuru wrote:
>
> Yes. Please find the details of the servers below. I am executing the command
> from one of the new servers.
I find it very hard to believe this. Shall I look at the version control when
backup was added as option to doveadm?
2.2.36
Yes. Please find the details of the servers below. I am executing the
command from one of the new servers.
My Current Production Server details:
Linux OS- Red Hat Enterprise Linux Server release 6.5 (Santiago)
Dovecot version - 2.0.9
Postfix version - 2.6.6
> On 27. Jul 2020, at 23.11, Kishore Potnuru wrote:
>
> Hi ,
>
> I have tried the below command from the new server. But I am getting an
> error. Anything is missing here?
>
Are you sure that is dovecot 2.2.36?
Sami
Hi ,
I have tried the below command from the new server. But I am getting an
error. Anything is missing here?
[root@production1 test.org.com]# doveadm backup -R -u kish...@test.org.com
remote:vm...@production2.baplc.com
vm...@production1.baplc.com's password:
usage: doveadm [-Dv] [-f ]
Hi,
the idea was to run it on the new server and not on the old server.
That is also why you should use -R parameter to pull the mails from remote, not
push.
Sami
> On 27. Jul 2020, at 17.13, Kishore Potnuru wrote:
>
>
> I tried this command also. It didn't work. It shows syntax again.
> On Jul 27, 2020, at 10:13 AM, Kishore Potnuru
> wrote:
>
>
> I tried this command also. It didn't work. It shows syntax again. Please see
> the supported commands in dovecot 2.0.9 version. This doesn't support
> replication also as per syntax, if i am not wrong. Please suggest me.
>
>
I tried this command also. It didn't work. It shows syntax again. Please
see the supported commands in dovecot 2.0.9 version. This doesn't support
replication also as per syntax, if i am not wrong. Please suggest me.
[root@production ~]# doveadm backup -u kish...@test.org.com
No, but there is backup option on the new server. That's why the -R, which
means "backup to here".
Aki
> On 27/07/2020 16:20 Kishore Potnuru wrote:
>
>
> Hi,
>
> But there is no "doveadm backup" option in dovecot 2.0.9 version.
>
> [root@production ~]# doveadm -backup
> doveadm: invalid
* Ralf Hildebrandt :
> Today I was looking for some spam and issued this command:
> ==
>
> doveadm import -u restore@backup.invalid mdbox:/home/copymail2/mdbox INBOX
> header Reply-To bixrs.com
Little typo on my part in the syntax:
> On Jul 27, 2020, at 9:20 AM, Kishore Potnuru
> wrote:
>
> Hi,
>
> But there is no "doveadm backup" option in dovecot 2.0.9 version.
>
> [root@production ~]# doveadm -backup
> doveadm: invalid option -- 'b'
> [root@production ~]# dovecot --version
> 2.0.9
The command is "doveadm backup”.
> On Jul 27, 2020, at 4:59 AM, Kishore Potnuru
> wrote:
>
> Hi
>
> I am in the process/planning of moving from my existing dovecot imap/pop3
> server to 2 new servers (for HA/Resilience). I will be implementing dovecot
> replication on new servers. Please find my current and new servers
Hi,
But there is no "doveadm backup" option in dovecot 2.0.9 version.
[root@production ~]# doveadm -backup
doveadm: invalid option -- 'b'
[root@production ~]# dovecot --version
2.0.9
Copy the contents by using "scp", will that work?
Thanks,
Kishore Potnuru
On Mon, Jul 27, 2020 at 10:00 AM Aki
hi, i have a problem with a dovecot 2.2.36 (1f10bfa63) server, using maildir,
some mails change the file format, the flag is modified and they appear
again in the inbox as unread.
ex.
1548753605.56008.server-mail,S=5935:2 (origin)
1548~RZ!.ESS:2 (modified)
Could someone give me some light? thx.
* Ralf Hildebrandt :
> Today I was looking for some spam and issued this command:
> ==
>
> doveadm import -u restore@backup.invalid mdbox:/home/copymail2/mdbox INBOX
> header Reply-To bixrs.com
This is dovecot from the package
Today I was looking for some spam and issued this command:
==
doveadm import -u restore@backup.invalid mdbox:/home/copymail2/mdbox INBOX
header Reply-To bixrs.com
Then I immediately got a crash:
doveadm(restore@backup.invalid): Panic:
> On 27/07/2020 11:59 Kishore Potnuru wrote:
>
>
> Hi
>
> I am in the process/planning of moving from my existing dovecot imap/pop3
> server to 2 new servers (for HA/Resilience). I will be implementing dovecot
> replication on new servers. Please find my current and new servers versions.
>
Hi
I am in the process/planning of moving from my existing dovecot imap/pop3
server to 2 new servers (for HA/Resilience). I will be implementing dovecot
replication on new servers. Please find my current and new servers
versions.
My Current Production Server details:
Hi there,
I am trying to make a paranoid IMAPS/Submission server. I'm running
Ubuntu 20.04 with Dovecot 2.3.7.2 (3c910f64b).
I mostly use my mail-server from the LAN/Realm where I have GSSAPI
working well for both IMAPS and Submission and most other services
But... I would like to be able to
27 matches
Mail list logo
