On Thursday, January 20, 2005, 1:46:45 AM, Martin Martin wrote:
Hi,
The following mail got through even though it's listed in SURBL (check the link in the middle of the message):
[...]
yahoo.durkee.knfhbfndkeMUNGED.info/?TRACKING-ID_CHANGED<br><br>
[...]
Are they fooling SURBL by not include www or http? I've got several of these and wonder if i can do anything about this?
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:
http://bugzilla.spamassassin.org/show_bug.cgi?id=4087
Jeff C. -- "If it appears in hams, then don't list it."