Re: [WebDNA] Re: html email.. should be a no-brainer.. but it is not parsing. (?)
This WebDNA talk-list message is from 2010
It keeps the original formatting.
numero = 106047
interpreted = N
texte = --Apple-Mail-1--949457765 Content-Type: text/plain; charset=WINDOWS-1252; format=flowed; delsp=yes Content-Transfer-Encoding: quoted-printable OK, thanks Michael. That makes sense. In this case this is for a client.. and they would =20= have to agree to go back and force all their clients to now set that =20 (new) preference in their accounts. Don't we love computers?! Switching that email from plain text to =20 multipart/alternative-type was (we assumed) just a 7-mintute =20 task ...before all kinds of real (major) hacks that have to get done... http://blisscode.com/BC_images/babyBlues-18Oct09-Gov.jpg ;-) -G On Dec 22, 2010, at 8:32 AM, Michael A. DeLorenzo wrote: > Yes. That is why I give the user and option to receive text or HTML =20= > when they fill out the information request form. > > From: Govinda [mailto:govinda.webdnatalk@gmail.com] > Sent: Tuesday, December 21, 2010 4:28 PM > To: talk@webdna.us > Subject: Re: [WebDNA] Re: html email.. should be a no-brainer.. but =20= > it is not parsing. (?) > > Hi Michael > > thanks for chiming in! > > Well that works! > > But wouldn't you say that it is bad practice to send email out that =20= > way, without a plain-text alternative, in case the user has HTML =20 > email turned off, whether by choice, or otherwise? > > -Govinda > > On Dec 21, 2010, at 3:58 PM, Michael A. DeLorenzo wrote: > > > Try changing your content type to the code below as the last =20 > variable in the sendmail.=85=85 > > &content-type=3Dtext/html > > Mike > --Apple-Mail-1--949457765 Content-Type: text/html; charset=WINDOWS-1252 Content-Transfer-Encoding: quoted-printable OK, thanks Michael. =
That makes sense. In this case this is for a client.. = and they would have to agree to go back and force all their clients to = now set that (new) preference in their accounts.
Don't we = love computers?! Switching that email from plain text = to multipart/alternative-type was (we assumed) just a 7-mintute = task ...before all kinds of real (major) hacks that have to get = done...
-G
On Dec 22, = 2010, at 8:32 AM, Michael A. DeLorenzo wrote:
Yes. That is why I give = the user and option to receive text or HTML when they fill out the = information request form.
Govinda = [
Sent: Tuesday, December 21, 2010 = 4:28 PM
To: talk@webdna.us
Subject: Re: [WebDNA] Re: html = email.. should be a no-brainer.. but it is not parsing. = (?) Hi = Michael
But wouldn't you say that = it is bad practice to send email out that way, without a plain-text = alternative, in case the user has HTML email turned off, whether by = choice, or otherwise?
On Dec 21, 2010, at 3:58 = PM, Michael A. DeLorenzo wrote:
Try changing your content type to the code below as = the last variable in the sendmail.=85=85
| |
|
--Apple-Mail-1--949457765 Content-Type: text/plain; charset=WINDOWS-1252; format=flowed; delsp=yes Content-Transfer-Encoding: quoted-printable OK, thanks Michael. That makes sense. In this case this is for a client.. and they would =20= have to agree to go back and force all their clients to now set that =20 (new) preference in their accounts. Don't we love computers?! Switching that email from plain text to =20 multipart/alternative-type was (we assumed) just a 7-mintute =20 task ...before all kinds of real (major) hacks that have to get done... http://blisscode.com/BC_images/babyBlues-18Oct09-Gov.jpg ;-) -G On Dec 22, 2010, at 8:32 AM, Michael A. DeLorenzo wrote: > Yes. That is why I give the user and option to receive text or HTML =20= > when they fill out the information request form. > > From: Govinda [mailto:govinda.webdnatalk@gmail.com] > Sent: Tuesday, December 21, 2010 4:28 PM > To: talk@webdna.us > Subject: Re: [WebDNA] Re: html email.. should be a no-brainer.. but =20= > it is not parsing. (?) > > Hi Michael > > thanks for chiming in! > > Well that works! > > But wouldn't you say that it is bad practice to send email out that =20= > way, without a plain-text alternative, in case the user has HTML =20 > email turned off, whether by choice, or otherwise? > > -Govinda > > On Dec 21, 2010, at 3:58 PM, Michael A. DeLorenzo wrote: > > > Try changing your content type to the code below as the last =20 > variable in the sendmail.=85=85 > > &content-type=3Dtext/html > > Mike > --Apple-Mail-1--949457765 Content-Type: text/html; charset=WINDOWS-1252 Content-Transfer-Encoding: quoted-printable OK, thanks Michael. = That makes sense. In this case this is for a client.. = and they would have to agree to go back and force all their clients to = now set that (new) preference in their accounts.
Don't we = love computers?! Switching that email from plain text = to multipart/alternative-type was (we assumed) just a 7-mintute = task ...before all kinds of real (major) hacks that have to get = done...
-G
On Dec 22, = 2010, at 8:32 AM, Michael A. DeLorenzo wrote:
Yes. That is why I give = the user and option to receive text or HTML when they fill out the = information request form.
Govinda = [
Sent: Tuesday, December 21, 2010 = 4:28 PM
To: talk@webdna.us
Subject: Re: [WebDNA] Re: html = email.. should be a no-brainer.. but it is not parsing. = (?) Hi = Michael
But wouldn't you say that = it is bad practice to send email out that way, without a plain-text = alternative, in case the user has HTML email turned off, whether by = choice, or otherwise?
On Dec 21, 2010, at 3:58 = PM, Michael A. DeLorenzo wrote:
Try changing your content type to the code below as = the last variable in the sendmail.=85=85
![http://b= lisscode.com/BC_images/babyBlues-18Oct09-Gov.jpg](3D"http://blisscode.com/BC_images/babyBlues-18Oct09-Gov.jpg"){kind=link}