Vista - Links in WLM get 'wlmailhtml...' prefix added and then don't work

I'm running Windows Live Mail in POP mode on my XP computer. Links in some
incoming emails do not work. The source code of the original email might
contain a link URL of say "https://www.citigroupgeo.com/pdf/ANMCALL.pdf", but
if I hover my mouse over the link the status line at the bottom of the WLM
screen displays
"wlmailhtml:{F6911BF2-0D36-4C65-81EF-1993AFF4FE2E}mid://00000050/!x-usc:https://www.citigroupgeo.com/pdf/ANMCALL.pdf"
(without the double-quotes). If I click the link, IE7 opens, displaying the
latter of these URLs in its address bar, and showing below "The address is
not valid".

Why is WLM adding the "wlmailhtml (etc)" prefix onto the original URL? Is
seems to be related to the fact that the original URL is a secure one
(https). How can I prevent this happening, so that such links in incoming
emails work OK? The only workaround I've been able to discover is to
manually remove the prefix within IE7's address bar each time. Prior to
switching to WLM a couple of weeks ago, I used OE6 and never had this problem
with links in emails from the same source.

Thanks in advance for any suggestions.

The link worked for me. Australia/NZ Investment Daily
Try viewing the email as plain text.
Tools, Options, Read tab, check Read all messages as plain text.
Post the html code for the link.
--
Ronald Sommer

"pg5555" <pg5555@xxxxxx> wrote in message
news:FA46D602-95FC-4E14-A4A5-83D81C78592E@xxxxxx

Thanks for your feedback Ron. Do you mean that the short link worked for
you, or that the long link (ie. wlmailhtml...) which WLM forces upon me
worked for you? My problem is that I can't seem to avoid WLM sending me to
the long link, which never works for me.

One further clue is that I only have this problem when reading the original
email in WLM. If I save the message via File>SaveAs>*.eml, and then open the
message just by double-clicking it in Windows Explorer, it displays fine and
the links work perfectly. Mysterious.

The HTML from the message source is:
PDF version on GEO <https://www.citigroupgeo.com/pdf/ANMCALL.pdf>
which of course works fine. But that's not what WLM normally sends me to,
instead sending me to the "wlmailhtml..." version of the link.

Later in the message source I found the following. I'm not HTML-literate,
so I'm not sure why this next bit of code seems to exist in addition to the
above bit.

<TD
style="BORDER-RIGHT: #d4d0c8; PADDING-RIGHT: 5.4pt; BORDER-TOP: #d4d0c8;
PADDING-LEFT: 5.4pt; BACKGROUND: white; PADDING-BOTTOM: 2.85pt; BORDER-LEFT:
#d4d0c8; WIDTH: 422.55pt; PADDING-TOP: 5.65pt; BORDER-BOTTOM: #d4d0c8"
width=563 bgColor=white>
<P class=MsoNormal style="MARGIN: 0cm 0cm 0pt"><B
style="mso-bidi-font-weight: normal"><FONT face="Arial Narrow"
color=#5f5f5f><SPAN
style="FONT-WEIGHT: bold; FONT-SIZE: 10pt; COLOR: #5f5f5f;
FONT-FAMILY: 'Arial Narrow'; mso-bidi-font-family: Arial;
mso-bidi-font-weight: normal">Click
hyperlink to view on GEO<SPAN
style="mso-tab-count:
6">
</SPAN></SPAN></FONT></B><A
title=https://www.citigroupgeo.com/pdf/ANMCALL.pdf
href="https://www.citigroupgeo.com/pdf/ANMCALL.pdf"><B
title=https://www.citigroupgeo.com/pdf/ANMCALL.pdf
style="mso-bidi-font-weight: normal"><FONT
title=https://www.citigroupgeo.com/pdf/ANMCALL.pdf face="Arial Narrow"
size=2><SPAN title=https://www.citigroupgeo.com/pdf/ANMCALL.pdf
style="FONT-WEIGHT: bold; FONT-FAMILY: 'Arial Narrow';
mso-bidi-font-family: Arial; mso-bidi-font-weight: normal">PDF
version on GEO</SPAN></FONT></B></A><B
style="mso-bidi-font-weight: normal"><FONT face="Arial Narrow"
color=white
size=5><SPAN
style="FONT-WEIGHT: bold; FONT-SIZE: 16pt; COLOR: white; FONT-FAMILY:
'Arial Narrow'; mso-bidi-font-weight:
normal"><o></o></SPAN></FONT></B></P></TD></TR>

Regards
Peter G.


"Ron Sommer" wrote:

The short link worked.
The html code seems excessive. I don't know if the code is correct.
Did you try viewing the email in plain text?
--
Ronald Sommer

"pg5555" <pg5555@xxxxxx> wrote in message
news:C2EEA3B6-4873-4C76-B844-E275833C4A7A@xxxxxx

"pg5555" <pg5555@xxxxxx> wrote in message news:C2EEA3B6-4873-4C76-B844-E275833C4A7A@xxxxxx

Please be clearer about what you are seeing as anchor text.
Also, if you are seeing a URL as the anchor text have you tried
just selecting it (e.g. by dragging your mouse over it or by click,
Shift-,click) and copying that and then pasting the result into an
IE Address bar?


Let's break out the anchor tag from your source:


<A
I can see why the parser would get confused by this.
Where is the anchor text? I think the idea may be to ignore
all those title= attributes, somehow interpret the enclosed FONT tag
and display only "PDF version on GEO" as anchor text,
then using the href= URL as the actual location both to be opened
and shown in the Status bar when the mouse points to the anchor text
or a reader gives it keyboard focus (e.g. by tabbing to it).

BTW this is an example of why it was a deficiency for WLMail
to abandon OE's three panes for HTML composition.
E.g. in OE what you could do in this situation is press Ctrl-r
to start an E-mail reply to this (assuming E-mail implies HTML
sending format). That would appear in the Edit pane.
Then you would switch to the Source pane, find the offending
broken link and repair it. Then you would switch to the Preview pane
and actually use your repaired link. None of that is possible in WLMail.
Instead the best you might be able to do with Live products is perhaps
copy your E-mail to Live Writer and use the equivalent functionality
that it provides.


HTH

Robert Aldwinckle
---

Hi Robert

The visible anchor text is just "PDF version on GEO", so the URL appears
only in WLM's status line (when I hover the mouse over the anchor text).

As I said in an earlier reply, I think I'll give up on this issue - it only
seems to affect messages from one source and I assume that their email
generator software must have some issues, which you have already implied in
your comment about the parser potentially getting confused by the HTML
they've generated.

Thanks for your help.

Regards
Peter G.




"Robert Aldwinckle" wrote: