Corporate Information | Software | Support | Contact Us
Corporate Information
Software
Messenger Pro
Messenger Pro Downloads
Beta and Archived Downloads
Evaluate
Support
Messenger Pro FAQ
Messenger Pro Change Log
Messenger Pro (Windows/Linux/Mac) Mailing List Archive
Messenger Pro (RISC OS) Mailing List Archive
Bug Tracker
Contact Us

Re: Gemini and XHTML in emails

From:David Eaton Date:25 Nov 2011 02:25
In Reply To: Re: Gemini and XHTML in emails (Darren Salt)

On 25 Nov Darren Salt <ds@...> wrote:

> I demand that David Eaton may or may not have written...
> 
> [snip]
> > Looking at 'view source' in IE9 after opening some of the problem ones
> > from Gemini, I can see why. in the browser, the images aren't there, why
> > what should be links are just text, and why the layout is broken. Every
> > =" is missing in every html tag. So each link is hrefhttp instead of
> > href="http, every image tag goes srchttp instead of src="http, and so on
> > in the formatting tags and attributes.
> 
> I'm guessing that quoted-printable decoding is being applied due to
> relevant headers, but (at least) the ‘=’s in the text aren't encoded.

Ah. Thanks.

Checking back over ones that are working OK and ones that aren't just over
the last couple of days, I note:

1 The ones still working, in the HTML parts, have = encoded, and in the
headers for that part have either just Content Transfer Encoding:
quoted-printable, or that and mention of 7-Bit.

2 In the ones not working, the = is just =, but all the ones I've checked so
far have:

Content Transfer Encoding: 8bit
Content Transfer Encoding: quoted-printable

(Hyphens removed, just in case the fully written attributes would monkey
with this email)

Dear me. 10 years ago I knew all about the RFCs, POP3 and SMTP mail
protocls, MIME and all that. Now I can't remember any of what I used to know
at all.

Anyway ...

So maybe this sudden appearance of problems for me is due to the release of
some new version of emailing software some weeks ago that several of my
newsletter sources adopted when it came out, which does this putting in the
8bit content transfer encoding attribute and then don't encode the = etc,
whereas whatever they used before did standard 7bit qp encoding.

So the questions then become:

1 Are what they are doing (now) valid?

2 Whether it's technically valid or not (given that it's clearly being done
anyway, and a lot of not-technically valid things have been in the past),
does MPro cope with this, given that Gemini 2.29m clearly doesn't?

David

______________________________________________________________________
This message was sent via the gemini-users mailing list
To unsubscribe, mail gemini-users-unsubscribe@...




© 2024 intellegit ltd. - info@intellegit.com