Académique Documents
Professionnel Documents
Culture Documents
3 GA
Release Notes
Technical Documentation
Knowledge Base
Customer Service & Support
Training Services
FortiGuard
Document Feedback
docs.fortinet.com
kb.fortinet.com
support.fortinet.com
training.fortinet.com
fortiguard.com
techdocs@fortinet.com
Table of Contents
Introduction ...................................................................................................... 4
Supported Platforms ........................................................................................... 4
What's New....................................................................................................... 5
New file type support on FortiSandbox integration ............................................. 5
More flexibility on mail data backup schedule .................................................... 5
Task-based search for system quarantine .......................................................... 5
Traffic capture tool on GUI .................................................................................. 5
Introduction
This document provides a summary of new features, support information, upgrade/downgrade
instructions, and resolved issues in FortiMail 5.2.3 release build 0434.
Supported Platforms
FortiMail 5.2.3 release supports the following platforms:
FortiMail 200D
FortiMail 400C
FortiMail 1000D
FortiMail 2000B
FortiMail 3000C
FortiMail 3000D
FortiMail 5002B
FortiMail VM (VMware vSphere Hypervisor ESX/ESXi 5.0 and higher)
FortiMail VM (Microsoft Hyper-V Server 2008 R2 and 2012)
FortiMail VM (KVM qemu 0.12.1)
FortiMail VM (Citrix XenServer v5.6sp2, 6.0 and higher)
What's New
New file type support on FortiSandbox integration
FortiMail can upload more email attachment types that have been added to the new
FortiSandbox release.
Special Notices
TFTP firmware install
Using TFTP via the serial console to install firmware during system boot time will erase all
current FortiMail configurations and replace them with factory default settings.
FortiSandbox support
FortiMail 5.2.3 release requires FortiSandbox 1.4.0 or newer releases.
Firmware Upgrade/Downgrade
Information
Before and after any firmware upgrade/downgrade
If you are using the web UI, clear the browser cache prior to login on the FortiMail
unit to ensure proper display of the web UI screens.
The antivirus signatures included with an image upgrade may be older than those
currently available from the Fortinet FortiGuard Distribution Network (FDN). Fortinet
recommends performing an immediate AV signature update as soon as possible
after upgrading. Consult the FortiMail Administration Guide for detailed procedures.
Upgrade path
For any older 3.0 release
Any 3.0 release older than 3.5.4
Firmware downgrade
Downgrading from 5.2 to 5.1, 5.0 or 4.0 releases
Downgrading from 5.2 to any 5.1, 5.0, or 4.0 release is not fully supported. If you have to
downgrade, follow these steps:
1. Back up the 5.2 configuration.
2. Install the older image.
3. In the CLI, enter execute factoryreset to reset the FortiMail unit to factory defaults.
4. Configure the device IP address and other network settings.
5. Reload the 5.2 backup configuration if needed.
Resolved Issues
This section lists the resolved issues in this release, but is not a complete list. For inquires
about a particular bug, please contact Fortinet Technical Support.
Antispam
Bug ID
Description
265094
Dictionary entries are not detected when they exist in some type of
replied email.
254841
263292
263405
In some cases, email from blacklisted senders is not handled with the
configured action.
263170
264102
Email should not be rejected with "User unknown" if the LDAP server is
unreachable and "Bypass recipient verification if server unavailable" is
enabled.
265514
265267
264318
Bug ID
Description
267136
MTA
Webmail
Bug ID
Description
265605
267271
IBE users get an error message ("Error: Failed to open mailbox") when
sending reply messages.
System
Bug ID
Description
267437
263435
In a config-only HA cluster, the log file rotation size setting is not handled
correctly after firmware upgrading, if the old size limit is above the
maximum allowed size in the new release.
263576
265063
265665
265363
Clicking the firmware update link on the dashboard causes endless error
message loop for read-only administrator accounts.
266985
10
Image Checksums
To verify the integrity of the firmware file, use a checksum tool and compute the firmware file's
MD5 checksum. Compare it with the checksum indicated by Fortinet. If the checksums match,
the file is intact.
MD5 checksums for Fortinet software and firmware releases are available from Fortinet
Customer Service & Support. After logging in to the web site, near the bottom of the page,
click the Firmware Checksums button. (The button appears only if one or more of your devices
have a current support contract.) In the File Name field, enter the firmware image file name
including its extension, then click Get Checksum Code.
11
12