razor 1:2.85-5 source package in Ubuntu

Changelog

razor (1:2.85-5) unstable; urgency=medium

  * QA upload.
  * Set Maintainer to Debian QA Group. (see #866833)
  * debian/rules: Add build-{arch,indep}. (Closes: #999005)

 -- Adrian Bunk <email address hidden>  Mon, 27 Dec 2021 23:34:34 +0200

Upload details

Uploaded by:
Debian QA Group
Uploaded to:
Sid
Original maintainer:
Debian QA Group
Architectures:
any
Section:
mail
Urgency:
Medium Urgency

See full publishing history Publishing

Series Pocket Published Component Section

Downloads

File Size SHA-256 Checksum
razor_2.85-5.dsc 1.8 KiB 97fc9ac1f46dc0441dc4a7eff248b917fb4586f29b197d810d58ac4e50cb3e89
razor_2.85.orig.tar.gz 90.3 KiB 094b54713f1e6d2a39aaf4e02633ade7024fc36e9a5a069872cc95c7bf950f58
razor_2.85-5.diff.gz 15.1 KiB 18e9a2383cce7d9d82af40819a78b1f1b6e12f228bd302b9c19a01c95171e931

No changes file available.

Binary packages built by this source

razor: spam-catcher using a collaborative filtering network

 Vipul's Razor is a distributed, collaborative, spam detection and
 filtering network. Razor establishes a distributed and constantly updating
 catalogue of spam in propagation. This catalogue is used by clients to
 filter out known spam. On receiving a spam, a Razor Reporting Agent (run
 by an end-user or a troll box) calculates and submits a 20-character unique
 identification of the spam (a SHA Digest) to its closest Razor
 Catalogue Server. The Catalogue Server echos this signature to other
 trusted servers after storing it in its database. Prior to manual
 processing or transport-level reception, Razor Filtering Agents (end-users
 and MTAs) check their incoming mail against a Catalogue Server and filter
 out or deny transport in case of a signature match. Catalogued spam, once
 identified and reported by a Reporting Agent, can be blocked out by the
 rest of the Filtering Agents on the network.

razor-dbgsym: debug symbols for razor