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-385975057Content-Transfer-Encoding: quoted-printableContent-Type: text/plain;charset=us-asciiThanks TomYes 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-385975057Content-Transfer-Encoding: quoted-printableContent-Type: text/html;charset=us-asciiThanks 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.
---------------------------------------------------------This message is sent to you because you are subscribed tothe mailing list .To unsubscribe, E-mail to: archives: http://mail.webdna.us/l=ist/talk@webdna.usBug Reporting: support@webdna.us
- =Govinda
Old WebDNA =talklist archives:
=div>
<=/span>
=--Apple-Mail-1-385975057--
Associated Messages, from the most recent to the oldest:
--Apple-Mail-1-385975057Content-Transfer-Encoding: quoted-printableContent-Type: text/plain;charset=us-asciiThanks TomYes 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-385975057Content-Transfer-Encoding: quoted-printableContent-Type: text/html;charset=us-asciiThanks 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?