Release Notes: Aspera Add-in for Microsoft Outlook 1.3.5

Product Release: June 21, 2016

Release Notes Updated: June 22, 2016


Welcome to this release of the IBM Aspera Add-in for Microsoft Outlook. The Aspera Add-in 1.3.5 is a maintenance release.


#32098 - Under certain circumstances, the Aspera Add-in prompted users to install Connect although Connect was already installed.

#12974 - In rich-text mode, the email template did not display the package contents correctly.


  • Windows 7, 8, or 10
  • Microsoft Office:
    • Outlook 2007 (32-bit) with 2007 Microsoft Office Suite Service Pack 2 (SP2) and the Security Update for Microsoft Office 2007 System (KB2584063)
    • Outlook 2010 (32- or 64-bit) with, at a minimum, 2010 Microsoft Office Suite Service Pack 1 (SP1)
    • Outlook 2013 (32- or 64-bit)
    • Outlook 2016 (32- or 64-bit)
  • Microsoft .NET Framework version 4.5.1 or higher
  • Microsoft Visual Studio Tools for Office 2010 Runtime version 10.0.50903 or higher
  • Aspera Connect 3.6.0 or higher


Windows: OutlookAddinFullLtdMSI-
md5: 9c5259ab239900f8f07cbeede20e17e2
sha1: cc7fd062b3902069d93217644d8dc176b511bcea


#36005 - If a SAML token has expired on your Faspex server, you must add the accounts from the affected transfer server back into the Aspera Add-in.

#35979 - When you attach a large file by dragging and dropping it from a file browser, an error message appears warning that the file is too large to transfer. As a workaround, use the Attach File button instead.

#35577 - If you add a folder as an attachment, but then delete it from the file system before sending the email message, the Aspera Add-in displays the following message:
Error sending email. Please check your Microsoft Outlook and Aspera Add-in settings and try again.
The error message does not specify the actual source of the problem.

#35235 - If your Faspex server is configured to require external users to register with Faspex, the packages sent to external users before they register cannot be downloaded using the Aspera Add-in. However, external users can still download these packages from the Faspex server using the Faspex UI in a Web browser.

#35206 - In Faspex, if you address a package with the form user@address (external), Faspex treats the recipient as an external user. However, because of how Microsoft Outlook parses email addresses, you cannot use this syntax in the Aspera Add-in.

#35006 - If you delete a Faspex SAML account from the Aspera Add-in, the token for the account is not deleted.

#33724 - [Outlook 2016 only] If you attach a file using the Aspera Attach File button, the resulting notification email erroneously refers to "a OneDrive for Business file."

#33460 - [Outlook 2016 only] When you use Outlook's Attach File button (not the Aspera Add-in's button) to add multiple attachments, if the total size is too large, you must use the Aspera Attach File button. This is the expected behavior. However, when you use the Aspera Attach File button to attach the same files, Outlook displays the following message:
You have already chosen a file or folder named name. Each file or folder chosen must have a unique name.
As a workaround, close the draft email window, and start a new email message. In the new message, use the Aspera Attach File button to attach the files.

#32351 - When the Aspera Add-in uploads attachments, it uses the default account you have specified. But when it views and downloads attachments, it searches your list of accounts and uses the first account it finds that can access your attachments. This account might not be the designated default account for downloads from Faspex. This is a change in behavior from Aspera Add-in 1.3.3.

#31790 - The Aspera Add-in offers Connect 3.5.1, rather than the latest Connect release.

#31517 - When you download a package through the Aspera Add-in, Connect and applications that use Connect (such as Outlook and web browsers) may freeze for a few seconds.

#17284 - The displayed file size in the Attachments list is not correct when the attachment is larger than 2 GB.

#16481 - The format for the Aspera Add-in configuration file has changed in version 1.2.0. If this file has been modified for Aspera Add-in 1.1.0, you must create a backup of the configuration file before upgrading to version 1.2.0. After the upgrade, previous changes to this file will be lost, and you must edit the settings in the new configuration file manually. The configuration file is named AsperaConnectOutlook2007.dll.config (Outlook 2007) or AsperaConnectOutlook.dll.config (Outlook 2010), and is located at C:\Users\user\AppData\Local\Programs\Aspera Add-In for Microsoft Outlook

#15596 - If the total attached file size is less than the Faspex account threshold, but greater than Outlook’s attachment limit, you will receive an error message stating that the attachment size exceeds the limit. A subsequent attempt to add more files (such that the total size is greater than the account threshold) transfers successfully through Faspex; however, some of the files may also be attached to the notification email.

#13210 - [Outlook 2007 only] If you receive a Faspex message through the Aspera Add-in, but do not have the correct permissions to view the attached packages, you can still open the message, but no attachments will be listed in the Downloads area.

#12974 - In rich-text mode, the email template does not display the package contents correctly.


For on-line support resources for Aspera products, including raising new support tickets, please visit the Aspera Support Portal. Note that you may have an existing account if you contacted the Aspera support team in the past. Before creating a new account, first try setting a password for the email that you use to interact with us. You may also call one of our regional support centers.

Powered by Zendesk