Thanks for the reply.
Responses inline:
"David E. Ross" <no****@nowhere.notwrote in message
news:OZ******************************@softcom.net. ..
This is a promotional mailshot so image is important. I understand what you>>
Because the HTML generators for E-mail often fail to create valid HTML,
different E-mail clients display the results differently. Sometimes,
this causes displays to be totally corrupted.
If you are trying to distribute a newsletter, I suggest you instead
create the newsletter as a Web page. Validate the HTML at
<http://validator.w3.org/>. Then, send an ASCII message to your
subscription list, announcing the newsletter with the link to that page.
If you do this, then all recipients of the announcement message should
be able to view the newsletter properly.
are saying here, however, the powers that be want something above plaintext
for this project.
Note that some spam filters treat HTML-formatted messages as more likelyAgreed. However, as you can see, the HTML is minimal and our testing so far
to be spam. Of course, HTML formatting is not the only criterion; but
when added to certain words in the message text -- words that might be
quite innocent -- HTML formatting might be enough to make a filter
reject your message. Your message might not reach its intended addressee.
indicates that it isn't going to fall foul of most spam filters (e.g.
MessageLabs, SpamAssassin etc).
The issue of HTML-formatted E-mail messages generates endless debate inYes, I'm aware of (and sympathetic to) the debate. This is one of the
this and other newsgroups. See my
<http://www.seamonkey-project.org/ASCII_mail.htmlto read why I'm in
the group that opposes the use of HTML-formatting for E-mail. (One of
my reasons is in the third paragraph of this message.)
occasions where I think html emails can have a benefit, however, there is a
proper plaintext version in the multi-part email that we are going to send,
should anyone prefer that version.
Since posting, I've 'fixed' the layout issue by regressing to
tables-for-layout, so that no longer is a problem.
However, the issue regarding character sets/codepages and Danish characters
is still the principle concern. This problem is (obviously) a problem with
both html and plaintext version, so currently it is a show-stopper.
Any thoughts on this issue?