This screen lets you specify options regarding how Overseer sends Email. Note
that Overseer uses Email to send text messages as well.
- Relay Server:
This is the SMTP Relay server you wish to use. If you have one internally,
that will work. Alternatively, you can use an external SMTP server, such as
a gmail SMTP server.
- Server Port:
This is the port to use when contacting the SMTP Relay Server
- Use TLS/SSL:
This instructs Overseer to connect to the relay server using TLS/SSL for security. Note that the server must support this.
- Use Gmail:
This button lets you simply enter your valid Gmail username and password(@gmail.com or @yourdomain.com if you
host Email with Google Apps), and Overseer will automatically fill in the correct SMTP Relay Server information.
This lets you specify the username to login to the SMTP relay server. If using
gmail's SMTP server, this is your firstname.lastname@example.org Email address.
This is the password for the username specified above.
- Use built-in SMTP delivery agent as backup:
This instructs Overseer to attempt direct delivery to destination SMTP servers
if the relay server fails. In modern day, this is likely to be rejected by
most destination SMTP servers, due to requirements for non-residential IPs,
reverse DNS records, etc. from the connecting server. Please don't rely on this
feature as your primary means to be notified of alerts.
- From Name:
This is the name that appears in the 'From' field when Overseer sends a
notification. If you're deploying multiple Overseer installations, it is
best to change this to something meaningful, such as [Officename] - Overseer
- From Address:
This is the address that Overseer sends Email from. Note that this doesn't
have to be a real Email address, but it should look like one so no SMTP
mail servers drop your notification messages.
Copyright 2003-2012 Sensible Software, Inc. All Rights Reserved.
Network Monitoring Software