Risk updating brightmail
Then click the icon and add at least one IP address of an application server or device that requires external SMTP relay access. Next we need to configure some additional settings for the receive connector. The final step involves granting anonymous users (such as the unauthenticated SMTP connections coming from applications and devices on your network) the ability to send to external recipients.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.When a new definition update is available, Live Update will detect it and automatically download it to the Symantec Messaging Gateway scanner.
Risk updating brightmail comments