Jeff Chan wrote:
I don't think this can be considered a failing of SURBLs since they contain the right data to catch this. The issue is more of applications using SURBL data and what they decide to parse as URIs.
You're probably right that SpamAssassin (perhaps the application you're using?) may not treat as URIs something that does not begin with www or a URI scheme like http. But that's more of a question for applications than data. See:
Hi Jeff,
Yes, im using SA 2.xx with SpamCopURI. I will check that link you posted. And btw, in the last days i've seen this kind of spam:
This is the link in the HTML formatted spam-message:
http://anne.jiagebnhamMUNGED.info/?RANDOM_CHARSsobedient
And this is how it looks in the "source":
ht<detonate>tp://anne.jiag<artifice>ebnham.info/?RANDOM_CHARSsobedient
What is your suggestion to stop this type of spam?
Thank you
/ Martin