<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Blocked for phishing</title>
	<atom:link href="http://blog.wordtothewise.com/2009/07/blocked-for-phishing/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.wordtothewise.com/2009/07/blocked-for-phishing/</link>
	<description>Email, Delivery, Spam and more</description>
	<lastBuildDate>Wed, 08 Feb 2012 05:06:27 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.3</generator>
	<item>
		<title>By: laura</title>
		<link>http://blog.wordtothewise.com/2009/07/blocked-for-phishing/comment-page-1/#comment-2290</link>
		<dc:creator>laura</dc:creator>
		<pubDate>Fri, 17 Jul 2009 23:59:40 +0000</pubDate>
		<guid isPermaLink="false">http://blog.wordtothewise.com/?p=484#comment-2290</guid>
		<description>I don&#039;t think it was SpamAssassin in either case, and it does seem to be relatively rare. But there are at least 2 different filters out there catching this mail.</description>
		<content:encoded><![CDATA[<p>I don&#8217;t think it was SpamAssassin in either case, and it does seem to be relatively rare. But there are at least 2 different filters out there catching this mail.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Justin Mason</title>
		<link>http://blog.wordtothewise.com/2009/07/blocked-for-phishing/comment-page-1/#comment-2295</link>
		<dc:creator>Justin Mason</dc:creator>
		<pubDate>Fri, 17 Jul 2009 20:38:24 +0000</pubDate>
		<guid isPermaLink="false">http://blog.wordtothewise.com/?p=484#comment-2295</guid>
		<description>We have avoided this heuristic in SpamAssassin for years because of this risk, btw.  too many false positives in existing nonspam mail...</description>
		<content:encoded><![CDATA[<p>We have avoided this heuristic in SpamAssassin for years because of this risk, btw.  too many false positives in existing nonspam mail&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul Maye</title>
		<link>http://blog.wordtothewise.com/2009/07/blocked-for-phishing/comment-page-1/#comment-2291</link>
		<dc:creator>Paul Maye</dc:creator>
		<pubDate>Fri, 17 Jul 2009 10:25:45 +0000</pubDate>
		<guid isPermaLink="false">http://blog.wordtothewise.com/?p=484#comment-2291</guid>
		<description>Interesting issue that so I just did a test with GroupMetrics which is a redirection tracking service http://www.group-metrics.com and there didn&#039;t see to be any problems with blocking when I used an ebay.com link.

I think because the actual URL is in the same tag as the redirection URL so there should be no false positive phishing filter being triggered.

Try it out on your own links and see how it goes, I&#039;m curious myself.  The service if free to sign up to anyway and you get 100 credits free for testing.</description>
		<content:encoded><![CDATA[<p>Interesting issue that so I just did a test with GroupMetrics which is a redirection tracking service <a href="http://www.group-metrics.com" rel="nofollow">http://www.group-metrics.com</a> and there didn&#8217;t see to be any problems with blocking when I used an ebay.com link.</p>
<p>I think because the actual URL is in the same tag as the redirection URL so there should be no false positive phishing filter being triggered.</p>
<p>Try it out on your own links and see how it goes, I&#8217;m curious myself.  The service if free to sign up to anyway and you get 100 credits free for testing.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: laura</title>
		<link>http://blog.wordtothewise.com/2009/07/blocked-for-phishing/comment-page-1/#comment-2293</link>
		<dc:creator>laura</dc:creator>
		<pubDate>Fri, 17 Jul 2009 01:10:18 +0000</pubDate>
		<guid isPermaLink="false">http://blog.wordtothewise.com/?p=484#comment-2293</guid>
		<description>I&#039;ve also seen this happen when the link isn&#039;t in the anchor text, but is present in the URL itself. A link that looks like http://redirector.example.com/amazon.com/ does sometimes trigger the phishing filters.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve also seen this happen when the link isn&#8217;t in the anchor text, but is present in the URL itself. A link that looks like <a href="http://redirector.example.com/amazon.com/" rel="nofollow">http://redirector.example.com/amazon.com/</a> does sometimes trigger the phishing filters.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lane</title>
		<link>http://blog.wordtothewise.com/2009/07/blocked-for-phishing/comment-page-1/#comment-2292</link>
		<dc:creator>Lane</dc:creator>
		<pubDate>Fri, 17 Jul 2009 00:43:27 +0000</pubDate>
		<guid isPermaLink="false">http://blog.wordtothewise.com/?p=484#comment-2292</guid>
		<description>I just received an email from a subscriber today on this precise issue.  I had an Amazon link in the newsletter; however, I did not use the domain name as the anchor text.

Any thoughts?</description>
		<content:encoded><![CDATA[<p>I just received an email from a subscriber today on this precise issue.  I had an Amazon link in the newsletter; however, I did not use the domain name as the anchor text.</p>
<p>Any thoughts?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

