Bug 5826 - add ip_private boolean to received header metadata
Summary: add ip_private boolean to received header metadata
Status: NEW
Alias: None
Product: Spamassassin
Classification: Unclassified
Component: Libraries (show other bugs)
Version: SVN Trunk (Latest Devel Version)
Hardware: Other other
: P5 enhancement
Target Milestone: Future
Assignee: SpamAssassin Developer Mailing List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-02-13 16:43 UTC by Daryl C. W. O'Shea
Modified: 2010-04-21 20:40 UTC (History)
0 users



Attachment Type Modified Status Actions Submitter/CLA Status

Note You need to log in before you can comment on or make changes to this bug.
Description Daryl C. W. O'Shea 2008-02-13 16:43:10 UTC
It'd be handy to include a field & value in the generic
"X-Spam-Relays-Untrusted" (etc) headers that indicate whether an IP is private
or not so that header rules can be written without having to re-implement the
IP_PRIVATE regex.

It could be called ip_private or whatever.

ex:

[ ip=10.1.1.1 rdns= helo= by=blah ident= envfrom= intl=0 id= auth= msa=0
ip_private=1 ]
Comment 1 Justin Mason 2010-01-27 02:20:21 UTC
moving most remaining 3.3.0 bugs to 3.3.1 milestone
Comment 2 Justin Mason 2010-01-27 03:16:12 UTC
reassigning, too
Comment 3 Justin Mason 2010-03-23 16:33:18 UTC
moving all open 3.3.1 bugs to 3.3.2
Comment 4 Karsten Bräckelmann 2010-03-23 17:42:32 UTC
Moving back off of Security, which got changed by accident during the mass Target Milestone move.