Educational ICT Virtualisation Specialist

Twitter LinkedIn E-mail
Precedence Technologies Ltd
Technology House, 36a Union Lane
Cambridge, CB4 1QB, United Kingdom
T: +44 (0)8456 446 800 / +44 (0)1223 359900
F: +44 (0)8456 446 899 / +44 (0)1223 359459

Jump To: Support > KB > NetManager > Email > ExchangeRelay

Sending system reports if NetManager is not your main mailserver

Configuring NetManager to be able to send email externally

 and to users on an alternative local mail server (e.g. Exchange)
  1. Determine the email domain name ( in this example)
  2. Determine what mail relay to use, if any. This could be any of:
    • On-premises mail server (e.g. Exchange)
    • ISP SMTP relay
    • Authenticated sending via Gmail (see here for details)
    • Send direct, no relay
  3. Set mail relay on NetManager to the IP address of the mail relay (or leave empty to send direct). This can be done through Email > Send/Rcv in webadmin, from option I and then M on the Console Menu or by setting mail_relay in the NetManager configuration file. If configured, all non-local email will be sent to this server for onwards delivery.
  4. Set mail_local_domain in the NetManager configuration file. This will cause email to be sent from Do not configure a local domain (using the console menu, webadmin or domain_external configuration setting) as this will make the NetManager believe that mail for should be delivered to itself
  5. Once the changes have been made, you must run build_server to make the changes live. Do not be tempted to run just the sendmail build script.
  6. To receive system mails, set an email alias from root to a suitable user account
  7. Test sending mail externally from the command line:
    netmanager 1# echo "Hello" | mail -s Test
  8. Test sending mail to root internally from the command line:
    netmanager 1# echo "Hello" | mail -s Test root
In summary, the NetManager configuration file should contain:

Setting up Exchange 2010 to relay SMTP email from NetManager

  1. Launch Exchange Management Console
  2. Expand tree in left-hand panel and selectServer Configuration
  3. Select Hub Transport
  4. Select the server and then from the Actions (right-hand) pane of the console choose New Receive Connector
  5. Type in a suitable name, e.g. NetManager. Leave intended use as Custom and click Next >
  6. On the Local Network settings page, leave the IP address as is. Enter the standard amil domain name of the site in the FQDN box and click Next >
  7. On the Remote Network settings page, select the default range and click the X button above to delete
  8. For each NetManager, click on Add... and enter its IP address. When you have added all, click Next >
  9. Review settings and click New
  10. Once completed, click Finish
  11. In the bottom half of the Hub Transport panel, right-click on the new receive connector you have just created and choose Properties
  12. Switch to the Permission Groups tab and select Anonymous Users and Exchange Servers.
  13. Switch to the Authentication tab and select Externally Secured
  14. Click OK
  15. Test
© Copyright Precedence Technologies 1999-2019
Page last modified on November 16, 2018, at 10:42 AM by sborrill