IronPort - advanced configuration guide

More documents

Recommendations

Info

2-52 recipient_limit = 100 table_tls = require_verify limit_apply = VG bounce_profile = tls_failed limit_type = host [example2.com] table_tls = on bounce_profile = tls_failed Cisco IronPort AsyncOS 7.6 for Email Advanced Configuration Guide Chapter 2 Configuring Routing and Delivery Features The above example results in the following Destination Control entries for example1.com and example2.com: example1.com IP Address Preference: IPv6 Preferred Maximum messages per connection: 50 Rate Limiting: 500 concurrent connections 100 recipients per 60 minutes Limits applied to entire domain, across all virtual gateways TLS: Required (Verify) Bounce Profile: tls_failed example2.com IP Address Preference: IPv6 Preferred Maximum messages per connection: Default Rate Limiting: Default TLS: Preferred Bounce Profile: tls_failed OL-25137-01
Chapter 2 Configuring Routing and Delivery Features Destination Controls and the CLI OL-25137-01 Use the Import Table button on the Destination Controls page or the destconfig -> import command to import a configuration file.You can also export your Destination Control entries to an INI file using the Export Table button on the Destination Controls page or the destconfig -> export command. AsyncOS includes the [Default] domain control entry in the exported INI file. You can use the destconfig command in the CLI to configure Destination Control entries. This command is discussed in the Cisco IronPort AsyncOS CLI Reference Guide. Cisco IronPort Bounce Verification A “bounce” message is a new message that is sent by a receiving MTA, using the Envelope Sender of the original email as the new Envelope Recipient. This bounce is sent back to the Envelope Recipient (usually) with a blank Envelope Sender (MAIL FROM: < >) when the original message is undeliverable (typically due to a non-existent recipient address). Increasingly, spammers are attacking email infrastructure via misdirected bounce attacks. These attacks consist of a flood of bounce messages, sent by unknowing, legitimate mail servers. Basically, the process spammers use is to send email via open relays and “zombie” networks to multiple, potentially invalid addresses (Envelope Recipients) at various domains. In these messages, the Envelope Sender is forged so that the spam appears to be coming from a legitimate domain (this is known as a “Joe job”). In turn, for each incoming email with an invalid Envelope Recipient, the receiving mail servers generate a new email — a bounce message — and send it along to the Envelope Sender at the innocent domain (the one whose Envelope Sender address was forged). As a result, this target domain receives a flood of “misdirected” bounces — potentially millions of messages. This type of distributed denial of service attack can bring down email infrastructure and render it impossible for the target to send or receive legitimate email. To combat these misdirected bounce attacks, AsyncOS includes Cisco IronPort Bounce Verification. When enabled, Cisco IronPort Bounce Verification tags the Envelope Sender address for messages sent via your Cisco IronPort appliance. The Envelope Recipient for any bounce message received by the Cisco IronPort appliance is then checked for the presence of this tag. Legitimate bounces (which should contain this tag) are untagged and delivered. Bounce messages that do not contain the tag can be handled separately. Note that you can use Cisco IronPort Bounce Verification to manage incoming bounce messages based on your outgoing mail. To control how your Cisco IronPort appliance generates outgoing bounces (based on incoming mail), see Directing Bounced Email, page 2-35. Overview: Tagging and Cisco IronPort Bounce Verification When sending email with bounce verification enabled, your Cisco IronPort appliance will rewrite the Envelope Sender address in the message. For example, MAIL FROM: joe@example.com becomes MAIL FROM: prvs=joe=123ABCDEFG@example.com. The 123... string in the example is the “bounce verification tag” that gets added to the Envelope Sender as it is sent by your Cisco IronPort appliance. The tag is generated using a key defined in the Bounce Verification settings (see Cisco IronPort Bounce Verification Address Tagging Keys, page 2-54 for more information about specifying a key). If this message bounces, the Envelope Recipient address in the bounce will typically include this bounce verification tag. Cisco IronPort AsyncOS 7.6 for Email Advanced Configuration Guide 2-53
Page 1 and 2:
Cisco IronPort AsyncOS 7.6 for Emai
Page 3 and 4:
OL-25137-01 Preface xvii Before you
Page 5 and 6:
OL-25137-01 Deleting Entries from t
Page 7 and 8:
OL-25137-01 Configuring Global Sett
Page 9 and 10:
OL-25137-01 DomainKeys and DKIM Sig
Page 11 and 12:
OL-25137-01 Valid Rule 6-20 Subject
Page 13 and 14:
OL-25137-01 Viewing Non-ASCII Chara
Page 15 and 16:
OL-25137-01 Administering a Cluster
Page 17 and 18:
OL-25137-01 Preface The Cisco IronP
Page 19 and 20:
Typographic Conventions Typeface or
Page 21 and 22:
OL-25137-01 Customizing Listeners C
Page 23 and 24:
Chapter 1 Customizing Listeners OL-
Page 25 and 26:
Page 27 and 28:
Chapter 1 Customizing Listeners Con
Page 29 and 30:
Chapter 1 Customizing Listeners Loo
Page 31 and 32:
Chapter 1 Customizing Listeners Par
Page 33 and 34:
Chapter 1 Customizing Listeners Rou
Page 35 and 36:
Chapter 1 Customizing Listeners Adv
Page 37 and 38:
Chapter 1 Customizing Listeners Tim
Page 39 and 40:
Chapter 1 Customizing Listeners Inj
Page 41 and 42:
Page 43 and 44:
Page 45 and 46:
Page 47 and 48:
Chapter 1 Customizing Listeners Ena
Page 49 and 50:
Page 51 and 52:
Page 53 and 54:
Page 55 and 56:
Page 57 and 58:
Page 59 and 60: OL-25137-01 CHAPTER 2 Configuring R
Page 61 and 62: Chapter 2 Configuring Routing and D
Page 109: Chapter 2 Configuring Routing and D
Page 135 and 136: Overview OL-25137-01 LDAP Queries C
Page 137 and 138: Chapter 3 LDAP Queries Understandin
Page 139 and 140: Chapter 3 LDAP Queries OL-25137-01
Page 141 and 142: Chapter 3 LDAP Queries Configuring
Page 147 and 148: Chapter 3 LDAP Queries LDAP Query S
Page 151 and 152: Chapter 3 LDAP Queries Testing LDAP
Page 153 and 154: Chapter 3 LDAP Queries Sample Accep
Page 155 and 156: Chapter 3 LDAP Queries Sample Masqu
Page 159 and 160: Chapter 3 LDAP Queries Example: Usi
Page 161 and 162:
Chapter 3 LDAP Queries OL-25137-01
Page 163 and 164:
Chapter 3 LDAP Queries Directory Ha
Page 165 and 166:
Page 167 and 168:
Page 169 and 170:
Page 171 and 172:
Page 173 and 174:
Page 175 and 176:
Page 177 and 178:
Chapter 3 LDAP Queries Spam Quarant
Page 179 and 180:
Chapter 3 LDAP Queries Sample Activ
Page 181 and 182:
Page 183 and 184:
OL-25137-01 CHAPTER 4 Validating Re
Page 185 and 186:
Chapter 4 Validating Recipients Usi
Page 187 and 188:
Page 189 and 190:
Page 191 and 192:
Page 193 and 194:
OL-25137-01 Email Authentication CH
Page 195 and 196:
Chapter 5 Email Authentication Doma
Page 197 and 198:
Chapter 5 Email Authentication Publ
Page 199 and 200:
Chapter 5 Email Authentication OL-2
Page 201 and 202:
Page 203 and 204:
Page 205 and 206:
Page 207 and 208:
Page 209 and 210:
Page 211 and 212:
Chapter 5 Email Authentication Expo
Page 213 and 214:
Chapter 5 Email Authentication Conf
Page 215 and 216:
Chapter 5 Email Authentication Test
Page 217 and 218:
Page 219 and 220:
Page 221 and 222:
Page 223 and 224:
Chapter 5 Email Authentication Dete
Page 225 and 226:
Page 227 and 228:
Chapter 5 Email Authentication Grea
Page 229 and 230:
Overview OL-25137-01 CHAPTER 6 Usin
Page 231 and 232:
Chapter 6 Using Message Filters to
Page 233 and 234:
Page 235 and 236:
Page 237 and 238:
Page 239 and 240:
Page 241 and 242:
Page 243 and 244:
Page 245 and 246:
Page 247 and 248:
Page 249 and 250:
Page 251 and 252:
Page 253 and 254:
Page 255 and 256:
Page 257 and 258:
Page 259 and 260:
Page 261 and 262:
Page 263 and 264:
Page 265 and 266:
Page 267 and 268:
Page 269 and 270:
Page 271 and 272:
Page 273 and 274:
Page 275 and 276:
Page 277 and 278:
Page 279 and 280:
Page 281 and 282:
Page 283 and 284:
Page 285 and 286:
Page 287 and 288:
Page 289 and 290:
Page 291 and 292:
Page 293 and 294:
Page 295 and 296:
Page 297 and 298:
Page 299 and 300:
Page 301 and 302:
Page 303 and 304:
Page 305 and 306:
Page 307 and 308:
Page 309 and 310:
Page 311 and 312:
Page 313 and 314:
Page 315 and 316:
Page 317 and 318:
Page 319 and 320:
Page 321 and 322:
Page 323 and 324:
Page 325 and 326:
Page 327 and 328:
Page 329 and 330:
Page 331 and 332:
Page 333 and 334:
OL-25137-01 CHAPTER Advanced Networ
Page 335 and 336:
Chapter 7 Advanced Network Configur
Page 337 and 338:
Page 339 and 340:
Page 341 and 342:
Page 343 and 344:
Page 345 and 346:
Page 347 and 348:
Page 349 and 350:
Page 351 and 352:
Page 353 and 354:
OL-25137-01 Centralized Management
Page 355 and 356:
Chapter 8 Centralized Management Fi
Page 357 and 358:
Chapter 8 Centralized Management OL
Page 359 and 360:
Page 361 and 362:
Page 363 and 364:
Page 365 and 366:
Chapter 8 Centralized Management Le
Page 367 and 368:
Chapter 8 Centralized Management Ne
Page 369 and 370:
Page 371 and 372:
Chapter 8 Centralized Management Cl
Page 373 and 374:
Chapter 8 Centralized Management Di
Page 375 and 376:
Page 377 and 378:
Page 379 and 380:
Page 381 and 382:
Page 383 and 384:
OL-25137-01 AsyncOS Quick Reference
Page 385 and 386:
Appendix A AsyncOS Quick Reference
Page 387 and 388:
FTP Access OL-25137-01 Accessing th
Page 389 and 390:
Appendix B Accessing the Appliance
Page 391 and 392:
Appendix B Accessing the Appliance
Page 393 and 394:
Symbols /dev/null, in alias tables
Page 395 and 396:
overview 2-28 domain profile deleti
Page 397 and 398:
loose SMTP address parsing 1-9 malf
Page 399 and 400:
scanning images 6-67 scp command B-
show all

IronPort - advanced configuration guide

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?