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

This WebDNA talk-list message is from

2011


It keeps the original formatting.
numero = 106535
interpreted = N
texte = --Apple-Mail-1-385975057 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Thanks Tom Yes now I vaguely remember you describing before how you came to the = point of having to do it that way in order to have access to one of the = webdna-uneditable email headers (the return-path) (if I said that = right). Since I do not run any production mail servers.. I am not really = familiar with that end of things.. can you describe a little more about = how you handle the emails that bounce? Here I am assuming: that they = come in to a special folder (by virtue of the custom return path = header).. and then you do what exactly? ...Hack out the TO address and = extract that from the master list of addresses to send to the next time = you run your script? Do you do that with another webdna script? Has = anyone posted such code in the past? > Govinda, >=20 > We use [writefile] to write the raw emails to a folder. Then we use = [listfiles] to go though these and use a [shell] command to send the = emails - the server is running on CentOS. >=20 > We find that the emails are processed much quicker, and it allows us = to write a custom 'return-path' header which is then used for auto = bounce management. =20 >=20 > - Tom >=20 >=20 > --------------------------------------------------------- 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=3Dwebdna-talk --Apple-Mail-1-385975057 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii Thanks Tom

Yes now I vaguely remember you = describing before how you came to the point of having to do it that way = in order to have access to one of the webdna-uneditable email = headers (the return-path)  (if I said that = right).

Since I do not run any production mail = servers.. I am not really familiar with that end of things.. can you = describe a little more about how you handle the emails that bounce? =  Here I am assuming: that they come in to a special folder (by = virtue of the custom return path header).. and then you do what exactly? =  ...Hack out the TO address and extract that from the master list = of addresses to send to the next time you run your script?  Do you = do that with another webdna script?  Has anyone posted such code in = the past?

Govinda,

We use [writefile] to write = the raw emails to a folder.   Then we use [listfiles] to go though = these and use a [shell] command to send the emails - the server is = running on CentOS.

We find that the emails are processed much quicker, and it = allows us to write a custom 'return-path' header which is then used for = auto bounce management.   

- = Tom


--------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: archives: http://mail.webdna.us/l= ist/talk@webdna.us Bug Reporting: support@webdna.us

- = Govinda
--------------
Old WebDNA = talklist archives:
<= /span>

= --Apple-Mail-1-385975057-- 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)
--Apple-Mail-1-385975057 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Thanks Tom Yes now I vaguely remember you describing before how you came to the = point of having to do it that way in order to have access to one of the = webdna-uneditable email headers (the return-path) (if I said that = right). Since I do not run any production mail servers.. I am not really = familiar with that end of things.. can you describe a little more about = how you handle the emails that bounce? Here I am assuming: that they = come in to a special folder (by virtue of the custom return path = header).. and then you do what exactly? ...Hack out the TO address and = extract that from the master list of addresses to send to the next time = you run your script? Do you do that with another webdna script? Has = anyone posted such code in the past? > Govinda, >=20 > We use [writefile] to write the raw emails to a folder. Then we use = [listfiles] to go though these and use a [shell] command to send the = emails - the server is running on CentOS. >=20 > We find that the emails are processed much quicker, and it allows us = to write a custom 'return-path' header which is then used for auto = bounce management. =20 >=20 > - Tom >=20 >=20 > --------------------------------------------------------- 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=3Dwebdna-talk --Apple-Mail-1-385975057 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii Thanks Tom

Yes now I vaguely remember you = describing before how you came to the point of having to do it that way = in order to have access to one of the webdna-uneditable email = headers (the return-path)  (if I said that = right).

Since I do not run any production mail = servers.. I am not really familiar with that end of things.. can you = describe a little more about how you handle the emails that bounce? =  Here I am assuming: that they come in to a special folder (by = virtue of the custom return path header).. and then you do what exactly? =  ...Hack out the TO address and extract that from the master list = of addresses to send to the next time you run your script?  Do you = do that with another webdna script?  Has anyone posted such code in = the past?

Govinda,

We use [writefile] to write = the raw emails to a folder.   Then we use [listfiles] to go though = these and use a [shell] command to send the emails - the server is = running on CentOS.

We find that the emails are processed much quicker, and it = allows us to write a custom 'return-path' header which is then used for = auto bounce management.   

- = Tom


--------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: archives: http://mail.webdna.us/l= ist/talk@webdna.us Bug Reporting: support@webdna.us

- = Govinda
--------------
Old WebDNA = talklist archives:
<= /span>

= --Apple-Mail-1-385975057-- Govinda

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:

SiteGuard Use Question (1997) WCS Newbie question (1997) Include a big block of text (1997) Inventory Debit Procedure (1998) Show shoppingcart after remove last item (1997) page redirect in webDNA (1997) WebCat2 beta FTP site (1997) international time (1997) Nesting format tags (1997) Latin Characters (1998) Graphing Modules (2004) Pithy questions on webcommerce & siteedit (1997) Shopping cart not being assigned (1999) Spiders and Bots (2000) bugs w/! &/or bad scripting??? (1997) Summing fields (1997) Webcatalog error, Plug-in for Webstar (1996) Searching Dates (2000) Multiple matches in a search (2004) [shownext] and sort (1998)