http://bugzilla.spamassassin.org/show_bug.cgi?id=3631
------- Additional Comments From [EMAIL PROTECTED] 2004-07-28 11:14 ------- Subject: Re: [review] update reserved IP list > (a) the reason 192.168, 10, and 172.16 et al are at the top of the old > one is because they are by far the most frequently-encountered > reserved ranges; it adds a little efficiency. (I don't know if that > actually helps though.) These should be put into a separate regular expression, actually. I'll append my recent posting to spamassassin-dev which seems to have been missed by everyone. > (b) I don't actually see any use of CYMRU as a source, going by the > comments. It's useful as a second check, also their changelog is very useful for making updates and changes. > (c) I would suggest not listing the "growth edges" of the existing > registrar spaces, such as 071 -- since once the ARIN space from > 063-070 is exhausted, IANA will start registering networks in that /8. IANA has already done non-sequential allocations and re-reservations. I don't really buy the "growth edges" argument. Either list them or don't. > This rev of the code could still be in use at several sites by that > stage, and it'd mean they'd miss DNSBL hits for relays in those > networks; this has happened before. So what I did last time was to > allow lookups for hosts in 071 and similar "growth edge" areas, > assuming they may be allocated in the code's lifetime. I don't think we should be listing <reserved but not allocated> ranges at all. The benefit is minor and the downside is generally larger than the benefit. ------- start of cut text -------------- From: Daniel Quinlan <[EMAIL PROTECTED]> Subject: IP_IN_RESERVED_RANGE To: [EMAIL PROTECTED] Date: Sat, 24 Jul 2004 23:03:39 -0700 Message-ID: <[EMAIL PROTECTED]> I think this constant is trying to do three things (and one of them it shouldn't be doing). 1. remove private use networks 2. remove reserved networks 3. remove multicast networks I think there's little reason for us to maintain a list of reserved networks. It just means when Asia or whereever gets a new class A that we don't do DNSBL queries. Private use and multicast should be separated into two regular expressions. Multicast is a sure-fire spam sign. Private use is okay and we should remove those as we do now. Daniel -- Daniel Quinlan http://www.pathname.com/~quinlan/ ------- end ---------------------------- ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
