TECH235737 - Following a OS crash, Messaging Gateway deployed on Hyper-V 2012 may loose network cards TECH235317 - Bounce attack validation causes some messages to fail recipient validation TECH235626 - Strip all attachments action may not occur when message is released from virus quarantine TECH235038 - Mail server restarts with signal 6 at regular intervals TECH234968 - Configuration saved but cannot be published to some SMG hosts TECH234974 - Fan failure alert on the Messaging Gateway 8340 appliance TECH234596 - Some messages become corrupted when Recipient Validation is enabled TECH234540 - Messaging Gateway content filtering dictionary rules fail to match message headers TECH234173 - Messages queue in inbound queue following update to SMG 10.6 TECH233957 - Sending Brightmail Admin Events to remote syslog server cannot be enabled for Control Center only device TECH223693 - DNS DNAME record results in failed message delivery TECH228278 - Using both aliasing and subaddress removal causes Recipient Validation failure TECH230314 - Symantec Messaging Gateway closes network connection prematurely when delivering messages.
Open the regsitry editor (Start -\Server\Components\SMTP\BMIConfig Init 3.
In the right pane, locate the value BMIConfig Init, right click it and choose Delete. Restart the Symantec Mail Security for Microsoft Exchange service.
Services stopped from Symantec Messaging Gateway (SMG) command line interface (CLI) cannot be started from Control Center GUI Services stopped from SMG Control Center GUI cannot be started from CLI.
Affected services: Conduit, Live Update, Brightmail Engine, MTA, Directory Data Service This behavior is not considered a defect and is a function of the SMG process control.
Live Update Administrator 2.x functions as an internal mirror to the contents of the Live Update source servers on the Internet.
Certified Anti Virus definitions and other non-spam updates are available through LUA 2.x for SMSDOM, SMSMSE, SMG and many other products. Install the SPA and Anti-virus licenses previously saved. Fix possible ruleset accumulation issues - SMSMSE 6.5.2 and earlier. Start the following Windows services: Symantec Mail Security for Microsoft Exchange Symantec Mail Security Utility Service 8. Remove the files and cert.pem, if they exist, from the following directory: 32-bit Operating System: Program Files (x86)\Symantec\SMSMSE.5\Server\UPLOADS 7. Reset IIS to reset the Premium Anti Spam event sync within Exchange 2003. Confirm Whitelisting with Exchange 2007/2010 and SMSMSE 6.5.1 and earlier. Confirm transport agent priority for Exchange 2007/2010. Confirm authenticated Exchange servers with SMSMSE 6.5.1 and earlier. Remove all existing SPA rules and download new ones J. The following is an example for 6.5 on a 64-bit operating system: C:\Program Files (x86)\Symantec\SMSMSE.5\Server\Spam Prevention 5. These updates are released by Symantec several times per hour.