Kent,

You are being prompted for a password, so it isn't using private key 
authentication. I recommend you get ssh working first, prove you are indeed 
connecting to your secondary server, and only then introduce doveadm.

Is mail.borg.org the name of your "matching server" or is that the name of your 
primary server? If so, it looks to me like you are using ssh to connect back to 
yourself. You should have something like mail.borg.org as primary, 
mail2.borg.org as backup, and if necessary, add mail2.borg.org to your hosts 
file if there is no DNS for it. Or even connect via IP address like this:

ssh [email protected] 

I'll leave the discussion on whether to use root in this fashion even makes 
sense to others. Suffice to say, once you get something working perhaps 
consider removing the private key and use a non-root user. 

Doug

> -----Original Message-----
> From: Kent Borg via dovecot <[email protected]>
> Sent: Thursday, January 23, 2025 2:12 PM
> To: [email protected]
> Subject: Re: newbie dsync problems
> 
> I had a typo (I said I'm a newbie).
> 
> On 1/23/25 10:50 AM, Kent Borg via dovecot wrote:
> > But when I try to make the command more complete and send a username
> > to the remote end, and now I am no longer talking to the remote end:
> >
> >> root@la:/etc/dovecot# doveadm sync  -u kentborg -1 ssh -i
> >> /root/.ssh/id_rsa_rc.borg.org.dsync [email protected]
> >> [email protected]'s password:
> 
> 
> This better version also doesn't work:
> 
> > root@la:/etc/dovecot# doveadm sync  -u kentborg -1 ssh -i
> > /root/.ssh/id_rsa_rc.borg.org.dsync remoteprefix:[email protected]
> > remoteprefix:[email protected]'s password
> 
> 
> Sorry for the error,
> 
> -kb//
> _______________________________________________
> dovecot mailing list -- [email protected]
> To unsubscribe send an email to [email protected]

_______________________________________________
dovecot mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to