Quesion is how to send email to 1000 people?
Status: Beta
Brought to you by:
mikelbridge
Menu
▾
▴
I have a newsletter every week and want to send this to customers(over 1000) every week.
Could you tell me how to handle it with DotNetOpenMail?
Thanks very much in advance!
Hi-
DotNetOpenMail assumes that you're sending these one-at-a-time to 1000 subscribers. Most servers should be able to handle 1000 separate emails without too much problem.
The only other option I know of is to add a huge number of email addresses to the To:, CC: or BCC: fields, but this is usually a Bad Idea.
Cheers,
-Mike
Thank you so much for your reply.
Another questions is how do I know if an email send is faild or not?
Thanks in advance!
Jusitn
Hi-
If there's a problem sending, it will throw either an SmtpException or a MailException. doing a "catch (Exception ex)" and examining the ex.Message should tell you what happened.
-Mike
Hi Mike
I am also doing something similar and is just that the numbers are around 5000 and the email is a html email. I have a few queries:
1. Dont you think adding a huge number of addresses to the TO, CC and/or BCC would be better?
2. Whats the limitation for the number of email addresses you can add?
3. If we send the email like No.1, what happens if some email addresses fail? How do we know?
4. If we send individually, can I get a response whether the email was sent successful or failed? And if failed why?
Hi-
Admittedly, this isn't something I've tried with DotNetOpenMail, but it *should* either fail entirely or be accepted entirely by your server. Individual failed emails that are accepted should be returned as bounces. Normally, you'll only get SMTP errors (that will cause everything to fail) if you send to badly-formed addresses or addresses which are immediately rejected by your server such as local mailboxes that don't exist, but this depends on how it's set up (if you go this route, you need to either talk to your email admin, or test out some bad addresses).
However, To-ing, CC-ing or BCC-ing is an act of hubris that would certainly get you a good God-smiting:
1) Having a lot of people in your To or Cc fields is usually something easy for spam filters check for. Even if it doesn't catch any spam, it is usually a good method of filtering out stupid jokes forwarded for the n-th time by people who have just acquired internet access for the first time.
2) You'll annoy most of the recipients, who---understandably---don't like having their email address show up in 5000 other mailboxes. Any group of 5000 people will contain a good number of morons---let's say 163. There are at least two moronic responses: Moron-Type A will spam your 5000-person list. Moron-Type B will hit Reply-All and append some obscenities to your original email, which will offend the other 4837 people on your list. I would estimate that of these, at least 538 will succumb to "temporary-moronity" and will follow suit sending obscenities to All. The rest will all email you en-masse asking to never ever ever ever to email them again and will threaten legal action which will never occur. If you're really unlucky to have some well-connected gurus on your list, your server server will get added to some RBLs, which will really impress your boss. At some point during this process, you will also suddenly be struck by the fear that some the Type-B morons are actually Type-C "Truly Unbalanced" Morons who also live across town from you.
3) If you use the BCC field, there is also the possibility that your BCC list will be visible to all 5000 recipients. This is a quirk of RFC 822, sec 4.5.3, which no one knows about until they truly embarrass themselves. This clause means that one of two things will happen: your server will (as most do) break up the email into 5000 individual emails thus removing any gains in efficiency you might have had, or it will send a huge BCC field to everyone, including the 163 morons (see #2 above).
-Mike