G
Greg9Strat
I'm trying to figure out the best strategy for sending out an email to
roughly 2,000 contacts. I have an html file that will be the body of
the email and a SQL database containing the contact list of emails.
These emails are our newsletters that get sent out each time there is
something noteworthy (so this happens on average about 3 times each
month...).
I envision creating an email object in .NET and setting the body text
and subject as static items and then iterating through the database for
email addresses. For each email address, the application should send,
and then clear the To field for the next entry... individual emails is
chosen mostly because of SPAM filters looking for an empty TO and all
recipients are in BCC field...
My question now is whether I should do this on an ASP.NET page, or
should I make this a standalone application (like console or WinForms)?
We have an Exchange server that already is fairly consumed throughout
the day (on a dual CPU w/ 2GB RAM, so it's fairly robust), and I'm
concerned about the performance hit on the mail server that will most
likely affect internal users.
However, if I choose to go with a console application, I could thread
it to delay the sending of messages in order to reduce the impact of
flooding the server...
Any feedback would be appreciated and helpful - thanks!!
Greg
roughly 2,000 contacts. I have an html file that will be the body of
the email and a SQL database containing the contact list of emails.
These emails are our newsletters that get sent out each time there is
something noteworthy (so this happens on average about 3 times each
month...).
I envision creating an email object in .NET and setting the body text
and subject as static items and then iterating through the database for
email addresses. For each email address, the application should send,
and then clear the To field for the next entry... individual emails is
chosen mostly because of SPAM filters looking for an empty TO and all
recipients are in BCC field...
My question now is whether I should do this on an ASP.NET page, or
should I make this a standalone application (like console or WinForms)?
We have an Exchange server that already is fairly consumed throughout
the day (on a dual CPU w/ 2GB RAM, so it's fairly robust), and I'm
concerned about the performance hit on the mail server that will most
likely affect internal users.
However, if I choose to go with a console application, I could thread
it to delay the sending of messages in order to reduce the impact of
flooding the server...
Any feedback would be appreciated and helpful - thanks!!
Greg