This article applies to:
- Trustwave MailMarshal (SEG)
- Trustwave ECM/MailMarshal Exchange 7.X
Question:
- What HTTP errors could be returned by MailMarshal?
Information:
MailMarshal uses HTTP and HTTPS (web requests) for update functionality including the SpamCensor updates, Known Threat updates, Blended Threats Module updates or provisioning (depending on product version), and licensing/maintenance provisioning.
The following is a list of common HTTP error messages that could be returned by MailMarshal. These messages could appear in the text logs or in the web interface or Configurator > MailMarshal Properties > Automatic Updates:
- Request failed, please see Trustwave Knowledgebase article Q13703. <Detailed error>
- An SSL certificate validation error occurred. The most likely cause of this error is that the required CA root certificates were not available. For more information see the linked article.
- Request failed, please check your proxy settings: <Detailed error>
- A proxy server is specified, and a large number of redirects occurred while attempting to connect. This error could indicate your proxy server settings (server name or proxy authentication details) are invalid.
- Request failed: Response code: <HTTPcode> returned
- The request was processed, but the HTTP response code received from the server was in the 4xx or 5xx range. The specific HTTP response code is returned.
- Code 403 could indicate your MailMarshal maintenance is out of date. See Trustwave Knowledgebase article Q11998
- Code 410 indicates that Trustwave no longer provides updates for the product version. You should upgrade.
- Request failed: Failed to get response code: <Detailed error>
- The request was processed, but a HTTP response code was not provided.
- Request failed: <Detailed error>
- The request failed for some other reason. The error returned should provide more information.
- "Received HTTP Code 407" indicates proxy credentials are required