Failed imapsync authentication.
I am trying to migrate my emails using imapsync tool.
When I installed imapsync I managed to do some migration, but now it does not.
I think it's some of cPanel configuration that is blocking access.
The following message appears in the log:
Does anyone know how to solve this? Thanks
/usr/bin/imapsync --host1 imap.domain.com --user1 myemail@mydomain.com --password1 MASKED --host2 myIP --user2 destemail@sourcedomain.com --password2 MASKED
Temp directory is /tmp
PID file is /tmp/imapsync.pid
Modules version list:
Mail::IMAPClient 3.35
IO::Socket 1.31
IO::Socket::IP ?
IO::Socket::INET 1.31
IO::Socket::SSL 2.007
Net::SSLeay 1.66
Digest::MD5 2.39
Digest::HMAC_MD5 1.01
Digest::HMAC_SHA1 1.03
Term::ReadKey 2.30
Authen::NTLM 1.09
File::Spec 3.3
Time::HiRes 1.9721
URI::Escape 3.31
Data::Uniqid 0.12
Unicode::String 2.09
Info: turned ON syncinternaldates, will set the internal dates (arrival dates) on host2 same as host1.
Info: will try to use LOGIN authentication on host1
Info: will try to use LOGIN authentication on host2
Info: imap connexions timeout is 120 seconds
Host1: IMAP server [imap.domain.com] port [143] user [myemail@mydomain.com]
Host2: IMAP server [myIP] port [143] user [destemail@sourcedomain.com]
Host1: * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE STARTTLS AUTH=PLAIN AUTH=LOGIN] Dovecot ready.
Host1: imap.domain.com says it has CAPABILITY for AUTHENTICATE LOGIN
Host1: success login on [imap.domain.com] with user [myemail@mydomain.com] auth [LOGIN]
Host2: * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE NAMESPACE STARTTLS AUTH=PLAIN AUTH=LOGIN] Dovecot ready.
Host2: myIP says it has CAPABILITY for AUTHENTICATE LOGIN
Failure: error login on [myIP] with user [destemail@sourcedomain.com] auth [LOGIN]: 2 NO [AUTHENTICATIONFAILED] Authentication failed.
Does anyone know how to solve this? Thanks
-
Unfortunately I could not help anywhere. But with a little test could solve the problem. Just change the IP of the target server to 127.0.0.1 I hope new people who have this problem can solve it here. 0 -
Hello :) I am happy to see you were able to resolve the issue. Thank you for updating us with the outcome. 0
Please sign in to leave a comment.
Comments
2 comments