We are pleased to announce an update is available for BarricadeMX Plus which adds two new features:

•   The quarantine report email has been enhanced to allow users to apply white list, black blacklist and release quarantined messages directly from the email. It is no longer necessary to login to the web interface to white list, blacklist or release messages.

•   BarricadeMX Plus can now be configured to route email to destination mail hubs on port 587 instead of port 25. This feature is available on a domain by domain basis.

This upgrade also provides fixes for all known bugs for BarricadeMX and BarricadeMX Plus.

BarricadeMX and BarricadeMX Plus Change Log, April 14, 2011

BarricadeMX Plus 

•   Allow mail to be routed to destination on port 587 instead of port 25 on a per-domain basis.

•   Updated quarantine report to allow users to apply actions directly from the mail without logging-in.

 •   Remove background display on message/text parts in the message viewer.

•   SMTP authentication was displayed as 'unknown' on domains page.

•   Year was miscalculated on certain dates in click.php

•   Improve database connection handling at start-up on machines where PostgreSQL starts but rejects all connections as it starts.

•   Correct display of multi-byte characters sets in message viewer.

•   Fix BMX Log Viewer not working correctly in IE.

•   Missing pager variable in Message Listing Report caused pager not to appear.

•   Fix domain exception counter was showing incorrect value.

•   Fix ruleset stored procedure for singular from/to: rules.

•   mailwatchd: on bind to local address 0.0.0.0 as IPv6 is not supported in HTTP::Daemon currently.

•   Fix domain admins/aliases form on IE.

•   Fix kvmaps error on domains, blackwhite/whitelist and access-map when an entry is deleted and another identical entry is added later.

•   Engine: Fix Return-Path header for SpamAssassin to prevent rule mis-fire (RP_8BIT).

•   Engine: Improve database connection handling at start-up on machines where PostgreSQL starts but rejects all connections as it starts.

•   Engine: Fix ClamAV error (cosmetic) when running MailScanner --lint.

•   DBsocketmap: Prevent main thread from accepting connections until child threads have loaded their data to prevent segfault

BarricadeMX

 •   smtpf: Fix MIME API handling of Base64 decoding when EOF is passed.

For customers who are using BarricadeMX, 

 Package Name                                            Version Number  

BarricadeMX                                                  2.2-5 (Not Updated)

smtpf                                                              2.3.33

You do NOT need to upgrade if you are currently using the versions listed above.

For customers who are using BarricadeMX Plus, the current versions are now:

 Package Name                                            Version Number  

bmxplus                                                          2.1-4

bmxplus-common                                           2.1-4

bmxplusd                                                        2.1-4

bmxplus-db                                                     2.1-4

smtpf                                                              2.3-33

fsl-bmxplus-mailscanner                                4.77.10-5

fsl-dbsocketmap                                            1.22-1

To upgrade to the latest version of BarricadeMX Plus or the latest versions BarricadeMX:

The directions for upgrading BarricadeMX or BarricadeMX Plus are identical. Email delivery should be interrupted only for a very brief period of time during the update process and no messages should be lost, only delayed by the update. Still it's a good idea to install the updates at a relatively slow time for email processing. Many sites prefer to install updates after normal business hours. 

To update or to see if you need an update for your BarricadeMX or BarricadeMX Plus system(s) simply login as root and run:

          yum update

and respond by pressing y when prompted.

If you have more than one gateway (a cluster) please update the master gateway first and when the master gateway is finished updating, update the slave gateways one at a time, until all  gateways have been updated. 

If a "kernel" rpm is installed by the yum update process, please reboot your system(s) as soon as practical so the system will use the new kernel.

Please contact support@fsl.com to schedule your update if you need assistance with the upgrade installation, have any questions or experience any problems. 

And please note:

•  Our DefenderMX software is no longer supported. Contact support@fsl.com as soon as possible to schedule your upgrade.

•  If this message should be sent to another person or an additional individual at your firm, please send instructions for the necessary changes to support@fsl.com.