Re-coding of existing c# newsletter sending application

I have a quick and dirty written c# newsletter sending application which needs to be recoded in a good quality to work more robust. Existing features: Edit plaintext email content and html body via mshtml control. Each field can contain a spacer for the database field to be included to create user defined emails (Dear $userName$). Enter start and end row number. Enter validator to decide if the user gets a plaintext or html mail: userHasHTML = True Specify MSSQL and OleDB data source. Host, database, table, SQL-statement to collect data. Specify html style template file containing a variable for the content text. Sending is the most important part which makes troubles actually. The tool must work reliable and robust with large amouts of emails (> 1 mio in one sequence). So it must be able to share sending work with other SMTP servers in a server farm. User enters a list of SMTP servers which relay and define how many parallel connections to the servers can be established. Opens this number of connections and then transfer as long emails as the server accepps and don't throws a timeout. Works multithreaded to work fast. If a connection is broken the tool re-establishes the connection. Is able to save and load the configuration in an xml config file. New features: Full implementation of switch between SMTP server list and local SMTP service (win 2000 or win 2003 server). Currently only SMTP server list works correctly. Simple HTML editor features for headlines, bold, italic, images where first steps are already done. Requirements: Write the source to work very fast and reliable. Current version has ~2000 lines. Or make suggestions to completely other ways to reach the goal (send 1 mio mails in a short time with little servers). Make it multi language enabled (ini or xml language file). No use of third party components if possible. ## Deliverables 1) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done. 2) Deliverables must be in ready-to-run condition, as follows (depending on the nature of the deliverables): a) For web sites or other server-side deliverables intended to only ever exist in one place in the Buyer's environment--Deliverables must be installed by the Seller in ready-to-run condition in the Buyer's environment. b) For all others including desktop software or software the buyer intends to distribute: A software installation package that will install the software in ready-to-run condition on the platform(s) specified in this bid request. 3) All deliverables will be considered "work made for hire" under U.S. Copyright law. Buyer will receive exclusive and complete copyrights to all work purchased. (No GPL, GNU, 3rd party components, etc. unless all copyright ramifications are explained AND AGREED TO by the buyer on the site per the coder's Seller Legal Agreement). ## Platform Windows with .net Framework 1.1 and MS-IE (for mshtml control)