Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Migration to Outlook365 with IMAP - GoDaddy

  • 1 پاسخ
  • 2 have this problem
  • 1 view
  • آخرین پاسخ توسّط jeff132

more options

I was recently migrated to Outlook365 from "Workspace" by GoDaddy. Despite their communications that said that I didn't have to do anything, all of my existing IMAP accounts stopped working, both through Thunderbird and iOS.

After some communication with their tech support (which was fairly clueless) I found out that I indeed needed to update all of my email settings. On my iOS devices I was able to set them up for an Exchange server and those worked fine. On Thunderbird, I needed to set them up as IMAP. I got the server information from my Outlook webmail, but despite trying several different things (letting Thunderbird autodetect, manually putting in server info, trying different settings) All I get is an Inbox (no folders) and SMTP doesn't work.

As an experiment, I used an iOS device and setup an IMAP email to the new Outlook365 server, and it works-- I get all my folders, SMTP works, etc. The only difference I can see is that in iOS it doesn't have username and password on the SMTP (shown as optional, but could be pulling it in from the outgoing), and it isn't clear what the security and authentication settings are. "Use SSL" is checked. I also can't really be sure what SMTP iOS is using since I also have the same email setup as an exchange server on the same device.

Has anyone successfully setup a GoDaddy Outlook365 account in Thunderbird with IMAP?

I was recently migrated to Outlook365 from "Workspace" by GoDaddy. Despite their communications that said that I didn't have to do anything, all of my existing IMAP accounts stopped working, both through Thunderbird and iOS. After some communication with their tech support (which was fairly clueless) I found out that I indeed needed to update all of my email settings. On my iOS devices I was able to set them up for an Exchange server and those worked fine. On Thunderbird, I needed to set them up as IMAP. I got the server information from my Outlook webmail, but despite trying several different things (letting Thunderbird autodetect, manually putting in server info, trying different settings) All I get is an Inbox (no folders) and SMTP doesn't work. As an experiment, I used an iOS device and setup an IMAP email to the new Outlook365 server, and it works-- I get all my folders, SMTP works, etc. The only difference I can see is that in iOS it doesn't have username and password on the SMTP (shown as optional, but could be pulling it in from the outgoing), and it isn't clear what the security and authentication settings are. "Use SSL" is checked. I also can't really be sure what SMTP iOS is using since I also have the same email setup as an exchange server on the same device. Has anyone successfully setup a GoDaddy Outlook365 account in Thunderbird with IMAP?

Chosen solution

Hopefully this helps out someone else, I seem to have it resolved:

1. The SMTP on iOS actually wasn't working; since I had the account in there twice on the same device, it was using a different SMTP server.

2. The missing folders was due to them not being "subscribed". I don't recall having to manually subscribe to all folders when setting up IMAP accounts before.

3. The SMTP server not working was because GoDaddy didn't have SMTP enabled. Their tech support had to do this.

Read this answer in context 👍 1

All Replies (1)

more options

Chosen Solution

Hopefully this helps out someone else, I seem to have it resolved:

1. The SMTP on iOS actually wasn't working; since I had the account in there twice on the same device, it was using a different SMTP server.

2. The missing folders was due to them not being "subscribed". I don't recall having to manually subscribe to all folders when setting up IMAP accounts before.

3. The SMTP server not working was because GoDaddy didn't have SMTP enabled. Their tech support had to do this.