Re: [WebDNA] current thinking on architecture of mass email scripts?

This WebDNA talk-list message is from

2011


It keeps the original formatting.
numero = 106538
interpreted = N
texte = This is a multi-part message in MIME format.--------------030900000701040601010408Content-Type: text/plain; charset=ISO-8859-1; format=flowedContent-Transfer-Encoding: 7bitGovinda,I have an email account setup titled "subscriber" which is used as the FROM within the [sendmail]. I my case when we send the email newsletter, the client "subscriber" currently receives 866 emails (which are immediately deleted) after sending the entire list. 26,000/30 = 866 emails addressed to "subscriber" with (30) customer email addresses BCC'd. I chose to have someone manually review each email received by the client "subscriber" as some people are using a mail filter that when they receive an email, their mail filter sends out an email requiring a response from the sender to permit the original email to be delivered to the recipient plus some "out of office" replies come back which are not actual bounce backs. We do receive a few hundred actual undeliverable bounce backs of which we manually remove from the master list. This sounds like a lot but we are sending out 26,000 emails and doesn't take a human very long to remove the undeliverable addresses from the master list.The majority of our master list is handled by the customers themselves via our website in real time.Best Regards,SteveGovinda wrote:> Steve,> Thanks for taking the time to describe to me.>> I appreciate hearing how everyone is handling real world live cases.>> At this point I am mostly information gathering. It will be up to the client to make any final decisions about changing things, or not. I'll save this your post and let you know if I end up wanting to reproduce something similar to your setup. Glad it is working!>> Do you take any steps to handle bounces (and/or keep your master list current)?>> -Govinda>>> >> Hi Govinda,>>>> I have an email subscriber list of nearly 26,000 email addresses that we send a monthly email newsletter to each month. Several on this list warning me that my server would get black listed if a receiving email server saw emails coming in with many BCC's indicated. >>>> I have been using BCC within [sendmail] and Postfix on a Linux server for nearly a year and for several years prior I was using this method on a Windows server. There is NO info in the header of the emails we are sending that indicates the use of BCC for the receiving server to see. Each BCC email header only indicates a single "to" email address of the individual subscriber. Our server has not once been blacklisted.>>>> I do not throttle the outgoing email. I do receive bounce back messages from Gmail, Yahoo and maybe a few others that state your email server IS NOT being blacklisted however do to the high volume of emails coming from our server that email from our server is temporarily being blocked and to resend at a later time. Postfix then is configured to retry these emails every hour until all are sent.>>>> I have an actual email account titled "subscriber" and then am currently BCC'ing 30 actual customer email addresses. I copy the actual email address database to a temporary send email list database of which I assign each email address a group number. In this instance of sending 30 customer email address at a time, webDNA is sending a total of 866 emails. This takes our server @ 3.09 minutes to send all 26,000 emails. The only thing I am doing that may throttle down the speed of the sends is that as each group of addresses are sent from the temporary send database the addresses are appended to a "sent" database and deleted from the temporary "send" database.>>>> Despite popular opinion, this works for me and our server has never been blacklisted.>>>> If you are interested in seeing my code I would be happy to share it with you.>>>> Best Regards,>> Steve>>>> Govinda wrote:>> >>> Hi All>>>>>> One clients has some scripts we wrote for a trigger to send email to users.. and sometimes the number of emails that need to go out at once is in range of several hundred .>>>>>> In the old days we used to hand-throttle the rate at which those email files were written to disk. >>>>>> Just now it came to my attention that webdna has a built-in throttler. I.e. "send X emails per minute"... >>> Does anyone know where that number/pref. lives and can be changed?>>>>>> And to further the discussion a bit, how are you guys (who need to fire alot of [sendmail]s at once) handling it?>>> Or are you happy to just leave a [sendmail] inside a loop that loops 1,000 times?>>>>>> Thanks>>> -Govinda>>>>>> >>>>>> >> --------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: archives: http://mail.webdna.us/list/talk@webdna.us Bug Reporting: support@webdna.us>> >> - Govinda> --------------> Old WebDNA talklist archives:> http://dev.webdna.us/TalkListArchive/index.tpl?db=webdna-talk>> ---------------------------------------------------------> This message is sent to you because you are subscribed to> the mailing list .> To unsubscribe, E-mail to: > archives: http://mail.webdna.us/list/talk@webdna.us> Bug Reporting: support@webdna.us> --------------030900000701040601010408Content-Type: text/html; charset=ISO-8859-1Content-Transfer-Encoding: 7bit Govinda,

I have an email account setup titled "subscriber" which is used as theFROM within the [sendmail]. I my case when we send the emailnewsletter, the client "subscriber" currently receives 866 emails(which are immediately deleted) after sending the entire list.26,000/30 = 866 emails addressed to "subscriber" with (30) customeremail addresses BCC'd. I chose to have someone manually review eachemail received by the client "subscriber" as some people are using amail filter that when they receive an email, their mail filter sendsout an email requiring a response from the sender to permit theoriginal email to be delivered to the recipient plus some "out ofoffice" replies come back which are not actual bounce backs. We doreceive a few hundred actual undeliverable bounce backs of which wemanually remove from the master list. This sounds like a lot but we aresending out 26,000 emails and doesn't take a human very long to removethe undeliverable addresses from the master list.

The majority of our master list is handled by the customers themselvesvia our website in real time.

Best Regards,
Steve






Govinda wrote:
Steve,Thanks for taking the time to describe to me.I appreciate hearing how everyone is handling real world live cases.At this point I am mostly information gathering.  It will be up to the client to make any final decisions about changing things, or not.   I'll save this your post and let you know if I end up wanting to reproduce something similar to your setup.  Glad it is working!Do you take any steps to handle bounces (and/or keep your master list current)?-Govinda  
Hi Govinda,I have an email subscriber list of nearly 26,000 email addresses that we send a monthly email newsletter to each month. Several on this list warning me that my server would get black listed if a receiving email server saw emails coming in with many BCC's indicated. I have been using BCC within [sendmail] and Postfix on a Linux server for nearly a year and for several years prior I was using this method on a Windows server. There is NO info in the header of the emails we are sending that indicates the use of BCC for the receiving server to see. Each BCC email header only indicates a single "to" email address of the individual subscriber. Our server has not once been blacklisted.I do not throttle the outgoing email. I do receive bounce back messages from Gmail, Yahoo and maybe a few others that state your email server IS NOT being blacklisted however do to the high volume of emails coming from our server that email from our server is temporarily being blocked and to resend at a later time. Postfix then is configured to retry these emails every hour until all are sent.I have an actual email account titled "subscriber" and then am currently BCC'ing 30 actual customer email addresses. I copy the actual email address database to a temporary send email list database of which I assign each email address a group number. In this instance of sending 30 customer email address at a time, webDNA is sending a total of 866 emails. This takes our server @ 3.09 minutes to send all 26,000 emails. The only thing I am doing that may throttle down the speed of the sends is that as each group of addresses are sent from the temporary send database the addresses are appended to a "sent" database and deleted from the temporary "send" database.Despite popular opinion, this works for me and our server has never been blacklisted.If you are interested in seeing my code I would be happy to share it with you.Best Regards,SteveGovinda wrote:    
Hi AllOne clients has some scripts we wrote for a trigger to send email to users.. and sometimes the number of emails that need to go out at once is in range of several hundred .In the old days we used to hand-throttle the rate at which those email files were written to disk. Just now it came to my attention that webdna has a built-in throttler.  I.e. "send X emails per minute"...  Does anyone know where that number/pref. lives and can be changed?And to further the discussion a bit, how are you guys (who need to fire alot of [sendmail]s at once) handling it?Or are you happy to just leave a [sendmail] inside a loop that loops 1,000 times?Thanks-Govinda        
--------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: archives: http://mail.webdna.us/list/talk@webdna.us Bug Reporting: support@webdna.us    
- Govinda--------------Old WebDNA talklist archives:http://dev.webdna.us/TalkListArchive/index.tpl?db=webdna-talk---------------------------------------------------------This message is sent to you because you are subscribed tothe mailing list 





Associated Messages, from the most recent to the oldest:

    
  1. Re: [WebDNA] current thinking on architecture of mass email scripts? (Govinda 2011)
  2. Re: [WebDNA] current thinking on architecture of mass email scripts? (Tom Duke 2011)
  3. Re: [WebDNA] current thinking on architecture of mass email scripts? (Steve Raslevich - Northern Sound 2011)
  4. Re: [WebDNA] current thinking on architecture of mass email scripts? (Govinda 2011)
  5. Re: [WebDNA] current thinking on architecture of mass email scripts? (Steve Raslevich - Northern Sound 2011)
  6. Re: [WebDNA] current thinking on architecture of mass email scripts? (Govinda 2011)
  7. Re: [WebDNA] current thinking on architecture of mass email scripts? (Tom Duke 2011)
  8. [WebDNA] current thinking on architecture of mass email scripts? (Govinda 2011)
This is a multi-part message in MIME format.--------------030900000701040601010408Content-Type: text/plain; charset=ISO-8859-1; format=flowedContent-Transfer-Encoding: 7bitGovinda,I have an email account setup titled "subscriber" which is used as the FROM within the
[sendmail]. I my case when we send the email newsletter, the client "subscriber" currently receives 866 emails (which are immediately deleted) after sending the entire list. 26,000/30 = 866 emails addressed to "subscriber" with (30) customer email addresses BCC'd. I chose to have someone manually review each email received by the client "subscriber" as some people are using a mail filter that when they receive an email, their mail filter sends out an email requiring a response from the sender to permit the original email to be delivered to the recipient plus some "out of office" replies come back which are not actual bounce backs. We do receive a few hundred actual undeliverable bounce backs of which we manually remove from the master list. This sounds like a lot but we are sending out 26,000 emails and doesn't take a human very long to remove the undeliverable addresses from the master list.The majority of our master list is handled by the customers themselves via our website in real time.Best Regards,SteveGovinda wrote:> Steve,> Thanks for taking the time to describe to me.>> I appreciate hearing how everyone is handling real world live cases.>> At this point I am mostly information gathering. It will be up to the client to make any final decisions about changing things, or not. I'll save this your post and let you know if I end up wanting to reproduce something similar to your setup. Glad it is working!>> Do you take any steps to handle bounces (and/or keep your master list current)?>> -Govinda>>> >> Hi Govinda,>>>> I have an email subscriber list of nearly 26,000 email addresses that we send a monthly email newsletter to each month. Several on this list warning me that my server would get black listed if a receiving email server saw emails coming in with many BCC's indicated. >>>> I have been using BCC within [sendmail] and Postfix on a Linux server for nearly a year and for several years prior I was using this method on a Windows server. There is NO info in the header of the emails we are sending that indicates the use of BCC for the receiving server to see. Each BCC email header only indicates a single "to" email address of the individual subscriber. Our server has not once been blacklisted.>>>> I do not throttle the outgoing email. I do receive bounce back messages from Gmail, Yahoo and maybe a few others that state your email server IS NOT being blacklisted however do to the high volume of emails coming from our server that email from our server is temporarily being blocked and to resend at a later time. Postfix then is configured to retry these emails every hour until all are sent.>>>> I have an actual email account titled "subscriber" and then am currently BCC'ing 30 actual customer email addresses. I copy the actual email address database to a temporary send email list database of which I assign each email address a group number. In this instance of sending 30 customer email address at a time, webDNA is sending a total of 866 emails. This takes our server @ 3.09 minutes to send all 26,000 emails. The only thing I am doing that may throttle down the speed of the sends is that as each group of addresses are sent from the temporary send database the addresses are appended to a "sent" database and deleted from the temporary "send" database.>>>> Despite popular opinion, this works for me and our server has never been blacklisted.>>>> If you are interested in seeing my code I would be happy to share it with you.>>>> Best Regards,>> Steve>>>> Govinda wrote:>> >>> Hi All>>>>>> One clients has some scripts we wrote for a trigger to send email to users.. and sometimes the number of emails that need to go out at once is in range of several hundred .>>>>>> In the old days we used to hand-throttle the rate at which those email files were written to disk. >>>>>> Just now it came to my attention that webdna has a built-in throttler. I.e. "send X emails per minute"... >>> Does anyone know where that number/pref. lives and can be changed?>>>>>> And to further the discussion a bit, how are you guys (who need to fire alot of [sendmail]s at once) handling it?>>> Or are you happy to just leave a [sendmail] inside a loop that loops 1,000 times?>>>>>> Thanks>>> -Govinda>>>>>> >>>>>> >> --------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: archives: http://mail.webdna.us/list/talk@webdna.us Bug Reporting: support@webdna.us>> >> - Govinda> --------------> Old WebDNA talklist archives:> http://dev.webdna.us/TalkListArchive/index.tpl?db=webdna-talk>> ---------------------------------------------------------> This message is sent to you because you are subscribed to> the mailing list .> To unsubscribe, E-mail to: > archives: http://mail.webdna.us/list/talk@webdna.us> Bug Reporting: support@webdna.us> --------------030900000701040601010408Content-Type: text/html; charset=ISO-8859-1Content-Transfer-Encoding: 7bit Govinda,

I have an email account setup titled "subscriber" which is used as theFROM within the [sendmail]. I my case when we send the emailnewsletter, the client "subscriber" currently receives 866 emails(which are immediately deleted) after sending the entire list.26,000/30 = 866 emails addressed to "subscriber" with (30) customeremail addresses BCC'd. I chose to have someone manually review eachemail received by the client "subscriber" as some people are using amail filter that when they receive an email, their mail filter sendsout an email requiring a response from the sender to permit theoriginal email to be delivered to the recipient plus some "out ofoffice" replies come back which are not actual bounce backs. We doreceive a few hundred actual undeliverable bounce backs of which wemanually remove from the master list. This sounds like a lot but we aresending out 26,000 emails and doesn't take a human very long to removethe undeliverable addresses from the master list.

The majority of our master list is handled by the customers themselvesvia our website in real time.

Best Regards,
Steve






Govinda wrote:
Steve,Thanks for taking the time to describe to me.I appreciate hearing how everyone is handling real world live cases.At this point I am mostly information gathering.  It will be up to the client to make any final decisions about changing things, or not.   I'll save this your post and let you know if I end up wanting to reproduce something similar to your setup.  Glad it is working!Do you take any steps to handle bounces (and/or keep your master list current)?-Govinda  
Hi Govinda,I have an email subscriber list of nearly 26,000 email addresses that we send a monthly email newsletter to each month. Several on this list warning me that my server would get black listed if a receiving email server saw emails coming in with many BCC's indicated. I have been using BCC within [sendmail] and Postfix on a Linux server for nearly a year and for several years prior I was using this method on a Windows server. There is NO info in the header of the emails we are sending that indicates the use of BCC for the receiving server to see. Each BCC email header only indicates a single "to" email address of the individual subscriber. Our server has not once been blacklisted.I do not throttle the outgoing email. I do receive bounce back messages from Gmail, Yahoo and maybe a few others that state your email server IS NOT being blacklisted however do to the high volume of emails coming from our server that email from our server is temporarily being blocked and to resend at a later time. Postfix then is configured to retry these emails every hour until all are sent.I have an actual email account titled "subscriber" and then am currently BCC'ing 30 actual customer email addresses. I copy the actual email address database to a temporary send email list database of which I assign each email address a group number. In this instance of sending 30 customer email address at a time, webDNA is sending a total of 866 emails. This takes our server @ 3.09 minutes to send all 26,000 emails. The only thing I am doing that may throttle down the speed of the sends is that as each group of addresses are sent from the temporary send database the addresses are appended to a "sent" database and deleted from the temporary "send" database.Despite popular opinion, this works for me and our server has never been blacklisted.If you are interested in seeing my code I would be happy to share it with you.Best Regards,SteveGovinda wrote:    
Hi AllOne clients has some scripts we wrote for a trigger to send email to users.. and sometimes the number of emails that need to go out at once is in range of several hundred .In the old days we used to hand-throttle the rate at which those email files were written to disk. Just now it came to my attention that webdna has a built-in throttler.  I.e. "send X emails per minute"...  Does anyone know where that number/pref. lives and can be changed?And to further the discussion a bit, how are you guys (who need to fire alot of [sendmail]s at once) handling it?Or are you happy to just leave a [sendmail] inside a loop that loops 1,000 times?Thanks-Govinda        
--------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: archives: http://mail.webdna.us/list/talk@webdna.us Bug Reporting: support@webdna.us    
- Govinda--------------Old WebDNA talklist archives:http://dev.webdna.us/TalkListArchive/index.tpl?db=webdna-talk---------------------------------------------------------This message is sent to you because you are subscribed tothe mailing list 



Steve Raslevich - Northern Sound 

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:

japanese characters (1997) Format question WC Mac f3 (1997) Firesite and [referrer] atg broke (1997) Date Time Oddness (1999) limitation found on group searching (1997) Summing fields (1997) AOL and [referrer] (2001) Modulo function? (2000) [WebDNA] Calendar Examples (2019) Re:2nd WebCatalog2 Feature Request (1996) multi-paragraph fields (1997) Stop the madness. (1997) Editing the search string (1997) WebCat2b12--[searchstring] bug (1997) Secure Server basic question... (1997) minimalist shopping cart. (1997) Cart Question (1998) Listserver problem (1997) Re[3]: 2nd WebCatalog2 Feature Request (1996) Error handling for accountNum (1997)