Hi

We are training up some novices to write HTML emails.
Any recommendations on what we should be reading?

a) HTML primer(s?)

b) Writing HTML emails in particular that
i) have good delivery rates (i.e. avoid spam filters)
ii) get good response rates?

- Any recommendations? - (i.e. books, online guides etc.)

Something easy to read, waffle-free, and with lots of
pictures & examples would be good !

With thanks


Ship
Shiperton Henethe

P.S. Fwiw, someone has recommended the following HTML primers
> Good books to read would be "Head First HTML" or Lie & Bos' "Cascading
> Style Sheets"

[end]

On May 30, 7:38 am, ship <ship...@gmail.com> wrote:
> We are training up some novices to write HTML emails.
> Any recommendations on what we should be reading?

http://mailformat.dan.info/body/html.html
http://webtips.dan.info/email.html

--
Dan

On 2007-05-30, ship wrote:
>
> We are training up some novices to write HTML emails.
> Any recommendations on what we should be reading?

Don't!

> a) HTML primer(s?)
>
> b) Writing HTML emails in particular that
> i) have good delivery rates (i.e. avoid spam filters)

HTML e-mails do not get through my spam filter.

--
Chris F.A. Johnson <http://cfaj.freeshell.org>
================================================== =================
Author:
Shell Scripting Recipes: A Problem-Solution Approach (2005, Apress)

Chris F.A. Johnson wrote:
> On 2007-05-30, ship wrote:
>>
>> We are training up some novices to write HTML emails.
>
> Don't!

Actually, it depends on the subject matter and who the audience is
whether HTML email is likely to be well received or not. If it's a
newsletter, multi-part/alternative HTML is pretty much required.

--
Berg

Bergamot wrote:
: Chris F.A. Johnson wrote:
:: On 2007-05-30, ship wrote:
:::
::: We are training up some novices to write HTML emails.
::
:: Don't!
:
: Actually, it depends on the subject matter and who the audience is
: whether HTML email is likely to be well received or not. If it's a
: newsletter, multi-part/alternative HTML is pretty much required.

Depending on who is sending it I like getting HTML email.
Looking to buy a new home for instance. I get emails now when there are new
listings from a few realtors. I like them in HTML because it is easier to
read the specifics of the property and I always know where to see the
pictures of the property if there are any.

I read all message in plain text though so if it spam then I don't see
anything. If it is from the realtors or any other newsletter I have asked
for then I open the HTML attachment in my browser.

Heidi

In article <EMAIL REMOVED>,
Bergamot <EMAIL REMOVED> wrote:

> Chris F.A. Johnson wrote:
> > On 2007-05-30, ship wrote:
> >>
> >> We are training up some novices to write HTML emails.
> >
> > Don't!
>
> Actually, it depends on the subject matter and who the audience is
> whether HTML email is likely to be well received or not. If it's a
> newsletter, multi-part/alternative HTML is pretty much required.

You are wrong. Just email a URL so the HTML will be properly displayed
in a browser. Better yet, ditch the newsletter BS and just provide an
RSS feed.

--
My personal UDP list: 127.0.0.1, 4ax.com, buzzardnews.com, googlegroups.com,
heapnode.com, localhost, x-privat.org

Doc O'Leary wrote:
> In article <EMAIL REMOVED>,
> Bergamot <EMAIL REMOVED> wrote:
>>
>> Actually, it depends on the subject matter and who the audience is
>> whether HTML email is likely to be well received or not. If it's a
>> newsletter, multi-part/alternative HTML is pretty much required.
>
> You are wrong. Just email a URL so the HTML will be properly displayed
> in a browser. Better yet, ditch the newsletter BS and just provide an
> RSS feed.

Maybe "required" was a bit strong, but I stand by the rest - it depends
on the audience and the subject matter. Not everyone is into RSS.

--
Berg

On Thu, 31 May 2007 15:48:48 -0500, Bergamot put finger to keyboard
and typed:

>Doc O'Leary wrote:
>> In article <EMAIL REMOVED>,
>> Bergamot <EMAIL REMOVED> wrote:
>>>
>>> Actually, it depends on the subject matter and who the audience is
>>> whether HTML email is likely to be well received or not. If it's a
>>> newsletter, multi-part/alternative HTML is pretty much required.
>>
>> You are wrong. Just email a URL so the HTML will be properly displayed
>> in a browser. Better yet, ditch the newsletter BS and just provide an
>> RSS feed.
>
>Maybe "required" was a bit strong, but I stand by the rest - it depends
>on the audience and the subject matter. Not everyone is into RSS.

With very few exceptions, the only sensible solution is to allow
people the choice of HTML or plain text when they sign up in the first
place. If you don't allow a choice, and always send in HTML, then you
will annoy all the subscribers who prefer plain text and probably lose
them from the list. If you don't allow a choice, and always send in
plain text, then you will annoy fewer people but you'll also get
significantly lower response rates from people who would otherwise
have chosen HTML. Either way, you're shooting yourself in the foot,
from a marketing perspective.

Mark
--
Visit: http://www.BritishSurnames.co.uk - British surname distribution profiles
"Let's see colours that have never been seen"

On Jun 1, 2:59 am, Mark Goodge <use...@listmail.good-stuff.co.uk>
wrote:
> Either way, you're shooting yourself in the foot,
> from a marketing perspective.

Well, I wish all the Marketing Types of the world would go shoot
themselves, hopefully in a more vital part of their anatomy than the
foot... that would make the world a better place, much like
Shakespeare's plea to kill all the lawyers.

--
Dan