Urgent: Need a (rewrite in .net/C#) for an existing vb6 front-end pc client-side smtp utility.

We need a dev to write the utility using .net/C# with OpenSSL & possibly compiled with Delphi, or something like, for a clean GUI. Experience coding for smtp is a must. C# may be best route (over C++) since it h&les events better & has the .net framework & OpenSSL. Our old vb6 SMTP utility is a front-end for our 15-yr email & contact mgmt software, Postmaster. We want to eventually re-write its code, but cost & client upgrade challenges make it prohibitive right now. Postmaster is hard-coded to send only via port 25. So the current light-weight utility runs in the background, listening for traffic (messages being sent) on port 25 - 'localhost', intercepts the messages, secures them & sends them on to the ISP through port 465/SSL or port 587/TLS. *We have an example of the new program nearly the way we need it to see an example. (Screenshots uploaded) The project is actually two near identical utilities, with one add. capability in build 2. (More details in Additional requirement for build 2) Simply front-end GUI: 1) Displays the live sending log. 2) Password protects the utility. (encrypted) 3) Adds the email authentication credentials: • Server add. • Port #: SSL/TLS • User/Pass (encrypted) 4) Max messages sent per time-frame (Event based, C#) Utility Considerations: • Must include all features in the new 'portable' program PMXMailer.exe. It's compiled in Delphi, C++/C# & .net was used. Delphi used for an easy clean GUI. Even SQL has been mentioned. • One addition is a counter on log file/live sending thread view screen to know when done. See screenshot 2016-04-26_1613.png. Need a counter showing # emails sent & #, if any, that failed. • Must encode RFC Compliant emails & headers. • Multipart MIME Message Bodies (The ability to send messages as both text & html.) [login to view URL] • Server auth & secure auth transport layers, decoding for non ASCII messages, CR LF line break format, etc. • Must work on 32bit & 64bit systems up to windows 10 • Include options to start with windows, exit & move to taskbar. (see screenshot) • Charset="UTF-8", Content-Transfer-Encoding: 8bit, MIME-Version: 1.0 • No X-markdowns in headers • Allow email attachments • Examples of header code for RFC Compliance. (See resources below if needed) Return-path: Delivered-To: Reply-To: Date: Tue, 26 Apr 2016 02:05:14 -0500 compliant format: [login to view URL] Message-Id: <[login to view URL](a)[login to view URL]> compliant format: [login to view URL] To: From: Subject: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="=====================VariableData==.ALT" • See the attached new [login to view URL] [login to view URL] for reference & ideas. Additional requirements for build 2: • Mail limit / throttle - limit messages sent per time-frame. Able to disconnect from the server, wait for the difference from X time, reconnect & continue till done. THE best way is save messages Postmaster pushes out, into a temp flat file then read the stream from the file. NOTE: If there is ANY way to have this feature built into ONE build, I'm all for it. The challenge is with build 1, not sending the messages to a flat file, Postmaster (through the utility) is able to detect whether the email message was in fact sent or not. This affects both the outgoing history correctness, & the message staying in the Postmaster outbox (in queue) to try to send again later. When the messages are pushed directly to a flat file for throttling, Postmaster has to assume the every message was sent. • To comply with milestone pay we must possess the complete” project files” for both utilities. Get back to me if you're able to complete this project within one week. We have a max budget on this project at $300USD Sincerely, Mark Wittkowski, Founder & Partner Online Automation & Responsive Leads, LLP *Resource links if needed.