Aspera Add-in for Microsoft Outlook 1.2.0 Release Notes
Created: September 7, 2012
Created: September 7, 2012
- Miscellaneous bug fixes and GUI updates.
- There is now a visual indicator (by way of the Aspera Transfer Settings menu) of which Faspex account is the default for sending emails and packages. In Outlook 2007, the default Faspex account is marked as "(default)"; whereas, in Outlook 2010, it's identified by a checkmark icon. A user can change the default account (if there is more than one Faspex account configured in the Aspera Add-in) by highlighting and selecting a different account in the list.
- A new field has been added under Aspera Faspex account settings that allows you to input file extensions that will--by default--be sent through Faspex. For example, if you input “zip”, then a message’s attachments will be sent through Faspex if at least one file has file extension “zip”.
- When creating a new email message, you have the option of using Aspera Add-in’s automatic settings or your own, one-time settings.
- Automatic: If your email message does not contain folder attachments, does not contain file extensions identified as being Faspex-specific and the total attachment size is below the configured threshold, then the email and attachments will be sent through Outlook's default transfer protocol. Otherwise, the email and attachments will be sent through the default Faspex account.
- One-time settings: Override the Aspera Add-in's default/automatic rules and send your message via Outlook Send/Receive or via a configured Faspex account.
- (#12974) In rich-text mode, the email template doesn't display the package contents correctly.
- (#13210) Outlook / Office 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, then you can still open the message, but no attachments will be listed in the “downloads” area.
- (#15596) If the total attached file size is less than the Aspera Faspex account threshold, but greater than Outlook’s attachment limit, then 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) will transfer successfully via Faspex; however, some of the files may also be attached to the notification email.
- IMPORTANT: (#16481) The format for Aspera Add-in's configuration file has changed in version 1.2. If this file has been modified for Aspera Add-in 1.1, please create a backup of the configuration file before upgrading to version 1.2. After the upgrade, previous changes to this file will be lost and you will need to manually edit the settings in the new configuration file. The configuration file is named AsperaConnectOutlook2007.dll.config (Outlook 2007) or AsperaConnectOutlook.dll.config (Outlook 2010), and its location is as follows:
- Windows XP
- C:\Documents and Settings\<user>\Local Settings\Application Data\Programs\Aspera Add-In for Microsoft Outlook\
- Windows Vista, Windows 7
- C:\Users\<user>\AppData\Local\Programs\Aspera Add-In for Microsoft Outlook
- Windows XP
- (#16596) If you open a “New Email” window, then make changes to any of your configured Faspex accounts, and lastly click [X] to exit the Options panel, those changes will not be reflected in the open window. For example, if you delete a Faspex account from the Aspera Add-in and click the [X] to exit the Options panel, the email that you have open will still use the deleted account to send the package. If you then send another email, it will use the new, default account. Alternately, if you click OK to exit the Options panel, changes are applied to the open email window.
- (#17284) The displayed size in the “Attachments” list is not correct when the attachment > 2 GB.
- 63ba73d386ef39ba45a8c7d25a1b43da OutlookAddinFullLtdMSI-188.8.131.52374.msi
- bf05822f92b9cf6fcb532af18ee77feb370c4bb3 OutlookAddinFullLtdMSI-184.108.40.206374.msi