Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email firstname.lastname@example.org
From: Stan Hoeppner (stanhardwarefreak.com)
Date: Tue Aug 31 2010 - 15:06:28 CDT
Charles Marcus put forth on 8/31/2010 11:44 AM:
> What the following looked like to me:
> REJECT Generic - Please relay via ISP (telesp.net.br)
> was that *everything* rejected by this regex would get the same reject
> Please relay via ISP (telesp.net.br)
> Apparently that isn't the case...?
The particular regular expression you're referring to (which you omitted
with your paste) only matches rDNS patterns containing telesp.net.br.
Many/most ISPs use one basic rDNS pattern for consumer dynamic accounts
(cable/dsl/dial) and another for consumer static accounts. Some use the
same rDNS pattern for both. Beyond that you're looking at business
class accounts. These regexes don't tend to target such business class
Thus, when you say "everything rejected by this regex" you're talking
about 1-3 distinct patterns per ISP. Some use more, some less (think
acquisitions). Some don't even assign rDNS to consumer IP space, which
is great as reject_unknown_reverse_client_hostname will stop all bot
spam from such consumer IPs.
Have you browsed over that file Charles? There are over 1600 fully
qualified rDNS pattens, one per line. Most are specific to a particular
ISP, and those all have unique custom reject messages with the ISP name
Does this help any?