469,609 Members | 1,640 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 469,609 developers. It's quick & easy.

Bulk email using ASP

I need to send out about 800 emails from addresses stored
in an Access Database, can this be achieved using ASP and
maybe an emailing component? Any other resources?

Thanks
Jul 19 '05 #1
7 7238
On Fri, 19 Dec 2003 10:37:31 -0800, "James Thompson"
<an*******@discussions.microsoft.com> wrote:
I need to send out about 800 emails from addresses stored
in an Access Database, can this be achieved using ASP and
maybe an emailing component?
Sure. Though it's not the ideal method.
Any other resources?


There are a bazillion bulk mailing programs out there, Google and take
your pick.

Jeff
Jul 19 '05 #2
For the hell of, I just ran a quick test on CDO vs. FSO for generating
e-mails, and this is what I got. I ran it a number of times, and the
difference between the two numbers was fairly consistent.

Sending 10,000 e-mails per object

CDO: 33.50781 seconds
FSO: 7.914063 seconds

Ray at home
"James Thompson" <an*******@discussions.microsoft.com> wrote in message
news:01****************************@phx.gbl...
I need to send out about 800 emails from addresses stored
in an Access Database, can this be achieved using ASP and
maybe an emailing component? Any other resources?

Thanks

Jul 19 '05 #3
a subject close to my heart at the moment - I have to send alert emails from
an application I develop for my company and have found CDO a bit
"sluggish" - care to post your FSO solution?

best regards

H

For the hell of, I just ran a quick test on CDO vs. FSO for generating
e-mails, and this is what I got. I ran it a number of times, and the
difference between the two numbers was fairly consistent.

Sending 10,000 e-mails per object

CDO: 33.50781 seconds
FSO: 7.914063 seconds

Ray at home

Jul 19 '05 #4
I read recently that it's better to create emails outside the SMTP Pickup
folder and then move them in, otherwise the SMTP service will attempt to
read the file immediately - if it's locked by the creating application this
might slow SMTP.
http://www.microsoft.com/technet/pro...nfeat/mail.asp

question - do we know if CDO writes direct to Pickup folder

also came across reference to trade-off between performance and delivery
guarantee
http://msdn.microsoft.com/library/en..._directory.asp

question - have you changed from the default (use buffering) to guarantee
delivery

regards
paul

"UncleWobbly" <he***@talk21.com> wrote in message
news:3f**********************@lovejoy.zen.co.uk...
a subject close to my heart at the moment - I have to send alert emails from an application I develop for my company and have found CDO a bit
"sluggish" - care to post your FSO solution?

best regard

H

For the hell of, I just ran a quick test on CDO vs. FSO for generating
e-mails, and this is what I got. I ran it a number of times, and the
difference between the two numbers was fairly consistent.

Sending 10,000 e-mails per object

CDO: 33.50781 seconds
FSO: 7.914063 seconds

Ray at home


Jul 19 '05 #5
ah, OK, the FSO hasn't got any magic here - thanks for this.
"Paul" <pa**@nospam.com> wrote in message
news:ex**************@TK2MSFTNGP09.phx.gbl...
I read recently that it's better to create emails outside the SMTP Pickup
folder and then move them in, otherwise the SMTP service will attempt to
read the file immediately - if it's locked by the creating application this might slow SMTP.
http://www.microsoft.com/technet/pro...nfeat/mail.asp
question - do we know if CDO writes direct to Pickup folder

also came across reference to trade-off between performance and delivery
guarantee
http://msdn.microsoft.com/library/en..._directory.asp
question - have you changed from the default (use buffering) to guarantee
delivery

regards
paul

"UncleWobbly" <he***@talk21.com> wrote in message
news:3f**********************@lovejoy.zen.co.uk...
a subject close to my heart at the moment - I have to send alert emails

from
an application I develop for my company and have found CDO a bit
"sluggish" - care to post your FSO solution?

best regard

H

For the hell of, I just ran a quick test on CDO vs. FSO for generating
e-mails, and this is what I got. I ran it a number of times, and the
difference between the two numbers was fairly consistent.

Sending 10,000 e-mails per object

CDO: 33.50781 seconds
FSO: 7.914063 seconds

Ray at home



Jul 19 '05 #6
This is the basicest of a ".eml" file, but like so: (I stopped the smtp
service while doing this 10,000 times...)

Sub GenerateByFSO(NumberOfMessages)
Dim i
Dim oFSO, oFile

Set oFSO = Server.CreateObject("Scripting.FileSystemObject")
For i = 1 To NumberOfMessages
Set oFile = oFSO.CreateTextFile("C:\Inetpub\mailroot\pickup\ms g" & CStr(i)
& ".eml")
oFile.WriteLine "X-Receiver: me@mydomain.com"
oFile.WriteLine "X-Sender: me@mydomain.com"
oFile.WriteLine "To: <me@mydomain.com>"
oFile.WriteLine "Subject: Test FSO"
oFile.WriteLine vbCrLf
oFile.WriteLine "Test e-mail FSO"
oFile.Close
Set oFile = Nothing
Next
End Sub

It would have been a bit speedier (I'd imagine) to generate on string with
vbCrLfs and then doing only one .write on the file.

Ray at home

"UncleWobbly" <he***@talk21.com> wrote in message
news:3f**********************@lovejoy.zen.co.uk...
a subject close to my heart at the moment - I have to send alert emails from an application I develop for my company and have found CDO a bit
"sluggish" - care to post your FSO solution?

best regards

H

For the hell of, I just ran a quick test on CDO vs. FSO for generating
e-mails, and this is what I got. I ran it a number of times, and the
difference between the two numbers was fairly consistent.

Sending 10,000 e-mails per object

CDO: 33.50781 seconds
FSO: 7.914063 seconds

Ray at home


Jul 19 '05 #7
Yeash, thanks for this Ray. When you said you'd done it with FSO I thought
you had some method for FSO I had not encountered for dealing with mail but
I understand now - not enough vision on my part in reading your original
post here... Thanks anyway.
"Ray at <%=sLocation%>" <myFirstNameATlane34dotKOMM> wrote in message
news:ek*************@tk2msftngp13.phx.gbl...
This is the basicest of a ".eml" file, but like so: (I stopped the smtp
service while doing this 10,000 times...)

Sub GenerateByFSO(NumberOfMessages)
Dim i
Dim oFSO, oFile

Set oFSO = Server.CreateObject("Scripting.FileSystemObject")
For i = 1 To NumberOfMessages
Set oFile = oFSO.CreateTextFile("C:\Inetpub\mailroot\pickup\ms g" & CStr(i) & ".eml")
oFile.WriteLine "X-Receiver: me@mydomain.com"
oFile.WriteLine "X-Sender: me@mydomain.com"
oFile.WriteLine "To: <me@mydomain.com>"
oFile.WriteLine "Subject: Test FSO"
oFile.WriteLine vbCrLf
oFile.WriteLine "Test e-mail FSO"
oFile.Close
Set oFile = Nothing
Next
End Sub

It would have been a bit speedier (I'd imagine) to generate on string with
vbCrLfs and then doing only one .write on the file.

Ray at home

"UncleWobbly" <he***@talk21.com> wrote in message
news:3f**********************@lovejoy.zen.co.uk...
a subject close to my heart at the moment - I have to send alert emails

from
an application I develop for my company and have found CDO a bit
"sluggish" - care to post your FSO solution?

best regards

H

For the hell of, I just ran a quick test on CDO vs. FSO for generating
e-mails, and this is what I got. I ran it a number of times, and the
difference between the two numbers was fairly consistent.

Sending 10,000 e-mails per object

CDO: 33.50781 seconds
FSO: 7.914063 seconds

Ray at home



Jul 19 '05 #8

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

2 posts views Thread by Chris | last post: by
2 posts views Thread by David Sharp | last post: by
3 posts views Thread by Jim Geissman | last post: by
20 posts views Thread by akej via SQLMonster.com | last post: by
6 posts views Thread by pk | last post: by
16 posts views Thread by Philip Boonzaaier | last post: by
1 post views Thread by Jennifer | last post: by
reply views Thread by devrayhaan | last post: by
reply views Thread by gheharukoh7 | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.