Why do SpamCensor updates fail?


This article applies to:

  • MailMarshal 

Question:

  • Why do SpamCensor updates fail?

Information:

If SpamCensor updates fail with error code 403 or 410, see the following articles.

  • Q11998, 403 Access Forbidden: Product Key or Maintenance is not current.
  • Q14242, 410 Updates are no longer provided for this product version.
    • Updates are no longer provided for Trustwave MailMarshal (SEG) versions below 7.2.3.

If these solutions do not apply and your SpamCensor updates fail it can be because the MailMarshal Array Manager server has been denied access to the Internet (HTTP and HTTPS). Trustwave strongly recommends that you allow this access. You can configure MailMarshal to use a proxy server if required. For details, see the documentation for "Internet Access" for your version of MailMarshal.

Workaround:

If you cannot grant the Array Manager Internet access, you can update SpamCensor manually. See the following Trustwave Knowledgebase article for more information:  

    • Q11406: How do I manually update SpamCensor scripts?

    Notes:

    Information about issues with WinInet in much older versions of MailMarshal has been removed from this article.

    Last Modified 3/1/2020.
    https://support.trustwave.com/kb/KnowledgebaseArticle11718.aspx