From jeffc@surbl.org Thu Jul 15 08:11:29 2004
From: Jeff Chan <jeffc@surbl.org>
To: discuss@lists.surbl.org
Subject: Re: [SURBL-Discuss] {Spam?} RE: Perfect example of URL Poison
Date: Wed, 14 Jul 2004 23:11:04 -0700
Message-ID: <1944011495.20040714231104@supranet.net>
In-Reply-To: <MEEKIPHNBGKKJPCJOAMLAEFINFAA.bipsen@andebakken.dk>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============5453028624859579086=="

--===============5453028624859579086==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit

On Saturday, July 10, 2004, 2:19:10 AM, Brian Ipsen wrote:
>  Well - to make things easy, I guess it's just a matter of checking whether
> any text is present from the <A HREF=""> to the </A> ... So <A
> HREF="http://domain.org/"></A> won't trigger anything - but <A
> HREF="http://domain.org/">Some text</A> will....

> Just my 5 cents of input ;-)

I believe is what SpamAssassin and SpamCop correctly ignore
empty anchors.  If not they should.  Can't recall what Eric's
SpamCopURI does, but ignoring unclickable URIs is probably
a good way to defeat the kind of URI poisoning originally
mentioned, and likely should generally be used by message
parsers. 

Jeff C.

--===============5453028624859579086==--