What's new in GAMMO?
As we add features, enhancements, and fixes to Google Apps Migration for Microsoft Outlook®, (GAMMO) we'll release updates both automatically and from our download page. We'll also continue to update this page with the latest release information. Here's a look at what's new in the latest release, and how you can get it.
Getting the latest release
- If you installed GAMMO yourself: Updates are checked for and downloaded to your computer automatically.
- If your administrator installed GAMMO: Updates are downloaded to your computer automatically, if your administrator has enabled automatic updates.
- You can also download the latest version at any time from the GAMMO download page.
January 12, 2016
Fixed an issue where messages from a PST file containing invalid values in MAPI properties were converted to MIME messages with invalid From headers and then rejected by the Gmail API.
OAuth token is now refreshed before it expires, resulting in fewer 401 errors during large migrations.
Improved back-off behavior when the server returns an HTTP status 429 (Too Many Requests) response.
Message bodies are no longer written to the trace log when an email upload fails.
November 10, 2015
Added the quotaUser argument to all API requests to make sure the API quota is counted per user and not per IP.
Fixed an issue where messages were rejected by the Gmail API if the From header did not contain a valid SMTP address.
Failed API requests are now retried correctly using increasing intervals (exponential back-off).
October 25, 2015
Messages greater than 5Mb were failing to migrate.
October 1, 2015
Click-To-Run editions of Outlook 2013 and Outlook 2016 are now supported.
Windows 10 is now supported.
Migrates email using the Gmail API.
Removed deprecated 2-legged OAuth command line options --google_consumer_key and --google_consumer_secret.
Support Service Account authentication to migrate on behalf of a user from command line using --service_account_json_path option. See Run migration from command line for details.
Optionally collect and report crash data.
Email migration is more resilient to throttling and network or server failures with improved retries with exponential backoff.
Empty email folders on the source are migrated as labels to Gmail.
Messages in Outlook’s Deleted Items now are correctly migrated to Trash.
GAMMO now allows graceful cancellation of a running migration.
Other minor UI issues
April 28, 2015
The migration of secondary calendars was not working correctly. This issue has been fixed.
Removed the deprecated clientlogin command line option
Removed the command option
--noenable_calendar_fanout as this is the default behavior since moving to the Calendar v3 API.
April 1, 2015
Issue: Client migrations failed if three consecutive 503 backoff responses were received. The client would enter a “throttled” state which quickly exhausted the remaining retry requests and failed the migration with the “Migration failed due to network error” message.
This issue has been fixed. The client now properly performs exponential backoff when receiving 503 requests. The client retries up to 10 times increasing the sleep period exponentially before retrying a request. If a successful event occurs, the retry and sleep times are reset.
March 24, 2015
Added new command line option --emapi_sleep_time. This setting allows you to increase the number of milliseconds that GAMMO pauses between each email migration API request.
Deleted items were being migrated into the Gmail inbox and not trash. Deleted items now are properly migrated to trash.
Changed the required minimum wait between email migration API requests from 700ms to 1000ms.
December 15, 2014
GAMMO now uses the latest Email Migration API (version 2).
August 5, 2014
This release fixes the integration with Google Apps Sync for Microsoft Outlook. There was an issue that prevented existing Outlook profiles/PSTs from being imported when creating a new Google Apps Sync profile.
July 21, 2014
Google Apps Migration for Microsoft Outlook calendar migrations now uses the latest Google Calendar API (version 3).
Calendar migrations now recognize more time zones.
Google Apps Migration for Microsoft Outlook can now get the sender's email address from the message's internet headers even if it's missing from the sender field in Outlook.
This release fixes the following issues:
- Removed ClientLogin API support, as the API is deprecated. This means that users can now only authenticate using the browser with OAuth.
- Removed the incorrect request to copy the authorization code during the authorization flow. The prompt now only asks the user to switch back to the application after authorizing access.
- Fixed an issue where re-migrating secondary calendars would fail if the user had deleted the calendar in Google Apps.
- Fixed issue where the -noenable_label_prefixes command line option was not respected when using the GUI.
- The command line option -noenable_label_prefixes was renamed to -noenable_label_prefix to be consistent with Google Apps Migration for Microsoft® Exchange (GAMME).
- Fixed a crash that would happen if the password dialog was cancelled when performing a PST migration.
May 22, 2013
Google Apps Migration for Microsoft Outlook now supports Outlook 2013 (32-bit and 64-bit), and runs on Windows 8 in addition to previously-supported operating systems.
September 15, 2011
Google Apps Migration is now available in 26 new languages!
Google Apps Migration is now available in 26 languages (in addition to English). Its documentation is available in many of these languages, too.Which languages are supported?
Google Apps Migration now matches whichever language the user has defined for Microsoft Outlook, if that language is one that we support. If not, it matches the user's Windows default language, if supported. Otherwise it opens in English.
Google Apps Migration documentation is available in these languages, too. To view documentation in your language, visit the following links and choose your language from the pop-up list at the bottom of the page.
April 29, 2011
Google Apps Migration now supports SSO via 3-legged OAuth
Google Apps Migration now supports using 3-legged OAuth for migrating users' mail, contacts, and calendar data to Google Apps. When running the migration utility, users can now sign in to their Google Apps account via a Single Sign On (SSO) system—using their current service's login credentials, rather than their Google Apps credentials.
3-legged OAuth is also more secure since users can explicitly grant access to their account and then revoke it any time.
The new version also supports a new command-line flag to disable calendar fanouts, creating events only for the user whose data is being migrated—without adding the event to calendars of other attendees. This new flag is useful when performing test migrations.