This is a python extension module to enable python scripts to use libdspam functionality. A higher level wrapper handles a signature database and quarantine mbox in a user directory.
This release updates pydspam for dspam-3.10.2. Because the libdspam API changed drastically since dspam-2.6, this is considered a Beta release. I do have it running on several production systems.
1 maintainer
Metadata
1 maintainer
Release files for pydspam 1.3.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| pydspam-1.3.2.tar.gz | 124.4 kB | Without provenance | Details |
Release files / pydspam-1.3.2.tar.gz
| Download URL | pydspam-1.3.2.tar.gz |
|---|---|
| Size | 124.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2bf3599db4d98969898c948a139e571fe44ec056a703f7ae5265d2ab6c1e1439
|
|
BLAKE2b-256 checksum How to use checksums |
aab8ea97fbab8b83c81ed445d9e87207219d1ade2fc211132199be05b3426090
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for pydspam 1.3.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
