> Not sure where the "URI(1):" came from. If it is supposed to change, 
> I dislike that immensely.

I didn't put that (1) there !!

> Indented Lines
> ========================
> X-Assp-Detected-URI: hotmail.com:5, bar.net:3, foo.org:7 ...
>   msn.com:5, google.net:3, people.org:7 ...
> ========================

The above would be fine, instead of using multiple lines
just use indentation as specified by the RFCs so that there
will be only one line with the URIs, then, by the way ASSP
has a "max uri limit" which will help avoiding the generation
of "monster header lines" :)
 
> Hmmm. ASSP already adds "bad" URI hits to the header along with the
> points it scored (AddURIBLHeader).

Ok, if so just use (e.g.)

X-ASSP-Bad-URI:

X-ASSP-URI:

where the first line will list the bad URIs and the second all the
others (i.e. not listed... which doesn't necessarily mean they're
good btw... just that they aren't recognized as bad) still ... I think
that such headers should be made optional (i.e. set a checkbox
in the ASSP GUI to add them) also, notice that URIs may also
be detected/flagged by some ClamAV signatures so, dealing
with the above headers also means dealing with bad URIs
flagged by the AV scan; also, URIBL checks may also be
performed on the HELO domain, the sender (envelope or
MIME) domain and on the sending host PTR domain (given
it doesn't match the HELO)
 
> By adding the code I added, my goal was too get a clean list of 
> the URI in the message, so that they could be added to a URIBL. 
> So, I would certainly want the "good" and "bad" URI listed. 

Hm... you may get them by asking a "feed" from some URIBL
or either decoding some ClamAV signatures w/o any need to
get them "through ASSP"; using rsync to fetch some  URIBL db
or clamav signatures will give you a full list you may use w/o
having to add headers to ASSP and extracting data from there




------------------------------------------------------------------------------
Learn how Oracle Real Application Clusters (RAC) One Node allows customers
to consolidate database storage, standardize their database environment, and, 
should the need arise, upgrade to a full multi-node Oracle RAC database 
without downtime or disruption
http://p.sf.net/sfu/oracle-sfdevnl
_______________________________________________
Assp-test mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/assp-test

Reply via email to