WinDeveloper Message Recall Changelog
What's new in WinDeveloper Message Recall 2.0 Build 2.0.001.25
Dec 3, 2012- It is now possible to recall emails directly from the MS Exchange Outlook Web Access/App (OWA) interface. This is a significant advancement. So far MS Exchange users could only recall emails sent in error from their MS Office Outlook client. With OWA Recall this functionality is now available to all users whose primary mailbox interface is OWA.
- Apart from being able to recall emails directly from their browser, users also benefit from having the WinDeveloper Message Recall Engine handling their recall attempts. Users are able to reliably recall emails sent internally or outside the organization, without the recipients ever knowing
- Here are some screenshots that demonstrate what this extension looks like. The screenshots are from an Exchange 2010 installation, however note that the same is also available for Exchange 2007.
- WinDeveloper Message Recall adds a new icon at the sidebar. Here this is shown at the bottom left corner. Clicking on 'Recall Messages', the OWA Recall interface opens.
- The interface starts by listing the emails under the Sent Items folder. Double clicking an email, opens the 'Recall This Message' dialog.
- From here, clicking the Recall button a Recall request is submitted for processing.
- Notice how the 'Recall This Message' dialog also provides a checkbox for requesting notifications on the recall outcome.
New in WinDeveloper Message Recall 1.2 Build 1.2.006.28 (Dec 3, 2012)
- Configuration Overrides
- This is the feature many of you have been asking for, the ability to configure different message recalling setting for different email categories.
- Many of you wanted to allow for a long recall time window whenever an email was addressed to a foreign recipient. However internal emails were not to be held as long. Some wanted internal emails to be delivered immediately, employing WinDeveloper Message Recall only in case of foreign recipients.
- Another common request was to have a list of users who handle a lot of confidential information. These users require much more recalling opportunity than regular users.
- Configuration Overrides allow us to do just that. These identify an email category and provide unique settings for:
- The recall time window
- The handling of failed recalls
- Status Reporting:
- This release is also introducing Status Reporting. This is a reporting system that automatically sends emails to the administrator if some error condition is detected. When running the installation for the first time, you will now be prompted to enter the administrator address for this feature.
New in WinDeveloper Message Recall 1.0 Build 1.0.005.10 (Dec 3, 2012)
- Recalling messages in Exchange is widely considered to be a hopeless task. You quickly realize how sending a recall request is like telling recipients to open the email and spot the error. So we came up with a completely different approach.
- WinDeveloper Message Recall provides you with a time window during which you may recall the message just submitted. The idea is based on the fact that most often a sender realizes that an error was committed as soon as he clicks Send.
- To better understand how this works check:
- Message Recalling Works! Here is how
- So today we have a predictable, reliable solution that dramatically improves the recall success rate. That's not all. The solution works equally well with local and foreign recipients, is completely transparent to Outlook users, provides centralized reporting, archiving of recalled emails, and more. To see how we tackled the weaknesses in native Exchange message recalling from all angles check:
- WinDeveloper vs Native Exchange Message Recalling
- The product has been tested extensively in-house and at various partner installations. This is allowing us to immediately present you with the final release version. So you can safely go ahead download and install the 30 day evaluation version.
- WinDeveloper Message Recall is a 64-bit application supporting MS Exchange versions 2007 and 2010, including Small Business Server SBS installations. Earlier Exchange versions are not supported. The product has to be installed on each Hub Transport server so as to process both internal and outgoing email traffic. As long as you have the correct Exchange version in place you have no additional requirements to worry about.