Email migration

In an effort to improve the speed and reliability of your email service, DreamHost is upgrading customer email accounts to new, faster hardware in its state-of-the-art data center. 

To boost the safety and security of your email, SSL is now enabled by default for connections to DreamHost’s mail servers.

Please note that there are a few changes you should be aware of if you are using vanity mail server URLs. View the section below for further details.

Potential issues

Duplicate emails during the migration process

You’ll continue to have access to your email accounts during migration, but please refrain from making any changes within your accounts until maintenance wraps up. Moving emails between folders, deleting messages, and even modifying “message-read” flags may cause those messages to duplicate at the new location during the cleanup synchronization. Rest assured, you will not lose any emails as a result of this migration.

DNS propagation issues

Incoming messages may be delayed as the new servers’ DNS records propagate across the Internet. Some messages may even temporarily appear to go missing on the new server. Don’t panic if this happens—they will return!

Time frame

As mailbox sizes can vary, your migration can take anywhere from one hour to one week. Keep an eye out for the completion notice that DreamHost sends once your entire account has finished migrating.

Do not add or remove users during the migration

Once you've received the email that DreamHost has begun your migration, please do not add or remove any email users until you've received the completion notice that the migration has completed. This can result in your users being split across two different mail clusters, as well as breaking important settings on your account.

Suggested changes

Though not required, DreamHost highly recommends you make the following suggested changes to your email settings to ensure a smooth email experience after your migration completes.

Updating your email client configuration

If you have been migrated to the mail server, your email client configuration may need to be updated.

New mail servers

In the past, your email servername (hostname) would have looked like 'sub4.mail.dreamhost.com'. Although this address will continue to work, DreamHost recommends you update your mail client settings with these new, simplified server URLs:

IMAP (most common)

  • imap.dreamhost.com — Port 993 (incoming IMAP connections)
  • smtp.dreamhost.com — Port 465 (outgoing SMTP connections)

POP

  • pop.dreamhost.com — Port 995 (incoming POP connections)
  • smtp.dreamhost.com — Port 465 (outgoing SMTP connections)

Webmail server

You can log into your webmail at the following address:

  • webmail.dreamhost.com

What if I'm using external DNS?

If you are using an external DNS provider, its records may need to be updated as well (including MX records).

MX servers

The following are the new MX servers:

  • mx1.dreamhost.com
  • mx2.dreamhost.com

Vanity mail server notice

After your email service is migrated to the new server, any email applications still using vanity mail server URLs (such as 'mail.example.com') will experience login issues until the DNS changes have fully resolved to point to the new IP address. To work around, or avoid this altogether, DreamHost strongly recommends modifying your email application to use the updated configuration settings shown in the section above.

If you choose to continue using 'mail.example.com' in your settings after DNS has finished resolving to the new IP address, your email application may show a 'SSL certificate name mismatch' error. You can find information on working around this in the following article:

Finally, if you are using 'webmail.example.com' to access the webmail interface, DreamHost strongly recommends switching to https://webmail.dreamhost.com, as this allows the secure interface to work without showing any security certificate errors in your web browser. Although http://webmail.example.com will continue to function for the time being, DreamHost may eventually discontinue this feature.

See also

 

Did this article answer your questions?

Article last updated PST.