> >
> > Bob, you are talking about something completely different.. He is
> > talking about _RAZOR_ for displaying in report, you are
> talking about
> > the razor rule for rule writing.
>
> I was looking for this too, buy it doesn't seem to exist. I wanted a
> Razor header, to go along with the rest ...
>
There isnt one in 3.0-cvs either, just to save you the time of looking.
_YESNOCAPS_ "YES"/"NO" for is/isn't spam
_YESNO_ "Yes"/"No" for is/isn't spam
_SCORE_ message score
_REQD_ message threshold
_VERSION_ version (eg. 2.61 or 2.70-r6142-foo1)
_SUBVERSION_ sub-version/code revision date (eg.
2004-01-10)
_HOSTNAME_ hostname
_BAYES_ bayes score
_AWL_ AWL modifier
_DATE_ rfc-2822 date of scan
_STARS(*)_ one * (use any character) for each score point
(note: this
is limited to 50 'stars' to stay on the right
side of the RFCs)
_RELAYSTRUSTED_ relays used and deemed to be trusted
_RELAYSUNTRUSTED_ relays used that can not be trusted
_AUTOLEARN_ autolearn status ("ham", "no", "spam",
"disabled",
"failed", "unavailable")
_TESTS(,)_ tests hit separated by , (or other separator)
_TESTSSCORES(,)_ as above, except with scores appended (eg.
AWL=-3.0,...)
_DCCB_ DCC's "Brand"
_DCCR_ DCC's results
_PYZOR_ Pyzor results
_RBL_ full results for positive RBL queries in DNS
URI format
_LANGUAGES_ possible languages of mail
_PREVIEW_ content preview
_REPORT_ terse report of tests hit (for header reports)
_SUMMARY_ summary of tests hit for standard report (for
body reports)
_CONTACTADDRESS_ contents of the 'report_contact' setting
