Brightmail spam definitions not updating
Symantec Messaging Gateway refreshes virus definitions in periodically, even though new viruses may not be discovered.This allows administrators to check whether their protection is up to date by simply looking at the date of their virus definitions.But first, let's cover some of the fundamental Exchange 2013 concepts that apply here.Looking at the Exchange 2013 transport architecture there are multiple services involved.Symantec Mail Security for Microsoft Exchange provides integrated mail protection against virus threats, spam, and other unwanted content for Microsoft Exchange 2000/2003 servers.
See Enabling and disabling spam and unwanted email policies.A very common scenario for Exchange Server 2013 administrators is the need to allow applications and devices on the network to use the Exchange server as an SMTP service.There are generally two specific business requirements: In this article I will demonstrate how to meet both of those requirements in Exchange Server 2013.The Client Access server role is configured with a receive connector called “Default Frontend SERVERNAME” that is intended to be the internet-facing receive connector, so is already set up to receive SMTP connections from unauthenticated sources and allow them to send email to internal recipients.
220 E15MB1.exchange2013Microsoft ESMTP MAIL Service ready at Mon, 1000 helo 250 E15MB1.exchange2013Hello [192.168.0.181] mail from: [email protected] 2.1.0 Sender OK rcpt to: [email protected] 2.1.5 Recipient OK data 354 Start mail input; end with . 250 2.6.0 <[email protected]> [In ternal Id=19911468384257] Queued mail for delivery This means that the only additional (and optional) step for making internal SMTP relay available to your applications and devices is to provide a DNS name for them to connect to.
Table: Set up the Customer-specific Spam submissions feature describes the process that you must take to set up the customer-specific spam submission feature.