February 3, 2014 at 11:56 am
Hello,
I have a problem with my client, who want to passe from Lotus Notes App to SQL Server/.NET App and want to use Database Mail for sending massive number of mails (over 5000 mails, in one shot, in asynchronous processing). I don't have a dedicated production server for this specific application and I don't want performance problems. Just help me with some infos for Database Mail limitations (or SMTP limitations) and performance impact. I need proofs that this is not a good ideea, use SQL Server for sending thousand of mails. Or this is ?
Thanks all !
Paula
February 3, 2014 at 12:15 pm
i baby sit a non profit that has a 6000 member email list, and we used send out various notifications just like you plan; the whole one at a time, personalized emails. worked beautifully, and my throughput would see the whole queue of 6K+ emails go out in a two or three hours hours or so.
the number one problem has been that our domain got flagged/recognized by comcast, gmail, yahoo and aol as a spammer, so after a certain point, our users never get their emails, which would get bounced back with errors from their servers, refusing to accept the emails.
the number two problem is our email provider limits us to 400 mails per day, without upgrading to a special smtp mail account that allowed various tiers of more emails per day; 2K, 10K,etc or more, all for more and more money. as your bandwidth gets higher. That special account did not solve the spamming-list issue, so it was not worth any upgrades.
we switched over to using constant contact instead, just because of that specific spamming issue.
apparently, massive email batches is an art form i never bothered to master.
Lowell
February 4, 2014 at 7:17 am
Thanks for infos, Lowell, but 2h-3h for 6000 emails is far too long for my server and my others app.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply