Jump to content

Recommended Posts

Posted

Yup.

 

What did you put on the server settings? you didn't leave it as SSL did you?

 

Encryption should be none and the port should be 143.

 

Ben

Posted

Try it with one and triple check what you put in the server settings, in fact before you hit next on the server settings upload a screenshot, I know it works as I did it with the test account.

 

Ben

Posted

You can test that your Office 365 can talk to the easy mail server via Powershell if you are able to connect via that method. The following command would confirm that the connection is working (But only if you know how to login to it.....if you do not know don't worry)

Test-MigrationServerAvailability -IMAP -RemoteServer mail.school.dorset.sch.uk -Port 143

 

Easymail does not like using port 993, so just update the migration endpoint to use port 143 and it should start to behave. If you just add your own account details up that will confirm if it's working, and if so just restart the rest of them

Posted

But I DID tell it to use port 143 as plexer's excellent instructions told me to.

Still, no point arguing. I'll have another go tomorrow

Posted

When it comes to talking to Easymail I fully expect it to complain so not to worry :)

 

I have checked a powershell test for our local primary that is on easymail and it came back without an error.

I've added their server as an endpoint migration target for our tenancy with it set to no encryption and port 143.

 

When adding a mail box to sync the dialog still shows port 993 in the greyed out section. I selected to run the task straight away and it is currently showing all the e-mails appearing in my test account.

 

The CSV file was in the same format of following which is the same as you had.

[email protected],[email protected],password

Posted (edited)

screenshot.docx

 

Two issues here

My instructions do say SSL although @plexer says not above which might explain the problem

BUT I cannot change the setting anyway, it is greyed out - and I cant remove the bit in the top box, which I didnt add, it just appeared, either

 

So what now?

Edited by witch
Posted

You already have an endpoint for this migration, it was created when you ran the steps for the first time.

 

You should see migration endpoints as one of the tabs you can select you need to go to that and delete the existing one and then run the wizard again making sure to de-select ssl and to use 143 as the port.

 

Ben

Posted (edited)

Sorry, cant see a tab anywhere - not sure where that would be as I dont know what a migration endpoint is?

And how do I remove the ones that failed?

 

There doesnt seem to be anywhere that I can change anything. I must be missing something...

Edited by witch
Posted (edited)

In Exchange Admin Centre, Click Migration

Click the 3 dot icon to get the Migration Endpoints screen up.

Click on your endpoint, then the rubbish bin to delete it.

Recreate the endpoint then test with a single account.

 

Hopefully I've attached the image this time :)

migration.png

Edited by Boredguy
Posted
Just checked out the screenshot doc. That message is a red herring as it will claim to use port 993 even if you have set it to port 143 and no encryption when you configured the endpoint. I had the same yesterday but it did process the migration request.
Posted
Just checked out the screenshot doc. That message is a red herring as it will claim to use port 993 even if you have set it to port 143 and no encryption when you configured the endpoint. I had the same yesterday but it did process the migration request.

 

But I cant set it to anything other than SSL and 993 as it is greyed out

Posted

You can create a new endpoint, and when you try and add a new task it will then give you a drop down to pick which endpoint you wish to connect to. In my case yesterday it was our old MDaemon server and the Easymail server for the primary.

 

Sometimes it can take Office 365 a while before you can delete items, but it will eventually go.

I have done a migration test for your easymail server and it has come back as a success.

 

PS N:\> Test-MigrationServerAvailability -IMAP -RemoteServer mail.yourschoolname.dorset.sch.uk -Port 143

 

RunspaceId : 839752c9-f9d6-487e-aa05-077c1cf1a64f

Result : Success

Message :

ConnectionSettings :

SupportsCutover : False

ErrorDetail :

IsValid : True

Identity :

ObjectState : New

Posted
Just checked out the screenshot doc. That message is a red herring as it will claim to use port 993 even if you have set it to port 143 and no encryption when you configured the endpoint. I had the same yesterday but it did process the migration request.

This makes sense

I have deleted the endpoint and started again and I asked the person who helped me and she DEFINITELY remembers putting in port 143

Anyway, it is going now so we will see

Posted

It should take a few minutes at most if there is not much in the account, but most of mine claimed completion after about half an hour but I only selected a maximum of 1 sync.

 

If you log in to the office 365 account they should be there now.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...