Just sitting at working on a draft for internal mail flow design and i'm thinking about using two C170 as internal relay boxes, to seperate "bulk mail" away form the MTA hosting the usermailboxes, making sure we can deliver lots off news for oure outsite customers with no impact on the internal users mailboxes.
What i'm thinking about is putting up two C170 as an cluster, with only feature key for AV and central management since its not gonna be on the edge.
Does anyone have som benchmark on C170, how many emails will it be able to handle per hour ?
1st: The actual number of messages per minute/hour/day the C170 can process with AV enabled. I could give some estimates about this, but experiences show that they are heavily depending on the kind of message, injection frequency, and network design. If you have any numbers you think about, feel free to post them here, and I can probably already tell you if two C170s are sufficientto handle them, or if it needs further details
2nd: While processing a lot of messages is one thing, getting them delivered is something totally different. Especial if you plan to send large amounts of messages to big hosted services such as Gmail, Yahoo, Hotmail, etc., as those only allow a certain amount of messages per timeframe (hour, day), and everything else then is queued on the appliance until the recipient hosts allows further injection. So this need special attention and often fine tuning, just using agressive delivery settings only makes these problems worse.
To make a longer story short, delivery and processing speed never has been a big problem for IronPort appliances, these boxes are simply made to deliver messages quick and efficiently. Problems are usually found either if internal mailservers causing traffic peaks by pushing out large numbers of messages in too little time, or, as already mentioned, on delivery getting throttled by the remote host.
Table of ContentsIntroductionVersion HistoryPossible Future
UpdatesDocuments PurposeNAT Operation in ASA 8.3+ SectionsRule Types
Network Object NATTwice NAT / Manual NATRule Types used per SectionNAT
Types used with Twice NAT / Manual NAT and Network Obje...
Table of Contents Introduction:This document describes details on how
NAT-T works. Background: ESP encrypts all critical information,
encapsulating the entire inner TCP/UDP datagram within an ESP header.
ESP is an IP protocol in the same sense that TCP an...