There is no efficiency in bulk data, you have to be patient in this scenario.
Now let me give you an answer. If you can (somehow) manage to get 200 threads on your CPU and allow each of this thread to send an email to your client. You still won't be able to, until you are having an SMTP server and the network strong enough to,
- Send the data to SMTP server.
- Process the request and send the email.
- Return the response; most probably "Ok".
... All in
just one second. Only then you can expect your
Bulk email sending program to send 200 emails in one second.
If you cannot perform this... Then the only thing left is
patience. I did answer similar questions before, and I gave the same solution. Emails (and all other type of network related resources and data) do not only depend on your threads, CPU, code efficiency. They depend on the network speed and the SMTP server response. If you get able to create the (above mentioned) program but your SMTP is not fast and strong enough, you will still not get to the desired results. Sending bulk emails really requires a lot of patience (on both sides; client and sender).
Personal experience...
200 emails/seconds is not accessible; also you should never pay a fortune cookie for spam Whoops,
bulk emails. I remember day before yesterday I was teaching my brother how to write applications in C# and the topic was
Sending emails. We created a Windows Forms application and when we sent (only one) email; we were using Dual Core CPU, 4 MB internet connection, the response sent by the SMTP server (Gmail) was received after
4 seconds.