IMAP migration error from Hosted Email to office 365

%3CLINGO-SUB%20id%3D%22lingo-sub-134917%22%20slang%3D%22en-US%22%3EIMAP%20migration%20error%20from%20Hosted%20Email%20to%20office%20365%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-134917%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%0A%3CP%3EGot%20error%20while%20doing%20IMAP%20migration%20%3A%3C%2FP%3E%0A%3CP%3EError%3A%26nbsp%3BMigrationTransientException%3A%20We%20were%20unable%20to%20reach%20your%20email%20provider.%20Please%20check%20your%20server%20settings%2C%20or%20try%20again%20later.%20--%26gt%3B%20We%20were%20unable%20to%20reach%20your%20email%20provider.%20Please%20check%20your%20server%20settings%2C%20or%20try%20again%20later.%20--%26gt%3B%20Connection%20timed%20out.%20--%26gt%3B%20A%20connection%20attempt%20failed%20because%20the%20connected%20party%20did%20not%20properly%20respond%20after%20a%20period%20of%20time%2C%20or%20established%20connection%20failed%20because%20connected%20host%20has%20failed%20to%20respond%20%5B%3A%3Affff%3A%3CU%3E%3CEM%3Exxx.xxx.xxx.xxx%3C%2FEM%3E%3C%2FU%3E%5D%3A143%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EError%3A%26nbsp%3BMigrationTransientException%3A%20Imap%20server%20reported%20an%20error%20during%20AuthenticateCommand%20indicating%20that%20a%20subsystem%20is%20currently%20unavailable%3A%20%E2%80%8E'Temporary%20authentication%20failure.%20%5B%20%3CU%3E%3CEM%3EDestination%20Server%20URL%3C%2FEM%3E%3C%2FU%3E%20%3A2017-12-07%2003%3A05%3A17%5D%E2%80%8E'.%20--%26gt%3B%20Imap%20server%20reported%20an%20error%20during%20AuthenticateCommand%20indicating%20that%20a%20subsystem%20is%20currently%20unavailable%3A%20%E2%80%8E'Temporary%20authentication%20failure.%20%5B%3CU%3E%3CEM%3EDestination%20Server%20UR%3C%2FEM%3E%3C%2FU%3EL%3A2017-12-07%2003%3A05%3A17%5D%E2%80%8E'.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EAny%20suggestions%20%3F%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThanks%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-134917%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EMigration%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOffice%20365%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-176210%22%20slang%3D%22en-US%22%3ERe%3A%20IMAP%20migration%20error%20from%20Hosted%20Email%20to%20office%20365%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-176210%22%20slang%3D%22en-US%22%3E%3CP%3EDoes%20your%20current%20email%20provider%20allows%20IMAP%20connection%20to%20their%20servers%20from%20Microsoft%20%3F%3C%2FP%3E%0A%3CP%3EDo%20they%20have%20like%20a%20firewall%20which%20could%20not%20allow%20Microsoft%20servers%20to%20authenticate%20with%20them%20%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-176173%22%20slang%3D%22en-US%22%3ERe%3A%20IMAP%20migration%20error%20from%20Hosted%20Email%20to%20office%20365%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-176173%22%20slang%3D%22en-US%22%3E%3CP%3Esame%20issue%20-%20no%20solution%20%3A(%3C%2Fimg%3E%3C%2FP%3E%0A%3CBLOCKQUOTE%3E%3CHR%20%2F%3E%3C%2FBLOCKQUOTE%3E%3C%2FLINGO-BODY%3E
Highlighted
Contributor

Hi,

Got error while doing IMAP migration :

Error: MigrationTransientException: We were unable to reach your email provider. Please check your server settings, or try again later. --> We were unable to reach your email provider. Please check your server settings, or try again later. --> Connection timed out. --> A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond [::ffff:xxx.xxx.xxx.xxx]:143 

 

Error: MigrationTransientException: Imap server reported an error during AuthenticateCommand indicating that a subsystem is currently unavailable: ‎'Temporary authentication failure. [ Destination Server URL :2017-12-07 03:05:17]‎'. --> Imap server reported an error during AuthenticateCommand indicating that a subsystem is currently unavailable: ‎'Temporary authentication failure. [Destination Server URL:2017-12-07 03:05:17]‎'. 

 

Any suggestions ?

 

Thanks

1 Reply
Highlighted

same issue - no solution :(