Sophos Puremessage

Puremessage
  • PureMessage installs Microsoft .NET Framework 3.5 Service Pack 1 as a prerequisite, because of which you may experience issues with components related to Exchange Web services including:
    • Outlook Web Access
    • Office Communications Server integration
    • Outlook Address Book
    • Out of Office notifications

    To resolve these issues, install the update for .NET Framework provided in Microsoft knowledgebase article 959209 (http://support.microsoft.com/kb/959209).

  • Microsoft Essential Business Server 2008 and Microsoft Small Business Server 2008 both come with Microsoft Forefront Security for Exchange Server preinstalled. You should uninstall Forefront before installing PureMessage.
  • If you install PureMessage on a computer in a workgroup, you cannot use a Microsoft SQL Server database located on a different computer (that is, a remote database). You can specify a remote database during installation, but PureMessage does not set the necessary access rights. In this case, contact Sophos technical support for a workaround.
  • If you install PureMessage on a Windows Server 2003 R2 SP2 computer, the configuration settings entered during the installation of PureMessage may be lost if either of the following two prerequisites is not installed:
    • .NET Framework 3.5 SP1
    • Windows Installer 4.5

    To workaround this problem, install these prerequisites before installing PureMessage.

  • The installer may fail with an error Setup was unable to create the PureMessage databases.
    This can happen if, in the past, you have uninstalled the SOPHOS database instance from Microsoft SQL Server or uninstalled Microsoft SQL Server itself. In this case, delete the following files from the MS_SQL_INSTALL_FOLDERMSSQL.XMSSQLData folder.
    • SavexCnfg.mdf
    • SavexCnfg_log.ldf
    • SavexDir.mdf
    • SavexDir_log.ldf
    • SavexQuar.mdf
    • SavexQuar_log.ldf
    • SavexRprt.mdf
    • SavexRprt_log.ldf
  • (DEF 83210) The installer may fail with the following error:
    0x80040e14 - idispatch error 3092 unable to start the PureMessage database.

    This can happen if you try to install PureMessage to a SQL instance which was installed to be case sensitive. To avoid this, install PureMessage to a SQL instance that is not case sensitive .

  • (DEF 83055) The installer may fail with an error similar to:
    PMInstallUtil.cpp ln 5750: ERR Failed '(iErr != ERROR_SUCCESS) && (iErr != ERROR_ALREADY_EXISTS)' : Win32 error 0x800700a1.

    This can occur when attempting to install on an SCC cluster using folder-mounted shared storage.

  • (WKI 50085) After the installation of PureMessage, you may receive a message 'Could not connect to master synchronization server' while opening the PureMessage administration console. You receive this message if some of the servers in a configuration have been upgraded and others are not. To avoid this, ensure you upgrade all the servers in the configuration group one after another.
  • (WKI 50589) While attempting to install PureMessage on a Microsoft Essential Business Server (EBS), the installer may fail during .NET Framework installation. For information on how to workaround this issue, see http://blogs.technet.com/essentialbusinessserver/archive/2009/05/07/microsoft-net-framework-3-5-sp1-kb951847-fails-to-install-on-ebs-servers.aspx.
  • (WKI 51027) When installing PureMessage on Windows 2008 R2, installation of SQL 2008 Express Edition may fail with a message similar to:
    Error code 2064843076 was returned when running:

    <path>SQLEXPR_x64_ENU.exe /QUIETSIMPLE /ACTION=INSTALL /FEATURES=SQL /INSTANCENAME =SOPHOS /SQLSVCACCOUNT ='NT AUTHORITYNETWORK SERVICE' /SQLSYSADMINACCOUNTS='BUILTINAdministrators'

    This is due to an issue with Microsoft SQL 2008 Express Edition. Reinstalling PureMessage usually resolves this problem.

  • (WKI 51471) When attempting to install PureMessage, the installation may fail with a message similar to:

    Error code 1 was returned while running:<path>Bootstrap.exe install sav <path>

    You receive this message if the installer path has exceeded the maximum character length of 256, or if you are installing from a network location. To avoid this, copy the installer locally with install path not exceeding 256 characters.
  • (WKI 52804) When installing PureMessage on Windows Server 2008 Active Directory with Exchange Server 2007. You may receive the following error:

    Error code 2067529721 was returned when running:

    <path>/SQLEXPR_x64_ENU.exe /QUIETSIMPLE /ACTION=INSTALL /FEATURES=SQL /INSTANCENAME=SOPHOS /SQLSVACCOUNT='NT AUTHORITYSYSTEM'/SQLSYSADMINACCOUNTS='BUILTINAdministrators'

    With 'Error: Unable to find media for .Net version 2.0' in the SqlSetup.log file created in the system's Temp directory.

    This is due to an issue with Microsoft SQL 2008 Express Edition. Reinstalling PureMessage usually resolves this problem.

  • Tags added to email subject lines (if you set up Email tagging) may be displayed as question marks.
    This occurs when all the following conditions apply:
    • The subject tag contains extended characters, such as Japanese text.
    • The message is encoded in TNEF, which requires that it is sent from a MAPI mail client.
    • The message is encoded using a character set that doesn't support characters specified in the subject tag.
    • The message is viewed with a mail client that uses the multi-byte subject property rather than the wide-character subject property.

      For messages sent from Outlook Web Access with Exchange 2003, the issue can be resolved by modifying the registry value UseRegionalCharset in key HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesMSExchangeWEBOWA to zero. See http://support.microsoft.com/kb/830827 for details.

  • X-header tagging only works for Exchange 2003. It does not work for Exchange 2007 and Exchange 2010.

  • (WKI 57286) Non-ASCII characters in Disclaimer text may be displayed as question marks when added to the TNEF messages sent in plain-text format. This issue occurs when the original message Charset does not support the non-ASCII characters.

    To avoid this, it is recommended to use standard ASCII characters when defining disclaimers in PureMessage.

  • (WKI 55150) If you install PureMessage on a computer that has Sophos Enterprise Console (SEC) installed, SEC will display a 'Differs from policy' error. The error is displayed as PureMessage will set the autoupdate frequency to 5 minutes from SEC's default update policy of 10 minutes.

    To Workaround this problem, reapply the default update policy for PureMessage systems, or create a seperate group and add allPureMessage servers to that group with a new updating policy.

Sophos Puremessage For Microsoft Exchange

PureMessage now supports Microsoft Exchange Server 2016. (GWPME-466) Resolved an issue where PureMessage store scanning failed to find more than the first thousand mailboxes during the discovery phase. (GWPME-439) PureMessage now performs a Sophos Live Protection query during each scan. The PureMessage Manager is a web-based graphical interface to PureMessage. Can only be performed from the command line, the majority of tasks can be accomplished via the Manager. PureMessage 4.0.4 can be used with Microsoft Exchange 2013 and 2016.

The latest tweets from @nycsouthpaw. Southpaw, Royal Tunbridge Wells. We are Southpaw, a creative company that moves people. Southpaw twitter. Twitter.com Thomas P. (Tom) Logan 🇺🇸 🇯🇵 on Twitter “S. Korean daily 'Chosun Ilbo' picks up the story from local Korean press who accessed eyewitness to mass shooting today, and claims suspect shouted 'I am going to kill all Asians' as he shot victims.

Mysophos Account

Overview Sophos PureMessage version 4.0.4 also installs the CheckDBConnection test tool alongside the main components of PureMessage. This can be used to verify whether your Database is compatible with TLS 1.2. This article explains all of the database connection checks that the CheckDBConnection tool makes. To provide you with the best possible protection and the latest technology, Sophos Central is available for trial. Sophos PureMessage has entered the End of Sale/End of Life phase of the product lifecycle. For more information on product retirements, see the Product Lifecycle Page.