Bug 99 - filtering private networks
Summary: filtering private networks
Status: RESOLVED INVALID
Alias: None
Product: Spamassassin
Classification: Unclassified
Component: Rules (show other bugs)
Version: unspecified
Hardware: All All
: P2 trivial
Target Milestone: ---
Assignee: Craig Hughes
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-03-13 14:21 UTC by james leigh
Modified: 2002-03-16 18:46 UTC (History)
0 users


Attachment Type Modified Status Actions Submitter/CLA Status
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description james leigh 2002-03-13 14:21:48 UTC 
My email was thought to be spam because it can from 192.168.32.18, which is a
private ip.  I suggest you add a rule to not include the server as spam if it
have a private ip address, since there many computers with the ip 192.168.*

> SPAM: -------------------- Start SpamAssassin results ----------------------
> SPAM: This mail is probably spam.  The original message has been altered
> SPAM: so you can recognise or block similar unwanted mail in future.
> SPAM: See http://spamassassin.org/tag/ for more details.
> SPAM: 
> SPAM: Content analysis details:   (5 hits, 5 required)
> SPAM: Hit! (2 points)    Received via a relay in relays.osirusoft.com
> SPAM:                    [RBL check: found
18.32.168.192.relays.osirusoft.com., type: 127.0.0.4]
> SPAM: Hit! (3 points)    DNSBL: sender is Confirmed Spam Source
> SPAM: 
> SPAM: -------------------- End of SpamAssassin results ---------------------
Comment 1 Craig Hughes 2002-03-17 03:46:29 UTC 
That's not a spamassassin issue -- it's the RBL you're using.  If you don't want
to penalize that IP address, don't use RBLs which block those IPs.  To turn off
a particular RBL, set its SA score to 0