FruitWorks MailFlow Monitor - Changelog

IMPORTANT: Rather than relying on the Agent version detection and upgrade processes it is strongly recommended that you use your currently installed version to uninstall the Agent and then uninstall the Application itself from Control Panel > Programs and Features. At that point it would also be a good idea to reboot your Exchange server to ensure it releases the lock on the MailFlowMonitorAgent.dll in the Exchange program folder.

Version 4.4.2 (current release) Released 24/07/2017

  • This is a maintenance release to support Exchange 2013 CU17 and Exchange 2016 CU6.
  • There are no new features in this release.

Version 4.3.1 Released 30/12/2016

MailFlow Monitor has undergone significant development in the last few years but the vast majority of the releases have been for internal use only. In this new release I have taken the difficult decision to cease support for Exchange 2010. Please do not attempt to install this version on an Exchange 2010 server as the Transport Agent will not install successfully and the product will not work.

MailFlow Monitor 4.3.1 supports Microsoft Exchange 2013 and Microsoft Exchange 2016 with .NET Framework 4.6.2

Please note that .NET Framework 4.6.2 is a requirement for the upcoming March 2017 Exchange cumulative updates as announced at the link below so now would be a good time to start planning the installation/upgrade of the .NET Framework on your Exchange server(s) if you have not already done so:

https://blogs.technet.microsoft.com/exchange/2016/09/20/released-september-2016-quarterly-exchange-updates/

With all of the above said, I'm therefore proud to announce this major new version which includes the following new features:

  • Major new feature: MailFlow Monitor now displays a queue summary at the bottom of the main application window, and this will be coloured red if there is one or more message in the Poison queue.
  • A Debug mode has been added (contact me if you need to enable this) - at the moment this is to specifically allow the application to remain loaded if the Agent version detection logic gets stuck in a loop and cannot perform an Agent upgrade.
  • If you select to Clear Application Log at Startup it will now actually rename the existing/previous log to Application.bak (and delete any existing/previous Application.bak) - this allows you to have full visibility of the previous log if you accidentally start the application but wanted a copy of the previous log.
  • Numerous internal optimisations have been made which will both increase performance and reduce the likelihood of an error caused by a logic problem - with Exchange 2010 support removed from the application there are considerably fewer "if... then" statements required in the code.
  • All registry settings are now located at HKLM\Software\FruitWorks\MailFlow Monitor (where previously on some systems they may have been stored in the WOW6432Node, causing further complexity when reading or writing settings values from the registry).
Version 2.3 Released 09/08/2012
  • Resolved an issue whereby the Agent Installation process did not work correctly on some systems

Version 2.2 Released 14/07/2012

  • Major new feature: MailFlow Monitor now recognises emails that are staying within the organisation and displays them in a different colour. This allows you to more easily recognise incoming, outgoing, or inter-organisation emails.
  • Minor code optimisations and bug fixes

Version 2.1 Released 28/06/2012

  • Changed the communication method between the GUI and the Agents to improve performance

Version 2.0 Released 27/05/2012

  • Major new feature: MailFlow Monitor now monitors incoming and outgoing emails
  • Minor code optimisations to improve performance

Version 1.3 Released 01/02/2012

  • The IP address of the sending server is now displayed in the MailFlow Monitor application(and also recorded in the SMTP.log)
  • Resolved a 32/64-bit detection bug in the main application
  • Minor code optimisations to improve performance

Version 1.2-BETA Released 24/01/2012

  • Added support for Microsoft Exchange 2010 with Service Pack 2
  • Removed support for Microsoft Exchange 2010 with Service Pack 1 (please use version 1.1 if you have not upgraded your Exchange 2010 server to Service Pack 2)

Version 1.1-BETA Released 18/01/2012

  • Initial public release

Version 1.0-BETAReleased 02/01/2012

  • Internal release for testing