Re: [WebDNA] Emailer breaking format
This WebDNA talk-list message is from 2015
It keeps the original formatting.
numero = 112206
interpreted = N
texte = This isn't how I handle such multiple emails. I do it thusly: search founditems sendmail /sendmail /founditems /search Why not try that. For some reason, early on I figured it was just = cleaner to send individual emails. Or maybe it was breaking on a bad = email; I really don't remember that far back. That also gives you a = chance to grab other variables from the founditems loop, like "Hello = [firstname],". Makes no difference to the mail server. Or perhaps it = makes it easier for the mail server; I wouldn't know about that. For = sure it will take WebDNA longer to process the page. But so what. As for the comma, that's just bizarre. I use commas all the time, no = problem (but they aren't within a founditems loop). = BCC,CC,Sender,Reply-to.. use them all; never seen a problem. Even more = curious - how did you come up with the idea to even try [raw]? That's = like wondering how anyone ever came up with the idea of cooking an = artichoke bud. BTW anyone who ever had chicken pox should get the shingles vaccine. You = can guess why I'm sending this advice... Terry On Mar 24, 2015, at 10:57 AM, Kenneth Grome
= wrote: > These are good things to know. >=20 > I think they should be added to the documentation since they are > clearly unexpected behavior, at least for many of us. >=20 > Regards, > Kenneth Grome > WebDNA Solutions > http://www.webdnasolutions.com > Web Database Systems and Linux Server Management >=20 >=20 > On 03/24/2015 11:01 AM, Steve Raslevich wrote: >> I have no idea for the behavior but do know that only the first BCC=20= >> email address will be sent if the comma separating the addresses in a=20= >> [founditems] is now within [raw] >>=20 >> Another finding about sending to multiple addresses with [sendmail] = is=20 >> that if one email address is an invalid formatted address, the email = is=20 >> not sent to any of the addresses. >>=20 >> I send out an email newsletter to @ 30,000 addresses and break the=20 >> sending down to groups of 35 - 50. >>=20 >> Kenneth Grome wrote: >>>> Ken, only the comma is in the raw context. no space: >>>>=20 >>> But I still do not understand why [raw],[/raw] would modify the >>> comma (or the code around it) in any way, much less in a way that >>> would cause the sendmail to work properly with it but not without = it. >>>=20 >>> Apparently it has some kind of reaction with the founditems? Does >>> it introduce an invisible character or something? >>>=20 >>> Regards, >>> Kenneth Grome >>> WebDNA Solutions >>> http://www.webdnasolutions.com >>> Web Database Systems and Linux Server Management >>>=20 >>>=20 >>> On 03/24/2015 10:41 AM, Steve Raslevich wrote: >>>=20 >>>> Ken, only the comma is in the raw context. no space: >>>>=20 >>>> If not using [founditems] and sending to multiple BCC or TO's the = syntax >>>> would look like this: >>>>=20 >>>> [SendMail >>>> = to=3Dcustomer@abc.com&bcc=3Daddy1@example.com,addy2@example.com,addy3@exam= ple.com&from=3Dsupport@xyz&subject=3Dsend >>>> tomany&Content-Type=3Dtext/html] >>>>=20 >>>> [SendMail >>>> = to=3Dcustomer@abc.com&bcc=3D[founditems][EMAILADDRESS][raw],[/raw][/foundi= tems]&from=3Dsupport@xyz&subject=3Dsend >>>> tomany&Content-Type=3Dtext/html] >>>>=20 >>>>=20 >>>>=20 >>>> Kenneth Grome wrote: >>>>=20 >>>>>>> Had the same problem with BCC, wrapping the , (comma) in [raw] >>>>>>> required between the BCC addresses fixed it for me. Also works >>>>>>> for TO: >>>>>>>=20 >>>>>>>=20 >>>>>> Good tip, thanks Steve. >>>>>>=20 >>>>>>=20 >>>>> I wish I could understand how this works. Putting something >>>>> inside a raw context is not supposed to change it. The raw >>>>> context encloses only two chars, a comma and a space, correct? >>>>>=20 >>>>> Regards, >>>>> Kenneth Grome >>>>> WebDNA Solutions >>>>> http://www.webdnasolutions.com >>>>> Web Database Systems and Linux Server Management >>>>>=20 >>>>>=20 >>>>> On 03/23/2015 05:56 PM, Stuart Tremain wrote: >>>>>=20 >>>>>=20 >>>>>> Kind regards >>>>>>=20 >>>>>> Stuart Tremain >>>>>> IDFK Web Developments >>>>>> AUSTRALIA >>>>>> webdna@idfk.com.au >>>>>>=20 >>>>>>=20 >>>>>>=20 >>>>>>=20 >>>>>>=20 >>>>>>=20 >>>>>>=20 >>>>>>> On 24 Mar 2015, at 09:09, Steve Raslevich >>>>>>> >>>>>> > wrote: >>>>>>>=20 >>>>>>> Hello Stuart, >>>>>>>=20 >>>>>>>=20 >>>>>>>=20 >>>>>=20 >>>>>=20 >>>>>>> [SendMail >>>>>>> to=3Dcustomer@abc.com&bcc=3D[founditems][EMAILADDRESS][raw], >>>>>>> [/raw][/founditems]&from=3Dsupport@xyz&subject=3Dsend to >>>>>>> many]&Content-Type=3Dtext/html] >>>>>>>=20 >>>>>>>=20 >>>>>>>=20 >>>>>>> Stuart Tremain wrote: >>>>>>>=20 >>>>>>>=20 >>>>>>>> Are you sending one email to one recipient or one email to many >>>>>>>> recipients ? >>>>>>>>=20 >>>>>>>> I had a problem with the latter, making it one to one solved >>>>>>>> the problem, but I don=92t know what was causing it. >>>>>>>>=20 >>>>>>>> Kind regards >>>>>>>>=20 >>>>>>>> Stuart Tremain >>>>>>>> IDFK Web Developments >>>>>>>> AUSTRALIA >>>>>>>> webdna@idfk.com.au >>>>>>>>=20 >>>>>>>>=20 >>>>>>>>=20 >>>>>>>>=20 >>>>>>>>=20 >>>>>>>>=20 >>>>>>>>=20 >>>>>>>>> On 20 Mar 2015, at 12:13, Diane Blackmore >>>>>>>>> > wrote: >>>>>>>>>=20 >>>>>>>>> Hi >>>>>>>>>=20 >>>>>>>>> Frequently, and increasingly, the Emailer seems to be breaking >>>>>>>>> the format of the emails resulting in garbled receipts etc >>>>>>>>> being sent to customers of our clients. This is happening now >>>>>>>>> more often than not - 20-30 times a day in one case, and needs >>>>>>>>> to be resolved so I=92d be interested if anyone knows of >>>>>>>>> anything buggy here. >>>>>>>>>=20 >>>>>>>>> The files that Emailer is sending are fine both before and >>>>>>>>> after sending. The content of the email contains html and so >>>>>>>>> is being sent as file that is written to the EmailFolder - I >>>>>>>>> stress that the format of the email can=92t be at issue as it >>>>>>>>> often comes through OK. It tends to happen more on larger >>>>>>>>> files, but none of them contain anything more than 11kb. >>>>>>>>> Images are absolute ref=92d back to the server etc so no = images >>>>>>>>> are bing sent. >>>>>>>>>=20 >>>>>>>>> It could be that the problem is not with Emailer but is >>>>>>>>> instead breaking down between Emailer and the localhost mail >>>>>>>>> server (not sure what we're using for this but its on the same >>>>>>>>> server somewhere). >>>>>>>>>=20 >>>>>>>>> WebDNA version is *unix-Linux Intel Apache Module version >>>>>>>>> 6.2.1* on Ubuntu 12.04.5 LTS (GNU/Linux 3.12.27-xenU x86_64), >>>>>>>>> Apache2, >>>>>>>>> Package updates etc were run last week but the problem existed >>>>>>>>> before then. Emailer is set to send every 20 ticks, and is >>>>>>>>> not really busy. >>>>>>>>>=20 >>>>>>>>> It has been suggested that we could replace Emailer with >>>>>>>>> something that does the same job but I=92d be interested to = find >>>>>>>>> out if there=92s a quicker fix before I go down that bumpy = path. >>>>>>>>>=20 >>>>>>>>>=20 >>>>>>>>> Cheers, >>>>>>>>>=20 >>>>>>>>>=20 >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>>=20 >>>>>>>>> To: Sandra Hillyard>>>>>>>> > >>>>>>>>> From: "Best Blooms Florist">>>>>>>> > >>>>>>>>> Subject: Best Blooms Florist Receipt >>>>>>>>> BCC: diane@cohesion.co.nz >>>>>>>>> Organization: Best Blooms Florist >>>>>>>>> MIME-Version: 1.0 >>>>>>>>> Content-Type: multipart/alternative; >>>>>>>>> boundary=3D"----=3D_NextPart_01jvh893459rhw" >>>>>>>>> X-Priority: 3 >>>>>>>>> X-MSMail-Priority: Normal >>>>>>>>>=20 >>>>>>>>> This is a multi-part message in MIME format. >>>>>>>>>=20 >>>>>>>>> ------=3D_NextPart_01jvh893459rhw >>>>>>>>> Content-Type: text/plain; >>>>>>>>> charset=3D"iso-8859-1" >>>>>>>>> Content-Transfer-Encoding: 7bit >>>>>>>>>=20 >>>>>>>>> This message is in a format that cannot be read by your email >>>>>>>>> software. Time to upgrade! >>>>>>>>>=20 >>>>>>>>> ------=3D_NextPart_01jvh893459rhw >>>>>>>>> Content-Type: text/html; >>>>>>>>> charset=3D"iso-8859-1" >>>>>>>>> Content-Transfer-Encoding: 7bit >>>>>>>>>=20 >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> Best Blooms Florist >>>>>>>>>=20 >>>>>>>>> >>>>>>>>>=20 >>>>>>>>> >>>>>>>>> >>>>>>>>>=20 >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>> align=3D"center" style=3D"padding:5px 0;"> >>>>>>>>> >>>>>>>>> | >>>>>>>>> >>>>>>>>> | >>>>>>>>> >>>>>>>>> >>>>>>>>> | >>>>>>>>>
>>>>>>>>> >>>>>>>>> | >>>>>>>>> >>>>>>>>> | >>>>>>>>>
>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>> align=3D"center"> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> Order Ref. 42230 >>>>>>>>> Tax Invoice Receipt >>>>>>>>>=20 >>>>>>>>>=20 >>>>>>>>>=20 >>>>>>>>> >>>>>>>> class=3D"tableForm"> >>>>>>>>> >>>>>>>>> | Arrangement / Accessory | >>>>>>>>> Price | >>>>>>>>> Quantity | >>>>>>>>> Cost | >>>>>>>>> >>>>>>>>>=20 >>>>>>>>> >>>>>>>>> >>>>>>>> = href=3D"http://www.bestblooms.co.nz/online/product_information.csn?product= id=3D1132151">Hot >>>>>>>>> Pink and Purple Bouquet - Standard
| >>>>>>>>> $80.00 | >>>>>>>>> 1 | >>>>>>>>> $80.00 | >>>>>>>>> >>>>>>>>>=20 >>>>>>>>>=20 >>>>>>>>>=20 >>>>>>>>> >>>>>>>>> | >>>>>>>> style=3D"background:#fff;text-align:right;">Sub-Total: | >>>>>>>>> $80.00 | >>>>>>>>> >>>>>>>>>=20 >>>>>>>>> >>>>>>>>> | >>>>>>>> style=3D"background:#fff;text-align:right;">Signature = Card: | >>>>>>>>> $0.00 | >>>>>>>>> >>>>>>>>> >>>>>>>>> | >>>>>>>> style=3D"background:#fff;text-align:right;">Delivery: | >>>>>>>>> $0.00 | >>>>>>>>> >>>>>>>>>=20 >>>>>>>>> >>>>>>>>> | Grand = Total: | >>>>>>>>> $80.00 | >>>>>>>>> >>>>>>>>> >>>>>>>>>
* Prices are in New Zealand Dollars and >>>>>>>>> include Goods and Services Tax within New Zealand. GST Number >>>>>>>>> 94-374-936.
>>>>>>>>>=20 >>>>>>>>>=20 >>>>>>>>> Delivery Details >>>>>>>>>=20 >>>>>>>>> Your Details >>>>>>>>>=20 >>>>>>>>>=20 >>>>>>>>> Billing Details >>>>>>>>>=20 >>>>>>>>>=20 >>>>>>>>>=20 >>>>>>>>>=20 >>>>>>>>> >>>>>>>>>=20 >>>>>>>>>=20 >>>>>>>>>=20 >>>>>>>>> | >>>>>>>>>=20 >>>>>>>>> >>>>>>>>>=20 >>>>>>>>> >>>>>>>>>=20 >>>>>>>>>=20 >>>>>>>>> | >>>>>>>>>=20 >>>>>>>>>
>>>>>>>>>=20 >>>>>>>>> >>>>>>>>>=20 >>>>>>>>> | >>>>>>>>>=20 >>>>>>>>>=20 >>>>>>>>> >>>>>>>>>=20 >>>>>>>>>=20 >>>>>>>>> | >>>>>>>>>=20 >>>>>>>>>
>>>>>>>>>=20 >>>>>>>>> >>>>>>>>>=20 >>>>>>>>> >>>>>>>>>=20 >>>>>>>>>=20 >>>>>>>>> >>>>>>>> align=3D"center"> >>>>>>>>>=20 >>>>>>>>> >>>>>>>>>=20 >>>>>>>>> | >>>>>>>>>=20 >>>>>>>>>=20 >>>>>>>>> >>>>>>>>>=20 >>>>>>>>> >>>>>>>>>=20 >>>>>>>>> >>>>>>>>>=20 >>>>>>>>>=20 >>>>>>>>> | >>>>>>>>>=20 >>>>>>>>> >>>>>>>>>=20 >>>>>>>>> >>>>>>>>>=20 >>>>>>>>>=20 >>>>>>>>> | >>>>>>>>>=20 >>>>>>>>>
>>>>>>>>>=20 >>>>>>>>>
>>>>>>>>>=20 >>>>>>>>>=20 >>>>>>>>>=20 >>>>>>>>>=20 >>>>>>>>>=20 >>>>>>>>>=20 >>>>>>>>>=20 >>>>>>>>> >>>>>>>>>=20 >>>>>>>>> >>>>>>>>>=20 >>>>>>>>>=20 >>>>>>>>>=20 >>>>>>>>> ------=3D_NextPart_01jvh893459rhw-- >>>>>>>>>=20 >>>>>>>>>=20 >>>>>>>>=20 >>>>>>>>=20 >>>>>>=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 >>>>>=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 >>>>=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 >>>=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 >>=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
Associated Messages, from the most recent to the oldest:
This isn't how I handle such multiple emails. I do it thusly: search founditems sendmail /sendmail /founditems /search Why not try that. For some reason, early on I figured it was just = cleaner to send individual emails. Or maybe it was breaking on a bad = email; I really don't remember that far back. That also gives you a = chance to grab other variables from the founditems loop, like "Hello = [firstname],". Makes no difference to the mail server. Or perhaps it = makes it easier for the mail server; I wouldn't know about that. For = sure it will take WebDNA longer to process the page. But so what. As for the comma, that's just bizarre. I use commas all the time, no = problem (but they aren't within a founditems loop). = BCC,CC,Sender,Reply-to.. use them all; never seen a problem. Even more = curious - how did you come up with the idea to even try [raw]? That's = like wondering how anyone ever came up with the idea of cooking an = artichoke bud. BTW anyone who ever had chicken pox should get the shingles vaccine. You = can guess why I'm sending this advice... Terry On Mar 24, 2015, at 10:57 AM, Kenneth Grome = wrote: > These are good things to know. >=20 > I think they should be added to the documentation since they are > clearly unexpected behavior, at least for many of us. >=20 > Regards, > Kenneth Grome > WebDNA Solutions > http://www.webdnasolutions.com > Web Database Systems and Linux Server Management >=20 >=20 > On 03/24/2015 11:01 AM, Steve Raslevich wrote: >> I have no idea for the behavior but do know that only the first BCC=20= >> email address will be sent if the comma separating the addresses in a=20= >> [founditems] is now within [raw] >>=20 >> Another finding about sending to multiple addresses with [sendmail] = is=20 >> that if one email address is an invalid formatted address, the email = is=20 >> not sent to any of the addresses. >>=20 >> I send out an email newsletter to @ 30,000 addresses and break the=20 >> sending down to groups of 35 - 50. >>=20 >> Kenneth Grome wrote: >>>> Ken, only the comma is in the raw context. no space: >>>>=20 >>> But I still do not understand why [raw],[/raw] would modify the >>> comma (or the code around it) in any way, much less in a way that >>> would cause the sendmail to work properly with it but not without = it. >>>=20 >>> Apparently it has some kind of reaction with the founditems? Does >>> it introduce an invisible character or something? >>>=20 >>> Regards, >>> Kenneth Grome >>> WebDNA Solutions >>> http://www.webdnasolutions.com >>> Web Database Systems and Linux Server Management >>>=20 >>>=20 >>> On 03/24/2015 10:41 AM, Steve Raslevich wrote: >>>=20 >>>> Ken, only the comma is in the raw context. no space: >>>>=20 >>>> If not using [founditems] and sending to multiple BCC or TO's the = syntax >>>> would look like this: >>>>=20 >>>> [SendMail >>>> = to=3Dcustomer@abc.com&bcc=3Daddy1@example.com,addy2@example.com,addy3@exam= ple.com&from=3Dsupport@xyz&subject=3Dsend >>>> tomany&Content-Type=3Dtext/html] >>>>=20 >>>> [SendMail >>>> = to=3Dcustomer@abc.com&bcc=3D[founditems][EMAILADDRESS][raw],[/raw][/foundi= tems]&from=3Dsupport@xyz&subject=3Dsend >>>> tomany&Content-Type=3Dtext/html] >>>>=20 >>>>=20 >>>>=20 >>>> Kenneth Grome wrote: >>>>=20 >>>>>>> Had the same problem with BCC, wrapping the , (comma) in [raw] >>>>>>> required between the BCC addresses fixed it for me. Also works >>>>>>> for TO: >>>>>>>=20 >>>>>>>=20 >>>>>> Good tip, thanks Steve. >>>>>>=20 >>>>>>=20 >>>>> I wish I could understand how this works. Putting something >>>>> inside a raw context is not supposed to change it. The raw >>>>> context encloses only two chars, a comma and a space, correct? >>>>>=20 >>>>> Regards, >>>>> Kenneth Grome >>>>> WebDNA Solutions >>>>> http://www.webdnasolutions.com >>>>> Web Database Systems and Linux Server Management >>>>>=20 >>>>>=20 >>>>> On 03/23/2015 05:56 PM, Stuart Tremain wrote: >>>>>=20 >>>>>=20 >>>>>> Kind regards >>>>>>=20 >>>>>> Stuart Tremain >>>>>> IDFK Web Developments >>>>>> AUSTRALIA >>>>>> webdna@idfk.com.au >>>>>>=20 >>>>>>=20 >>>>>>=20 >>>>>>=20 >>>>>>=20 >>>>>>=20 >>>>>>=20 >>>>>>> On 24 Mar 2015, at 09:09, Steve Raslevich >>>>>>> >>>>>> > wrote: >>>>>>>=20 >>>>>>> Hello Stuart, >>>>>>>=20 >>>>>>>=20 >>>>>>>=20 >>>>>=20 >>>>>=20 >>>>>>> [SendMail >>>>>>> to=3Dcustomer@abc.com&bcc=3D[founditems][EMAILADDRESS][raw], >>>>>>> [/raw][/founditems]&from=3Dsupport@xyz&subject=3Dsend to >>>>>>> many]&Content-Type=3Dtext/html] >>>>>>>=20 >>>>>>>=20 >>>>>>>=20 >>>>>>> Stuart Tremain wrote: >>>>>>>=20 >>>>>>>=20 >>>>>>>> Are you sending one email to one recipient or one email to many >>>>>>>> recipients ? >>>>>>>>=20 >>>>>>>> I had a problem with the latter, making it one to one solved >>>>>>>> the problem, but I don=92t know what was causing it. >>>>>>>>=20 >>>>>>>> Kind regards >>>>>>>>=20 >>>>>>>> Stuart Tremain >>>>>>>> IDFK Web Developments >>>>>>>> AUSTRALIA >>>>>>>> webdna@idfk.com.au >>>>>>>>=20 >>>>>>>>=20 >>>>>>>>=20 >>>>>>>>=20 >>>>>>>>=20 >>>>>>>>=20 >>>>>>>>=20 >>>>>>>>> On 20 Mar 2015, at 12:13, Diane Blackmore >>>>>>>>> > wrote: >>>>>>>>>=20 >>>>>>>>> Hi >>>>>>>>>=20 >>>>>>>>> Frequently, and increasingly, the Emailer seems to be breaking >>>>>>>>> the format of the emails resulting in garbled receipts etc >>>>>>>>> being sent to customers of our clients. This is happening now >>>>>>>>> more often than not - 20-30 times a day in one case, and needs >>>>>>>>> to be resolved so I=92d be interested if anyone knows of >>>>>>>>> anything buggy here. >>>>>>>>>=20 >>>>>>>>> The files that Emailer is sending are fine both before and >>>>>>>>> after sending. The content of the email contains html and so >>>>>>>>> is being sent as file that is written to the EmailFolder - I >>>>>>>>> stress that the format of the email can=92t be at issue as it >>>>>>>>> often comes through OK. It tends to happen more on larger >>>>>>>>> files, but none of them contain anything more than 11kb. >>>>>>>>> Images are absolute ref=92d back to the server etc so no = images >>>>>>>>> are bing sent. >>>>>>>>>=20 >>>>>>>>> It could be that the problem is not with Emailer but is >>>>>>>>> instead breaking down between Emailer and the localhost mail >>>>>>>>> server (not sure what we're using for this but its on the same >>>>>>>>> server somewhere). >>>>>>>>>=20 >>>>>>>>> WebDNA version is *unix-Linux Intel Apache Module version >>>>>>>>> 6.2.1* on Ubuntu 12.04.5 LTS (GNU/Linux 3.12.27-xenU x86_64), >>>>>>>>> Apache2, >>>>>>>>> Package updates etc were run last week but the problem existed >>>>>>>>> before then. Emailer is set to send every 20 ticks, and is >>>>>>>>> not really busy. >>>>>>>>>=20 >>>>>>>>> It has been suggested that we could replace Emailer with >>>>>>>>> something that does the same job but I=92d be interested to = find >>>>>>>>> out if there=92s a quicker fix before I go down that bumpy = path. >>>>>>>>>=20 >>>>>>>>>=20 >>>>>>>>> Cheers, >>>>>>>>>=20 >>>>>>>>>=20 >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>>=20 >>>>>>>>> To: Sandra Hillyard>>>>>>>> > >>>>>>>>> From: "Best Blooms Florist">>>>>>>> > >>>>>>>>> Subject: Best Blooms Florist Receipt >>>>>>>>> BCC: diane@cohesion.co.nz >>>>>>>>> Organization: Best Blooms Florist >>>>>>>>> MIME-Version: 1.0 >>>>>>>>> Content-Type: multipart/alternative; >>>>>>>>> boundary=3D"----=3D_NextPart_01jvh893459rhw" >>>>>>>>> X-Priority: 3 >>>>>>>>> X-MSMail-Priority: Normal >>>>>>>>>=20 >>>>>>>>> This is a multi-part message in MIME format. >>>>>>>>>=20 >>>>>>>>> ------=3D_NextPart_01jvh893459rhw >>>>>>>>> Content-Type: text/plain; >>>>>>>>> charset=3D"iso-8859-1" >>>>>>>>> Content-Transfer-Encoding: 7bit >>>>>>>>>=20 >>>>>>>>> This message is in a format that cannot be read by your email >>>>>>>>> software. Time to upgrade! >>>>>>>>>=20 >>>>>>>>> ------=3D_NextPart_01jvh893459rhw >>>>>>>>> Content-Type: text/html; >>>>>>>>> charset=3D"iso-8859-1" >>>>>>>>> Content-Transfer-Encoding: 7bit >>>>>>>>>=20 >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> Best Blooms Florist >>>>>>>>>=20 >>>>>>>>> >>>>>>>>>=20 >>>>>>>>> >>>>>>>>> >>>>>>>>>=20 >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>> align=3D"center" style=3D"padding:5px 0;"> >>>>>>>>> >>>>>>>>> | >>>>>>>>> >>>>>>>>> | >>>>>>>>> >>>>>>>>> >>>>>>>>> | >>>>>>>>>
>>>>>>>>> >>>>>>>>> | >>>>>>>>> >>>>>>>>> | >>>>>>>>>
>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>> align=3D"center"> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> Order Ref. 42230 >>>>>>>>> Tax Invoice Receipt >>>>>>>>>=20 >>>>>>>>>=20 >>>>>>>>>=20 >>>>>>>>> >>>>>>>> class=3D"tableForm"> >>>>>>>>> >>>>>>>>> | Arrangement / Accessory | >>>>>>>>> Price | >>>>>>>>> Quantity | >>>>>>>>> Cost | >>>>>>>>> >>>>>>>>>=20 >>>>>>>>> >>>>>>>>> >>>>>>>> = href=3D"http://www.bestblooms.co.nz/online/product_information.csn?product= id=3D1132151">Hot >>>>>>>>> Pink and Purple Bouquet - Standard
| >>>>>>>>> $80.00 | >>>>>>>>> 1 | >>>>>>>>> $80.00 | >>>>>>>>> >>>>>>>>>=20 >>>>>>>>>=20 >>>>>>>>>=20 >>>>>>>>> >>>>>>>>> | >>>>>>>> style=3D"background:#fff;text-align:right;">Sub-Total: | >>>>>>>>> $80.00 | >>>>>>>>> >>>>>>>>>=20 >>>>>>>>> >>>>>>>>> | >>>>>>>> style=3D"background:#fff;text-align:right;">Signature = Card: | >>>>>>>>> $0.00 | >>>>>>>>> >>>>>>>>> >>>>>>>>> | >>>>>>>> style=3D"background:#fff;text-align:right;">Delivery: | >>>>>>>>> $0.00 | >>>>>>>>> >>>>>>>>>=20 >>>>>>>>> >>>>>>>>> | Grand = Total: | >>>>>>>>> $80.00 | >>>>>>>>> >>>>>>>>> >>>>>>>>>
* Prices are in New Zealand Dollars and >>>>>>>>> include Goods and Services Tax within New Zealand. GST Number >>>>>>>>> 94-374-936.
>>>>>>>>>=20 >>>>>>>>>=20 >>>>>>>>> Delivery Details >>>>>>>>>=20 >>>>>>>>> Your Details >>>>>>>>>=20 >>>>>>>>>=20 >>>>>>>>> Billing Details >>>>>>>>>=20 >>>>>>>>>=20 >>>>>>>>>=20 >>>>>>>>>=20 >>>>>>>>> >>>>>>>>>=20 >>>>>>>>>=20 >>>>>>>>>=20 >>>>>>>>> | >>>>>>>>>=20 >>>>>>>>> >>>>>>>>>=20 >>>>>>>>> >>>>>>>>>=20 >>>>>>>>>=20 >>>>>>>>> | >>>>>>>>>=20 >>>>>>>>>
>>>>>>>>>=20 >>>>>>>>> >>>>>>>>>=20 >>>>>>>>> | >>>>>>>>>=20 >>>>>>>>>=20 >>>>>>>>> >>>>>>>>>=20 >>>>>>>>>=20 >>>>>>>>> | >>>>>>>>>=20 >>>>>>>>>
>>>>>>>>>=20 >>>>>>>>> >>>>>>>>>=20 >>>>>>>>> >>>>>>>>>=20 >>>>>>>>>=20 >>>>>>>>> >>>>>>>> align=3D"center"> >>>>>>>>>=20 >>>>>>>>> >>>>>>>>>=20 >>>>>>>>> | >>>>>>>>>=20 >>>>>>>>>=20 >>>>>>>>> >>>>>>>>>=20 >>>>>>>>> >>>>>>>>>=20 >>>>>>>>> >>>>>>>>>=20 >>>>>>>>>=20 >>>>>>>>> | >>>>>>>>>=20 >>>>>>>>> >>>>>>>>>=20 >>>>>>>>> >>>>>>>>>=20 >>>>>>>>>=20 >>>>>>>>> | >>>>>>>>>=20 >>>>>>>>>
>>>>>>>>>=20 >>>>>>>>>
>>>>>>>>>=20 >>>>>>>>>=20 >>>>>>>>>=20 >>>>>>>>>=20 >>>>>>>>>=20 >>>>>>>>>=20 >>>>>>>>>=20 >>>>>>>>> >>>>>>>>>=20 >>>>>>>>> >>>>>>>>>=20 >>>>>>>>>=20 >>>>>>>>>=20 >>>>>>>>> ------=3D_NextPart_01jvh893459rhw-- >>>>>>>>>=20 >>>>>>>>>=20 >>>>>>>>=20 >>>>>>>>=20 >>>>>>=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 >>>>>=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 >>>>=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 >>>=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 >>=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
Terry Wilson
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:
Date range (2006)
What am I missing (1997)
Searching multiple fields from one form field (1997)
Problems getting parameters passed into email. (1997)
drop down selection list for a search (1998)
Showif, Hideif reverse logic ? (1997)
Automated FTP from Shell (2004)
upgrading (1997)
WebCat 2.1beta etc (1997)
Javascript/WebCatalog form population (2001)
ANet? (2002)
Protecting Files (2005)
WebCat2b12 CGI Mac -- Problems propagating the cart through (1997)
Separate SSL Server (1997)
error: Too many nested [xxx] contexts (1997)
Multiple Passwords (1997)
Help name our technology! (1997)
Counting LineItems (2000)
[WebDNA] Intermittent Encryption Issue (2009)
Ads.db (1997)
![](3D"http://www.bestblooms.co.nz/e_images/phone.png")
>>>>>>>> alt=3D"phone" border=3D"0" width=3D"39" height=3D"27"> >>>>>>>>> ![](3D"http://www.bestblooms.co.nz/e_images/gplus.png")
>>>>>>>> alt=3D"gplus" border=3D"0" width=3D"28" height=3D"27">