RAZOR-REPORT(1p)

RAZOR-REPORT(1p) β€” yes bestie, that's the manpage id, and this is the user-contributed Perl documentation for it. Buckle up, we're reporting spam πŸ’–


✨ NAME ✨

razor-report β€” the Razor Reporting Agent πŸŽ€


πŸ¦‹ SYNOPSIS πŸ¦‹

razor-report [options]  file_with_mail_in_rfc822_format

$ cat mail | razor-report
$ razor-report ./mail
$ razor-report -d ./mail

πŸ’œ DESCRIPTION πŸ’œ

okay so razor-report is the Razor Reporting Agent, and its whole job is reporting spam messages to a Razor Nomination Server. Best practice is calling it from a MUA, but ngl there are no restrictions on running it straight from the command line. It's a filter, which means you pipe spam messages through it. And by default? It backgrounds itself and detaches from the control terminal at start-up. main character energy, honestly 🫢

If you pass razor-report more than one mail, it will report each one against the database. Please use this with caution β€” we do NOT want the database filled up with mails incorrectly identified as spam, that's giving chaos 😭 razor-report supports mbox-formatted files with 1 or more mails in them, and also files containing a single RFC 822 (non-mbox) mail. More than one file may be present on the command line, and each can be either non-mbox or mbox, in any order. slay.

However β€” and this is the catch β€” more than one non-mbox mail cannot be read from stdin. βœ‹ Both razor-report and razor-revoke(1) require user authentication to work, see razor-admin(1). This is what lets the Razor Nomination Server keep track of how many messages a user reports and revokes. The more messages a user correctly reports and/or correctly revokes, the more trust the user earns. Likewise, when messages are incorrectly reported or revoked, the trust goes down for that user. Highly trusted users will have the most affect on the Razor Catalogue πŸ‘‘


🌸 USAGE 🌸

razor-report takes following arguments:

  • -h β€” Print a usage message and exit. short and sweet, we love.
  • -v β€” Print the version number and exit. πŸ’…
  • -d, --verbose β€” Print debugging information to stdout.
  • -debuglevel=n, -dl=n β€” Set debug level to 'n'. Default is 3 without -d option, 9 with.
  • -whitelist=file β€” Specify file to use for whitelisting. Overrides 'whitelist' option in razor-agent.conf.
  • -s β€” Simulate a check. Do everything except talk to the server. πŸ™ˆ pretend mode fr fr.
  • -conf=filename β€” Specifies an alternate configuration file. If not specified, it is computed, see razor-agents(1) manpage for details. See razor-agent.conf(5) manpage for various configuration options. The default is <razorhome>/razor-agent.conf.
  • -home=dir β€” Specify razorhome directory. This is where the configuration file, logfiles, identities, and server files live. If not specified, it is computed, see razor-agents(1) manpage for details.
  • -logfile=file β€” Specify file to log to instead of whats in configuration file. The default is <razorhome>/razor-agent.log.
  • -ident=filename β€” Specify an identify file to use for authenticating with Razor Servers. If not specified, <razorhome>/identity-<user> is used.
  • -rs=razor.server.com β€” Use this Razor Nomination Server instead of reading servers.nomination.lst.
  • -H β€” Compute and print the signature of the mail contents and exit. If -e=integer is not specified, all supported engines will be used.
  • -S=string β€” Accept a list of pre-computed (with -H) signatures on the command line, instead of computing one from mail content. Signatures can be submitted in hex or base64, but base64 is preferred. Requires -e=integer. Usage:
razor-report -e 1 -S a8a3d545adb73f9733675571ffeaf10cba87745b
  • -e=integer β€” Specify engine used to create signatures. Must be 1, 2, 3, or 4 in this version. Engine 1, or -e=1, is used for Razor 1.x signatures. Used only with -S=string or -H.
  • -ep4=string β€” String used by engine 4 when computing signatures. Published by the Razor Nomination Servers and updated very frequently. Used only when -e=4.
  • -i=filename β€” Use identity from filename instead of reading <razorhome>/identity. Razor Servers compute trust for each unique identity. Razor Agents figure out the identity by a 2 step process. First, check if identity is specified via cmd-line (-i=file). If not there, then look in <razorhome> for identity file. If <razorhome> has no identity file, authentication will fail β€” you cannot report or revoke. See razor-agents.conf(5) for more on <razorhome>. ---fixme----
  • -a β€” Authenticate only. If authenticated, exit 0; if not, exit 1. βœ… or πŸ’€, no in between.
  • -f β€” Stay in foreground, do not detach and run in background.

🌈 INTEGRATION WITH MUTT 🌈

Add the following line to mutt.conf

macro index S "|/usr/bin/razor-report"

Then press S on the spam message in mutt to report it with razor-report. Since razor-report forks, the control will return immediately. iconic tbh ✨


🫢 AUTHORS 🫢

Vipul Ved Prakash <mail@vipul.net>, and Chad Norwood <chad@samo.org>


⭐ SEE ALSO ⭐

razor-agents(1), razor-agent.conf(5), razor-check(1), razor-admin(1), razor-revoke(1), razor-whitelist(5)


πŸ‘‘ LICENSE πŸ‘‘

This is free software, distributed under the Artistic License 2.0.


and that's the whole page bestie!! πŸ’– this one's from perl v5.40.1, dated 2025-05-24 β€” go forth and report responsibly, no cap πŸŽ€πŸ¦‹

πŸ“¦ where this page comes from