IronPort - daily management guide - AsyncOS 7.6.1

More documents

Recommendations

Info

Debugging Mail Flow Using Test Messages: Trace 9-2 Cisco IronPort AsyncOS 7.6 for Email Daily Management Guide Chapter 9 Testing and Troubleshooting The Trace page (and trace CLI command) prompts you for the input parameters listed in Table 9-1. Table 9-1 Input for the Trace page Value Description Example Source IP address Type the IP address of the remote client to mimic the source of the remote domain. 203.45.98.109 Fully Qualified Domain Name of the Source IP Listener to Trace Behavior on SenderBase Network Owner Organization ID SenderBase Reputation Score (SBRS scores) Note: The trace command prompts for an IP address and a fully-qualified domain name. It does not attempt to reverse the IP address to see if it matches the fully-qualified domain name. The trace command does not allow the fully-qualified domain name field to be blank, so it is impossible to test a scenario where the DNS does not reverse match properly. Type the fully-qualified remote domain name to mimic. Choose from the list of listeners configured on the system to emulate sending the test message to. Type the unique identification number of the SenderBase network owner, or allow the system to Lookup network owner ID associated with source IP address. You can view this information if you added network owners to sender groups via the GUI. Type the SBRS you want to provide for the spoofed domain, or allow the system to lookup SBRS associated with source IP address. This can be helpful when testing policies that use SBRS scores. See “Implementing Reputation Filtering in a Listener’s HAT” in the Cisco IronPort AsyncOS for Email Configuration Guide for more information. smtp.example.com InboundMail Envelope Sender Type the Envelope Sender of the test message. admin@example.net Envelope Recipients Type a list of recipients for the test message. Separate multiple entries with commas. Message Body Type the message body for the test message. Type a period on a separate line to end entering the message body. Note that “headers” are considered part of a message body. After you have entered the values, click Start Trace. A summary of all features configured on the system affecting the message is printed. 34 -7.5 joe frank@example.com To: 1@example.com From: ralph Subject: Test this is a test message . OL-25138-01
Chapter 9 Testing and Troubleshooting OL-25138-01 Debugging Mail Flow Using Test Messages: Trace You can upload message bodies from your local file system. (In the CLI, you can test with message bodies you have uploaded to the /configuration directory. See Appendix A, “Accessing the Appliance” for more information on placing files for import onto the Cisco IronPort appliance.) After the summary is printed, you are prompted to view the resulting message and re-run the test message again. If you enter another test message, the Trace page and the trace command uses any previous values from Table 9-1 you entered. Note The sections of configuration tested by the trace command listed in Table 9-2 are performed in order. This can be extremely helpful in understanding how the configuration of one feature affects another. For example, a recipient address transformed by the domain map feature will affect the address as it is evaluated by the RAT. A recipient that is affected by the RAT will affect the address as it is evaluated by alias table, and so on. Table 9-2 Viewing Output When Performing a Trace trace Command Section Output Host Access Table (HAT) and Mail Flow Policy Processing The Host Access Table settings for the listener you specified are processed. The system reports which entry in the HAT matched from the remote IP address and remote domain name you entered. You can see the default mail flow policies and sender groups and which one matched the given entries. If the Cisco IronPort appliance was configured to reject the connection (either through a REJECT or TCPREFUSE access rule), the trace command exits at the point in the processing. For more information on setting HAT parameters, see “The Host Access Table (HAT): Sender Groups and Mail Flow Policies” in the Cisco IronPort AsyncOS for Email Configuration Guide. Envelope Sender Address Processing These sections summarize how the appliance configuration affects the Envelope Sender you supply. (That is, how the MAIL FROM command would be interpreted by the configuration of the appliance.) The trace command prints “Processing MAIL FROM:” before this section. Default Domain If you specified that a listener to change the default sender domain of messages it receives, any change to the Envelope Sender is printed in this section. For more information, see the “Customizing Listeners” chapter in the Cisco IronPort AsyncOS for Email Advanced Configuration Guide. Cisco IronPort AsyncOS 7.6 for Email Daily Management Guide 9-3
Page 1 and 2:
Cisco IronPort AsyncOS 7.6 for Emai
Page 3 and 4:
CHAPTER 1 Managing the Cisco IronPo
Page 5 and 6:
CHAPTER 4 Quarantines 4-1 OL-25138-
Page 7 and 8:
CHAPTER 5 Logging 5-1 OL-25138-01 M
Page 9 and 10:
OL-25138-01 Monitoring Detailed Ema
Page 11 and 12:
OL-25138-01 Managing Users 8-14 Add
Page 13 and 14:
OL-25138-01 CHAPTER 1 Managing the
Page 15 and 16:
Chapter 1 Managing the Cisco IronPo
Page 17 and 18:
Chapter 1 Managing the Cisco IronPo
Page 19 and 20:
OL-25138-01 Using Email Security Mo
Page 21 and 22:
Chapter 2 Using Email Security Moni
Page 23 and 24:
Page 25 and 26:
Page 27 and 28:
Page 29 and 30:
Page 31 and 32:
Page 33 and 34:
Page 35 and 36:
Page 37 and 38:
Page 39 and 40:
Page 41 and 42:
Page 43 and 44:
Page 45 and 46:
Page 47 and 48:
Page 49 and 50:
Page 51 and 52:
Page 53 and 54:
Page 55 and 56:
Page 57 and 58:
Page 59 and 60:
Page 61 and 62:
Page 63 and 64:
Page 65 and 66:
Page 67 and 68:
OL-25138-01 Tracking Email Messages
Page 69 and 70:
Chapter 3 Tracking Email Messages O
Page 71 and 72:
Chapter 3 Tracking Email Messages R
Page 73 and 74:
Chapter 3 Tracking Email Messages M
Page 75 and 76:
OL-25138-01 Quarantines CHAPTER 4 Q
Page 77 and 78:
Chapter 4 Quarantines OL-25138-01 M
Page 79 and 80:
Page 81 and 82:
Page 83 and 84:
Chapter 4 Quarantines Viewing Messa
Page 85 and 86:
Chapter 4 Quarantines OL-25138-01 F
Page 87 and 88:
Chapter 4 Quarantines Selecting a M
Page 89 and 90:
Chapter 4 Quarantines OL-25138-01 S
Page 91 and 92:
Chapter 4 Quarantines OL-25138-01 W
Page 93 and 94:
Chapter 4 Quarantines OL-25138-01 C
Page 95 and 96:
Chapter 4 Quarantines Cisco IronPor
Page 97 and 98:
Page 99 and 100:
Chapter 4 Quarantines Configuring S
Page 101 and 102:
Chapter 4 Quarantines OL-25138-01 S
Page 103 and 104:
Page 105 and 106:
Chapter 4 Quarantines Disk Space OL
Page 107 and 108:
Chapter 4 Quarantines Ensuring that
Page 109 and 110:
Page 111 and 112:
Chapter 4 Quarantines Deleting Mess
Page 113 and 114:
Chapter 4 Quarantines OL-25138-01 W
Page 115 and 116:
Chapter 4 Quarantines OL-25138-01 T
Page 117 and 118:
Chapter 4 Quarantines Method 2 OL-2
Page 119 and 120:
Chapter 4 Quarantines OL-25138-01 F
Page 121 and 122:
Overview OL-25138-01 Logging CHAPTE
Page 123 and 124:
Chapter 5 Logging OL-25138-01 Table
Page 125 and 126:
Page 127 and 128:
Chapter 5 Logging Logs Enabled by D
Page 129 and 130:
Chapter 5 Logging OL-25138-01 Infor
Page 131 and 132:
Chapter 5 Logging Successful Messag
Page 133 and 134:
Chapter 5 Logging Message with Atta
Page 135 and 136:
Chapter 5 Logging Using IronPort De
Page 137 and 138:
Chapter 5 Logging Successful Messag
Page 139 and 140:
Chapter 5 Logging Examples of Bounc
Page 141 and 142:
Page 143 and 144:
Chapter 5 Logging Domain Debug Log
Page 145 and 146:
Chapter 5 Logging Using IronPort CL
Page 147 and 148:
Chapter 5 Logging Using IronPort HT
Page 149 and 150:
Chapter 5 Logging Using IronPort An
Page 151 and 152:
Chapter 5 Logging Using IronPort LD
Page 153 and 154:
Chapter 5 Logging Safelist/Blocklis
Page 155 and 156:
Chapter 5 Logging Using Updater Log
Page 157 and 158:
Chapter 5 Logging Using Authenticat
Page 159 and 160:
Chapter 5 Logging Configuring Log S
Page 161 and 162:
Chapter 5 Logging Figure 5-1 Creati
Page 163 and 164:
Chapter 5 Logging Logging Message H
Page 165 and 166:
Chapter 5 Logging Rollover By File
Page 167 and 168:
Chapter 5 Logging Viewing Recent Lo
Page 169 and 170:
Chapter 5 Logging Configuring Host
Page 171 and 172:
Chapter 5 Logging OL-25138-01 - PRI
Page 173 and 174:
Chapter 5 Logging OL-25138-01 mail3
Page 175 and 176:
OL-25138-01 CHAPTER Managing and Mo
Page 177 and 178:
Chapter 6 Managing and Monitoring v
Page 179 and 180:
Page 181 and 182:
Page 183 and 184:
Page 185 and 186:
Page 187 and 188:
Page 189 and 190:
Page 191 and 192:
Page 193 and 194:
Page 195 and 196:
Page 197 and 198:
Page 199 and 200:
Page 201 and 202:
Page 203 and 204:
Page 205 and 206:
Page 207 and 208:
Page 209 and 210:
Page 211 and 212:
Page 213 and 214:
Page 215 and 216:
Page 217 and 218:
Page 219 and 220:
Page 221 and 222:
OL-25138-01 Other Tasks in the GUI
Page 223 and 224:
Chapter 7 Other Tasks in the GUI Ex
Page 225 and 226:
Chapter 7 Other Tasks in the GUI OL
Page 227 and 228:
Page 229 and 230:
Page 231 and 232:
Page 233 and 234:
Page 235 and 236: Chapter 7 Other Tasks in the GUI OL
Page 237 and 238: Chapter 7 Other Tasks in the GUI OL
Page 239 and 240: OL-25138-01 CHAPTER Common Administ
Page 241 and 242: Chapter 8 Common Administrative Tas
Page 285: OL-25138-01 Testing and Troubleshoo
Page 289 and 290: Chapter 9 Testing and Troubleshooti
Page 317 and 318: A accessing 2-2 access privileges f
Page 319 and 320: Injection Connection ID (ICID) 6-4
Page 321 and 322: subject tagging 4-5 testing message
Page 323 and 324: work queue, pausing 6-35 X XML 5-2,
show all

IronPort - daily management guide - AsyncOS 7.6.1

Create successful ePaper yourself

Delete template?

Save as template?