hsc message board > Purify appears to overlook URLs within the text

Wayne

Jan 12 2010, 09:59 PM

I am getting Spamed via one of Google's groups that Google insists have been forged when reported to them by Purify. The problem is that Purify is neither reporting the URL contained within the body of the message to the IP nor to you as not being resolved.

Two recent examples are:

hahhahaha))my husband was angry)) http://www.jamezz.us/anecdotes

Which your DNS Tools / WhoIS resolved to:

209.190.24.9
postmaster@jamezz.us
abuse@ee.net
hostmaster@ee.net
president@ee.net

The other is:

http://lu.mu/tutorial

Which your DNS Tools / WhoIS resolved to:

203.219.138.134
postmaster@lu.mu
hostmaster@apnic.net
hostmaster@tpg.com.au
abuse@tpg.com.au
trouble@tpg.com.au

Is there a way to get Purify to pick these up and report them?

Jeff Hendrickson

Jan 13 2010, 11:54 PM

Purify uses Regular Expressions to find / parse URIs that are embedded in emails.

During development, I had to have a "stop point" where I was satisfied with the number of URIs that it was catching. It's not perfect, but it's pretty good, and it catches most URIs.

If you could provide me with a sample of the offending email in question (like before, .zipped raw message source), the URI Regular Expression engine would probably be updated to catch your example in the next Purify update.

Wayne

Jan 14 2010, 02:30 AM

QUOTE (Jeff Hendrickson @ Jan 13 2010, 11:54 PM)

Purify uses Regular Expressions to find / parse URIs that are embedded in emails.

During development, I had to have a "stop point" where I was satisfied with the number of URIs that it was catching. It's not perfect, but it's pretty good, and it catches most URIs.

If you could provide me with a sample of the offending email in question (like before, .zipped raw message source), the URI Regular Expression engine would probably be updated to catch your example in the next Purify update.

They should be in your inbox.
Thanks, Wayne

Wayne

Jan 15 2010, 05:17 PM

QUOTE (Jeff Hendrickson @ Jan 13 2010, 11:54 PM)

Purify uses Regular Expressions to find / parse URIs that are embedded in emails.

During development, I had to have a "stop point" where I was satisfied with the number of URIs that it was catching. It's not perfect, but it's pretty good, and it catches most URIs.

If you could provide me with a sample of the offending email in question (like before, .zipped raw message source), the URI Regular Expression engine would probably be updated to catch your example in the next Purify update.

Do you need any more samples of this?

Jeff Hendrickson

Jan 19 2010, 12:15 PM

QUOTE (Wayne @ Jan 15 2010, 12:17 PM)

Do you need any more samples of this?

No sir, thanks.