[SURBL-Discuss] Submissions to SURBL list thru SARE website.

Steven Champeon schampeo at hesketh.com
Thu Jul 8 16:26:34 CEST 2004

on Thu, Jul 08, 2004 at 03:17:52PM -0400, Chris Santerre wrote:
> Good grief. Let me say this slowly....
> SURBL is for domains in LINKS, URLS, websites, images, things you click on,
> images hosted in the email.
> SURBL is NOT, will never be used, doesn't care, /dev/null's, any domain or
> IP the email came from. 

Well, I for one won't be sending any more domains along if I have to also
distinguish between the domains I happened to find in email bodies from
those I happened to find in message headers. Sorry. The overlap is far too
great, as for example in a recent message I got (summarized):

Received: from mx51.AfClawFrog1.us (mx51.afclawfrog1.us [])
Subject: [Target-removed] Free Break-In & Fire Protection System
Message-ID: <wfbzwsbunaxhmuetqnef at mx51.AfClawFrog1.us>

[text part with a snippet of fictional text]

[html part containing several links to 

<a href="http://medium.AfClawFrog1.us?id=[snipped long hash id]

<img src="http://images.AfClawFrog1.us/images/HomeSecurityProfessionals2_r1_c1.gif

I ran a rDNS scan on the netblock and found another 40+ domains all of
the same type. As they are found in both the body and the message headers,
I want to be able to block all future mail rather than archiving it; which
I can do from sendmail. SURBL just lets me filter after acceptance.

Sorry, I don't have time to deal with the distinction. Because for me, for
the most part, there quite simply is no distinction.

hesketh.com/inc. v: +1(919)834-2552 f: +1(919)834-2554 w: http://hesketh.com
Buy "Cascading Style Sheets: Separating Content from Presentation, 2/e" today!

More information about the Discuss mailing list