The differences are described in the AsyncOS User Guide, in their own chapter just for the C300D. It's chapter 18 in the v5.1 User Guide.
Briefly, the most significant is IronPort Mail Merge. It's an extension to SMTP that allows the mail-merge for an outgoing message to be done on the appliance. Rather than generating and sending potentially thousands of individualized messages on your own servers, you send one copy to the appliance along with the merge data. The appliance then does all the grunt work of generating and delivering the individualized copies of the message.
Does anyone have some whitepaper or so how to implement the D series into your infrastructure? We have C600's for our Day2Day mailflow, since there are several departments sending out daily mailings to large groups of recipients we consider implementing a separate mass mailing solution for that. I have a few questions on how to do such thing:
1) is the 300D only a gateway product or is it also capable of maintaining the recipient lists, including (un)subscribe functions?
2) what is a smart way to configure such gateway, use several IP's for sending mass-mail, of keeping the number of IP's limited. What should be the arguments for (or against) one or the other?
3) If the 300D is "only" a gateway, what systems can I use for recipient-list management including unsubscribe functionality
4) tools are available to give non-technical users the possibility to create nice looking HTML mail?
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...