RE: [WebDNA] Sending 100 mails an hour then pausing

This WebDNA talk-list message is from

2010


It keeps the original formatting.
numero = 105994
interpreted = N
texte = This is a multipart message in MIME format. ------=_NextPart_000_18B2_01CB87E5.C7A37530 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit I actually wrote a WebDNA snippet that batch sent 100 emails an hour awhile back. Many mail servers will limit outbound to 100 per hour. However, if you don't do something like Ken suggest to mark which ones got sent, if the process fails, a server crashes, etc. it is a pain to set up again. I've had to try and figure out where crashed scripts left off L The most important thing for me though is to make sure the emails get delivered and that I can track open/click through rates. That is why I use services like VerticalResponse.com. Plus they are Can SPAM compliant. If you need to customize emails, you write your custom table out via WebDNA and then import into VerticalResponse (or one of the many others like this). Then you can insert custom fields into each template email and know that they will get delivered. VerticalResponse I think supports up to 100 custom fields so highly customized emails are not a problem. Hope this helps. From: Govinda [mailto:govinda.webdnatalk@gmail.com] Sent: Friday, November 19, 2010 11:39 AM To: talk@webdna.us Subject: Re: [WebDNA] Sending 100 mails an hour then pausing I also used to use a script just like you guys are discussing here. I posted it to the list in the late 90's, if you want (old archives). But Olin's kind of advice comes up alot these days (on various lists) because the tendency to end up blacklisted is so much higher these days than back then. Even when you thought you followed the rules, then later you find out someone blacklisted you based on such-and-such criteria. And it is of course understandable how that happens... everyone is sick of spam... so anti-spam efforts proliferate, despite how obtuse they can be at times. I am still always at least tempted to write my own, but on this topic... I have a hard time ignoring the dangers. -Govinda I never used the services Olin suggests but he's pretty smart so I'm sure they are worth considering. If you still want to do it the WebDNA way your proposal should work. I always fired them off one at a time but if your 100-per-batch code is working you may as well re-use it. Sincerely, Kenneth Grome > I would recommend you use constant contact or vertical > response. Likely you'll get higher delivery rates and > you get lots of tracking to see which emails people > click and view. ------=_NextPart_000_18B2_01CB87E5.C7A37530 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

I actually wrote a WebDNA snippet that batch sent 100 emails an hour = awhile back. Many mail servers will limit outbound to 100 per hour. = However, if you don’t do something like Ken suggest to mark which = ones got sent, if the process fails, a server crashes, etc. it is a pain = to set up again. I’ve had to try and figure out where crashed = scripts left off L

 

The most important thing for me though is to make sure the emails get = delivered and that I can track open/click through rates. That is why I = use services like VerticalResponse.com. Plus they are Can SPAM = compliant. If you need to customize emails, you write your custom table = out via WebDNA and then import into VerticalResponse (or one of the many = others like this). Then you can insert custom fields into each template = email and know that they will get delivered. VerticalResponse I think = supports up to 100 custom fields so highly customized emails are not a = problem.

 

Hope this helps.

 

From:= = Govinda [mailto:govinda.webdnatalk@gmail.com]
Sent: Friday, = November 19, 2010 11:39 AM
To: = talk@webdna.us
Subject: Re: [WebDNA] Sending 100 mails an hour = then pausing

 

I also used = to use a script just like you guys are discussing = here.

I posted it to the list in = the late 90's, if you want (old archives).

But Olin's kind of advice comes up alot these days (on = various lists) because the tendency to end up blacklisted is so much = higher these days than back then.

Even when you thought you followed the rules, then = later you find out someone blacklisted you based on such-and-such = criteria.  And it is of course understandable how that happens... =  everyone is sick of spam... so anti-spam efforts proliferate, = despite how obtuse they can be at times.

I am still always at least tempted to write my own, = but on this topic... I have a hard time ignoring the = dangers.

 

-Govinda



I never used the services Olin suggests but = he's pretty smart so I'm sure they are worth = considering.

If you still want = to do it the WebDNA way your proposal should work. I always fired them = off one at a time but if your 100-per-batch code is working you may as = well re-use it.

Sincerely,

Kenneth = Grome

> I would = recommend you use constant contact or = vertical

> response. = Likely you’ll get higher delivery rates = and

> you get lots = of tracking to see which emails = people

> click and = view.

 

------=_NextPart_000_18B2_01CB87E5.C7A37530-- Associated Messages, from the most recent to the oldest:

    
  1. Re: [WebDNA] Sending 100 mails an hour then pausing (Govinda 2010)
  2. Re: [WebDNA] Sending 100 mails an hour then pausing (Kenneth Grome 2010)
  3. RE: [WebDNA] Sending 100 mails an hour then pausing ("Olin Lagon" 2010)
  4. Re: [WebDNA] Sending 100 mails an hour then pausing (Govinda 2010)
  5. Re: [WebDNA] Sending 100 mails an hour then pausing (Kenneth Grome 2010)
  6. RE: [WebDNA] Sending 100 mails an hour then pausing ("Olin Lagon" 2010)
  7. RE: [WebDNA] Sending 100 mails an hour then pausing ("Will Starck" 2010)
  8. RE: [WebDNA] Sending 100 mails an hour then pausing ("Will Starck" 2010)
  9. Re: [WebDNA] Sending 100 mails an hour then pausing (Kenneth Grome 2010)
This is a multipart message in MIME format. ------=_NextPart_000_18B2_01CB87E5.C7A37530 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit I actually wrote a WebDNA snippet that batch sent 100 emails an hour awhile back. Many mail servers will limit outbound to 100 per hour. However, if you don't do something like Ken suggest to mark which ones got sent, if the process fails, a server crashes, etc. it is a pain to set up again. I've had to try and figure out where crashed scripts left off L The most important thing for me though is to make sure the emails get delivered and that I can track open/click through rates. That is why I use services like VerticalResponse.com. Plus they are Can SPAM compliant. If you need to customize emails, you write your custom table out via WebDNA and then import into VerticalResponse (or one of the many others like this). Then you can insert custom fields into each template email and know that they will get delivered. VerticalResponse I think supports up to 100 custom fields so highly customized emails are not a problem. Hope this helps. From: Govinda [mailto:govinda.webdnatalk@gmail.com] Sent: Friday, November 19, 2010 11:39 AM To: talk@webdna.us Subject: Re: [WebDNA] Sending 100 mails an hour then pausing I also used to use a script just like you guys are discussing here. I posted it to the list in the late 90's, if you want (old archives). But Olin's kind of advice comes up alot these days (on various lists) because the tendency to end up blacklisted is so much higher these days than back then. Even when you thought you followed the rules, then later you find out someone blacklisted you based on such-and-such criteria. And it is of course understandable how that happens... everyone is sick of spam... so anti-spam efforts proliferate, despite how obtuse they can be at times. I am still always at least tempted to write my own, but on this topic... I have a hard time ignoring the dangers. -Govinda I never used the services Olin suggests but he's pretty smart so I'm sure they are worth considering. If you still want to do it the WebDNA way your proposal should work. I always fired them off one at a time but if your 100-per-batch code is working you may as well re-use it. Sincerely, Kenneth Grome > I would recommend you use constant contact or vertical > response. Likely you'll get higher delivery rates and > you get lots of tracking to see which emails people > click and view. ------=_NextPart_000_18B2_01CB87E5.C7A37530 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

I actually wrote a WebDNA snippet that batch sent 100 emails an hour = awhile back. Many mail servers will limit outbound to 100 per hour. = However, if you don’t do something like Ken suggest to mark which = ones got sent, if the process fails, a server crashes, etc. it is a pain = to set up again. I’ve had to try and figure out where crashed = scripts left off L

 

The most important thing for me though is to make sure the emails get = delivered and that I can track open/click through rates. That is why I = use services like VerticalResponse.com. Plus they are Can SPAM = compliant. If you need to customize emails, you write your custom table = out via WebDNA and then import into VerticalResponse (or one of the many = others like this). Then you can insert custom fields into each template = email and know that they will get delivered. VerticalResponse I think = supports up to 100 custom fields so highly customized emails are not a = problem.

 

Hope this helps.

 

From:= = Govinda [mailto:govinda.webdnatalk@gmail.com]
Sent: Friday, = November 19, 2010 11:39 AM
To: = talk@webdna.us
Subject: Re: [WebDNA] Sending 100 mails an hour = then pausing

 

I also used = to use a script just like you guys are discussing = here.

I posted it to the list in = the late 90's, if you want (old archives).

But Olin's kind of advice comes up alot these days (on = various lists) because the tendency to end up blacklisted is so much = higher these days than back then.

Even when you thought you followed the rules, then = later you find out someone blacklisted you based on such-and-such = criteria.  And it is of course understandable how that happens... =  everyone is sick of spam... so anti-spam efforts proliferate, = despite how obtuse they can be at times.

I am still always at least tempted to write my own, = but on this topic... I have a hard time ignoring the = dangers.

 

-Govinda



I never used the services Olin suggests but = he's pretty smart so I'm sure they are worth = considering.

If you still want = to do it the WebDNA way your proposal should work. I always fired them = off one at a time but if your 100-per-batch code is working you may as = well re-use it.

Sincerely,

Kenneth = Grome

> I would = recommend you use constant contact or = vertical

> response. = Likely you’ll get higher delivery rates = and

> you get lots = of tracking to see which emails = people

> click and = view.

 

------=_NextPart_000_18B2_01CB87E5.C7A37530-- "Olin Lagon"

DOWNLOAD WEBDNA NOW!

Top Articles:

Talk List

The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...

Related Readings:

Question re: FlushDatabases (1997) Forms Search Questions (1997) PIXO (1997) Nested vs conditional (1997) Server slowing down. (1997) Searching multiple Databases (1997) RAM variables (1997) WC2b15 File Corruption (1997) RE: Can't get appendfile to work (1997) Ad Serving Software (2002) GoLive CyberStudio 1.0.1 (1997) First postarg not taking in $Commands (1997) OSX Continued (2000) Hiding HTML and page breaks (1997) Execute Applescript (1997) [LOOKUP] (1997) WebCatalog Programmer looking for a new job (2001) Location of Browser Info.txt file (1997) Mime-Version in email header (1997) Hey .. so when are you guys (2004)