I just read a newsgroup post in which there is a website cited:
For many years, my bash page (tiswww.case.edu/~chet/bash/bashtop.html) has
sported a bash logo that someone whose name I have lost donated long ago.
Note that the URL in parentheses is wrongly detected as
although the "tis" is really part of it. The message headers include "Content-Type: text/plain; charset=utf-8" so this is not a "bug" of the author of that post having wrongly specified an <a href...> html tag.
This is probably because the URL detector is trying to be smart to help you, but in fact that string is not even a valid URL since it lacks the protocol part.
(In reply to comment #1)
> This is probably because the URL detector is trying to be smart to help you,
> but in fact that string is not even a valid URL since it lacks the protocol
Sure, I agree with your analysis. But even though the URL is invalid, it's interpretation is so, too. I guess the detector uses a regexp containing something like '\bwww\.' which is too restrictive. Protocol-less URLs are far too common and usually refer to http. So I think the detector should either except the URL from the OP or not accept any protocol-less URLs at all.