Cisco Cisco Email Security Appliance C170 Guia Do Utilizador

Página de 1140
 
23-64
Cisco AsyncOS 8.5.5 for Email Security User Guide
 
Chapter 23      Configuring Routing and Delivery Features
  Configuring Mail Gateways for all Hosted Domains Using Virtual Gateway™ Technology
An illustration of the configuration change in this example is shown in 
Figure 23-14
Example: Selecting an IP Interface or Interface Group to Use
Monitoring the Virtual Gateway Addresses
While each Virtual Gateway address has its own email queue for delivery purposes, the system 
administration, logging, and reporting capabilities still provide a holistic view into all Virtual Gateway 
queues as if they were one. To monitor the recipient host status for each Virtual Gateway queue, use the 
hoststatus
 and 
hostrate 
command. See the “Reading the Available Components of Monitoring” 
section in the “Managing and Monitoring Using the CLI” chapter. 
The 
hoststatus
 command returns monitoring information about email operations relating to a specific 
recipient host. 
If you are using Virtual Gateway technology, information about each Virtual Gateway address is also 
displayed. The command requires you to input the domain of the host information to be returned. DNS 
information stored in the AsyncOS cache and the last error returned from the recipient host is also given. 
Data returned is cumulative since the last 
resetcounters
 command. 
The statistics returned are grouped into two categories: counters and gauges. In addition, other data 
returned include: last activity, MX records, and last 5XX error. 
Managing Delivery Connections per Virtual Gateway Address
Certain system parameters require settings at the system and Virtual Gateway address levels. 
For example, some recipient ISPs limit the number of connections they allow for each client host. 
Therefore, it is important to manage relationships with the ISPs, especially when email is being delivered 
over multiple Virtual Gateway addresses. 
See 
 for information about the 
destconfig
 command and how Virtual Gateway addresses are affected.
Please enter some comments describing your changes:
[]> Added 2 altsrchost mappings 
Changes committed: Thu Mar 27 14:57:56 2003
Ethernet interface: Data 2
IP interface: 
PublicNet 
192.168.2.1
IP interface: 
PublicNet2 
192.168.2.2
exchange.example.com
192.168.35.35
The 
altsrchost
 table was 
modified to create these 
mappings. Messages from 
@exchange.example.com
 use the 
interface PublicNet, and 
messages from 192.168.35.35 use 
the interface PublicNet2.