You have to have your own task queue, separate from the one used by the normal thread pool.Instead, I would post the request to a message queue, and have a seperate service process items from the queue and send emails.Ĭreating background threads in the asp.net app is another possibility, but then you end up in a situation where either: If you have many such requests it could drag down server performance. The user that submitted the request will be waiting for the server to respond until the emails send, and that's one less thread available for processing requests from other users. You probably don't want to send 2000 emails on a thread that is servicing http requests. Lastly, if you're sending the same message to many recipients, you can either use a distribution list or append many target recipients to the same message. Other than that, I don't see a need to run concurrent threads for the email generation task. You may want to use threading if your sending an email from an ASP.NET webpage.
MASSIVE MAIL GROWTH HOW TO
More questions on how to set up the MTA can be answered serverfault.
Just have a MTA that allows you to relay and it will "smart host" on your behalf out to the internet. Not much is needed for a mail infrastructure. Just use to hand the delivery task to the mail infrastructure. Reason 3: The preferred way to do this is to have a dedicated IIS SMTP server (or Exchange.) that allows concurrent connections at high volume. This is a per MTA setting that will need to be adjusted to permit your situation. If you're dealing with Exchange 2010, or 2007, then there is a throttling feature that gets activated if you send more than x messages per minute. Most Windows SMTP relays have a default block of more than 15 (or 25?) concurrent connections. Reason 2: If you do use threading, you will overwhelm the target SMTP server and it will block you. Your code may not be robust enough to handle this.
Reason 1: A MTA is made to handle message retries and can handle failures. NET 4 to avoid any connection issues, as there was a bug filed on the Connect website that will cause your messages to not get sent. Use to send the messages however you should use.
0 kommentar(er)
