|
|
||||
|
Back Patch 4 for McAfee Email and Web Appliance 5.1 released McAfee released Patch 4 for Email and Web Security Appliance 5.1. This patch includes Patch 3, which makes Patch 2 a required installation. Resolved Issues: • Feature Name f_479243 o Description: ISSUE: The recipient authentication detections did not appear in the email reports. RESOLUTION: This is now fixed. Please refer to KnowledgeBase article KB 65928 for more information. o Severity: Normal o Services will be restarted after installing this package o Proxies will be restarted after installing this package
• Feature Name f_483116 o Description: ISSUE: Database maintenance values were not restored but reset to defaults on restoring a previous configuration. RESOLUTION: Database maintenance values are now correctly restored. Please refer to KnowledgeBase article KB 66370 for more information. o Severity: Normal
• Feature Name f_485237 o Description: ISSUE: The list of viruses detected by an installed extra DAT was not sent to the user interface display. RESOLUTION: Extra DAT information is now displayed. Please refer to KnowledgeBase article KB 65903 for more information. o Severity: Normal
• Feature Name f_485691 o Description: ISSUE: An attempt to export the time-based URL filtering settings produced the time-independent settings instead. RESOLUTION: URL Policy settings are now separated properly, so the correct settings are exported. Please refer to KnowledgeBase article KB 65949 for more information. o Severity: Normal
• Feature Name f_485963 o Description: ISSUE: When alert header/footer was customized in the interface, it did not reflect in the corresponding notification email messages. RESOLUTION: The issue is now resolved. Please refer to KnowledgeBase article KB 65908 for more information. o Severity: Normal o Services will be restarted after installing this package o Proxies will be restarted after installing this package
• Feature Name f_488678 o Description: ISSUE: AV DAT and engine failure events were not logged into reports and channels. RESOLUTION: The issue is now resolved. Please refer to KnowledgeBase article KB 66356 for more information. o Severity: Normal
• Feature Name f_489121 o Description: ISSUE: Proxy settings configuration was not merged properly from 5.0sp1 configuration to 5.1. RESOLUTION: Proxy settings configuration is now properly merged. Please refer to KnowledgeBase article KB 65886 for more information. o Severity: Normal
• Feature Name f_490345 o Description: ISSUE: The real-time log loadaverage5 value kept incrementing and as a result showed wrong values. RESOLUTION: The issue is now resolved. Please refer to KnowledgeBase article KB 66358 for more information. o Severity: Normal
• Feature Name f_492747 o Description: ISSUE: The HTTP proxy sometimes failed to process a server response if the server closed the connection immediately after sending the response. RESOLUTION: The HTTP proxy processes server response data to the end. Please refer to KnowledgeBase article KB 66323 for more information. o Severity: Normal o Services will be restarted after installing this package o Proxies will be restarted after installing this package
• Feature Name f_494350 o Description: ISSUE: PUPs were classified as virus and the Dashboard counter for viruses was incremented. RESOLUTION: PUPs are correctly classified and the right counters are incremented. Please refer to KnowledgeBase article KB 66410 for more information. o Severity: Normal o Services will be restarted after installing this package o Proxies will be restarted after installing this package
• Feature Name f_494875 o Description: ISSUE: TLS did not work when reverse DNS lookups were disabled. RESOLUTION: This is now fixed. Please refer to KnowledgeBase article KB 66313 for more information. o Severity: Normal o Services will be restarted after installing this package o Proxies will be restarted after installing this package
• Feature Name f_495154 o Description: ISSUE: One of the startup scripts was attempting to connect to a database which no longer exists on the appliance, causing error messages to appear on the logs. RESOLUTION: The erroneous references to the former database have been removed. Please refer to KnowledgeBase article KB 66343 for more information. o Severity: Normal
• Feature Name f_498376 o Description: ISSUE: HTTP authentication has a timeout controlled by the authentication cookie. The timeout is set at 5 minutes and was not configurable. This could cause difficulties for users of some websites where form data could be lost if not submitted within the authentication timeout. RESOLUTION: HTTP authentication timeout is now configurable. Please refer to KnowledgeBase article KB 66357 for more information. o Severity: Normal o Proxies will be restarted after installing this package
• Feature Name f_500104 o Description: ISSUE: Validation error occurred when adding multiple SNMP trap managers via the interface. RESOLUTION: Validation was modified to accept any number of SNMP trap managers from the interface. Please refer to KnowledgeBase article KB 66318 for more information. o Severity: Normal
• Feature Name f_500138 o Description: ISSUE: The base policy name was always logged for legitimate email events, though the right policy was being applied. RESOLUTION: The correct policy name is now displayed. Please refer to KnowledgeBase article KB 66337 for more information. o Severity: Normal o Proxies will be restarted after installing this package
• Feature Name f_501967 o Description: ISSUE: An HTTP request to a different port was wrongly sent to the Keep-Alive connection. RESOLUTION: HTTP port resolution works correctly now. Please refer to KnowledgeBase article KB 66380 for more information. o Severity: Normal o Services will be restarted after installing this package o Proxies will be restarted after installing this package
• Feature Name f_502574 o Description: ISSUE: Anti-relay events were not logged when email addresses contained denied routing characters. RESOLUTION: This issue is now fixed. Please refer to KnowledgeBase article KB 66382 for more information. o Severity: Normal o Services will be restarted after installing this package o Proxies will be restarted after installing this package
MWS 5.1 patch 3 • Feature Name f_466829 o Description: ISSUE: When 'Release All' was selected for on-box quarantined emails, all the quarantined emails would get lost. RESOLUTION: The issue is now resolved. Please refer to KnowledgeBase article KB 65386 for more information o Severity: Normal o Services will be restarted after installing this package
• Feature Name f_473248 o Description: ISSUE: vtysh binary was not available as part of the zebra package. RESOLUTION: vtysh is now provided as part of the zebra package. Please refer to KnowledgeBase article KB 66014 for more information o Severity: Normal
• Feature Name f_473350 o Description: ISSUE: The user-submitted Black and White lists did not work when used as part of sub policies. RESOLUTION: This is now resolved. Please refer to KnowledgeBase article KB 65973 for more information o Severity: Normal o Proxies will be restarted after installing this package
• Feature Name f_475696 o Description: ISSUE: Sometimes the ScheduleReports file could get corrupted and hence Reports page did not appear in the user interface. RESOLUTION: ScheduleReports file is properly handled. Reports page will never be lost. Please refer to KnowledgeBase article KB 66025 for more information o Severity: Normal
• Feature Name f_475923 o Description: ISSUE: The user interface for the LDAP relative DN field had a validation check which did not allow the field to be empty. RESOLUTION: An empty relative DN Field is now accepted. Please refer to KnowledgeBase article KB 65901 for more information o Severity: Normal
• Feature Name f_477142 o Description: ISSUE: When DNS resolution failed, the local domain was always appended to the DNS name and resolution was retried, which is not desired in some situations. RESOLUTION: the user can now suppress appending of local domain. Please refer to KnowledgeBase article KB 55059 for more information o Severity: Normal o Services will be restarted after installing this package o Proxies will be restarted after installing this package
• Feature Name f_479397 o Description: ISSUE: Repeated coach screen pages were displayed due to multiple tagged URLs under the same host. RESOLUTION: URL-filtering coach action works as expected. Please refer to KnowledgeBase article KB 66001 for more information o Severity: Normal o Proxies will be restarted after installing this package
• Feature Name f_481185 o Description: ISSUE: Appliance log backup using Date Range did not work correctly because the backup file list was being incorrectly sorted for selection. RESOLUTION: Log files are now properly sorted. These files can now be backed up based on Date Range. Please refer to KnowledgeBase article KB 65967 for more information o Severity: Normal o Services will be restarted after installing this package
• Feature Name f_482667 o Description: ISSUE: LDAP groups were only evaluated for the first recipient of an email, causing incorrect policy selection for the remaining recipients. RESOLUTION: LDAP groups are now stored per-recipient, for policy resolution. Please refer to KnowledgeBase article KB 66019 for more information o Severity: Normal o Services will be restarted after installing this package o Proxies will be restarted after installing this package
• Feature Name f_483814 o Description: ISSUE: When the user made changes to dictionary settings, the changes were not stored in the appliance configuration. RESOLUTION: Changes are now stored correctly. Please refer to KnowledgeBase article KB 65680 for more information o Severity: Normal
• Feature Name f_486296 o Description: ISSUE: Some corrupt GZIP files attached to email were replaced though the configuration had the "Corrupted Content" action set to "Allow Through". RESOLUTION: The correct action is now performed. Please refer to KnowledgeBase article KB 65902 for more information o Severity: Normal o Proxies will be restarted after installing this package
• Feature Name f_487694 o Description: ISSUE: If the appliance encountered an X-EXCH50 (A Microsoft Exchange-specific ESMTP extension) command as part of an SMTP transaction, it did not accept the SMTP DATA verb. RESOLUTION: This is now fixed. Please refer to KnowledgeBase article KB 66002 for more information o Severity: Normal o Services will be restarted after installing this package o Proxies will be restarted after installing this package
• Feature Name f_487919 o Description: ISSUE: Web traffic stopped when HTTP reverse lookup was disabled and protocol preset was configured using host name rule types. In the system log segv messages were seen when this problem occurred. RESOLUTION: This issue is now fixed. Please refer to KnowledgeBase article KB 65872 for more information o Severity: Normal o Services will be restarted after installing this package o Proxies will be restarted after installing this package
• Feature Name f_487958 o Description: ISSUE: HTTP event ids 30000, 30002 and 30003 did not appear in syslog. RESOLUTION: This is now fixed. Please refer to KnowledgeBase article KB 65946 for more information o Severity: Normal o Proxies will be restarted after installing this package
• Feature Name f_488208 o Description: ISSUE: On older 3400 appliances, those with a hardware accelerator card, installing a DAT zip via the user interface would fail because the newer DAT zips used on 5.1 do not include the hardware acceleration file, scmdat.pdb. (A network update fetches the scmdat.pbd separately.) RESOLUTION: Manual update by installing a DAT zip will now work. Lack of a scmdat.pdb is no longer a fatal error. Please refer to KnowledgeBase article KB 65871 for more information o Severity: Normal
• Feature Name f_488311 o Description: ISSUE: When editing plain-text alerts, Internet Explorer 7 would dump an exception. RESOLUTION: IE7 no longer gives an exception dump when editing plain-text alerts. Please refer to KnowledgeBase article KB 65906 for more information o Severity: Normal
• Feature Name f_489674 o Description: ISSUE: With HTTP policies based on LDAP groups, web browsing could be slow with occasional page load errors. This was caused by repeated LDAP lookups causing excessive traffic between the appliance and the LDAP server. RESOLUTION: The LDAP, network and HTTP proxy software have been updated to do the lookups more efficiently and cache the results to avoid unnecessary repetition. Please refer to KnowledgeBase article KB 65914 for more information o Severity: Normal o Appliance will be rebooted after installing this package o Services will be restarted after installing this package o Proxies will be restarted after installing this package
• Feature Name f_490710 o Description: ISSUE: When email addresses with special characters in the local part were sent through the appliance, the corresponding events could not be logged. RESOLUTION: This issue is now resolved. Please refer to KnowledgeBase article KB 65980 for more information o Severity: Normal
• Feature Name f_481469 o Description: ISSUE: Policies based on wildcards were casesensitive, but email-address matching should always be case-insensitive. RESOLUTION: This is now fixed. Please refer to KnowledgeBase article KB 66007 for more information o Severity: Normal o Services will be restarted after installing this package o Proxies will be restarted after installing this package
• Feature Name f_487557 o Description: ISSUE: In some cases, a series of email messages sent over a single SMTP connection could be stopped with a 503 error, causing the remaining email messages to be rejected. This happened when a detection occurred on an email message in the series if the sending MTA did not issue RSET between email messages sent over the same connection. RESOLUTION: This is now fixed. Please refer to KnowledgeBase article KB 66018 for more information o Severity: Normal o Proxies will be restarted after installing this package |
||||